Blue screen - perfmon wont save

[win7jak]

Hi
Got the dreaded but not unknown Windows Blue Screen of Death in Win7 Pro.

It came about because -
From hibernated state I reboot - no info comes up on screen / black screen.
Red light on boot hard drive is constantly illuminated indicating it is working. Cant confirm that though as no info came up on screen.
Reboot
Starts normally
Blue screen of death
Rebooted - it worked normally.
Came here [SevenForums]
Followed instructions for Blue Screen report
Tried to copy Windows_NT6_BSOD_jcgriff2 through Notepad - 'no response"/cancelled. This report is not in boot drive but another drive. Followed instructions - searched for Perfmon / report - no response. Here we are. The inability to noot normally from hibernation has happed a few times in the past two days. Have tried System restore points several times to no avail. Hmmm...very dissapointing since I've only had Win7 aboard for a few weeks, Couldnt bare another XP lookalike.:geek: Any ideas? thx:geek:

 

[usasma]

At a minimum, please do this:

Upload Dump Files:
Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.
Left click on the first minidump file.
Hold down the "Shift" key and left click on the last minidump file.
Right click on the blue highlighted area and select "Send to"
Select "Compressed (zipped) folder" and note where the folder is saved.
Upload that .zip file with your next post.

If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.

If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service . I recommend Windows Live SkyDrive - http://skydrive.live.com or another free, file-hosting service. Then post the link to it in your topic so that we can download it.

Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Set MiniDump

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.

 

[win7jak]

Thx for the reply.
An immediate problem...I try to zip the Minidump content and it tells me I don't have permission. BTW, there are 5 entires in the folder, do I include them all when I can get it together that is.

 

[usasma]

Copy (DO NOT "move") the minidump files (NOT the folder) to your desktop
Then try to zip them from there.

Include all 5. Sometimes all will establish a pattern that you can't see with just one. Also, sometimes only one of the 5 will have the answer - but you don't know which one in advance.

 

[win7jak]

OK, got it worked out.
Here are the two zipped files. I hope I got all the info you need.

BTW, since my first post I have used UBCD4Win v3.5 to try to correct errors. Cant remember the programs I used though. Didn't seem to help.

Other notables are -
reboot button doesn't work. Have to OFF/ON to re ignite.
Firefox is playing up v 3.6.10. When I install Add Ons / Extensions, the icons do not appear anywhere on screen.
If I leave to computer on and unattendedView attachment 100225

View attachment 100226 for about 20 minutes it automatically goes in hibernation. Upon hitting reboot, it is starting the boot, stops, starts, and so it goes on till I hit the OFF switch, then ON, then it will boot.

Did the attaches [2] work OK?

 

[usasma]

From a quick look at the MSINFO32 file, we're probably looking at a hardware issue.
Running the memory dumps right now and will post back in a few minutes with details

 

[win7jak]

Thx, looking forward to your reply

 

[usasma]

The hardware issue isn't as clear cut at this point. So, let's try some other stuff first (we'll revisit the hardware issue if this stuff doesn't fix it).

Please uninstall Ashampoo and leave it uninstalled while we troubleshoot. It has some problems with some installations of Win7.

DO NOT user registry cleaners!!! Read this link if you want to know why. Although it's written for XP it applies to Vista and Win7 also: XP Fixes Myth #1: Registry Cleaners

Please update your Blackberry software and drivers - they date from 2008 and could be causing problems. As the majority of the errors in the dump files point to classpnp.sys, I tend to suspect something with your Blackberry. The drivers are the first step, but trying a new cable would help rule out issues also.

I suspect all Internet Security applications, so please do this to ensure that your ESET Smart Security isn't causing problems:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the ESET Smart Security from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of ESET Smart Security using this free tool: ESET Knowledgebase - How do I manually uninstall my ESET security product?
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's

Finally, if the above stuff doesn't fix it, then please run Driver Verifier according to these directions:

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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

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:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: http://support.microsoft.com/?kbid=244617&sd=RMVP

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Sat Sep 25 07:04:01.260 2010 (UTC - 4:00)
System Uptime: 0 days 7:53:51.068
Probably caused by : CLASSPNP.SYS ( CLASSPNP!SubmitTransferPacket+103 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 9ab90550 00000002 00000000 82c5df04
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Thu Sep 23 18:48:37.820 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:16.708
Probably caused by : CLASSPNP.SYS ( CLASSPNP!SubmitTransferPacket+103 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 9c12e388 00000002 00000000 82c6df04
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Thu Sep 23 15:05:39.475 2010 (UTC - 4:00)
System Uptime: 0 days 1:29:59.364
Probably caused by : CLASSPNP.SYS ( CLASSPNP!SubmitTransferPacket+103 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 99a267e0 00000002 00000000 82c6af04
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Thu Sep 23 04:48:36.531 2010 (UTC - 4:00)
System Uptime: 0 days 8:10:16.419
Probably caused by : CLASSPNP.SYS ( CLASSPNP!SubmitTransferPacket+103 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 9a346350 00000002 00000000 82c6ef04
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Sun Sep 19 19:06:35.985 2010 (UTC - 4:00)
System Uptime: 0 days 0:55:18.873
BugCheck D1, {82d9501c, 2, 0, 8586aedc}
Probably caused by : CLASSPNP.SYS ( CLASSPNP!SubmitTransferPacket+103 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 000000D1
Arguments 82d9501c 00000002 00000000 8586aedc
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/FONT]