Jump to content

BSOD Help

Go to solution Solved by ionbasa,

So I just took a look at the dump files and can verify it is the CPU causing the crash. Probably due to your voltage and clock speed combination.

For reference:

 

Of note: Utilities like the one you posted a screenshot of won't display everything the Windows Debugger is able to display. In specific, the BUCKET_ID, Stack Text, and the full Bug-check String. 

 

Since the "GenuineIntel" module and image is being referenced, the BSODs are likely being caused by an unstable overclock. Either bump down your clock speed or bump up the CPU voltage (or set a more aggressive Load Line Calibration in your BIOS/UEFI).

Windows 8 Kernel Version 9600 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17668.amd64fre.winblue_r8.150127-1500Machine Name:Kernel base = 0xfffff802`b080c000 PsLoadedModuleList = 0xfffff802`b0ae5250Debug session time: Sun Mar 15 01:15:20.302 2015 (UTC - 4:00)System Uptime: 0 days 1:29:04.909********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe00158f2a028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  StarCitizen.exCURRENT_IRQL:  fSTACK_TEXT:  ffffd001`f899acf8 fffff802`b0fd7213 : 00000000`00000124 00000000`00000000 ffffe001`58f2a028 00000000`bf800000 : nt!KeBugCheckExffffd001`f899ad00 fffff802`b09d25a9 : 00000000`00000001 ffffe001`552aebc0 ffffe001`552aebc0 ffffe001`58f2a028 : hal!HalBugCheckSystem+0xcfffffd001`f899ad40 fffff802`b0fd76a0 : 00000000`00000728 00000000`00000002 ffffd001`f899b130 00000000`00000000 : nt!WheaReportHwError+0x22dffffd001`f899ada0 fffff802`b0fd7a0d : ffffe001`00000010 ffffe001`552aebc0 ffffd001`f899af48 ffffe001`552aebc0 : hal!HalpMcaReportError+0x50ffffd001`f899aef0 fffff802`b0fd78f8 : ffffe001`552ae810 00000000`00000001 00000000`00000002 00000000`00000000 : hal!HalpMceHandlerCore+0xe1ffffd001`f899af40 fffff802`b0fd7b42 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4ffffd001`f899af80 fffff802`b0fd7ccf : ffffe001`552ae810 ffffd001`f899b1b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xceffffd001`f899afb0 fffff802`b09674bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40ffffd001`f899afe0 fffff802`b0967271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bffffd001`f899b120 fffff802`b08be10e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171ffffd000`25ead960 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiTryUnwaitThread+0x13eSTACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17668.amd64fre.winblue_r8.150127-1500Machine Name:Kernel base = 0xfffff800`27076000 PsLoadedModuleList = 0xfffff800`2734f250Debug session time: Sat Mar 14 23:45:30.819 2015 (UTC - 4:00)System Uptime: 0 days 1:02:52.424********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe001b392e028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  Borderlands2.eCURRENT_IRQL:  fSTACK_TEXT:  fffff800`2911ca38 fffff800`2703d213 : 00000000`00000124 00000000`00000000 ffffe001`b392e028 00000000`bf800000 : nt!KeBugCheckExfffff800`2911ca40 fffff800`2723c5a9 : 00000000`00000001 ffffe001`b01e1690 ffffe001`b01e1690 ffffe001`b392e028 : hal!HalBugCheckSystem+0xcffffff800`2911ca80 fffff800`2703d6a0 : 00000000`00000728 00000000`00000000 fffff800`2911ce70 00000000`00000000 : nt!WheaReportHwError+0x22dfffff800`2911cae0 fffff800`2703da0d : ffffe001`00000010 ffffe001`b01e1690 fffff800`2911cc88 ffffe001`b01e1690 : hal!HalpMcaReportError+0x50fffff800`2911cc30 fffff800`2703d8f8 : ffffe001`afcae6b0 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe1fffff800`2911cc80 fffff800`2703db42 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4fffff800`2911ccc0 fffff800`2703dccf : ffffe001`afcae6b0 fffff800`2911cef0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xcefffff800`2911ccf0 fffff800`271d14bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40fffff800`2911cd20 fffff800`271d1271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bfffff800`2911ce60 fffff800`270bfa03 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171ffffd000`2bdf9730 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiUpdateWsle+0x463STACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17668.amd64fre.winblue_r8.150127-1500Machine Name:Kernel base = 0xfffff800`7e682000 PsLoadedModuleList = 0xfffff800`7e95b250Debug session time: Sat Mar 14 22:41:56.731 2015 (UTC - 4:00)System Uptime: 0 days 2:19:57.338********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe0011a732028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  GTAIV.exeCURRENT_IRQL:  fSTACK_TEXT:  ffffd001`16dd7cf8 fffff800`7e649213 : 00000000`00000124 00000000`00000000 ffffe001`1a732028 00000000`bf800000 : nt!KeBugCheckExffffd001`16dd7d00 fffff800`7e8485a9 : 00000000`00000001 ffffe001`16aadbc0 ffffe001`16aadbc0 ffffe001`1a732028 : hal!HalBugCheckSystem+0xcfffffd001`16dd7d40 fffff800`7e6496a0 : 00000000`00000728 00000000`00000002 ffffd001`16dd8130 00000000`00000000 : nt!WheaReportHwError+0x22dffffd001`16dd7da0 fffff800`7e649a0d : ffffe001`00000010 ffffe001`16aadbc0 ffffd001`16dd7f48 ffffe001`16aadbc0 : hal!HalpMcaReportError+0x50ffffd001`16dd7ef0 fffff800`7e6498f8 : ffffe001`16aad810 00000000`00000001 00000000`00000002 00000000`00000000 : hal!HalpMceHandlerCore+0xe1ffffd001`16dd7f40 fffff800`7e649b42 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4ffffd001`16dd7f80 fffff800`7e649ccf : ffffe001`16aad810 ffffd001`16dd81b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xceffffd001`16dd7fb0 fffff800`7e7dd4bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40ffffd001`16dd7fe0 fffff800`7e7dd271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bffffd001`16dd8120 fffff800`7e729bca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171ffffd000`281c6990 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeReleaseMutant+0x112STACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17668.amd64fre.winblue_r8.150127-1500Machine Name:Kernel base = 0xfffff802`ff20e000 PsLoadedModuleList = 0xfffff802`ff4e7250Debug session time: Sat Mar 14 19:37:03.992 2015 (UTC - 4:00)System Uptime: 0 days 20:24:01.598********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe0017172e028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  GTAIV.exeCURRENT_IRQL:  fSTACK_TEXT:  ffffd000`20381cf8 fffff802`ff9d9213 : 00000000`00000124 00000000`00000000 ffffe001`7172e028 00000000`bf800000 : nt!KeBugCheckExffffd000`20381d00 fffff802`ff3d45a9 : 00000000`00000001 ffffe001`6daaebc0 ffffe001`6daaebc0 ffffe001`7172e028 : hal!HalBugCheckSystem+0xcfffffd000`20381d40 fffff802`ff9d96a0 : 00000000`00000728 00000000`00000002 ffffd000`20382130 00000000`00000000 : nt!WheaReportHwError+0x22dffffd000`20381da0 fffff802`ff9d9a0d : ffffe001`00000010 ffffe001`6daaebc0 ffffd000`20381f48 ffffe001`6daaebc0 : hal!HalpMcaReportError+0x50ffffd000`20381ef0 fffff802`ff9d98f8 : ffffe001`6daae810 00000000`00000001 00000000`00000002 00000000`00000000 : hal!HalpMceHandlerCore+0xe1ffffd000`20381f40 fffff802`ff9d9b42 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4ffffd000`20381f80 fffff802`ff9d9ccf : ffffe001`6daae810 ffffd000`203821b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xceffffd000`20381fb0 fffff802`ff3694bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40ffffd000`20381fe0 fffff802`ff369271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bffffd000`20382120 fffff802`ff2aa114 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171ffffd000`21992660 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeReleaseInStackQueuedSpinLock+0x34STACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 

Been getting a lot of BSOD while gaming.

 

This is what I get.

 

RqV3UZr.png

 

iqYX8EZ.png

 

 

My CPU temps look good while gaming, around 60c. It's an i5-4690k.

 

I just now started getting these BSODs yesterday.

 

Mobo: Z97 MSI Gaming 7 / CPU: i5-4690k@4.5GHz 1.23v / GPU: EVGA GTX 1070 / RAM: 8GB DDR3 1600MHz@CL9 1.5v / PSU: Corsair CX500M / Case: NZXT 410 / Monitor: 1080p IPS Acer R240HY bidx

Link to comment
https://linustechtips.com/topic/328419-bsod-help/
Share on other sites

Link to post
Share on other sites

Post/Attach the dump files. 

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
https://linustechtips.com/topic/328419-bsod-help/#findComment-4458601
Share on other sites

Link to post
Share on other sites

overclocking? id so, you need more VCore voltage.

are you running GeoExperience or updated your GPU driver, lately?

Yeah, it's overclocked to 4.5Ghz @1.2v

It's been running stable for a few weeks until now it seems.

Post/Attach the dump files.

It's kinda big. :blink:

Mobo: Z97 MSI Gaming 7 / CPU: i5-4690k@4.5GHz 1.23v / GPU: EVGA GTX 1070 / RAM: 8GB DDR3 1600MHz@CL9 1.5v / PSU: Corsair CX500M / Case: NZXT 410 / Monitor: 1080p IPS Acer R240HY bidx

Link to comment
https://linustechtips.com/topic/328419-bsod-help/#findComment-4458654
Share on other sites

Link to post
Share on other sites

bump it up to 1.250v and retest as something has changed and now it is unstable.

I will try that. Sucks that I have to pump in more voltage now. Maybe some degradation happened or fluke.

Mobo: Z97 MSI Gaming 7 / CPU: i5-4690k@4.5GHz 1.23v / GPU: EVGA GTX 1070 / RAM: 8GB DDR3 1600MHz@CL9 1.5v / PSU: Corsair CX500M / Case: NZXT 410 / Monitor: 1080p IPS Acer R240HY bidx

Link to comment
https://linustechtips.com/topic/328419-bsod-help/#findComment-4458689
Share on other sites

Link to post
Share on other sites

Yeah, it's overclocked to 4.5Ghz @1.2v

It's been running stable for a few weeks until now it seems.

It's kinda big. :blink:

It doesn't need to be all of the dump files, just the most recent 5 or so. They should each be around a few megabytes. Share it with dropbox, mega, or similar.

 

EDIT:

 

I also wouldn't just blindly bump up voltages without doing a bit of diagnostics and reading what the dump files say.

Since the 0x124 stop code is a generic hardware fault. Has any aspect of your system configuration changed within the past month or so?

Was your overclock stable when you first tested it at that voltage? How long have you been running at that voltage and clock speed?

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
https://linustechtips.com/topic/328419-bsod-help/#findComment-4458738
Share on other sites

Link to post
Share on other sites

It doesn't need to be all of the dump files, just the most recent 5 or so. They should each be around a few megabytes. Share it with dropbox, mega, or similar.

 

EDIT:

 

I also wouldn't just blindly bump up voltages without doing a bit of diagnostics and reading what the dump files say.

Since the 0x124 stop code is a generic hardware fault. Has any aspect of your system configuration changed within the past month or so?

Was your overclock stable when you first tested it at that voltage? How long have you been running at that voltage and clock speed?

It's been running at 1.2v 4.5Ghz for a few weeks now without any crashes until yesterday.

 

I bumped it to 1.22 and the constant BSoD has stopped but I'll look into the dumb files when I get around to it.

 

Edit:

 

My last minidump

 

ZNim5Gc.png

 

http://www.mediafire.com/download/d4uab28tajd0j7y/031415-51421-01.zip

Mobo: Z97 MSI Gaming 7 / CPU: i5-4690k@4.5GHz 1.23v / GPU: EVGA GTX 1070 / RAM: 8GB DDR3 1600MHz@CL9 1.5v / PSU: Corsair CX500M / Case: NZXT 410 / Monitor: 1080p IPS Acer R240HY bidx

Link to comment
https://linustechtips.com/topic/328419-bsod-help/#findComment-4459002
Share on other sites

Link to post
Share on other sites

It's been running at 1.2v 4.5Ghz for a few weeks now without any crashes until yesterday.

 

I bumped it to 1.22 and the constant BSoD has stopped but I'll look into the dumb files when I get around to it.

No real need to. x0124 is voltage related with the OC. 1.2v for 4.5 is fairly low, most chips will need at least 1.25-1.275v. I highly doubt there was any degradation, you may have just not been thorough enough in benching/testing to expose the instability. To get voltage degradation you would need to be blasting it with 1.35-1.4+v for an extended period of time.

 

LanSyndicate Build | i5-6600k | ASRock OC Formula | G.Skill 3600MHz | Samsung 850 Evo | MSI R9-290X 8GB Alphacool Block | Enthoo Pro M | XTR Pro 750w | Custom Loop |

Daily | 5960X | X99 Sabertooth | G.Skill 3000MHz | 750 NVMe | 850 Evo | x2 WD Se 2TB | x2 Seagate 3TB | Sapphire R9-290X 8GB | Enthoo Primo | EVGA 1000G2 | Custom Loop |

Game Box | 4690K | Z97i-Plus | G.Skill 2400MHz | x2 840 Evo | GTX 970 shorty | Corsair 250D modded with H105 | EVGA 650w B2 |

 

Link to comment
https://linustechtips.com/topic/328419-bsod-help/#findComment-4459032
Share on other sites

Link to post
Share on other sites

So I just took a look at the dump files and can verify it is the CPU causing the crash. Probably due to your voltage and clock speed combination.

For reference:

 

Of note: Utilities like the one you posted a screenshot of won't display everything the Windows Debugger is able to display. In specific, the BUCKET_ID, Stack Text, and the full Bug-check String. 

 

Since the "GenuineIntel" module and image is being referenced, the BSODs are likely being caused by an unstable overclock. Either bump down your clock speed or bump up the CPU voltage (or set a more aggressive Load Line Calibration in your BIOS/UEFI).

Windows 8 Kernel Version 9600 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17668.amd64fre.winblue_r8.150127-1500Machine Name:Kernel base = 0xfffff802`b080c000 PsLoadedModuleList = 0xfffff802`b0ae5250Debug session time: Sun Mar 15 01:15:20.302 2015 (UTC - 4:00)System Uptime: 0 days 1:29:04.909********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe00158f2a028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  StarCitizen.exCURRENT_IRQL:  fSTACK_TEXT:  ffffd001`f899acf8 fffff802`b0fd7213 : 00000000`00000124 00000000`00000000 ffffe001`58f2a028 00000000`bf800000 : nt!KeBugCheckExffffd001`f899ad00 fffff802`b09d25a9 : 00000000`00000001 ffffe001`552aebc0 ffffe001`552aebc0 ffffe001`58f2a028 : hal!HalBugCheckSystem+0xcfffffd001`f899ad40 fffff802`b0fd76a0 : 00000000`00000728 00000000`00000002 ffffd001`f899b130 00000000`00000000 : nt!WheaReportHwError+0x22dffffd001`f899ada0 fffff802`b0fd7a0d : ffffe001`00000010 ffffe001`552aebc0 ffffd001`f899af48 ffffe001`552aebc0 : hal!HalpMcaReportError+0x50ffffd001`f899aef0 fffff802`b0fd78f8 : ffffe001`552ae810 00000000`00000001 00000000`00000002 00000000`00000000 : hal!HalpMceHandlerCore+0xe1ffffd001`f899af40 fffff802`b0fd7b42 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4ffffd001`f899af80 fffff802`b0fd7ccf : ffffe001`552ae810 ffffd001`f899b1b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xceffffd001`f899afb0 fffff802`b09674bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40ffffd001`f899afe0 fffff802`b0967271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bffffd001`f899b120 fffff802`b08be10e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171ffffd000`25ead960 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiTryUnwaitThread+0x13eSTACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17668.amd64fre.winblue_r8.150127-1500Machine Name:Kernel base = 0xfffff800`27076000 PsLoadedModuleList = 0xfffff800`2734f250Debug session time: Sat Mar 14 23:45:30.819 2015 (UTC - 4:00)System Uptime: 0 days 1:02:52.424********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe001b392e028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  Borderlands2.eCURRENT_IRQL:  fSTACK_TEXT:  fffff800`2911ca38 fffff800`2703d213 : 00000000`00000124 00000000`00000000 ffffe001`b392e028 00000000`bf800000 : nt!KeBugCheckExfffff800`2911ca40 fffff800`2723c5a9 : 00000000`00000001 ffffe001`b01e1690 ffffe001`b01e1690 ffffe001`b392e028 : hal!HalBugCheckSystem+0xcffffff800`2911ca80 fffff800`2703d6a0 : 00000000`00000728 00000000`00000000 fffff800`2911ce70 00000000`00000000 : nt!WheaReportHwError+0x22dfffff800`2911cae0 fffff800`2703da0d : ffffe001`00000010 ffffe001`b01e1690 fffff800`2911cc88 ffffe001`b01e1690 : hal!HalpMcaReportError+0x50fffff800`2911cc30 fffff800`2703d8f8 : ffffe001`afcae6b0 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe1fffff800`2911cc80 fffff800`2703db42 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4fffff800`2911ccc0 fffff800`2703dccf : ffffe001`afcae6b0 fffff800`2911cef0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xcefffff800`2911ccf0 fffff800`271d14bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40fffff800`2911cd20 fffff800`271d1271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bfffff800`2911ce60 fffff800`270bfa03 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171ffffd000`2bdf9730 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiUpdateWsle+0x463STACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17668.amd64fre.winblue_r8.150127-1500Machine Name:Kernel base = 0xfffff800`7e682000 PsLoadedModuleList = 0xfffff800`7e95b250Debug session time: Sat Mar 14 22:41:56.731 2015 (UTC - 4:00)System Uptime: 0 days 2:19:57.338********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe0011a732028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  GTAIV.exeCURRENT_IRQL:  fSTACK_TEXT:  ffffd001`16dd7cf8 fffff800`7e649213 : 00000000`00000124 00000000`00000000 ffffe001`1a732028 00000000`bf800000 : nt!KeBugCheckExffffd001`16dd7d00 fffff800`7e8485a9 : 00000000`00000001 ffffe001`16aadbc0 ffffe001`16aadbc0 ffffe001`1a732028 : hal!HalBugCheckSystem+0xcfffffd001`16dd7d40 fffff800`7e6496a0 : 00000000`00000728 00000000`00000002 ffffd001`16dd8130 00000000`00000000 : nt!WheaReportHwError+0x22dffffd001`16dd7da0 fffff800`7e649a0d : ffffe001`00000010 ffffe001`16aadbc0 ffffd001`16dd7f48 ffffe001`16aadbc0 : hal!HalpMcaReportError+0x50ffffd001`16dd7ef0 fffff800`7e6498f8 : ffffe001`16aad810 00000000`00000001 00000000`00000002 00000000`00000000 : hal!HalpMceHandlerCore+0xe1ffffd001`16dd7f40 fffff800`7e649b42 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4ffffd001`16dd7f80 fffff800`7e649ccf : ffffe001`16aad810 ffffd001`16dd81b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xceffffd001`16dd7fb0 fffff800`7e7dd4bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40ffffd001`16dd7fe0 fffff800`7e7dd271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bffffd001`16dd8120 fffff800`7e729bca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171ffffd000`281c6990 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeReleaseMutant+0x112STACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17668.amd64fre.winblue_r8.150127-1500Machine Name:Kernel base = 0xfffff802`ff20e000 PsLoadedModuleList = 0xfffff802`ff4e7250Debug session time: Sat Mar 14 19:37:03.992 2015 (UTC - 4:00)System Uptime: 0 days 20:24:01.598********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe0017172e028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  GTAIV.exeCURRENT_IRQL:  fSTACK_TEXT:  ffffd000`20381cf8 fffff802`ff9d9213 : 00000000`00000124 00000000`00000000 ffffe001`7172e028 00000000`bf800000 : nt!KeBugCheckExffffd000`20381d00 fffff802`ff3d45a9 : 00000000`00000001 ffffe001`6daaebc0 ffffe001`6daaebc0 ffffe001`7172e028 : hal!HalBugCheckSystem+0xcfffffd000`20381d40 fffff802`ff9d96a0 : 00000000`00000728 00000000`00000002 ffffd000`20382130 00000000`00000000 : nt!WheaReportHwError+0x22dffffd000`20381da0 fffff802`ff9d9a0d : ffffe001`00000010 ffffe001`6daaebc0 ffffd000`20381f48 ffffe001`6daaebc0 : hal!HalpMcaReportError+0x50ffffd000`20381ef0 fffff802`ff9d98f8 : ffffe001`6daae810 00000000`00000001 00000000`00000002 00000000`00000000 : hal!HalpMceHandlerCore+0xe1ffffd000`20381f40 fffff802`ff9d9b42 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4ffffd000`20381f80 fffff802`ff9d9ccf : ffffe001`6daae810 ffffd000`203821b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xceffffd000`20381fb0 fffff802`ff3694bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40ffffd000`20381fe0 fffff802`ff369271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bffffd000`20382120 fffff802`ff2aa114 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171ffffd000`21992660 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeReleaseInStackQueuedSpinLock+0x34STACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
https://linustechtips.com/topic/328419-bsod-help/#findComment-4459147
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×