BSOD | IRQL_NOT_LESS_OR_EQUAL | ntoskrnl.exe

Hi
Can someone possibly help me, please?
I upgraded to Windows 10 Pro for Workstations and since the upgrade, I have had the same BSOD. IRQL_NOT_LESS_OR_EQUAL caused by driver: ntoskrnl.exe

I have since downgraded back to Windows 10 Pro and I am having the same issue. I think it is driver related and I ideally don't want to format the machine. I spoke to Microsoft support and they have suggested connecting to a domain and this would fix the issue. HAHAHA. I have done the following since the issues have happened;
* Ran IPDT.
* Ran Memtest.
* Ran SFC, DISM and Chkdsk.
* Reinstalled USB, audio, graphics and chipset drivers.
* Ran verifier and then reinstalled any programs that flagged.

Oddly enough it only happens once from a cold boot. After that it is fine for the rest of the session.

I cannot think of anything else to try.

I have attached the file from the log collector.

Thank you in advance.

Attachment 210435

Ztruker said:

Also, do you have Fast Startup Enabled or Disabled? If Enabled, Disable it.
See here: How to Turn On or Off Fast Startup in Windows 10

Ztruker said:

The first dump, 102618-6328-01.dmp, shows a problem with gwdrv.sys.

Code:

BugCheck C4, {2000, fffff8022e981d25, 0, 44435747}
*** WARNING: Unable to verify timestamp for gwdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gwdrv.sys
Probably caused by : gwdrv.sys ( gwdrv+1d25 )

Driver Description: GlassWire Network Security driver
Driver Update Site: https://www.glasswire.com/

This appears to be some kind of firewall. I suggest uninstalling it for now and see if that makes a difference.
I see you have Kaspersky for anti-virus. If uninstalling GlassWire doesn't make any difference, try uninstalling all Kaspersky software. Run with the built-in Windows Defender and see if that makes any difference.

Decide what to do after doing these tests.

I have ran the Fast Startup bat as the setting was not there. I have also uninstalled Glass Wire. I will check tomorrow after a cold boot and if it still persists. I will remove Kaspersky. Thank you for looking at the files. It is now a waiting game.

Ztruker said:

I also looked at the other dumps but didn't see anything useful there. Event viewer data not helping much either.

If you get another BSOD, please use the Beta log collector shown after step 9 of the BSOD log collector link. Instructions there as well.

I have just had another BSOD. Same as last time. I removed Glass Wire last night. Today I have reinstalled Kaspersky and Malwarebytes. I have attached the logs from the beta as requested.


Attachment 210558

Ztruker said:

Does a BSOD occur every time you cold boot? 1/2 the time. every 3rd time? Any pattern to it?

Even though you said you ran memtest, I suggest removing one 16GB DIMM and testing. If it BSODS on a cold boot, power off and swap DIMMs and try again. Typically, a single DIMM will go in the 2nd slot, slot 1, if they are numbered 0, 1, 2, 3.

This has pretty much got to be a hardware or driver problem.

If testing memory doesn't help then I suggest doing a Clean Boot:
See here: How to Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

After every cold boot. Once it's BSOD then it's fine. When building the PC I looked at the manual for the best slots for dual channel and they are in those slots. I will remove one later and see how it goes.

Ztruker said:

What's different between a cold boot and a restart? If we can figure that out then we have a shot at fixing this.

Power? Are your power setting nominal or over/under voltage?

All the same processes start from cold and restart so it's a tough one to figure out.

The power settings are normal. I haven't over clocked the system.