Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Just got this BSOD, but I've been having a lot of them lately:

28 May 2010   #1
capheine

Windows 7 Home Premium 64-bit
 
 
Just got this BSOD, but I've been having a lot of them lately:

Anyone care to analyze the .dmp?

I appreciate it. Thanks


My System SpecsSystem Spec
.
28 May 2010   #2
usasma
Microsoft MVP

 
 

Single dump files aren't usually very helpful. Please zip up the entire contents of the C:\Windows\Minidump folder and upload it with your next post.

In this case the memory dump blames a core Windows file (win32k.sys) and that's not the cause (if it was the cause, you'd be having many more issues than just the occasional BSOD).

Summary of the BSOD:
Code:
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 28 16:58:41.103 2010 (GMT-4)
System Uptime: 0 days 0:01:00.508
BugCheck 3B, {c0000005, fffff96000164352, fffff88007c51d90, 0}
Probably caused by : win32k.sys ( win32k!RGNOBJ::vSet+26 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  firefox.exe
My System SpecsSystem Spec
29 May 2010   #3
capheine

Windows 7 Home Premium 64-bit
 
 

Thanks, here you go:
My System SpecsSystem Spec
.

29 May 2010   #4
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by capheine View Post
Thanks, here you go:
Sorry file is corrupt you need to upload again

Ken
My System SpecsSystem Spec
29 May 2010   #5
usasma
Microsoft MVP

 
 

16 memory dumps from 04 May 2010 to the present (3 weeks)
6 different STOP error codes, with 4 different causes listed.
Normally this pattern is suggestive of a hardware/compatibility problem - but there's enough evidence in the dump files to suggest a driver issue (in other words, this is gonna be complicated).

If it is a hardware issue, my suspicions would be with your storage sub-system (hard drive, connections, and hard drive controllers)

Let's start with Driver Verifier to ensure that it's not going to yield up an easy fix. Please follow these instructions in order to run it:
Quote:
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. 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 users
Once that's done, please try these diagnostics to check out the hard drive (and some other possibilities):
Quote:
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)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
Quote:
CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.
Please update the Asus Probe utility on your system due to it's age: Driver Reference

Summary of the BSOD's:
Code:
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 28 16:58:41.103 2010 (GMT-4)
System Uptime: 0 days 0:01:00.508
BugCheck 3B, {c0000005, fffff96000164352, fffff88007c51d90, 0}
Probably caused by : win32k.sys ( win32k!RGNOBJ::vSet+26 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  firefox.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu May 27 20:05:00.199 2010 (GMT-4)
System Uptime: 0 days 0:13:39.604
BugCheck 4E, {99, 8b06d, 2, 8b06a}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  dllhost.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May 25 01:27:56.162 2010 (GMT-4)
System Uptime: 0 days 0:06:25.816
BugCheck 3B, {c0000005, fffff80002a4d3fa, fffff88005c59f60, 0}
Probably caused by : ntkrnlmp.exe ( nt!RtlpCoalesceFreeBlocks+ae )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 17 22:59:04.006 2010 (GMT-4)
System Uptime: 0 days 0:04:16.660
BugCheck 4E, {99, 1ad3e, 3, 1a90d}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  chrome.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 17 22:50:43.454 2010 (GMT-4)
System Uptime: 0 days 0:02:52.109
BugCheck 1A, {41790, fffffa8000499b00, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  svchost.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 17 22:46:27.312 2010 (GMT-4)
System Uptime: 0 days 0:05:14.966
BugCheck 1A, {5003, fffff781c0000000, 9f8b, 75a40001bf16}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29f97 )
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 17 22:40:43.691 2010 (GMT-4)
System Uptime: 0 days 0:01:59.345
BugCheck 1A, {403, fffff68000010930, b04000002838a867, fffff68000021062}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31f32 )
BUGCHECK_STR:  0x1a_403
PROCESS_NAME:  svchost.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 16 18:21:19.358 2010 (GMT-4)
System Uptime: 0 days 0:01:17.012
BugCheck 1, {7740001a, 0, ffff, fffff88007b83ca0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
BUGCHECK_STR:  0x1
PROCESS_NAME:  wmpnscfg.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 14 16:28:53.422 2010 (GMT-4)
System Uptime: 0 days 0:18:25.076
BugCheck 24, {1904fb, fffff880029e2ba8, fffff880029e2410, fffff880012c8c27}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+1fe )
PROCESS_NAME:  windirstat.exe
BUGCHECK_STR:  0x24
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 14 16:01:12.172 2010 (GMT-4)
System Uptime: 0 days 0:03:15.826
BugCheck 3B, {c0000005, fffff9600005bcb6, fffff880080c3c40, 0}
Probably caused by : win32k.sys ( win32k!RFONTOBJ::bGetGlyphMetricsPlus+216 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  firefox.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May 11 19:47:18.789 2010 (GMT-4)
System Uptime: 0 days 0:05:00.444
BugCheck 4E, {99, 2658a, 1, 26592}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  firefox.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 10 16:18:22.963 2010 (GMT-4)
System Uptime: 0 days 0:13:29.352
BugCheck 4E, {99, 11d60c, 2, 122112}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  vlc.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May  7 19:46:09.894 2010 (GMT-4)
System Uptime: 0 days 0:04:26.549
BugCheck 1A, {3452, 7fefa158000, fffff700010816b0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33a23 )
BUGCHECK_STR:  0x1a_3452
PROCESS_NAME:  WMIADAP.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu May  6 20:39:19.192 2010 (GMT-4)
System Uptime: 0 days 0:10:51.846
BugCheck 4E, {2, e06a, 12ffff, 1}
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+8e )
BUGCHECK_STR:  0x4E_2
PROCESS_NAME:  MsMpEng.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu May  6 20:27:56.189 2010 (GMT-4)
System Uptime: 0 days 0:08:46.594
BugCheck 1A, {41284, 13361001, a1f5, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  firefox.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May  4 19:51:25.981 2010 (GMT-4)
System Uptime: 0 days 0:06:20.635
BugCheck A, {0, 2, 1, fffff80002a7b88c}
Probably caused by : ntkrnlmp.exe ( nt!KeWaitForSingleObject+17c )
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
My System SpecsSystem Spec
29 May 2010   #6
capheine

Windows 7 Home Premium 64-bit
 
 

Thanks! I'll try those fixes.
My System SpecsSystem Spec
30 May 2010   #7
capheine

Windows 7 Home Premium 64-bit
 
 

Thanks for the help so far. I ran driver verifier and followed the instructions usasma posted, and here are the results (2 crashes).

I have not run the diagnostic programs or updated the Asus Probe utility yet. I'll do those after I get a response.

I appreciate the help!
My System SpecsSystem Spec
30 May 2010   #8
usasma
Microsoft MVP

 
 

Run the diagnostics - they won't hurt and may help
Update the Asus PCProbe program (or at least remove it).

Don't forget to turn Driver Verifier off now.

The memory dump files blame ASACPI.sys - which is a component of the Asus PCProbe program.
Please download a fresh copy of the PCProbe program from the Asus website
Then uninstall the current copy (which will remove the corruption)
Then install the freshly downloaded copy of the PCProbe program.

Summary of the BSOD's:
Code:
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 30 10:43:37.808 2010 (GMT-4)
System Uptime: 0 days 0:00:32.478
BugCheck C4, {f6, e0, fffffa8006ecd360, fffff88004812257}
*** WARNING: Unable to verify timestamp for ASACPI.sys
*** ERROR: Module load completed but symbols could not be loaded for ASACPI.sys
Probably caused by : ASACPI.sys ( ASACPI+1257 )
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  FourEngine.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 30 10:42:35.170 2010 (GMT-4)
System Uptime: 0 days 0:00:33.840
BugCheck C4, {f6, e0, fffffa8006ec0b30, fffff88004964257}
*** WARNING: Unable to verify timestamp for ASACPI.sys
*** ERROR: Module load completed but symbols could not be loaded for ASACPI.sys
Probably caused by : ASACPI.sys ( ASACPI+1257 )
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  FourEngine.exe
My System SpecsSystem Spec
30 May 2010   #9
capheine

Windows 7 Home Premium 64-bit
 
 

Yup, Driver Verifier is off and things are looking good for now.

Will run diagnostics later today.

I uninstalled PCProbe (which I never use anyway). Might install new version, might not.

Thanks a bunch, usasma!
My System SpecsSystem Spec
30 May 2010   #10
usasma
Microsoft MVP

 
 

Be advised that the ASACPI.sys driver is also known to come from Windows Update (primarily when first setting up Win7 systems). Please be sure that you don't download it by accident!

Good luck!
My System SpecsSystem Spec
Reply

 Just got this BSOD, but I've been having a lot of them lately:




Thread Tools



Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 17:49.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App