Windows 7 BSOD on First Boot Up

[Rolovis]

Hello,

I just recently built a new computer, and it seems that every time that I boot up after the computer being off for a while, it Blue Screens. Then while rebooting, if I hold the power button and turn it back on, it works great all day.

I've ran the Windows memory test on normal and extended (I think those are the options) and haven't gotten any errors. I've also ran all 4 of the tests from Seagate on my HD and none of them showed errors. I've updated my drivers, attempted to uninstall programs that I thought could be causing errors (AVG, Curse Client, Ideazon Board Engine), but it didn't resolve anything. I've also ran a CHKDSK and no errors were found as well. I've reinstalled Windows 7 twice, thinking that it was a bad build.

I hope that someone can assist me in this. I've attached my .zip file of all of my BSOD's. There are some driver ones in there when I was attempting to track down the problem using verifier.exe. Also I'm attaching a DXDIAG if that helps at all.

System Specs:
CPU: AMD Phenom II X4 965 3.4ghz Quad Core
Motherboard: ASUS M4A78T-E AM3
RAM: G.Skill 3x2GB DDR3 1600 PC3 12800
Video Card: nVidia GeForce GTX260
Hard Drive: Seagate Barracuda 1TB 7200rpm Sata

Thanks in advance for everyone's help.

 

[Rolovis]

I went ahead and tried to upgrade my chipset again to no avail. I just replaced the SATA cable to my HD...but cannot test it until I get home later since it already Blue Screen'd this morning.

 

[usasma]

19 memory dumps from 02 to 15 Sep 2010 (about 2 weeks)
6 different BSOD error codes
8 different causes blamed
I suspect that this is a hardware problem...BUT....

There are 4 Verifier Enabled memory dumps and they blame 3 different 3rd party drivers. What settings did you use for Driver Verifier?

The drivers blamed are:
Alpham264.sys - Driver Reference
atdcm64a.sys - Driver Reference
ASACPI.sys - Driver Reference

Remove the Ideazon drivers (Alpham264.sys) and use the default Windows drivers until we're finished troubleshooting
Update the ATI drivers (atdcm64a.sys) from the AMD/ATI website (see the link above)
Update the Asus ATK0110 ACPI Utility driver (ASACPI.sys) from the Asus website (see the link above)

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers (You can look them up here: Driver Reference ).
Please pay particular attention to any dated 2008 or earlier:

Alpham164.sys Mon Jul 23 03:57:03 2007 - Ideazon ZBoard - http://www.carrona.org/dvrref.html#Alpham164.sys
Alpham264.sys Tue Mar 20 05:51:03 2007 - Ideazon ZBoard - http://www.carrona.org/dvrref.html#Alpham264.sys
AsIO.sys     Mon Dec 17 04:11:49 2007 - Asus PCProbe Utility (will also update the ASACPI.sys driver) - http://www.carrona.org/dvrref.html#AsIO.sys

If all of that doesn't fix things, please zip up and post the next BSOD's.
While waiting for a response you can try these free hardware diagnostics:

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) - I know that you've run this, please run it again.

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)

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep 15 20:23:32.044 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:12.356
BugCheck 3B, {c0000005, fffff9600003415e, fffff880076b97b0, 0}
Probably caused by : win32k.sys ( win32k!EngTextOut+11e )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  TurboV.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep 15 09:33:34.217 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:41.529
BugCheck 3B, {c0000005, fffff960000cdd37, fffff88008611e10, 0}
Probably caused by : win32k.sys ( win32k!xxxCreateWindowEx+2353 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  TurboV.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 14 21:58:04.470 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:10.172
BugCheck 24, {1904fb, fffff88006a46718, fffff88006a45f80, fffff880010cac50}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+227 )
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 12 00:30:53.716 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:29.417
BugCheck 3B, {c0000005, fffff960000c46f0, fffff88007c11d50, 0}
Probably caused by : win32k.sys ( win32k!GreUpdateSpriteVisRgn+c8 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  VDeck.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 11 17:28:48.681 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:37.383
BugCheck 3B, {c0000005, fffff80002bab00e, fffff88006271f40, 0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+182 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Sep 10 11:15:49.182 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:35.509
BugCheck 1000007E, {ffffffffc0000005, fffff80002dc9b4a, fffff88002fcb968, fffff88002fcb1d0}
Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceNameControlBlockWithLock+22 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Sep 10 00:12:44.206 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:48.908
BugCheck 3B, {c0000005, fffff960002d82f6, fffff8800865adb0, 0}
Probably caused by : win32k.sys ( win32k!RBRUSH::vRemoveRef+12 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep  9 09:24:52.666 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:17.977
BugCheck 24, {1904fb, fffff880066776b8, fffff88006676f20, fffff8800110f173}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFcbTableCompare+3 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  8 23:12:05.598 2010 (UTC - 4:00)
System Uptime: 0 days 0:23:17.315
BugCheck C4, {62, fffffa8007cc67c8, fffffa8007cc6600, 6}
*** WARNING: Unable to verify timestamp for Alpham264.sys
*** ERROR: Module load completed but symbols could not be loaded for Alpham264.sys
Probably caused by : Alpham264.sys
BUGCHECK_STR:  0xc4_62
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  8 22:48:15.654 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:12.371
BugCheck C9, {20e, fffff880072e3432, fffff980013f2ea0, 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 )
BUGCHECK_STR:  0xc9_20e
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  ATISetup.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  8 22:46:12.959 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:11.675
BugCheck C9, {20e, fffff88005f0c432, fffff98017e48ea0, 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 )
BUGCHECK_STR:  0xc9_20e
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  ATISetup.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  8 22:28:21.831 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:12.158
BugCheck C9, {22f, fffff88003ea09a0, fffff9801738acf0, 0}
*** 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+19a0 )
BUGCHECK_STR:  0xc9_22f
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  8 22:15:37.901 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:01.602
BugCheck 24, {1904fb, fffff88002f9a268, fffff88002f99ad0, fffff88001229e10}
Probably caused by : Ntfs.sys ( Ntfs!NtfsLookupNtfsMcbEntry+4c )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep  7 20:54:45.713 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:33.415
BugCheck 24, {1904fb, fffff88002f936a8, fffff88002f92f10, fffff800029aa0f3}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFullDeleteLcb+122 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep  7 20:51:53.982 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:00.293
BugCheck 24, {1904fb, fffff880056a0f68, fffff880056a07d0, fffff880012e2bf7}
Probably caused by : Ntfs.sys ( Ntfs!NtfsOpenAttribute+3a7 )
PROCESS_NAME:  WerFault.exe
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep  7 20:47:34.452 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:24.763
BugCheck 24, {1904fb, fffff880090fb718, fffff880090faf80, fffff880010ff183}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+75e )
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 14:01:19.667 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:38.368
BugCheck 50, {ffffb8a0001cbf10, 0, fffff800028d2d6c, 7}
Probably caused by : memory_corruption ( nt!MiCaptureProtectionFromProto+1c )
BUGCHECK_STR:  0x50
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Sep  3 20:36:08.388 2010 (UTC - 4:00)
System Uptime: 0 days 0:09:37.699
BugCheck 24, {1904fb, fffff88007e669a8, fffff88007e66210, fffff880010f9bf7}
Probably caused by : Ntfs.sys ( Ntfs!NtfsOpenAttribute+3a7 )
PROCESS_NAME:  Wow.exe
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep  2 20:31:25.545 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:25.856
BugCheck 24, {1904fb, fffff88002f856b8, fffff88002f84f20, fffff80002854938}
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteFcb+179 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  
 
 [/FONT]