New
#1
BSOD - multiple Errors
The last two were just today were:
Bad_Pool_Header
Page_Fault_in_Nonpaged_area
attached are analysis results:
Last edited by itauditor; 06 Sep 2010 at 10:37. Reason: Attachements failed
The last two were just today were:
Bad_Pool_Header
Page_Fault_in_Nonpaged_area
attached are analysis results:
Last edited by itauditor; 06 Sep 2010 at 10:37. Reason: Attachements failed
There are no current BSOD reports in the uploaded info. Please do the following:
For the older dump files: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
Unfortunately, the Windows Debugging Tools aren't able to access symbols for your operating system files (in particular NTOSKRNL.EXE / NTKRNLMP.EXE / NTKRNLPA.EXE / NTKRPAMP.EXE) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.
Please do the following (this will not affect the analysis of the current files - but it may help later files that are acquired):
- activate/validate the Windows installation at Genuine Microsoft Software
- run sfc.exe /scannow to replace any problem files
- open a support incident with Microsoft to see if they can fix the missing symbols issue ( Windows 7 Solution Center )
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds
So, based on your description, I'd run Driver Verifier according to the instructions (after resetting the system to generate minidumps):
BSOD BUGCHECK SUMMARYUsing 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:
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced usersCode: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\VerifyDriverLevelCode:*** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Thu Jul 1 10:03:38.959 2010 (UTC - 4:00) System Uptime: 0 days 0:09:10.676 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe BugCheck FE, {8, 6, 6, fffffa800829b000} Probably caused by : usbhub.sys ( usbhub!UsbhWaitEventWithTimeoutEx+3aa ) BUGCHECK_STR: 0xFE ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Thu Jul 1 09:53:18.833 2010 (UTC - 4:00) System Uptime: 0 days 17:44:49.549 *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe BugCheck 3B, {c0000005, fffff80002ba2121, fffff88005524160, 0} Probably caused by : ntoskrnl.exe ( nt+385121 ) BUGCHECK_STR: 0x3B ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Wed Jun 30 16:07:18.734 2010 (UTC - 4:00) System Uptime: 0 days 8:38:38.060 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe BugCheck 1A, {41201, fffff683ff7ef210, 2d10000214081025, fffffa800956bb10} Probably caused by : ntoskrnl.exe ( nt+71f00 ) BUGCHECK_STR: 0x1a_41201 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Wed Jun 30 07:27:42.053 2010 (UTC - 4:00) System Uptime: 0 days 0:43:03.029 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe BugCheck A, {0, 2, 1, fffff8000268b18c} Probably caused by : ntoskrnl.exe ( nt+7b18c ) BUGCHECK_STR: 0xA ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``