Windows 10: BSOD And random freeze

Hello everyone. For long time I was having problem with my old HDD it was faulty and my PC crashed from time to time (format + new windows). I decide to change my old HDD and get a new HDD and new SSD to act as window partition.

After i install everything i started to getting BSOD and once my PC startup it random start freezeing on 20sec - 30sec. Except new HDD that act as storage device i didint install anything new devices.

:)

 

Random Freezes and BSOD (DPC_WATCHDOG_VIOLATION)

Thank you for replying quickly.

My windows is currently up-to-date so it's not that. I've tried the troubleshooting and there seems to be no errors that are coming up.

I will check out the external devices, but its hard to tell. The freezes/bsod can appear at any time, sometimes its after several hours of PC usage, sometimes only a few minutes after start-up.

Any particular external devices should i take out?

 

Random Freezes and BSOD (DPC_WATCHDOG_VIOLATION)

Hey guys,

I was wondering if you could help me out.

I have recently purchased some new parts for my computer. I upgraded my rig, the parts i upgraded were my Motherboard, CPU, GPU, RAM, new cooling system and purchased a M2 SSD.

I've had **** on, trying to put the new rig together but managed to get everything sorted. Had to do a fresh install of Windows 10 Home Edition due to the m2 ssd. The problem I am still getting is that a random times, my PC decides to freeze. It's not just
a freeze and a bluescreen. Its a freeze, takes a 1min or 2mins to unfreeze, works for a few mins then decides to bluescreen. Mostly occurs when I'm on Google Chrome.

I've tried so many things to try and fix it but I think it's gone way above my head now.

Considering that its got a lot of new parts and it has a fresh install, I am not sure which drivers is causing this or even if it is related to the drivers.

I keep getting the same errors via event viewer, I will attach the picture down below.

Errors via Event viewer: Dropbox - errors via event viewer.png

Msinfo: Dropbox - mypcspecs.nfo

Speccy: Dropbox - PC.txt

Dumpfiles: Dropbox - memorydumps.zip

If I need any other type of information, you can ask me.

Hope you can help me out.

 

The zip file is missing file Genuine.txt. Please run slmgr /dlv and post a screen shot of the result.

 

bradyc, where do you see hal.dll and ntoskrnl.exe? I see the following in both dumps:

Code: BugCheck 124, {0, ffffe00193963028, b6000000, 100153} Probably caused by : AuthenticAMD[/quote] Code: =================================== Common Platform Error Record @ ffffe0019e244028 ---------------------------------------------------------------- Record Id : 01d1c8806eaed599 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 6/17/2016 10:19:59 (UTC) Flags : 0x00000000[/quote] A Machine Check Exception is a hardware error, most likely a CPU problem though it could actually be a firmware problem (BIOS)> See here: [SOLVED] BSOD - Tech Support Forum

Try updating your BIOS. The current one is version 2006 dated 10/01/2013. There are several newer ones on the ASUS website, try the latest which is Version 2603 dated 2015/07/24.

 

Code: =================================== Common Platform Error Record @ ffffe0019e244028 ---------------------------------------------------------------- Record Id : 01d1c8806eaed599 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 6/17/2016 10:19:59 (UTC) Flags : 0x00000000[/quote] A Machine Check Exception is a hardware error, most likely a CPU problem though it could actually be a firmware problem (BIOS)> See here: [SOLVED] BSOD - Tech Support Forum

Try updating your BIOS. The current one is version 2006 dated 10/01/2013. There are several newer ones on the ASUS website, try the latest which is Version 2603 dated 2015/07/24.[/quote] Both dumps show the same error in BlueScreenView to me, here is where I see the errors: Attachment 85799

 

Hi @bradyc,

Unfortunately what you say is not true.

The hal.dll is for communication with the drivers and the hardware, it does not mean there is a hardware problem.
Ntoskrnl.exe is a Windows kernel file, only flagged when there is nothing else to blame and thus is a 'false positive'
Both can be involved in many crashes, but I have rarely seen that it resulted in faulty hardware.

Your research is not proper, Windows files are often flagged but that does NOT mean corrupt system files are present.
As I mentioned Windows files are only flagged when nothing else is there to flag, that it could be due to memory is simply not true.

That isn't the worst case scenario, we're dealing with a hardware crash. The worst scenario is replacing the motherboard or CPU or something.


If someone would like to do research about BSODs, please do not use sites that give very improper information.

 

Hi, @axe0. I realize now how I got the false information that I got, and I just wanted to apologize for any trouble I may have caused. As you probably could tell, I was only trying to help because I would like to repay the site for helping me with my blue screen issue. Thank you for pointing out where I was wrong, and for telling me why the information I had "researched" was in fact, not necessarily true. I can see now that I should probably just stay out of these kinds of situations, and leave it to the professionals (like yourself). Although, if you wouldn't mind, I am very interested in learning how to help other people with blue screens because I know other people that have some problems with that. Thanks for replying!

 

If you are interested in learning it, here are a few links for the setup of Windbg, the program with which dumps can be opened.
WinDBG - Install Configure - Windows 10 Forums
WinDBG - The Basics for Debugging Crash Dumps in Windows 10 - Windows 10 Forums

That is however only a part of it, you need to read quite a bit about BSODs from trust worthy sites
I recommend to use this site for many BSOD information *Arrow www.carrona.org
The owner is BSOD Expert & Windows Expert John Caronna a.k.a. @usasma.

 

I've found reading BSOD threads handled by axe0, Arc and Essenbe is a great way to learn too. Take the time to look at what they post then figure out where they got the info and why.

ScorpioCRO, I also suggest doing the following:

Stress test the CPU

Prime95 - Stress Test Your CPU

It saves the result as a .txt file in the prime95's folder. Upload the file here please, zip first if necessary.