Solved whea_uncorrectable_error bsod after hardware upgrade

Hi

First off, I'm a total noob so you might need to explain in step by step format when there is something you want me to try to solve this issue.

I recently upgraded my desktop by buying a new motherboard, cpu and a ram kit. After changing the hardware I booted up (without formating and reinstalling windows) and installed some of the software (drivers + CPU-Z and some other stuff) that came with the motherboard, and then i started getting bsods. First i used the "SET DEVMGR_SHOW_NONPRESENT_DEVICES=1" so i could see the drivers for the old hardware and i uninstalled that, but i still kept getting bsods, so i tried to run a windows memory diagnosis and it said that everything was fine. But i still kept getting bsods, so i tried "sfc /scannow" and got the message:

"[SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired"

and it didn't fix a thing. So i tried "Dism /Online /Cleanup-Image /RestoreHealth" and got the message:

"The restore operation completed successfully. The component store corruption was repaired. The operation completed successfully"

but the issue still remains unsolved and i still get bsods. This might just be a coincidence but it seems to only happen when i watch video on youtube or twitch (i almost always do that tho, so might have nothing to do with the issue).

I'm sorry if my grammar is terrible but English isn't my native language. Lastly pleas tell me what info you need and how i get it and ill try to do it as quick as possible. thanks in advance.

View attachment 63230

I started testing to see if i could recreate the bsod at will, first leaving the pc on, with nothing happening but some light web surfing over a period of 12-14h, and no bsod. I then loaded a 1080p youtube video and let it play for about 5h, sopped because of an add that wouldn't load while i was sleeping, no bsod. Then i tried showing a 1080p youtube video on full screen on both of my screens (dual monitor, same video but in different browser windows) and i then finally got a bsod, got bsod by doing this 3 more times, takes anywhere from 5 to 45 min for it to happen. So i can now force the bsod, but since I'm a noob i still have no idea of what is causing it..

I also ran "BlueScreenView" and this is the info and the dump file from the last bsod (witch i forced by playing 2x1080p youtube videos on both my screens):

==================================================
Dump File : 062915-18328-01.dmp
Crash Time : 29.06.2015 14:49:56
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : ffffe000`f91a1028
Parameter 3 : 00000000`b6000000
Parameter 4 : 00000000`00100153
Caused By Driver : hal.dll
Caused By Address : hal.dll+37213
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+150ca0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\062915-18328-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9600
Dump File Size : 280 688
Dump File Time : 29.06.2015 14:50:54
==================================================

View attachment 63287

I'm new to this, but I give it a shot.
As far as I understood your last dump file, your cpu was the cause of the crash.
A cpu stress test can be done at Hardware Diagnostics


But for better help its waiting for an expert.

axe0 said:

I'm new to this, but I give it a shot.
As far as I understood your last dump file, your cpu was the cause of the crash.
A cpu stress test can be done at Hardware Diagnostics

Code:

********************************************************************************                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


WHEA_UNCORRECTABLE_ERROR (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
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe000f91a1028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000100153, Low order 32-bits of the MCi_STATUS value.


Debugging Details:
------------------




BUGCHECK_STR:  0x124_AuthenticAMD


CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


PROCESS_NAME:  firefox.exe


CURRENT_IRQL:  f


ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre


STACK_TEXT:  
ffffd001`928c9e28 fffff803`f61d8213 : 00000000`00000124 00000000`00000000 ffffe000`f91a1028 00000000`b6000000 : nt!KeBugCheckEx
ffffd001`928c9e30 fffff803`f5bd2f2d : 00000000`00000001 ffffe000`f6eaef20 ffffe000`f6eaef20 ffffe000`f91a1028 : hal!HalBugCheckSystem+0xcf
ffffd001`928c9e70 fffff803`f61d86a0 : 00000000`00000728 00000000`00000003 ffffd001`928ca230 00000000`00000000 : nt!WheaReportHwError+0x22d
ffffd001`928c9ed0 fffff803`f61d8a0d : ffffe000`00000010 ffffe000`f6eaef20 ffffd001`928ca078 ffffe000`f6eaef20 : hal!HalpMcaReportError+0x50
ffffd001`928ca020 fffff803`f61d88f8 : ffffe000`f6eae7f0 00000000`00000001 00000000`00000003 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
ffffd001`928ca070 fffff803`f61d8cd8 : ffffe000`f6eae7f0 ffffd001`928ca2b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd001`928ca0b0 fffff803`f5b687bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x49
ffffd001`928ca0e0 fffff803`f5b68571 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffd001`928ca220 fffff803`f5b6102d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
ffffd001`a993b6e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext_PatchLdMxCsr+0xc0




STACK_COMMAND:  kb


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: AuthenticAMD


IMAGE_NAME:  AuthenticAMD


DEBUG_FLR_IMAGE_TIMESTAMP:  0


IMAGE_VERSION:  


FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE


BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_cache


FAILURE_ID_HASH:  {b533751b-676e-7546-bcdc-24e6c40d0064}

But for better help its waiting for an expert.

Click to expand...

Thanks, ill try the stress test now! posting results as soon as i get them!

At about 3min the test stopped it self and gave me these results (no bsod):

Stability test started at 2015-06-29 20:26:55 Calculation Test > Illegal sumeout
Calculation Test > Possible hardware failure
Calculation Test > Illegal sumeout
Calculation Test > Possible hardware failure
Calculation Test > Illegal sumeout
Calculation Test > Possible hardware failure
Calculation Test > Illegal sumeout
Calculation Test > Possible hardware failure
Stability test stopped at 2015-06-29 20:29:53

I ran it again (AMD-Overdrive) but only for 1 min this time, and it was fine..Don't know how much "stress" a cpu like mine is supposed to be able to handle? View attachment 63293

Know any other tests i should run? Or other things i should to to gather data that could be helpful?

ps: thank you axe0, for taking an interest and trying to help

I've checked all your dump files, 7 of them are possibly pointing to your cpu.
1 is possibly pointing to you antivirus driver.
The others I'm not sure, I've seen them before but don't know a solution.

The following information could be usefull for the analysts

axe0 said:

I've checked all your dump files, 7 of them are possibly pointing to your cpu.
1 is possibly pointing to you antivirus driver.
The others I'm not sure, I've seen them before but don't know a solution.

The following information could be usefull for the analysts

Code:

********************************************************************************                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000


Debugging Details:
------------------




DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED


CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


BUGCHECK_STR:  0x133


PROCESS_NAME:  svchost.exe


CURRENT_IRQL:  d


ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre


LAST_CONTROL_TRANSFER:  from fffff802ce9aab2c to fffff802ce96afa0


STACK_TEXT:  
ffffd001`a0dc6c98 fffff802`ce9aab2c : 00000000`00000133 00000000`00000001 00000000`00001e00 00000000`00000000 : nt!KeBugCheckEx
ffffd001`a0dc6ca0 fffff802`ce8caf85 : ffffe000`6e601d50 00000000`00000000 00000000`00000001 ffffe000`6e611fe8 : nt! ?? ::FNODOBFM::`string'+0x2f67c
ffffd001`a0dc6d30 fffff802`cefa87b5 : 00000000`00400a02 ffffd001`a2476830 fffff801`b1f381c0 ffffe000`00009201 : nt!KeClockInterruptNotify+0x95
ffffd001`a0dc6f40 fffff802`ce8e6363 : ffffd001`a0dc6f60 00000000`00000008 ffffd001`a0dc6f50 00000000`0000000c : hal!HalpTimerClockIpiRoutine+0x15
ffffd001`a0dc6f70 fffff802`ce96c42a : ffffe000`6bc00100 ffffe000`6d3b3cd8 00000000`00000001 ffffd001`be3df460 : nt!KiCallInterruptServiceRoutine+0xa3
ffffd001`a0dc6fb0 fffff802`ce96cd9b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd001`be3df1d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xfb




STACK_COMMAND:  kb


FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+2f67c
fffff802`ce9aab2c cc              int     3


SYMBOL_STACK_INDEX:  1


SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+2f67c


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: nt


IMAGE_NAME:  ntkrnlmp.exe


DEBUG_FLR_IMAGE_TIMESTAMP:  53388e13


IMAGE_VERSION:  6.3.9600.17085


BUCKET_ID_FUNC_OFFSET:  2f67c


FAILURE_BUCKET_ID:  0x133_ISR_nt!_??_::FNODOBFM::_string_


BUCKET_ID:  0x133_ISR_nt!_??_::FNODOBFM::_string_


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:0x133_isr_nt!_??_::fnodobfm::_string_


FAILURE_ID_HASH:  {89366ad1-5557-ac2b-d015-8f6ec2fdbf31}

Code:

********************************************************************************                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 00007ff85ef1b06a, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffffd0005d894cc0, Call type (0 - system call, 1 - worker routine)


Debugging Details:
------------------




DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump


FAULTING_IP: 
+2495a8f3d0
00007ff8`5ef1b06a c3              ret


CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


BUGCHECK_STR:  0x1


PROCESS_NAME:  SteelSeriesEng


CURRENT_IRQL:  0


ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre


LAST_CONTROL_TRANSFER:  from fffff800289d3ae9 to fffff800289c7fa0


STACK_TEXT:  
ffffd000`5d894af8 fffff800`289d3ae9 : 00000000`00000001 00007ff8`5ef1b06a 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
ffffd000`5d894b00 fffff800`289d3a06 : ffffe001`0d5ca880 00000000`00a9e698 00000000`00000000 00000000`00000020 : nt!KiBugCheckDispatch+0x69
ffffd000`5d894c40 00007ff8`5ef1b06a : 00007ff8`5dfeac55 0000ec50`d8893dcc 00007ff8`447b2530 00000000`03abd0c0 : nt!KiSystemServiceExit+0x24b
00000000`00a9ccd8 00007ff8`5dfeac55 : 0000ec50`d8893dcc 00007ff8`447b2530 00000000`03abd0c0 00007ff8`44a2f7f6 : 0x00007ff8`5ef1b06a
00000000`00a9cce0 0000ec50`d8893dcc : 00007ff8`447b2530 00000000`03abd0c0 00007ff8`44a2f7f6 00000000`00001000 : 0x00007ff8`5dfeac55
00000000`00a9cce8 00007ff8`447b2530 : 00000000`03abd0c0 00007ff8`44a2f7f6 00000000`00001000 00007ff8`00000004 : 0x0000ec50`d8893dcc
00000000`00a9ccf0 00000000`03abd0c0 : 00007ff8`44a2f7f6 00000000`00001000 00007ff8`00000004 00000000`00000000 : 0x00007ff8`447b2530
00000000`00a9ccf8 00007ff8`44a2f7f6 : 00000000`00001000 00007ff8`00000004 00000000`00000000 00000000`00028000 : 0x3abd0c0
00000000`00a9cd00 00000000`00001000 : 00007ff8`00000004 00000000`00000000 00000000`00028000 00007ff8`44dfb2b0 : 0x00007ff8`44a2f7f6
00000000`00a9cd08 00007ff8`00000004 : 00000000`00000000 00000000`00028000 00007ff8`44dfb2b0 00000000`00000002 : 0x1000
00000000`00a9cd10 00000000`00000000 : 00000000`00028000 00007ff8`44dfb2b0 00000000`00000002 00000000`00000000 : 0x00007ff8`00000004




STACK_COMMAND:  kb


FOLLOWUP_IP: 
nt!KiSystemServiceExit+24b
fffff800`289d3a06 4883ec50        sub     rsp,50h


SYMBOL_STACK_INDEX:  2


SYMBOL_NAME:  nt!KiSystemServiceExit+24b


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: nt


IMAGE_NAME:  ntkrnlmp.exe


DEBUG_FLR_IMAGE_TIMESTAMP:  53388e13


IMAGE_VERSION:  6.3.9600.17085


BUCKET_ID_FUNC_OFFSET:  24b


FAILURE_BUCKET_ID:  0x1_SysCallNum_35_nt!KiSystemServiceExit


BUCKET_ID:  0x1_SysCallNum_35_nt!KiSystemServiceExit


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:0x1_syscallnum_35_nt!kisystemserviceexit


FAILURE_ID_HASH:  {6dbede56-1557-ea5c-9525-19e1c8b3f8be}


Followup: MachineOwner
---------


3: kd> lmvm nt
start             end                 module name
fffff800`28874000 fffff800`28ffd000   nt         (pdb symbols)          c:\windows\symbol_cache\ntkrnlmp.pdb\074CDA55DA7246348FABA374422939411\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Mapped memory image file: c:\windows\symbol_cache\ntoskrnl.exe\53388E13789000\ntoskrnl.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Timestamp:        Sun Mar 30 23:35:15 2014 (53388E13)
    CheckSum:         0071C6D7
    ImageSize:        00789000
    File version:     6.3.9600.17085
    Product version:  6.3.9600.17085
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ntkrnlmp.exe
    OriginalFilename: ntkrnlmp.exe
    ProductVersion:   6.3.9600.17085
    FileVersion:      6.3.9600.17085 (winblue_gdr.140330-1035)
    FileDescription:  NT Kernel & System
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Code:

********************************************************************************                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800cb8f2d13, address which referenced memory


Debugging Details:
------------------




READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800cbbd1138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 0000000000000008 


CURRENT_IRQL:  2


FAULTING_IP: 
nt!KiInsertTimerTable+a3
fffff800`cb8f2d13 4c397008        cmp     qword ptr [rax+8],r14


CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


BUGCHECK_STR:  AV


PROCESS_NAME:  firefox.exe


ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre


TRAP_FRAME:  ffffd000f132b8d0 -- (.trap 0xffffd000f132b8d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000009896
rdx=000000c52abc047a rsi=0000000000000000 rdi=0000000000000000
rip=fffff800cb8f2d13 rsp=ffffd000f132ba60 rbp=fffff800cbb75768
 r8=ffffe001c207a4f0  r9=00000000000000af r10=fffff800cb871000
r11=fffff78000000008 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KiInsertTimerTable+0xa3:
fffff800`cb8f2d13 4c397008        cmp     qword ptr [rax+8],r14 ds:00000000`00000008=????????????????
Resetting default scope


LAST_CONTROL_TRANSFER:  from fffff800cb9cbce9 to fffff800cb9c01a0


STACK_TEXT:  
ffffd000`f132b788 fffff800`cb9cbce9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`f132b790 fffff800`cb9ca53a : 00000000`00000000 fffff800`cb9c3036 fffff800`cbb71100 ffffd000`f132b8d0 : nt!KiBugCheckDispatch+0x69
ffffd000`f132b8d0 fffff800`cb8f2d13 : fffff901`42473b00 ffffd000`00000000 00000000`02322be0 ffffe59e`2cbdcf93 : nt!KiPageFault+0x23a
ffffd000`f132ba60 fffff800`cb8f13cd : ffffe001`c133e4c0 ffffe001`c49d69f0 00000000`00314ab1 00000000`00000000 : nt!KiInsertTimerTable+0xa3
ffffd000`f132bac0 fffff800`cb8d72f0 : 00000000`00000000 00000000`00000000 fffff901`000000af fffff960`0027d2b4 : nt!KiCommitThreadWait+0x1bd
ffffd000`f132bb40 fffff800`cbc32682 : ffffe001`c0113fe0 ffffd000`00000006 00000000`00000000 fffff901`00000002 : nt!KeWaitForSingleObject+0x2c0
ffffd000`f132bbd0 fffff800`cb9cb9b3 : ffffe001`c133e4c0 00000000`00000000 ffffd000`f132bc18 ffffe001`c0113fe0 : nt!NtWaitForSingleObject+0xb2
ffffd000`f132bc40 00000000`772c2772 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`078be958 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772c2772




STACK_COMMAND:  kb


FOLLOWUP_IP: 
nt!KiInsertTimerTable+a3
fffff800`cb8f2d13 4c397008        cmp     qword ptr [rax+8],r14


SYMBOL_STACK_INDEX:  3


SYMBOL_NAME:  nt!KiInsertTimerTable+a3


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: nt


IMAGE_NAME:  ntkrnlmp.exe


DEBUG_FLR_IMAGE_TIMESTAMP:  53fe6f2e


IMAGE_VERSION:  6.3.9600.17328


BUCKET_ID_FUNC_OFFSET:  a3


FAILURE_BUCKET_ID:  AV_nt!KiInsertTimerTable


BUCKET_ID:  AV_nt!KiInsertTimerTable


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:av_nt!kiinserttimertable


FAILURE_ID_HASH:  {1949fc55-7efe-b7ab-5126-09ed4666d971}


Followup: MachineOwner
---------


3: kd> lmvm nt
start             end                 module name
fffff800`cb871000 fffff800`cc007000   nt         (pdb symbols)          c:\windows\symbol_cache\ntkrnlmp.pdb\E018720B8C414EF799EACB23114763921\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Mapped memory image file: c:\windows\symbol_cache\ntoskrnl.exe\53FE6F2E796000\ntoskrnl.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Timestamp:        Thu Aug 28 01:52:14 2014 (53FE6F2E)
    CheckSum:         007311DE
    ImageSize:        00796000
    File version:     6.3.9600.17328
    Product version:  6.3.9600.17328
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ntkrnlmp.exe
    OriginalFilename: ntkrnlmp.exe
    ProductVersion:   6.3.9600.17328
    FileVersion:      6.3.9600.17328 (winblue_r3.140827-1500)
    FileDescription:  NT Kernel & System
    LegalCopyright:   © Microsoft Corporation. All rights reserved.


3: kd> .trap 0xffffd000f132b8d0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000009896
rdx=000000c52abc047a rsi=0000000000000000 rdi=0000000000000000
rip=fffff800cb8f2d13 rsp=ffffd000f132ba60 rbp=fffff800cbb75768
 r8=ffffe001c207a4f0  r9=00000000000000af r10=fffff800cb871000
r11=fffff78000000008 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KiInsertTimerTable+0xa3:
fffff800`cb8f2d13 4c397008        cmp     qword ptr [rax+8],r14 ds:00000000`00000008=????????????????

Code:

********************************************************************************                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000


Debugging Details:
------------------




DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED


CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


BUGCHECK_STR:  0x133


PROCESS_NAME:  svchost.exe


CURRENT_IRQL:  d


ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre


LAST_CONTROL_TRANSFER:  from fffff802843ec02e to fffff802843d01a0


STACK_TEXT:  
ffffd000`791f7c88 fffff802`843ec02e : 00000000`00000133 00000000`00000001 00000000`00001e00 00000000`00000000 : nt!KeBugCheckEx
ffffd000`791f7c90 fffff802`842bba71 : fffff801`00000003 00000000`06ec10f3 ffffe000`ccb9bd50 ffffd000`791f7e18 : nt! ?? ::FNODOBFM::`string'+0xb97e
ffffd000`791f7d20 fffff802`842197b5 : 00000000`000135bd fffff802`8435c8f5 0000000f`ffffffff 00000000`00000002 : nt!KeClockInterruptNotify+0x91
ffffd000`791f7f40 fffff802`8436276a : ffffd000`808fd1a0 fffff802`8437e75b ffffeba1`0941b25c 00000000`00000000 : hal!HalpTimerClockIpiRoutine+0x15
ffffd000`791f7f70 fffff802`843d162a : ffffe000`ca400500 fffffa80`003a1370 00000000`d00804ee 00000000`000135bd : nt!KiCallInterruptServiceRoutine+0x8a
ffffd000`791f7fb0 fffff802`843d1f9b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd000`808fd120 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xfb




STACK_COMMAND:  kb


FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+b97e
fffff802`843ec02e cc              int     3


SYMBOL_STACK_INDEX:  1


SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+b97e


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: nt


IMAGE_NAME:  ntkrnlmp.exe


DEBUG_FLR_IMAGE_TIMESTAMP:  53fe6f2e


IMAGE_VERSION:  6.3.9600.17328


BUCKET_ID_FUNC_OFFSET:  b97e


FAILURE_BUCKET_ID:  0x133_ISR_nt!_??_::FNODOBFM::_string_


BUCKET_ID:  0x133_ISR_nt!_??_::FNODOBFM::_string_


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:0x133_isr_nt!_??_::fnodobfm::_string_


FAILURE_ID_HASH:  {89366ad1-5557-ac2b-d015-8f6ec2fdbf31}


Followup: MachineOwner
---------


3: kd> lmvm nt
start             end                 module name
fffff802`84281000 fffff802`84a17000   nt         (pdb symbols)          c:\windows\symbol_cache\ntkrnlmp.pdb\E018720B8C414EF799EACB23114763921\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Mapped memory image file: c:\windows\symbol_cache\ntoskrnl.exe\53FE6F2E796000\ntoskrnl.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Timestamp:        Thu Aug 28 01:52:14 2014 (53FE6F2E)
    CheckSum:         007311DE
    ImageSize:        00796000
    File version:     6.3.9600.17328
    Product version:  6.3.9600.17328
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ntkrnlmp.exe
    OriginalFilename: ntkrnlmp.exe
    ProductVersion:   6.3.9600.17328
    FileVersion:      6.3.9600.17328 (winblue_r3.140827-1500)
    FileDescription:  NT Kernel & System
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Click to expand...

Thank you so much think its possible the store i baught it from sold me a busted cpu? or is this normaly more of a software problem?

I think its more incompatibility with your system, but I don't know if it has been checked with compatibility.

Is there anyway i can check that? and also, the motherboard, cpu and two of the ram sticks came in an upgrade package as a bundle, so i would at least hope they would work well together..

As a test, update the CPU drivers and uninstall eset via the eset uninstall tool.

Cant post a link as im via mobile.

axe0 said:

As a test, update the CPU drivers and uninstall eset via the eset uninstall tool.

Cant post a link as im via mobile.

Click to expand...

Okey, thanks. Im downloading now, then ill install, restart and try to replicate the bsod by running 2x1080p youtube videos like i did earlier today. ill report back as soon as something happens.

I also had a windows update i was missing, installed that to. the 1080p videos ran for about 40min before i got another bsod, was not sitting at my computer when it happened so i didn't see the message, and i also noticed i got another bsod when the computer was restarting (sry but was not paying to much attention, so didn't see the message there either). After that my computer just started crashing at the log inn screen and just kept restarting until i turned it off manually. When i bootet it up again now, everything seems fine. Also the dump file didn't show up in BluseScreenView, but i found it. View attachment 63296

Edit: Its getting late, so I'm going to bed now, but ill be checking here first thing in the morning.

Going out to buy an SSD now, then doing a fresh install of windows 8 pro when i get back, to see if it helps.

If you have installed the ssd + windows on it and get a new bsod, please upload a new zip file using the DM Log collector Tool.

axe0 said:

If you have installed the ssd + windows on it and get a new bsod, please upload a new zip file using the DM Log collector Tool.

Click to expand...

Done with the install, just have some small things left to fix, and then ill stress test it by 3dmark and 2x1080p videos like i did before. post back here when and if something happens.

Nope, still got bsod form doing the 2x1080p video thing. so here is the updated files: View attachment 63311

The AMD cpu is the cause of the crash, have you changed any settings in the bios for your cpu like overclocking?

axe0 said:

The AMD cpu is the cause of the crash, have you changed any settings in the bios for your cpu like overclocking?

Code:

********************************************************************************                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


WHEA_UNCORRECTABLE_ERROR (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
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe00002836028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000100153, Low order 32-bits of the MCi_STATUS value.


Debugging Details:
------------------




BUGCHECK_STR:  0x124_AuthenticAMD


CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


PROCESS_NAME:  firefox.exe


CURRENT_IRQL:  f


ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre


STACK_TEXT:  
ffffd000`20660da8 fffff802`a1fd2c9f : 00000000`00000124 00000000`00000000 ffffe000`02836028 00000000`b6000000 : nt!KeBugCheckEx
ffffd000`20660db0 fffff802`a19d3d41 : 00000000`00000001 ffffe000`003acdf0 ffffe000`003acdf0 ffffe000`02836028 : hal!HalBugCheckSystem+0xcf
ffffd000`20660df0 fffff802`a1fd312c : 00000000`00000728 00000000`00000002 ffffd000`206611b0 00000000`00000000 : nt!WheaReportHwError+0x22d
ffffd000`20660e50 fffff802`a1fd3499 : ffffe000`00000010 ffffe000`003acdf0 ffffd000`20660ff8 ffffe000`003acdf0 : hal!HalpMcaReportError+0x50
ffffd000`20660fa0 fffff802`a1fd3384 : ffffe000`003ac780 00000000`00000001 00000000`00000002 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
ffffd000`20660ff0 fffff802`a1fd3758 : ffffe000`003ac780 ffffd000`20661230 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd000`20661030 fffff802`a19747bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x49
ffffd000`20661060 fffff802`a1974571 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffd000`206611a0 00000000`5e3cd6b1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
00000000`3527f420 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5e3cd6b1




STACK_COMMAND:  kb


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: AuthenticAMD


IMAGE_NAME:  AuthenticAMD


DEBUG_FLR_IMAGE_TIMESTAMP:  0


IMAGE_VERSION:  


FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE


BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_cache


FAILURE_ID_HASH:  {b533751b-676e-7546-bcdc-24e6c40d0064}

Click to expand...

Nope, haven't changed anything in the bios, but i guess ill restart then set the bios to default to be sure, then test again?