Multiple BSOD erros when gaming and general use (new PC build)

Picas · 10 Feb 2017

Hi!

About a month ago I built a new gaming PC and quickly encountered BSOD issues. This was quite quickly fixed by letting windows run through the latest updates. Over the past few days, however, these same BSOD faults have cropped back up. The main offenders are (DRIVER_)IRQL_NOT_LESS_OR_EQUAL and HAL_INITIALIZATION_FAILED, though there are a few other ones every now and then (should be visible in the log info).

I've once again updated everything, run the Windows memory diagnostic tool and done a full scan for any threats; none seem to be at fault but I'm still getting issues. Whilst playing Overwatch either the game will crash or I'll get a BSOD. The PC will also crash (BSOD or no BSOD screen) with just general use. Most of the parts are brand new; it's a pretty beefy computer and it's running in a cool room with good ventilation, so I don't really expect overheating to be the issue. Not overclocking anything currently either.

Any help on these problems would be greatly appreciated,

Alex

axe0 · 10 Feb 2017

Please fill in your system specs

Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.
The PSU, cooling and other stuff are NOT mentioned in the tool.

In the left corner below in your post you find 'My System Specs'. After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.

Picas · 10 Feb 2017

Specs updated. Tried to make everything as detailed as possible, hope it's okay.

axe0 · 10 Feb 2017

Diagnostic Test

RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

Picas · 11 Feb 2017

So I've ran the memory test and it's just finished 8 passes; no errors found.

Picas · 11 Feb 2017

Sorry about the double post, but here's a photo of the requested results.
Attachment 120827

axe0 · 11 Feb 2017

Apologies for the delay.
I've been trying to find out what the parameters of the 0x5C crashes mean since I've found very little about 0x5C crashes (because they appear infrequently). I did so to identify what possible suggestions may help.

The current suggestion for now is to try driver verifier.

Diagnostic Test

DRIVER VERIFIER

Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

At first I thought this may be a defect with the CPU as it looks to me like the CPU is being unable to send a request to another processor to do something.

Code:

 # Child-SP          RetAddr           Call Site
00 fffff803`a1c7f588 fffff803`9fe40a59 nt!KeBugCheckEx
01 fffff803`a1c7f590 fffff803`9f7a6ac9 hal!HalRequestIpi+0x17349
02 fffff803`a1c7f810 fffff803`9f6d313a nt! ?? ::FNODOBFM::`string'+0x45f39 // nt!PpmIdleExecuteTransition
03 fffff803`a1c7fa80 fffff803`9f75474c nt!PoIdle+0x33a
04 fffff803`a1c7fbe0 00000000`00000000 nt!KiIdleLoop+0x2c

However, on examining a parameter (after many attempts finally result), it appears that a BSOD occurs because the call to make a request fails.
My first suspect on this is a driver, because there are many drivers that are simply buggy.

Code:

HAL_INITIALIZATION_FAILED (5c)
Arguments:
Arg1: 0000000000000201
Arg2: ffffffffffd015b0
Arg3: ffffffffc000000d
Arg4: 0000000000000000

0: kd> !error ffffffff`c000000d
Error code: (NTSTATUS) 0xc000000d (3221225485) - An invalid parameter was passed to a service or function.

Picas · 11 Feb 2017

No worries! I've been very impressed by the response times on these forums so far.

I've ran driver verifier and it blue screens on the boot up screen. The error message is DRIVER_VERIFIER_IOMANAGER_VIOLATION

Restarting does the same thing, except when I open the UEFI menu first it loads "Preparing Automatic Repair". This causes Windows Defender Offline to run and it will do a quick scan of the PC. It then restarts and the blue screen process repeats again.

Oh and I tried updating Windows Defender Offline through the same screen (only other option I seem to have) and I get another error. Not sure if it's at all relevant but this is what the error message gives:

"Windows Defender: msseces.exe - Application Error

The instruction at 0x00007FF7C96915AB referenced memory at 0x000000004A2AF208. The memory could not be read."

Should I try booting up the recovery drive to get out of the endless loop of BSODs?

axe0 · 11 Feb 2017

You should disable driver verifier to be able to boot the system properly again, use the recovery drive for disabling driver verifier.

Picas · 14 Feb 2017

Back again...

Having some weird issues trying to disable the driver verifier. I am unable to disable it using system restore; I receive an error message that thinks there are two OSes to choose from (there isn't), I can't seem to bypass this error.

Using the command prompt crops up some even stranger issues. All of my drives have now seemingly been jumbled around. My C:\ drive that originally kept Windows 10 and the majority of my program files has now been replaced by my games drive; Windows 10 now shows up on the D:\ drive. I've used the command prompt for X:\, C:\ and D:\ with no success. I don't know whether it's worth mentioning that on each boot Windows Defender offline scan will run every single time now. This causes the PC to reset as well, so I don't know if it's interfering with the command to disable the driver verifier that requires a failed boot before triggering.

The third option to disable driver signature enforcement through startup settings is not available for me. My only other option is to reinstall Windows 10 entirely, but I'm not sure if there's a better route to take here still.

Thank you for your patience and continued support!