BSOB on newly built PC dif. ones randomly

panicinwi · 14 Jun 2012

Hello, I am at my wits end trying to figure out why a newly built PC keeps getting BSOD and doing random shutoffs. I have replaced the memory and MB and have tested with and without the video card or OB video. I have also tried a different PSU to see if that would help. I am leaning towards a bad CPU or incompatible memory, but wanted to see what you folks think first. Also, the system has been reloaded twice. The first time was a new install and then I reloaded everything after I installed the new MB. Thank you in advance

edit: forgot the system specs:
OS - Windows 7 Pro 64
MB - Gigabyte GA-Z77-D3H
CPU - Intel i7-3770
RAM - Patriot PD000256-PXQ316G1866ELQK PC3-15000 1866MHz 16GB (4x4GB) Kit
Video - AMD FirePro V4900 1GB DP/DVI HF
PSU - Rosewill Hive-650

usasma · 15 Jun 2012

Intel High Definition Audio device is disabled. Is this deliberate? If so, why? Please be sure to re-enable the device and update it's drivers (feel free to disable it again after doing this).

Problems are noted with a PS2 keyboard. If using a USB keyboard, feel free to ignore this message

Only 46 updates after SP1 - most systems have more than 75. Please visit Windows Update and get all available updates (be sure to update drivers before doing this).

Recently we've been seeing issues with the AppleCharger software - please uninstall it.

Hibernation storage drivers date from 2009 - ensure that you get all Windows Updates.
BSOD's in association with hibernation usually involve video, storage, and chipset drivers. Please update all of them from the device manufacturer's website AMD video from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD ; Storage drivers and chipset drivers (to include Intel Management Engine) from http://downloadcenter.intel.com

If all these updates don't fix things, please run Driver Verifier according to these instructions: Driver Verifier Settings

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


AppleCharger.sys  Tue Nov 01 22:46:00 2011 (4EB0AEE8)
EtronHub3.sys     Fri Jan 06 03:59:47 2012 (4F06B803)
EtronXHCI.sys     Fri Jan 06 03:59:41 2012 (4F06B7FD)
HECIx64.sys       Wed Nov 09 19:52:25 2011 (4EBB2049)
L1C62x64.sys      Wed Aug 03 02:21:09 2011 (4E38E8D5)
amdxata.sys       Fri Mar 19 12:18:18 2010 (4BA3A3CA)
hiber_atapi.sys   Mon Jul 13 19:19:47 2009 (4A5BC113)
hiber_ataport.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
hiber_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
igdkmd64.sys      Mon Mar 19 19:31:54 2012 (4F67C1EA)
iusb3hcs.sys      Fri Jan 27 04:37:23 2012 (4F227053)
iusb3hub.sys      Fri Jan 27 04:35:25 2012 (4F226FDD)
iusb3xhc.sys      Fri Jan 27 04:35:28 2012 (4F226FE0)
viahduaa.sys      Tue Jan 10 06:33:14 2012 (4F0C21FA)

Code:


Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061312-13572-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Jun 13 18:00:00.574 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:12.339
BugCheck A, {fffffa80ca46b028, 2, 1, fffff80002afe741}
Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+181 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  TrustedInstall
FAILURE_BUCKET_ID:  X64_0xA_nt!MiUnlinkFreeOrZeroedPage+181
Bugcheck code 0000000A
Arguments fffffa80`ca46b028 00000000`00000002 00000000`00000001 fffff800`02afe741
BiosVersion = F8
BiosReleaseDate = 02/21/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
MaxSpeed:     3400
CurrentSpeed: 3430
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061412-13057-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Jun 14 09:05:49.915 2012 (UTC - 4:00)
System Uptime: 0 days 0:08:14.680
BugCheck DE, {2, fffff8a002e29a68, fffff8a006e29a69, 35b6ff8c0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2ce61 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xDE
PROCESS_NAME:  Hard Disk Sent
FAILURE_BUCKET_ID:  X64_0xDE_nt!_??_::FNODOBFM::_string_+2ce61
Bugcheck code 000000DE
Arguments 00000000`00000002 fffff8a0`02e29a68 fffff8a0`06e29a69 00000003`5b6ff8c0
BiosVersion = F8
BiosReleaseDate = 02/21/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
MaxSpeed:     3400
CurrentSpeed: 3430
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061412-13119-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Jun 13 18:30:51.360 2012 (UTC - 4:00)
System Uptime: 0 days 0:30:06.125
BugCheck 1A, {403, fffff6800013abf8, 8c900001b993f867, fffff6800413abf8}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3267c )
BUGCHECK_STR:  0x1a_403
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  WinSAT.exe
FAILURE_BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+3267c
Bugcheck code 0000001A
Arguments 00000000`00000403 fffff680`0013abf8 8c900001`b993f867 fffff680`0413abf8
BiosVersion = F8
BiosReleaseDate = 02/21/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
MaxSpeed:     3400
CurrentSpeed: 3430
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061412-13494-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Jun 14 11:13:51.186 2012 (UTC - 4:00)
System Uptime: 0 days 0:33:23.951
BugCheck A, {fffffa80c8f822b0, 2, 1, fffff80002cff830}
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+c0
Bugcheck code 0000000A
Arguments fffffa80`c8f822b0 00000000`00000002 00000000`00000001 fffff800`02cff830
BiosVersion = F8
BiosReleaseDate = 02/21/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
MaxSpeed:     3400
CurrentSpeed: 3430
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061412-16536-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Jun 14 09:50:01.307 2012 (UTC - 4:00)
System Uptime: 0 days 0:43:54.073
BugCheck A, {fffffa80c4de1760, 2, 0, fffff80002ed33f0}
Probably caused by : memory_corruption ( nt!MmDuplicateMemory+8d0 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!MmDuplicateMemory+8d0
Bugcheck code 0000000A
Arguments fffffa80`c4de1760 00000000`00000002 00000000`00000000 fffff800`02ed33f0
BiosVersion = F8
BiosReleaseDate = 02/21/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
MaxSpeed:     3400
CurrentSpeed: 3430
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

panicinwi · 15 Jun 2012

Thank you for the reply. Got all the drivers updated, Windows update done (which I was having issues with) and removed AppleCharger. System seems to be running smooth now. The other thing I did which i do not know if I should change back, but i changed the voltage for the memory in the BIOS to 1.5 instead of the 1.65 that the memory is rated at. After I did that it seemed like the system began to not have the BSOD. I guess I will change it back and see if I start getting them again.

Update - after I changed the voltage on the memory in the BIOS I have had two BSOD. Just wondering if I should just return the memory I currently have and get different ones with the 1.5v rating?

usasma · 15 Jun 2012

I'm not a hardware tweaker - but would suggest that you test again with the memory at 1.5 again. If it stops the BSOD, then you've got your issue nailed down.

If that's the case, then contact the RAM manufacturer for further advice.