Windows 10: Two different BSOD codes in one day. :/

I've had two BSOD's in one day: IRQL_NOT_LESS_OR_EQUAL and KMODE_EXCEPTION_NOT_HANDLED.
I don't overclock, but this system was considerably more reliable when I did (probably not because of the overclock).

I thought the problem occurred only when under load, since I compile a lot of software and transcode a lot of video, but I got the STOP: 0x0000000A while trying to register for these forums after the 1E, while CPU-Z was initializing and while the system was under minimal memory/CPU load.

I use an overkill Noctua NH-D15 CPU cooler, a Rosewill SilentNight 500W 80+ Platinum PSU, and I have my case wide open. My PSU is stable when running at 100% CPU+100% GPU, so I doubt it's having trouble providing stable power.

What could be causing these crashes?

:)

 

Constantly getting one of two different BSOD messages SYSTEM_SERVICE_EXCEPTION and IRQL_NOT_LESS_OR_EQUAL whilst playing games/idle, what can I do about this?

Nor me, it doesn't seem to be crashing as much as it did though so I'm quite content with that, It gives me a bit more time to investigate this further. It does seem to be clashing with Windows a fair bit, I was told on the Avast forums I have a vps version
of Avast so I'm not sure what to make of that, but for now I'm going to try uninstall Avast then see if I get any more bluescreens, just got to look around for a suitable antivirus replacement.

I'm thinking that too, I think it's doing something that's causing the other systems to crash as Avast has only really come up in two of the five or six minidump files, I haven't yet tested it with a game running but for now I'll try to remove Avast first.

Also, here's a link to the Avast forum post; https://forum.avast.com/index.php?topic=179868.0

 

Constantly getting one of two different BSOD messages SYSTEM_SERVICE_EXCEPTION and IRQL_NOT_LESS_OR_EQUAL whilst playing games/idle, what can I do about this?

Strange. I don't like that avast is triggering a BSOD one bit. since it hopefully isn't malware at this point, the only thing i can think of is some system level incompatibility. While the error number is a bit different, i managed to find this: Windows
forums - aswStm+0x2214

It does seem avast has clashed with windows before, it's possible it is doing it now with this new version.

At this point, from what i can tell, short of uninstalling avast the only option might be help from avast. I'll keep my eyes open for anything else i find. It's possible the BSOD was triggered when it tried to scan or check something.

 

We have checked the dumps, but before we conclude as to the failing modules, please let us see your msinfo32.nfo file (as that one included in the zip is not giving the complete info).System Information File - Create in Windows 10 - Windows 10 Forums Thanks.

CPUz (or Speccy, both uses the same hardware reading driver) causes this BSOD, for sure. Updating it to the latest should solve the issue. The main concern is the VPN caused BSOD; we need to check a bit more about it.
___________________________________________________________________________
Code: BugCheck A, {14f048, f, 1, fffff8032ca29197} *** WARNING: Unable to verify timestamp for cpuz139_x64.sys *** ERROR: Module load completed but symbols could not be loaded for cpuz139_x64.sys Probably caused by : cpuz139_x64.sys ( cpuz139_x64+2084 ) Followup: MachineOwner ---------[/quote] Code: BugCheck 1E, {ffffffffc0000005, fffff80248fbfc37, ffffd000232a30a8, ffffd000232a28c0} *** WARNING: Unable to verify timestamp for acsock64.sys *** ERROR: Module load completed but symbols could not be loaded for acsock64.sys Probably caused by : acsock64.sys ( acsock64+b5a6 ) Followup: MachineOwner --------------------------------------------------------------------------------- Image name: acsock64.sys Timestamp: Tue Jan 24 21:37:18 2012 (4F1ED736)[/quote]

 

Thank you for taking a look. I really appreciate your efforts.
I have attached the requested file.

 

► Cisco AnyConnect Secure Mobility Client

Update this program. Let us know for any further BSOD after doing it.

 

Thank you once again. Getting an updated client is an alarmingly slow process. I hope to update the thread ... sometime this year. *Smile