random reboot/no blue screen, loud buzzing sound when freeze prior to reboot

  Gaza336 19:52 24 Dec 2014
Locked

So I recently upgraded my psu, GPU, and cpu on my rig, triple checked all compatibility for this and ensured that my motherboards bios was upgraded as I hadn't upgraded that. Keep receiving random restarts (at the oddest moments see below).

Kernel power error/reboots Probably caused my AuthenticAMD (windows debugger)

Weird parts are, I can play assassins creed unity at the ultra graphics setting with no delay no error and it will not crash out at all. However on the desktop it will crash randomly (no specific tasks) and it will always crash out when playing mount and blade Viking conquest within 10 mins or less.

Specs are since upgrade (will be more detailed later) Motherboard - M5A78L-M/usb3 (upgraded bios to version 2001) Cpu - amd fx 8350 GPU - asus radeon r9 290 dc2oc Psu - Evga 600b 80+ (also troubleshot with corsair psu 650w) Cpu cooler - Evo hyper 212 with just one fan and an exhaust for more cool and hot hair relief on chasis. Ram 16gb ddr3

Win 7 64x home basic

DVD/cd rewritable standard sata 1tb standard sata hdd

Like I've said I've tried the old hardware one by one same error repeating.

Troubleshooting - Tested each hardware with memtest86, furmark, cpu stability, occt etc. Works fine. Only crashed on cpu stability once. Tested with different psu/cpu/GPU same again. Heat is fine GPU ranges from 50-68 Celsius (depending on game) and cpu idle is 28-30 and 40-50 during games (Celsius). GPU idle is 40 normally. Used with speed fan and afterburner.

I've removed amd catalyst control and installed drivers only as sometimes win7 has an issue no change. I do not understand nor do I overclock however my asus motherboard does have it auto built into the bios (not sure if I can change?) Tried using afterburner to increase 25mv+ as a previous solution, increased run time. Corsair psu 650w has increased run time.

Sorry for the delay guys, actually thought I had resolved this issue, was RMA'd a new PSU at 750W from Evga which allowed me to play the game that caused an error (M&B Viking conquest). However, after the initial installation of the AMD Catalyst drivers it blue screened during the installation (who crashed info as below). This was a different error code from previous attempts which made me believe the original error was resolved and this was new. It then decided to reboot (no blue screen) twice randomly after resulting in the same error codes and definitions.

Whocrashed error report - [spoiler]

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 24/12/2014 16:54:31 GMT your computer crashed crash dump file: C:\Windows\Minidump\122414-28392-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x4B18CC) Bugcheck code: 0x124 (0x0, 0xFFFFFA8008C938F8, 0x0, 0x0) Error: WHEAUNCORRECTABLEERROR file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 24/12/2014 16:47:08 GMT your computer crashed crash dump file: C:\Windows\Minidump\122414-30856-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x4B18CC) Bugcheck code: 0x124 (0x0, 0xFFFFFA800A9DB8F8, 0x0, 0x0) Error: WHEAUNCORRECTABLEERROR file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 24/12/2014 16:15:00 GMT your computer crashed crash dump file: C:\Windows\Minidump\122414-58781-01.dmp This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x5D000) Bugcheck code: 0x116 (0xFFFFFA800BAC94E0, 0xFFFFF88006A32D88, 0x0, 0x2) Error: VIDEOTDRERROR file path: C:\Windows\system32\drivers\dxgkrnl.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics Kernel Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. Google query: Microsoft Corporation VIDEOTDRERROR

On Wed 24/12/2014 16:15:00 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!TdrResetFromTimeout+0x214) Bugcheck code: 0x116 (0xFFFFFA800BAC94E0, 0xFFFFF88006A32D88, 0x0, 0x2) Error: VIDEOTDRERROR file path: C:\Windows\system32\drivers\dxgkrnl.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics Kernel Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. Google query: Microsoft Corporation VIDEOTDRERROR

On Tue 23/12/2014 21:00:01 GMT your computer crashed crash dump file: C:\Windows\Minidump\122314-26457-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x4B18CC) Bugcheck code: 0x124 (0x0, 0xFFFFFA8008D978F8, 0x0, 0x0) Error: WHEAUNCORRECTABLEERROR file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 23/12/2014 20:30:12 GMT your computer crashed crash dump file: C:\Windows\Minidump\122314-37221-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x4B18CC) Bugcheck code: 0x124 (0x0, 0xFFFFFA8008E068F8, 0x0, 0x0) Error: WHEAUNCORRECTABLEERROR file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 23/12/2014 19:01:03 GMT your computer crashed crash dump file: C:\Windows\Minidump\122314-30435-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x4B18CC) Bugcheck code: 0x124 (0x0, 0xFFFFFA8008D6F038, 0x0, 0x0) Error: WHEAUNCORRECTABLEERROR file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 23/12/2014 18:56:45 GMT your computer crashed crash dump file: C:\Windows\Minidump\122314-30076-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x4B18CC) Bugcheck code: 0x124 (0x0, 0xFFFFFA8008DCC808, 0x0, 0x0) Error: WHEAUNCORRECTABLEERROR file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 23/12/2014 16:09:48 GMT your computer crashed crash dump file: C:\Windows\Minidump\122314-42104-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x4B18CC) Bugcheck code: 0x124 (0x0, 0xFFFFFA8008F181B8, 0x0, 0x0) Error: WHEAUNCORRECTABLEERROR file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 23/12/2014 15:30:00 GMT your computer crashed crash dump file: C:\Windows\Minidump\122314-28797-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x4B18CC) Bugcheck code: 0x124 (0x0, 0xFFFFFA8008C50538, 0x0, 0x0) Error: WHEAUNCORRECTABLEERROR file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. [/spoiler]

Windows Debugger report - [spoiler]************************* * * * Bugcheck Analysis * * *


WHEAUNCORRECTABLEERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEAERRORRECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: fffffa8008c938f8, Address of the WHEAERRORRECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:

BUGCHECKSTR: 0x124AuthenticAMD

CUSTOMERCRASHCOUNT: 1

DEFAULTBUCKETID: WIN7DRIVERFAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:
fffff8800218d5b0 fffff80002313c59 : fffffa8008c938d0 fffffa8006be3680 0000000000000007 0000000000000000 : nt!WheapCreateLiveTriageDump+0x6c fffff8800218dad0 fffff800021f3fa7 : fffffa8008c938d0 fffff8000226e2b8 fffffa8006be3680 0000000000000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49 fffff8800218db00 fffff8000215b5c5 : fffff800022cfac0 0000000000000001 fffffa8008f82960 fffffa8006be3680 : nt!WheapProcessWorkQueueItem+0x57 fffff8800218db40 fffff800020db021 : fffff88000e70e00 fffff8000215b5a0 fffffa8006be3600 0000000000000000 : nt!WheapWorkQueueWorkerRoutine+0x25 fffff8800218db70 fffff8000236d32e : 0000000000000000 fffffa8006be3680 0000000000000080 fffffa8006bd6040 : nt!ExpWorkerThread+0x111 fffff8800218dc00 fffff800020c2666 : fffff880020a5180 fffffa8006be3680 fffff880020b00c0 0000000000000000 : nt!PspSystemThreadStartup+0x5a fffff8800218dc40 0000000000000000 : fffff8800218e000 fffff88002188000 fffff88002997400 0000000000000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD

DEBUGFLRIMAGE_TIMESTAMP: 0

IMAGE_VERSION:

FAILUREBUCKETID: X640x124AuthenticAMDPROCESSORBUS_PRV

BUCKETID: X640x124AuthenticAMDPROCESSORBUSPRV

ANALYSIS_SOURCE: KM

FAILUREIDHASHSTRING: km:x640x124authenticamdprocessorbusprv

FAILUREIDHASH: {78c2f422-5335-4ef3-5cef-a28518da5023}

Followup: MachineOwner ---------[/spoiler]

Windows debugger from new error -

[spoiler]************************* * * * Bugcheck Analysis * * *


WHEAUNCORRECTABLEERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEAERRORRECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: fffffa800a9db8f8, Address of the WHEAERRORRECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:

BUGCHECKSTR: 0x124AuthenticAMD

CUSTOMERCRASHCOUNT: 1

DEFAULTBUCKETID: WIN7DRIVERFAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:
fffff880033775b0 fffff80002ee0c59 : fffffa800a9db8d0 fffffa8006cafb60 fffffa8000000007 0000000000000000 : nt!WheapCreateLiveTriageDump+0x6c fffff88003377ad0 fffff80002dc0fa7 : fffffa800a9db8d0 fffff80002e3b2b8 fffffa8006cafb60 0000000000000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49 fffff88003377b00 fffff80002d285c5 : fffff80002e9cac0 0000000000000001 fffffa8009b26e60 fffffa8006cafb60 : nt!WheapProcessWorkQueueItem+0x57 fffff88003377b40 fffff80002ca8021 : fffff8800103de00 fffff80002d285a0 fffffa8006cafb00 0000000000000000 : nt!WheapWorkQueueWorkerRoutine+0x25 fffff88003377b70 fffff80002f3a32e : 0000000000000000 fffffa8006cafb60 0000000000000080 fffffa8006baf740 : nt!ExpWorkerThread+0x111 fffff88003377c00 fffff80002c8f666 : fffff88003189180 fffffa8006cafb60 fffff880031940c0 0000000000000000 : nt!PspSystemThreadStartup+0x5a fffff88003377c40 0000000000000000 : fffff88003378000 fffff88003372000 fffff8800412d400 0000000000000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD

DEBUGFLRIMAGE_TIMESTAMP: 0

IMAGE_VERSION:

FAILUREBUCKETID: X640x124AuthenticAMDPROCESSORBUS_PRV

BUCKETID: X640x124AuthenticAMDPROCESSORBUSPRV

ANALYSIS_SOURCE: KM

FAILUREIDHASHSTRING: km:x640x124authenticamdprocessorbusprv

FAILUREIDHASH: {78c2f422-5335-4ef3-5cef-a28518da5023}

Followup: MachineOwner

[/spoiler]

Currently in safe mode, but for todays crashes the first two were different from previously and now have resulted in the same continuous error reboots.

  Fruit Bat /\0/\ 11:55 25 Dec 2014

ntoskrnl.exe usually = failing hard drive or memory problems.

This thread is now locked and can not be replied to.

Elsewhere on IDG sites

OnePlus 5 review

Alice Saey's mesmerising animation for Dutch singer Mark Lotterman

iPad Pro 10.5in (2017) review

Comment booster votre iPhone ?