Stop Error: 0x0000007F (0x00000008,0x80042000,0x00000000,0x00000000)

[ryanoc]

I am getting a Stop Error: 0x0000007F (0x00000008,0x80042000,0x00000000,0x00000000) every time I turn on the computer. It dumps the memory and then reboots infinitely. I am able to boot in Safe Mode. After booting in Safe Mode, I am also able to boot using a selective startup (using msconfig) to load everything except "Plug and Play" under the Services tab. I have taken out all of my PCI cards and USB devices. I even changed my mouse and keyboard, but I still get the error. How can I find the device or software that is causing this error?

[Chucky]

The error that you are getting indicates that there is some issue on the software level. An exception occurs during a call to the handler for a prior exception. Basically there are two exceptions which are simply handled serially. And if there are many then they are not handled serially which are the cause of this kind of fault. Now there can be two reasons here. The first is a kernel stack overflow and if that is not the issue then the second problem can be hardware failure.

[ryanoc]

Thanks Gerry. There are no yellow question marks in Device Manager. I ran "sigverif.exe" and found 8 unsigned drivers. However, the most recent updated unsigned driver was over a year ago. I haven't added any new hardware to my computer recently. As stated before, I can boot up the computer using selective startup with everything checked except "Plug and Play". I don't know if this helps diagnose the problem. I am wondering if the problem is with a plug and play device, the motherboard, RAM, or software.
I have stripped out all USB and PCI devices from my computer, but I still get the error when doing a normal boot. I removed the RAM and blew compressed air into the RAM slots and everywhere else in the computer. There was a little dust, but not much. I am running Windows XP with Service Pack 3. Can I reinstall the OS without losing all the updates since my XP disk was produced (several years ago)? Any other suggestions would be greatly appreciated.

Thanks,

Ryan

[ryanoc]

I'm not sure where I learned how to count. I ran sigverif.exe again and found these unsigned drivers (sorted by "Modified"):

unires.dll - 3/22/2007
mxdwdrv.dll
mxdwdul.dll
j3gedrv43.dll
mxdwdul.gpd
mxdwdui.ini
adpdf8.ppd
adgelp.ini
ssgr3en.dat
pscript.hlp
sd4.ini
sd4.dll
zspool32.exe
imf16.drv
wfxunt40.dll
wfxdnthq.dll
msvcrt40.dll
zprint32.exe
winfax.fad - 9/27/1996

[Jasonholt]

Before making any major changes in your OS, I will advice you to check Device Manager. Just check that what you get in the same. If there are some pending or uninstalled drivers then it is recommended that you must check for drivers update. That will be more helpful. The device manager would be a great option to fix the driver bugs but that might not work well her. Try to boot your system in safe mode and then go with the new installation stuff. Check what you can find here.

[ryanoc]

I looked at the device manager after enabling "viewing of unplugged or hidden items". There still aren't any yellow question marks.

In addition to being able to start windows in safe-mode, I am also able to start windows using the "selective startup" option in the system configuration tool. Under "selective startup", I check all 4 options
- Process System.INI File
- Process WIN.INI File
- Load System Services
- Load Startup Items

I leave everything under each of the tabs checked except under the Services tab, I uncheck the service called "Plug and Play" wich lists "microsoft" as the manufacturer. I leave "Universal Plug and Play" and everything else checked.

When starting up in safe-mode, and then running MSCONFIG, it lists "Plug and Play" as running. So, I don't know why unchecking it, avoids the error when not it safe-mode.

When I restart without "Plug and Play", the system starts with normal screen resolution. The system doesn't crash, but this obviously isn't a solution to my problem. For instance, when I go into Device Manager, it doesn't show any devices. I had to reboot in safe-mode in order to view device manager. Anyway, I just thought this might help identify what is causing the problem.

I also ran CHCKDSK, but no errors were found.

Thanks for all the help so far.
Any other suggestions would be greatly appreciated.

Ryan

[prash_mate]

I got the similar issue due to a printer driver. It was a plug and play device. But somehow the drivers cause the bug and it crashed. It did not simply work great. I tried to disable ample of thing but nothing worked out. The last option that I had tested to fix the problem is removed all the drivers and the system started working properly. It was stable there was no issue at all. So I too think your case the problem can be with the internal drivers. Just check them back and see what you get.

[ryanoc]

I had 2 RAM DIMMs in my computer. I took them out and tried booting with just 1 DIMM and then just the other DIMM. I got the same error both times. So, I think I can rule out the RAM.

Right now, I'm recevering an old Ghost image from 3 months ago. This might take a while, so I'll post the results tomorrow. If this doesn't work, I am going to assume there's something wrong with the motherboard.

[ryanoc]

The Ghost image restoral worked! I'm going to add back all my peripherals and hope that the problem doesn't happen again.