BSOD Reboot Error

[seven7seven]

I've been using rb: 7 RC Build 7100 since almost a year now. And suddenly, it's started giving me a BSOD, rebooting after that. The stop error :

*** STOP: 0x0000007E (0xC0000005,0x8523AE7A,0x88D1773C,0x88d17320)

System Restore, Startup Repair or using a disc image to restore the system does not work.
I tried booting in safe mode w/o command prompt or networking and it hung on CLASSPNP.SYS
It's an x86 version. Hope I can get help soon.
:mad2:

I know there are a lot of threads about this, but none of them could solve the problem for me. So ...

 

[zigzag3143]

I've been using rb: 7 RC Build 7100 since almost a year now. And suddenly, it's started giving me a BSOD, rebooting after that. The stop error :

*** STOP: 0x0000007E (0xC0000005,0x8523AE7A,0x88D1773C,0x88d17320)

System Restore, Startup Repair or using a disc image to restore the system does not work.
I tried booting in safe mode w/o command prompt or networking and it hung on CLASSPNP.SYS
It's an x86 version. Hope I can get help soon.
:mad2:

I know there are a lot of threads about this, but none of them could solve the problem for me. So ...

Hi and welcome


We realy need the dmp file that was created during the crash use these to find and upload http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

thanks

Kenn J+

 

[seven7seven]

.dmp file

Is this it? And, I don't know WHY but the 'date modified' on the file is 28/12/09.

 

[usasma]

More info on the STOP 0x7E error: BSOD Index

It's dated from 12/28/09 because that's the date that the crash occurred.
Not much info will be available due to your using the RC (the symbols on the Microsoft server are for the RTM version).

Unfortunately, the dump file blames the Windows kernel. This probably isn't correct, as kernel corruption would most likely give you many more problems other than an occasional BSOD.

Please uninstall the Adobe File System driver from your system - it's outdated and is known to cause problems. Just uninstall your Adobe products from Control Panel...Programs...Uninstall a program.
Then, if you wish, download fresh copies of the latest version from the Adobe website.

In the absence of upgrading to the RTM version (my recommendation), I'd suggest running Driver Verifier according to these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Here's a summary of the BSOD:

*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7100.0.x86fre.winmain_win7rc.090421-1700
[U][I][B]Debug session time: Mon Dec 28 11:43:24.867 2009 (GMT-5)[/B][/I][/U]
System Uptime: 0 days 4:44:20.865
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 1000007E, {c0000005, 85241dee, 88d1773c, 88d17320}
Probably caused by : ntkrnlpa.exe ( nt+5eb3f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

 

[seven7seven]

It's dated from 12/28/09 because that's the date that the crash occurred.

Please uninstall the Adobe File System driver from your system - it's outdated and is known to cause problems. Just uninstall your Adobe products from Control Panel...Programs...Uninstall a program.
Then, if you wish, download fresh copies of the latest version from the Adobe website.

I started getting the BSoD just about 4 days ago so, I don't get why it should say the crash occured on 12/28.
And, I can't really uninstall anything cause Windows refuses to start.
BSoD -> Reboot -> BSod -> Reboot ...
I can't use Safe Mode either cause that gives me the same BSoD too after it says it's loading CLASSPNP.SYS
Startup Repair doesn't work, and neither does System Restore.
And I don't think I can do the Driver Verifier procedure if Windows doesn't start up, can I?

 

[usasma]

Try these bootable diagnostics:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

If possible, slave the hard drive to another system to recover your data.
Then wipe the hard drive with KillDisk or DBAN and reinstall Windows to see if you can get the system to function properly.

 

[seven7seven]

Should I get the RTM, then, or is it okay to continue with the RC?

Edit:
No error in Memory Doagnostics. Going for the HD Diagonstics now.
Thanks

 

[usasma]

I would advise getting a copy of the RTM. It'll make things easier on you - and will avoid the possibility of your system having a part of the OS that has known incompatibilities.

FYI - I just got an email from Microsoft warning of the expiration of the RC: Description of Windows 7 Beta and Windows 7 Release Candidate (RC) expiration dates and functionality

Windows 7 RC

Windows 7 RC expiration

Effective June 1, 2010, Windows 7 RC will expire.

To continue using your computer, you should prepare to install the retail release version of Windows 7 or install an earlier version of Windows before the June 1, 2010 expiration date. You will be unable to upgrade from Windows 7 RC to the retail release version of Windows 7. However, you can back up or transfer your data to your next or previous operating system. Windows 7 RC expiration functionality

Effective February 14, 2010, the expiration notification process begins:

• Windows 7 RC users receive an expiration notification in the task bar one time per day.
• Windows 7 RC users are presented with the Notification Wizard one time every four hours and then one time every hour.

Effective March 1, 2010, Windows 7 RC enters the next phase of expiration:

• Expiration notifications in the task bar continue.
• Computers that are running Windows 7 RC restart every two hours.

Effective June 1, 2010, Windows 7 RC expires:

• Windows starts to a black desktop.
• Windows 7 RC users are presented with a Windows Activation screen. The screen states that the Windows that you are running is not genuine.
• Computers that are running Windows 7 RC restart every two hours.

 

[seven7seven]

Yeah, I bought and installed the RTM.
Working fine now