BSOD idle/dota2/bf3 0x124 ntsokrnl.exe

TsMini · 28 Mar 2012

My system specs are updated in my profile, and here are my recent steps to resolve this problem.

1. Said "to hell with it" and did a FRESH install on a single SSD (Kingston Hyper-X 120g). Still the same BSoD event.
2. Figured at this point, hardware. Flashed to new BIOS, still BSoD
3. Updated ALL drivers from mobo website. STILL BSoD
4. Ran MEMTESTx86 overnight. STILL BSoD
5. Pulled one graphics card, still BSoD.
6. Pulled the other..still BSoD.
7. Ran IBT and passed, then BSoD while on facebook.

Temperatures are 12C idle 50C for IBT per coretemp.

Thanks for any help!

usasma · 28 Mar 2012

What's IBT?

We've seen a number of BSOD issues with SSD's recently. Here's the information that I've compiled:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.-
Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum

Looks like you have 2 different SSD's installed (Kingston and Crucial). If so, I've never seen this before and wonder if they're compatible together. Try running with only 1 SSD to see if that helps.

perfmon /report shows your High Definition Audio device is disabled. Is this deliberate? If so, why?

AMD Overdrive is installed on your system and is known to cause BSOD's. Uninstall it and check to make sure that the AOD service (in services.msc) and the AODDriver device (in devmgmt.msc - hidden devices) are gone. If problems remain, post back for more advanced removal instructions.

19 BSOD's in 4 days (24-27 Mar 2012)
All but 3 appear to be STOP 0x124's
This means that this is most likely a hardware problem - which includes overclocking, compatibility issues, low-level driver problems (such as AMD OverDrive), or even malware.

The other 3 are Driver Verifier errors and they point to a Windows USB driver. Since these drivers are protected by the System File Checker, it's most likely that this is the same sort of situation as described with the STOP 0x124 errors - but we can't be certain as we don't know what settings that you used for Driver Verifier.

IMO this is most likely an issue with the SSD(s) and/or the mobo controller. Ensure that the controllers are updated to the latest version available from the controller manufacturer (NOT the mobo manufacturer). The SSD's must have the latest firmware installed.

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


PxHlpa64.sys      Tue Jun 23 19:16:35 2009 (4A416253)
mv91xx.sys        Wed Mar 17 03:53:06 2010 (4BA08A62)
mvxxmm.sys        Wed Mar 17 03:52:37 2010 (4BA08A45)
amdxata.sys       Fri Mar 19 12:18:18 2010 (4BA3A3CA)
AsrAppCharger.sys Tue May 10 04:28:46 2011 (4DC8F73E)
EtronXHCI.sys     Fri Jan 28 16:46:43 2011 (4D433943)
usbfilter.sys     Wed Oct 07 03:44:08 2009 (4ACC46C8)
LGBusEnum.sys     Mon Nov 23 20:36:48 2009 (4B0B38B0)
EtronHub3.sys     Fri Jan 28 16:46:45 2011 (4D433945)
ladfGSRamd64.sys  Mon Apr 11 14:41:07 2011 (4DA34B43)
ladfGSCamd64.sys  Mon Apr 11 14:41:01 2011 (4DA34B3D)
LHidFilt.Sys      Fri Sep 02 02:23:09 2011 (4E60764D)
LMouFilt.Sys      Fri Sep 02 02:23:15 2011 (4E607653)
RTKVHD64.sys      Tue May 24 08:32:39 2011 (4DDBA567)
MBfilt64.sys      Thu Jul 30 23:40:32 2009 (4A7267B0)
cpuz135_x64.sys   Wed Sep 21 04:23:41 2011 (4E799F0D)
ALSysIO64.sys     Sat Jul 09 20:27:45 2011 (4E18F201)
LGVirHid.sys      Mon Nov 23 20:36:48 2009 (4B0B38B0)
nvlddmkm.sys      Wed Feb 29 13:04:52 2012 (4F4E68C4)
nvBridge.kmd      Fri May 20 23:58:23 2011 (4DD7385F)
k57nd60a.sys      Mon Feb 14 23:19:05 2011 (4D59FEB9)
dsNcAdpt.sys      Mon Mar 30 22:33:33 2009 (49D180FD)
nvhda64v.sys      Tue Jan 17 07:45:46 2012 (4F156D7A)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032712-36816-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Wed Mar 28 01:32:40.571 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:05.631
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`080ad038 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032712-35927-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Tue Mar 27 22:02:15.618 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:05.773
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`085478f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032712-36551-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Tue Mar 27 18:32:55.462 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:05.648
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`07f218f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032712-36363-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Tue Mar 27 17:42:13.587 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:05.758
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`07f3a8f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032712-37159-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Tue Mar 27 16:23:04.649 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:05.725
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`085448f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032712-37767-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Tue Mar 27 16:18:06.768 2012 (UTC - 4:00)
System Uptime: 0 days 0:04:29.938
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`0871e028 00000000`fe800000 00000000`00020015
BiosVersion = P1.30
BiosReleaseDate = 09/13/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032712-36317-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Tue Mar 27 16:13:42.602 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:05.773
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`0851f8f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032712-37175-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Tue Mar 27 02:01:35.493 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:05.664
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`085238f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032612-37128-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Tue Mar 27 01:55:10.556 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:05.742
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`0851c8f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032612-39749-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Mon Mar 26 21:02:51.695 2012 (UTC - 4:00)
System Uptime: 0 days 2:27:43.303
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`07eb3028 00000000`be800000 00000000`00000015
BiosVersion = P1.30
BiosReleaseDate = 09/13/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032612-39374-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Mon Mar 26 18:35:15.694 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:07.302
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`07cc18f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032612-39281-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Mon Mar 26 16:10:05.616 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:07.160
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`07ccc8f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032512-41480-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sun Mar 25 18:29:48.340 2012 (UTC - 4:00)
System Uptime: 0 days 0:02:46.761
*** WARNING: Unable to verify timestamp for LGVirHid.sys
*** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )
BUGCHECK_STR:  0xc9_220
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc9_220_HIDCLASS!HidpMajorHandler+0
Bugcheck code 000000C9
Arguments 00000000`00000220 fffff880`06e3b710 fffff980`2721edc0 fffffa80`09fe3450
BiosVersion = P1.50
BiosReleaseDate = 11/17/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032512-62275-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sun Mar 25 18:26:19.756 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:33.177
*** WARNING: Unable to verify timestamp for LGVirHid.sys
*** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )
BUGCHECK_STR:  0xc9_220
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc9_220_HIDCLASS!HidpMajorHandler+0
Bugcheck code 000000C9
Arguments 00000000`00000220 fffff880`0582d710 fffff980`2b50cdc0 fffffa80`07f1e8a0
BiosVersion = P1.50
BiosReleaseDate = 11/17/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032512-61729-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sun Mar 25 18:20:21.935 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:31.494
*** WARNING: Unable to verify timestamp for LGVirHid.sys
*** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )
BUGCHECK_STR:  0xc9_220
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc9_220_HIDCLASS!HidpMajorHandler+0
Bugcheck code 000000C9
Arguments 00000000`00000220 fffff880`05a2d710 fffff980`2a900dc0 fffffa80`0854a650
BiosVersion = P1.50
BiosReleaseDate = 11/17/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032512-63804-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sun Mar 25 18:09:59.957 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:03.362
*** WARNING: Unable to verify timestamp for LGVirHid.sys
*** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )
BUGCHECK_STR:  0xc9_220
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc9_220_HIDCLASS!HidpMajorHandler+0
Bugcheck code 000000C9
Arguments 00000000`00000220 fffff880`059de710 fffff980`2792edc0 fffffa80`0ac4b340
BiosVersion = P1.50
BiosReleaseDate = 11/17/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032512-43789-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sun Mar 25 17:17:43.038 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:07.676
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`08b226b8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032412-39717-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Mar 24 21:07:45.804 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:07.442
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`08b02038 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032412-38423-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Mar 24 21:04:22.991 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:07.645
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`08acf7a8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

TsMini · 28 Mar 2012

Here is some fun information.

Just completed another full installation. Same BSoD before even installing ANY drivers. Was at an ungodly small resolution without any network connection!
Installed to the Seagate 500g good old hd.

Processor bad?

usasma · 28 Mar 2012

Actually, a BSOD is more likely without updated drivers and without Windows Updates

If IBT stands for Intel Burnin test, then it's not likely that the processor is to blame.

Start with these free hardware diagnostics (the first 3 are bootable): Hardware Diags
Then try this stripdown procedure to help identify problem hardware: Hardware Troubleshooting Via System Stripdown

TsMini · 28 Mar 2012

Yeah that is IBT, sorry.

Will try those diagnostics and see what turns up!

Thanks