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: 0x0000000Awhile trying to register for these blog 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?

• CHARLES-PC-Sat_03_19_2016_210603_59.zip (560.6 KB, 2 views)

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 blog

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 ---

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)

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 blog

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

• latinum.zip (78.3 KB, 2 views)

► 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.