2 BSOD's Please help.....

seth500 · 24 Feb 2011

2 BSOD's Please help.....Files are attached thanks in advance....

usasma · 27 Feb 2011

Please visit Windows Update and check to ensure that you have all Windows Updates (most SP1 systems have 14 updates listed in the systeminfo.txt file - yours has 10)

Potential issues from MSINFO32:
Acronis True Image - uninstall it while testing. The drivers are old, but you probably don't want to spring for a new copy just to test.

Comodo Internet Security - when most internet security apps break, there's not much information that points the finger at them as being the cause of problems. As such we recommend this:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Comodo Internet Security from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Comodo Internet Security using this free tool (requires registration): Login
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's

ATI Catalyst Control Center - uninstall it, yours is from Sep 2010, the time when we were noticing issues with it causing BSOD's. If you absolutely must have it, then download the latest version (CCC 2.0) from the ATI website.

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Please update these drivers from the device manufacturer's website - or uninstall/remove them from your system. Reference links included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Windows Update exceptions may be noted below for Windows drivers:

Code:


amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
cmdguard.sys    Wed Jan 05 12:10:43 2011 (4D24A613)
timntr.sys      Wed Jun 02 08:56:47 2010 (4C06550F)
snapman.sys     Thu Nov 11 06:05:10 2010 (4CDBCDE6)
tdrpm273.sys    Tue Aug 10 05:54:18 2010 (4C6121CA)
truecrypt.sys   Sun Sep 05 10:23:16 2010 (4C83A7D4)
point64.sys     Tue Dec 14 06:09:25 2010 (4D075065)
ISODrv64.sys    Thu Jan 28 22:39:02 2010 (4B625856)
RTKVAC64.SYS    Thu Jun 18 15:37:20 2009 (4A3A9770)
atikmpag.sys    Wed Jan 26 17:13:33 2011 (4D409C8D)
GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
nvm62x64.sys    Fri Oct 17 17:01:06 2008 (48F8FD12)
AtihdW76.sys    Wed Nov 17 07:02:04 2010 (4CE3C43C)
tap0901.sys     Thu Aug 19 18:07:59 2010 (4C6DAB3F)
amdiox64.sys    Thu Feb 18 10:17:53 2010 (4B7D5A21)
ASACPI.sys      Wed Jul 15 23:31:29 2009 (4A5E9F11)
afcdp.sys       Thu Nov 18 11:20:02 2010 (4CE55232)
mbam.sys        Thu Dec 16 15:53:16 2010 (4D0A7C3C)
cmderd.sys      Wed Jan 05 12:09:44 2011 (4D24A5D8)
atikmdag.sys    Wed Jan 26 17:48:28 2011 (4D40A4BC)
inspect.sys     Wed Jan 05 12:09:49 2011 (4D24A5DD)

Once all of that's done, please run Driver Verifier according to these instructions:

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:

Code:

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: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu Feb 24 15:33:16.000 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:14.265
Probably caused by : ntkrnlmp.exe ( nt!CmpGetNameControlBlock+12e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!CmpGetNameControlBlock+12e
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02d57909 fffff880`036e9a30 00000000`00000000
SystemManufacturer = alienware
SystemProductName = alienware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu Feb 24 13:57:00.538 2011 (UTC - 5:00)
System Uptime: 0 days 2:14:32.803
Probably caused by : win32k.sys ( win32k!xxxRedrawTitle+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k!xxxRedrawTitle+0
Bugcheck code 00000050
Arguments ffffffff`ffffff9f 00000000`00000000 fffff960`00129924 00000000`00000000
SystemManufacturer = alienware
SystemProductName = alienware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed Feb 23 23:34:13.636 2011 (UTC - 5:00)
System Uptime: 0 days 1:33:38.902
Probably caused by : win32k.sys ( win32k!xxxDoButtonEvent+31f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!xxxDoButtonEvent+31f
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`00177dc7 fffff880`02b91fd0 00000000`00000000
SystemManufacturer = alienware
SystemProductName = alienware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed Feb 23 20:36:38.359 2011 (UTC - 5:00)
System Uptime: 0 days 6:16:13.625
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000060 00000000`00000000 fffff880`009e5180 00000000`00000001
SystemManufacturer = alienware
SystemProductName = alienware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``