BSOD ntoskrnl.exe+75c40

CPU test came back with no errors. Re-enabled verifier.exe, Bluescreen. Couldn't get to safe mode to disable verifier. Windows is attempting to repair.

Latest minidump after Verifier was enabled.

You need to run Prime95's torture test for several hours per test (blend for few hours and then large ffts for few hours). Prime95 will run indefinitely, working with increasingly larger and complex numbers until you decide to stop it.

Verifier does not run in Safe mode period, only in normal mode. You can disable it in safe mode by opening it up again and choosing "delete existing settings" then restart. If you are experiencing a boot loop (which it sounds like you are) you need to tap the F8 key to get into Safe Mode. If you do not hit the F8 key at the right time (after BIOS POST and before Windows logo) then Windows will attempt to start in normal mode, which is why you're probably getting slammed with the repair attempt. You'll have to tap the key pretty rapidly on a computer with a fast drive (like an SSD) since the window of opportunity is very small.

I know verifier doesn't run in safe mode, I was attempting to get into safe mode to disable it, which i was finally able to do. I will run Prime95 under blend and large ffts for a few hours. I was just stating that per the request of the other gentlemen helping ran the prime95 using the smallffs setting for 2 hours + and then enabled verifier.

Ah ok then, sorry about that. TBH, typically it's best to actually do two overnight runs, one for Blend and one for Large FFTs. The numbers it calculates once it reaches that amount of time gets long and complex enough to really start pressuring various assets of the CPU as well as RAM-to-CPU crosstalk on Blend settings. I've seen many problems with CPUs not show up in Prime95 until well after the 7th hour.

good to know. I plan on letting it run over night.

Ok ran the prime95 tests, let each run for over 8 hours, No warnings and no errors.

*bump*

If that's the case, then if this is a hardware problem it's going to be most likely a motherboard or PSU issue. Unfortunately there's no solid testing procedure besides just swapping parts to get a clear answer on that.

I've checked through the latest DV dump you gave. While I don't think it's the actual cause of your symptoms, it did detect an issue with a HID, which is the keyboard, much like what Arc discovered in a previous crash. In fact, I went ahead and reviewed the thread and you mentioned you've had a number of clean installs on this system and it's still causing you grief. We know for sure it's hardware then, but what hardware it is evidently is difficult to determine right now. Again, I blame PSU or Mobo. If you're having difficulty with USB devices like the keyboard here, then I'd put more blame on Mobo. However, I would like to know what brand/model of PSU you have.

Ronys2 said:

*bump*

Hi Ronys,

Any more answers/ideas regarding this one. I have recently started having exactly the same issues. My CPU and GPU were both overclocked, so I have turned that down and am testing now. Will let you kow how I get one.

Cheers.

Nick