Blue Screen: "STOP: 0X0000008E"

colton · Jul 7, 2006, 07:48 AM

I recently purchased the floor model (big mistake, there) of an HP m7360n Media Center PC, and have been getting Blue Screens of Death ever since.

My specs are as follows:

Code:

OS: Microsoft Windows XP Media Center Edition
CPU Type: DualCore Intel Pentium D, 2800 MHz
BIOS Type: Award (04/17/06)
Award BIOS Type: Phoenix - AwardBIOS v6.00PG
2 Gigs RAM
Video Adapter: nVIDIA Geforce 6200SE TurboCache

I originally got a blue screen with something like "nv4_disp.dll," but that disappeared after I updated my video card drivers.

I now have the most recent Forceware drivers, but I still get this stop code every few minutes:

Code:

STOP: 0X0000008E (0XC0000005, 0X891A2B6C, 0X9C386A70, 0X00000000)

I at one point tried installing Omega Drivers, but those seemed to make matters worse.

Also, I've attempted to run Driver Cleaner Pro in between installing video card drivers, but that causes a stop error even while running in safe mode.

Can I be sure that the problem is with video card drivers?
Would updating BIOS help? It seems to be fairly up to date (04/17/06).

Should I just suck it up and reformat? I wasn't given any CD's with this computer, so I'm hoping that this 9 gig partition the PC has labeled "HP_RECOVERY" will have everything I need. If not, I plan to storm CompUSA and ask them why they even sell floor model PC's.

Dyre Straits · Jul 7, 2006, 06:17 PM

Greetings and welcome to Driverheaven.

Before proceeding, do this:

Go into the Event Viewer and check for errors/warnings.

Right click on My Computer icon, then select Manage.

You'll see Event Viewer. Expand that and then open Applications and then System. Look for incidents around the time of the crash. Then read whatever information is provided.

Post back with any information.

Which version of Omega's drivers have you tried? Keep in mind that you do have a nVidia card....not ATI. So, you cannot use ATI drivers for your system.

PangingJr · Jul 7, 2006, 08:22 PM

if you get the BSOD since the beginning... and you want to play it safe, send or take the computer back to the store. you can first call to check with retailer for an exchange or something.

colton · Jul 7, 2006, 09:21 PM

I tried to use Nvidia Omega Drivers 1.6693 (Forceware 66.93).

There seem to be alot of events in the event viewer, so I will restart in normal mode, wait for a stop error, and post with whatever even comes closest to that.

colton · Jul 8, 2006, 05:13 AM

There are eight instances of this in a row:

Code:

Error code 1000008e, parameter1 c0000005, parameter2 89423b6c, parameter3 9b448a70, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

0000: 53 79 73 74 65 6d 20 45   System E
0008: 72 72 6f 72 20 20 45 72   rror  Er
0010: 72 6f 72 20 63 6f 64 65   ror code
0018: 20 31 30 30 30 30 30 38	1000008
0020: 65 20 20 50 61 72 61 6d   e  Param
0028: 65 74 65 72 73 20 63 30   eters c0
0030: 30 30 30 30 30 35 2c 20   000005, 
0038: 38 39 34 32 33 62 36 63   89423b6c
0040: 2c 20 39 62 34 34 38 61   , 9b448a
0048: 37 30 2c 20 30 30 30 30   70, 0000
0050: 30 30 30 30			   0000

The page on microsoft.com said that it might be a virus, but I checked, and there were no registry keys for that particular virus.

colton · Jul 8, 2006, 05:18 AM

Ah. As this is a dynamic page, and I cannot simply link you to it, I'll past what microsoft.com told me about the stop error.

Code:

Product: Windows Operating System  Event ID: 1003  Source: System Error  Version: 5.2  Symbolic Name: ER_KRNLCRASH_LOG  Message: Error code %1, parameter1 %2, parameter2 %3, parameter3 %4,  parameter4 %5.


Explanation   A blue screen (Stop error) was reported. The message contains details about  the error. A matching event with Event ID 1001 might also appear in the event  log. This matching event displays information about the specific error that  occurred.

       User Action   No user action is required.



• The HaxDoor virus may cause a "STOP 0x00000050" or "STOP  0x0000008e" error message  
Explains that the HaxDoor virus may generate a Stop error  message or restart your computer in Windows Server 2003, Windows 2000, or  Windows XP. You can manually remove the variant of the HaxDoor virus to resolve  this issue.

colton · Jul 8, 2006, 09:10 AM

I'd also like to revise my original post.

By "I recently bought," I mean, "my father recently bought and left me with the burden of maintainging."

Dyre Straits · Jul 8, 2006, 09:41 AM

How long after the purchase did this start happening? Are we talking weeks or months?

Yousaif · Jul 8, 2006, 01:56 PM

If it was a display model from the store was the full system restore ever run on it? If I ever bought a display model that would be the first thing I do. Amateur hacker wannabes are constantly trying to "h4xx0r" and mess up those machines.

colton · Jul 8, 2006, 09:18 PM

It started within days, really. Probably about a week.

When we made the purchase, they kept the computer for a day to run "optimizations" on it or something. We bought it at CompUSA.

Cube623 · Jul 9, 2006, 12:01 AM

Quote:

Originally Posted by colton

Should I just suck it up and reformat? I wasn't given any CD's with this computer, so I'm hoping that this 9 gig partition the PC has labeled "HP_RECOVERY" will have everything I need. If not, I plan to storm CompUSA and ask them why they even sell floor model PC's.

i'm back to using my old Hp Pavilion 434 while my new pc is getting fixed and i have a partition called HP_RECOVERY and yes that does reinstall windows etc.

To start this when you start your pc and you get the HP splash screen it should say at the bottom something like "F10 - System Recovery" press F10 and it will bring up a hp loading screen (simular to the windows loading screen but it has an hp logo instead of a windows xp logo). It then goes into a setup page which gives you the option to do a non-destructive install which basically reistalls xp over the top of the one already installed (NOT RECOMMENDED as i tried this and it only made this a lot worse) and a destructive install which formats your C: partition and installs windows.

edit: just thought that the hp system recovery might be different on your pc (like how to get into it, what options it gives you etc) as my hp pc is over 2 1\2 years old so hp might have changed the system recovery feature by now

H3X4D3C1M4L · Jul 10, 2006, 01:52 AM

I would reformat the thing. I know what I try and do to some floor model PC's so thats why I reccomend it. Plus some employees use them as their own personal bitch machines... I've witnessed this at Best Buy

Jul 7, 2006, 07:48 AM	#1
colton DriverHeaven Newbie Join Date: Jul 2006 Posts: 6 Rep Power: 0	Blue Screen: "STOP: 0X0000008E" I recently purchased the floor model (big mistake, there) of an HP m7360n Media Center PC, and have been getting Blue Screens of Death ever since. My specs are as follows: Code: OS: Microsoft Windows XP Media Center Edition CPU Type: DualCore Intel Pentium D, 2800 MHz BIOS Type: Award (04/17/06) Award BIOS Type: Phoenix - AwardBIOS v6.00PG 2 Gigs RAM Video Adapter: nVIDIA Geforce 6200SE TurboCache I originally got a blue screen with something like "nv4_disp.dll," but that disappeared after I updated my video card drivers. I now have the most recent Forceware drivers, but I still get this stop code every few minutes: Code: STOP: 0X0000008E (0XC0000005, 0X891A2B6C, 0X9C386A70, 0X00000000) I at one point tried installing Omega Drivers, but those seemed to make matters worse. Also, I've attempted to run Driver Cleaner Pro in between installing video card drivers, but that causes a stop error even while running in safe mode. Can I be sure that the problem is with video card drivers? Would updating BIOS help? It seems to be fairly up to date (04/17/06). Should I just suck it up and reformat? I wasn't given any CD's with this computer, so I'm hoping that this 9 gig partition the PC has labeled "HP_RECOVERY" will have everything I need. If not, I plan to storm CompUSA and ask them why they even sell floor model PC's.

Jul 7, 2006, 08:22 PM	#3
PangingJr Member Join Date: Mar 2003 Posts: 5,989 Rep Power: 71	if you get the BSOD since the beginning... and you want to play it safe, send or take the computer back to the store. you can first call to check with retailer for an exchange or something.

Jul 7, 2006, 09:21 PM	Thread Starter #4
colton DriverHeaven Newbie Join Date: Jul 2006 Posts: 6 Rep Power: 0	I tried to use Nvidia Omega Drivers 1.6693 (Forceware 66.93). There seem to be alot of events in the event viewer, so I will restart in normal mode, wait for a stop error, and post with whatever even comes closest to that.

Jul 8, 2006, 09:10 AM	Thread Starter #7
colton DriverHeaven Newbie Join Date: Jul 2006 Posts: 6 Rep Power: 0	I'd also like to revise my original post. By "I recently bought," I mean, "my father recently bought and left me with the burden of maintainging."

Jul 8, 2006, 09:18 PM	Thread Starter #10
colton DriverHeaven Newbie Join Date: Jul 2006 Posts: 6 Rep Power: 0	It started within days, really. Probably about a week. When we made the purchase, they kept the computer for a day to run "optimizations" on it or something. We bought it at CompUSA.

Jul 10, 2006, 01:52 AM	#12
H3X4D3C1M4L DriverHeaven Extreme Member Join Date: May 2005 Posts: 6,794 Rep Power: 0	I would reformat the thing. I know what I try and do to some floor model PC's so thats why I reccomend it. Plus some employees use them as their own personal bitch machines... I've witnessed this at Best Buy