Topic Title: System Crash
Topic Summary: WHEA error
Created On: 12/08/2012 07:53 AM
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
View similar topics View similar topics
View topic in raw text format. Print this topic.
 12/08/2012 07:53 AM
User is offline View Users Profile Print this message

Author Icon

Posts: 1
Joined: 12/08/2012

Hi i am running the below system, most games run ok, but i have now hit a brick wall with Call of Duty Black Ops II, and that is when i run the game, My system Freezes and then resets and upon recovery says ot has recovered from a serious hardware error, the Whoscarshed report, says it is a WHEA error that crashed the system, and everyone one i have asked has said it is a Graphics card problem that causes the particular error that is reported.


Help Please....


Asrock N68_VS3 FX board

Amd FX 4100 Cpu (no Overclocking)

8 GB Corsair Vengence DDR3 PC3-10700H (667Mhz) (SPD-XMP)

Amd HD6850 PCi-E usin DVI to VGA monitor convertor

Two Internal Hdd 200gb, 500gb

1 external Hdd USb 1TB


OS Windows 7 64bit with SP1


Board Temp 33c

Cpu temp 35c

Gfx temp 37c, fan spd at 21% Gpu Clock at 775, Mem clock at 1000


Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 07/12/2012 16:49:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120712-43820-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B094C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80079AB8F8, 0x0, 0x0)
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.

92918 users are registered to the AMD Support and Game forum.
There are currently 0 users logged in.

FuseTalk Hosting Executive Plan v3.2 - © 1999-2015 FuseTalk Inc. All rights reserved.