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: Persisten BSOD on a new RIG

25 Dec 2009   #1
Stanhope08

Windows 7
 
 
Persisten BSOD on a new RIG

Hi, i recently put together a new rig and installed windows 7 home premium. Right from the beginning i would get random BSODs. I reformatted and reinstalled windows 7 hoping the problem would go away. The strange thing about these BSODs were there in the beginning they would only happen after i leave the PC powered off for an extended period of time. Usually it would only happen once during a fresh session of using the PC. And initially it would usually happen only once, after the rebooted i could use the PC fine and no more BSODs would occur.

But in the last few days it has been occuring more often. Like maybe twice during startup, then once in the middle of using the PC. I ran windows memory diagnostics, harddisk scan but nothing wrong came up. Im kinda lost on this and already reformatted twice with no help. Pls advise what should i do.

Attached all the mini dumps of the BSODs.


My System SpecsSystem Spec
.
26 Dec 2009   #2
Stanhope08

Windows 7
 
 

any help please? did i omit information that could help troubleshoot?
My System SpecsSystem Spec
26 Dec 2009   #3
ickymay

win7 ultimate / virtual box
 
 

I'm no expert on reading minidumps but you could start by making sure all of your system drivers are fully up to date such as chipset and graphics card , then try running your system with maybe just one pair of RAM sticks and see if it's more stable ?
My System SpecsSystem Spec
.

26 Dec 2009   #4
usasma
Microsoft MVP

 
 

ickymay's advice is solid, please follow it.
I'm suspecting the Catalyst Control Center after a quick look.
-Download the driver ONLY (not the whole Catalyst Control Center program) from http://www.ati.com
-Uninstall all your ATI stuff from Control Panel...Programs...Uninstall a program
-Install the downloaded driver
-Monitor for further BSOD's

Start with this:
Quote:
H/W Diagnostics:
Please start by running these 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)
Running the minidumps, will be back when they're done....
My System SpecsSystem Spec
26 Dec 2009   #5
usasma
Microsoft MVP

 
 

Yep, it's most likely the Catalyst Control Center - so follow the advice in the previous post.
But you've also got Driver Verifier running - please turn it off ASAP! It will cause more frequent BSOD's just because it's running.

To turn it off, go to Start and type in "verifier" (without the quotes) and press Enter.
Select the "Delete existing settings" radio button, then click on Finish to exit the dialog.

Here's the summary of the dump file analysis:
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Dec 12 09:18:59.321 2009 (GMT-5)
System Uptime: 0 days 0:00:15.430
BugCheck 50, {fffff8a001711eb8, 0, fffff880012c376a, 0}
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCleanup+13a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 20 19:41:01.579 2009 (GMT-5)
System Uptime: 0 days 1:38:01.703
BugCheck 4E, {2, 23896e, 23ffff, 1}
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+8e )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  daorigins.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Dec 23 09:29:36.159 2009 (GMT-5)
System Uptime: 0 days 0:08:14.172
BugCheck C9, {20e, fffff88007136432, fffff980229e4ea0, 0}
*** WARNING: Unable to verify timestamp for atdcm64a.sys
*** ERROR: Module load completed but symbols could not be loaded for atdcm64a.sys
Probably caused by : atdcm64a.sys ( atdcm64a+2432 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  InstallManager
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Dec 23 08:08:59.849 2009 (GMT-5)
System Uptime: 0 days 0:23:01.973
BugCheck C9, {20e, fffff88007380432, fffff9802194cea0, 0}
*** WARNING: Unable to verify timestamp for atdcm64a.sys
*** ERROR: Module load completed but symbols could not be loaded for atdcm64a.sys
Probably caused by : atdcm64a.sys ( atdcm64a+2432 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  InstallManager
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Dec 23 00:25:12.921 2009 (GMT-5)
System Uptime: 0 days 5:23:06.030
BugCheck C1, {fffff98019c32fe0, fffff98019c320c2, 3d0020, 23}
Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+9a )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Dec 22 19:01:07.062 2009 (GMT-5)
System Uptime: 0 days 0:23:02.186
BugCheck 4E, {99, 1ca4eb, 3, 1c475d}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Dec 23 09:20:34.419 2009 (GMT-5)
System Uptime: 0 days 0:52:05.543
BugCheck C9, {20e, fffff88006f9e432, fffff98021b9cea0, 0}
*** WARNING: Unable to verify timestamp for atdcm64a.sys
*** ERROR: Module load completed but symbols could not be loaded for atdcm64a.sys
Probably caused by : atdcm64a.sys ( atdcm64a+2432 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  InstallManager
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Dec 23 08:27:36.797 2009 (GMT-5)
System Uptime: 0 days 0:17:49.906
BugCheck C9, {20e, fffff88007bac432, fffff98022470ea0, 0}
*** WARNING: Unable to verify timestamp for atdcm64a.sys
*** ERROR: Module load completed but symbols could not be loaded for atdcm64a.sys
Probably caused by : atdcm64a.sys ( atdcm64a+2432 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  InstallManager
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Dec 23 00:50:07.404 2009 (GMT-5)
System Uptime: 0 days 0:23:54.528
BugCheck 4E, {99, 8a766, 3, 8a464}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Dec 24 23:20:43.554 2009 (GMT-5)
System Uptime: 0 days 0:00:16.662
BugCheck F4, {3, fffffa80099d8b30, fffffa80099d8e10, fffff80002fcb240}
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Dec 25 21:19:52.537 2009 (GMT-5)
System Uptime: 0 days 0:28:50.661
BugCheck 1A, {5003, fffff781c0000000, 53e, 54000100a7c}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl+4d80b )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  dwm.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Dec 25 21:26:27.605 2009 (GMT-5)
System Uptime: 0 days 0:00:23.602
BugCheck 18, {0, 100000, 2, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46661 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  services.exe
My System SpecsSystem Spec
27 Dec 2009   #6
Stanhope08

Windows 7
 
 

thanks for the replies, i have uninstalled the catalyst control center, crashing a couple of times in the process.
turned off verifier as well.
downloaded Diag504fCD.iso from WD Support > Downloads > SATA & SAS > WD Raptor, booted from it but was unable to run, it said unable to find some acknowledgment.txt. burned 2 different CDs with the same results.
As for the system drivers, how do i check if all of them are up to date? is that a program or website that will make things easier?
My System SpecsSystem Spec
27 Dec 2009   #7
usasma
Microsoft MVP

 
 

If you're having issues with the WD test, please try the Hitachi Drive Fitness Test or the Seagate SeaTools

In order to update your drivers, don't use Windows Update or the Update driver function in Device Manager - that's not enough when you're having problems. FWIW - a quick look at the drivers loaded when the crash occurred shows that they were all dated from 2009.

Instead, visit the website of the manufacturer's of each device on your system and see if there are any newer drivers available.
My System SpecsSystem Spec
28 Dec 2009   #8
Stanhope08

Windows 7
 
 

dont get BSODs anymore but get crashes and restarts without the BSOD screen, and this time no mini dumps to go with it. i have no idea what is causing these crashes. first time it crashed when i was playing a game, then later when i rebooted the PC it would crash going to the windows logon page, restart, crash again, like 3 times b4 it finally booted into windows. how do i troubleshoot these random crashes and restarts?

also i tried running hitachi DFT it wont start, just stops at the starting blue screen.
My System SpecsSystem Spec
28 Dec 2009   #9
usasma
Microsoft MVP

 
 

Try the Seagate SeaTools bootable disk

Please upload this to help us:
Quote:
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.
My System SpecsSystem Spec
28 Dec 2009   #10
Stanhope08

Windows 7
 
 

ok thanks will try seagate one.
more crashes today. i noticed it will usually crash when it cold boots, like after its turned off for say 8 hours, the first time i try to start the pc, it will crash several times trying to get into the desktop then after that relatively stable for use. does that give any clue to whats causing the problem?

attached msinfo
My System SpecsSystem Spec
Reply

 Persisten BSOD on a new RIG




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 03:36.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App