BSOD errors - WhoCrashed info

[Michael Rachuba]

On Wed 2/26/2014 4:26:45 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022514-20295-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007AA7038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
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 2/26/2014 3:31:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022514-16114-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CD3EBE, 0xFFFFF8800278EC30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 2/26/2014 3:31:35 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngRestoreFloatingPointState+0xD9D5)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CD3EBE, 0xFFFFF8800278EC30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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.



On Sat 2/22/2014 8:27:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022214-28095-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6B7E0)
Bugcheck code: 0x1000007E (0xFFFFFFFF80000003, 0xFFFFF80002CB67E0, 0xFFFFF88005F2D5B8, 0xFFFFF88005F2CE10)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 2/22/2014 5:20:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022214-16723-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x171A4EEC0B, 0x2, 0x1, 0xFFFFF80002CCA420)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 2/22/2014 5:24:26 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022214-15990-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007A78738, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
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 Fri 2/21/2014 9:41:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022114-15600-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007A57038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
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 Sat 2/15/2014 8:23:14 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021514-20638-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007AAD558, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
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 Thu 2/13/2014 5:32:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021314-21512-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007AC58F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
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 Fri 1/3/2014 4:02:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010214-12932-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B2AEC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007A7D038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
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.
-----------------

THIS Only happens when I am in CS:GO and Left For Dead 2... I don't play anything else.
So I am going to assume its an issue with the video card, mobo or the CPU.
Before the blue screen comes up, it goes to a black screen with repeating sounds from the game I am playing, then it goes to no sound with black or dark green or mustard yellow screen then Reset.

 

[johnbl]

WHEA_UNCORRECTABLE_ERROR is a hardware error generated directly by the CPU and given to windows to attempt to bluescreen if it can.

generally it is caused by:
- overclocking
- incorrect voltages to CPU (causing cpu cache failures)
- fan stopped on CPU causing thermal shutdown.

best to update BIOS or reset it to defaults and reconfigure and confirm proper voltages.
confirm the CPU fan is not blocked and is spinning up.
if that fails, you would need to check your power supply or voltage regulators on you motherboard (if you can)

 

[Michael Rachuba]

WHEA_UNCORRECTABLE_ERROR is a hardware error generated directly by the CPU and given to windows to attempt to bluescreen if it can.

generally it is caused by:
- overclocking
- incorrect voltages to CPU (causing cpu cache failures)
- fan stopped on CPU causing thermal shutdown.

best to update BIOS or reset it to defaults and reconfigure and confirm proper voltages.
confirm the CPU fan is not blocked and is spinning up.
if that fails, you would need to check your power supply or voltage regulators on you motherboard (if you can)

I have a phenom x6 t1055 how would i find the correct voltages? or my mobo ASROCK 880gm-le fx

The fans working, it wasnt about a week ago tho, fixed it but still get the BSOD. So top 3 reports should be the ones after I fixed the fan.

 

[johnbl]

- Best to update the BIOS to get new stock settings and get your system stable.
- you will have to google for your chip to find the voltage specs and recommended voltages while overclocking.
(voltage may depend on the actual motherboard)

WHEA_UNCORRECTABLE_ERROR most often will be incorrect voltages but can also indicated damage to the CPU.
(this can occur if the max voltage for the CPU is exceeded, but most of the time it is just a incorrect voltage applied)

you can look at the crash dump in the windows debugger
and use the !errrec command on the reported address of the WHEA data structure
this will tell you what error the CPU is reporting. for example it will might say checksum error on a certain memory bank location. If all of the bugchecks indicate the same cache memory bank error then your cpu cache would be damaged. if each dump indicates a different memory bank then it will be a incorrect voltage to the CPU, (or one of the cpu voltages being incorrect)

best to start with a BIOS update/reset and then run memtest86.exe to make sure the hardware is ok

 

[Michael Rachuba]

- Best to update the BIOS to get new stock settings and get your system stable.
- you will have to google for your chip to find the voltage specs and recommended voltages while overclocking.
(voltage may depend on the actual motherboard)

WHEA_UNCORRECTABLE_ERROR most often will be incorrect voltages but can also indicated damage to the CPU.
(this can occur if the max voltage for the CPU is exceeded, but most of the time it is just a incorrect voltage applied)

you can look at the crash dump in the windows debugger
and use the !errrec command on the reported address of the WHEA data structure
this will tell you what error the CPU is reporting. for example it will might say checksum error on a certain memory bank location. If all of the bugchecks indicate the same cache memory bank error then your cpu cache would be damaged. if each dump indicates a different memory bank then it will be a incorrect voltage to the CPU, (or one of the cpu voltages being incorrect)

best to start with a BIOS update/reset and then run memtest86.exe to make sure the hardware is ok

Ok, Ill reset the bios, check the volts for the CPU when I get back home from work.

Just a heads up i ran the prime95 software last night for about 6 hours and It didnt come back with any errors or blue screen. I checked the log file and it said they all passed. The temps were about at 140f and 60c, I was reading around here and it was saying that 62c was max for the chip.