Question My new build freezes and goes to BSOD ?

Status
Not open for further replies.

droreni

Distinguished
Nov 24, 2012
85
4
18,535
Hi everyone,
I assembled a new computer in the last months, and now I am experiencing a lot of screen freezes, game crashes, BSOD's.. I am totally frustrated by it, since I cannot use it, let alone play it.

I got several msgs - "clock watchdog timeout", "IRQL not less or equal", "kernel security check failure"..
I am not sure about the timing it started, and since I introduced several upgrades during this period I cannot tell if one of those is the culprit.
I started up with:
MoBo- MSI z690 force
CPU - i5 13600k
Cooling - air-cooled with PCCOOLER paladin 400 tower (not very good one)
RAM - TeamGroup T-Force DDR5 2x16GB 6000 CL30
Storage - Samsung 980pro Nvme 2TB
PSU - Seasonic focus GX-1000 gold

Everything bought new except the Nvme which was never used second hand.
Then it seemed fine, but I didn't use it very much, but no errors.
Later I bought the GPU - XFX rx 7900xt - used, but looks like new.

Then I had some crashes in COD, randomly, after some minutes of playing.

I ran 3dmark time spy several times and it was OK, even when I tried undervolting it a bit. I also ran cinebench and it did good performance wise, even for long runs, but the temp was stuck at 100°c, without any cpu tweaking. I tried undervolting it as well to reach better temps, unsuccessfully.

Then I added another set of new 2x16GB, same as the 1st one.
Of course I reversed everything to default. Updated my BIOS, updated my chipset driver. Used DDU to clean all the amd drivers and installed it again (the driver with the "adrenaline" software).
And finally added a new barracuda 4tb drive.
Today it was the most freezes I had, even on my desktop while copying files..
On most of the crashes I had Hwinfo running and there was no spike in temps or loads or voltage that I could notice.
I tried reading around a bit, and good chance it's my RAM, (also had some post codes like 45, 47, that says its a RAM issue, though I ran the memtes86 and it passed with no problem (took the whole night to run 4 sets) and I also ran windows memory diagnosis and no problem found. I took all the RAM sticks out and left only one, still it persist.
Now I cannot barely bring my system to boot..
I need help and I am a noob in understanding all the dump files and stuff like that, have no clue where even to find 'em.. so if you need something, please be specific where can I find it..

I will appreciate any help, I gave up..
Sorry for the long post...
 

ubuysa

Distinguished
Jul 29, 2016
925
175
19,140
CLOCK_WATCHDOG_TIMEOUT is usually indicative of a faulty CPU. In a multiprocessor system the CPUs synchronise their clocks with regular interrupts between them, if a processor fails to respond to that clock interrupt you get the CLOCK_WATCHDOG_TIMEOUT bugcheck.

The other two bugcheck codes are commonly caused by third-party drivers.

Can you zip up the dump files (in C:\Windows\Minidump) and upload that here please?

In the meantime you might want to run the Intel Processor Diagnostic tool and see what that finds.
 
  • Like
Reactions: droreni

droreni

Distinguished
Nov 24, 2012
85
4
18,535
CLOCK_WATCHDOG_TIMEOUT is usually indicative of a faulty CPU. In a multiprocessor system the CPUs synchronise their clocks with regular interrupts between them, if a processor fails to respond to that clock interrupt you get the CLOCK_WATCHDOG_TIMEOUT bugcheck.

The other two bugcheck codes are commonly caused by third-party drivers.

Can you zip up the dump files (in C:\Windows\Minidump) and upload that here please?

In the meantime you might want to run the Intel Processor Diagnostic tool and see what that finds.
Unfortunately now I don't even manage to boot the system, I reach as far as the lock screen at best, and then it goes BSOD. I am trying to repeat resetting (only reset doesn't work so turning off and on again). If I get lucky I'll do it
 

ubuysa

Distinguished
Jul 29, 2016
925
175
19,140
There is an interesting mix in these six dumps...

Two of them are KMODE_EXCEPTION_NOT_HANDLED, which just means that an exception occurred in kernel mode and could not be recovered. Both dumps occurred during a disk access attempt and one of them has the third-party driver klbackupflt.sys on the call stack. This driver is a component of Kaspersky Security and that driver was the likely cause of this BSOD.

Two others are KERNEL_SECURITY_CHECK_FAILURE, which means that a critical kernel data structure has been corrupted. One of these dumps has the third-party driver klif.sys on the call stack, that's also a component of Kaspersky Security.

The final dump is a CRITICAL_PROCESS_DIED, which mean that an essential Windows process has crashed. In this case the process was csrss.exe, the Windows client/server runtime process. There are no third-party drivers on the call stack which generally points towards a hardware cause.

There are clearly issues with Kaspersky, and I suggest you uninstall that completely. I really have lost count of the number of BSODs I've seen that were caused by a third-party security product - which is why I use only Windows Defender and Windows Firewall.

However, the four other dumps have no third-party drivers on their call stacks and no obvious reason for the BSOD, that would suggest a hardware cause. However, I didn't see the CLOCK_WATCHDOG_TIMEOUT dump that you mentioned? I would still run the Intel Processor Diagnostic tool however. And uninstall Kaspersky.
 
  • Like
Reactions: droreni

droreni

Distinguished
Nov 24, 2012
85
4
18,535
There is an interesting mix in these six dumps...

Two of them are KMODE_EXCEPTION_NOT_HANDLED, which just means that an exception occurred in kernel mode and could not be recovered. Both dumps occurred during a disk access attempt and one of them has the third-party driver klbackupflt.sys on the call stack. This driver is a component of Kaspersky Security and that driver was the likely cause of this BSOD.

Two others are KERNEL_SECURITY_CHECK_FAILURE, which means that a critical kernel data structure has been corrupted. One of these dumps has the third-party driver klif.sys on the call stack, that's also a component of Kaspersky Security.

The final dump is a CRITICAL_PROCESS_DIED, which mean that an essential Windows process has crashed. In this case the process was csrss.exe, the Windows client/server runtime process. There are no third-party drivers on the call stack which generally points towards a hardware cause.

There are clearly issues with Kaspersky, and I suggest you uninstall that completely. I really have lost count of the number of BSODs I've seen that were caused by a third-party security product - which is why I use only Windows Defender and Windows Firewall.

However, the four other dumps have no third-party drivers on their call stacks and no obvious reason for the BSOD, that would suggest a hardware cause. However, I didn't see the CLOCK_WATCHDOG_TIMEOUT dump that you mentioned? I would still run the Intel Processor Diagnostic tool however. And uninstall Kaspersky.
Meantime I had cleared the CMOS and prepared a windows installation usb stick, tried to perform one, but it got stuck right in the beginning after clicking the "I don't have a key" option.
That's very interesting what you found out, I will try to uninstall Kaspersky and see if it changes anything.
I did have that clock watchdog timeout error before, and since I sent the files I had it once or twice more. Though the most I get is the kernel security one.
Now I can barely have a successful boot, it usually loops through BSODs and reseting itself, and freeze and various points.. on the debug led it usually code somewhere in the forties.. - 42, 45, 49, once 50.
I don't know what to do more.
In the next successful safe mode boot, which I can also hardly succeed in reaching, I will remove Kaspersky. Somehow I doubt it will help. Removed all the mem sticks, left only one, but no change..
Thank you so much for trying to help though. It's definitely further then I got by myself.
If you have any more ideas I'll be happy to hear.
Oh, and I cannot use the Intel Processor Diagnostic tool since I cannot install it on safe mode..

Edit:
Fun fact, I cannot uninstall a program in safe mode. any work around it?
 
Last edited:
Status
Not open for further replies.