Windows 10: Persistant Problem with BSOD, error code "TIMER_OR_DPC_INVALID"

I built a new computer 2 weeks ago and just recently I started getting BSODs. It started after Minecraft kept crashing, and then I started getting blue screens at random times, I reset the computer and it still happened, I installed all of the drivers and everything again and it still crashes. The crash code is Timer_or_dpc_invalid. I ran the sfc/scannow command in elevated command prompt and it came up that it found some corrupt files and was unable to fix them. There is a file with details of it but I don't understand what this means, I am trying to avoid taking it into Best Buy or somewhere similar but I don't see many other options. After resetting it I installed Norton and ran Malwarebytes and removed malware from my computer but the BSOD is still happening. I would really appreciate any help.

This is my build https://pcpartpicker.com/list/QPD6hg

submitted by /u/_AB_22_
[link] [comments]

:)

 

BSOD error codes HELP!!!!!!

yeah, i did the chkdsk /r and passed it. I was not aware of needing to run sfc at the time as most everything i had found indicated Bad sectors as the cause. The codes are 2 separate codes. The system had had problems posting and the Mobo had previously been replaced. As soon as the Cx received the system he started getting the BSOD errors.

 

BSOD - Registry Error

Your BSOD code is 0X000000051

Here's the Google search I did for it: https://www.google.com/search?q=0x0...j5.399j0j7&sourceid=chrome&es_sm=122&ie=UTF-8

There is a hotfix available that might help, https://support.microsoft.com/en-us/kb/810558

This thread makes a few good suggestions too: http://www.sevenforums.com/bsod-hel...dows-7-pro-sp1-registry-error-0x00000051.html

+1 to listing your full system specs, OS version, etc. I did only look at your BSOD log file.

Run a Diskchk /R (I know you already ran one, so you can skip this)

Run SFC /SCANNOW

Report back.

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.