Hi. . .
Why do you not consider these to be "real BSODs"? Any BSOD is serious as it tells us that there is something very wrong with your system, be it a rogue driver (which I think by now we have pretty much discounted software as the cause - although that BSOD with the
0x80000004 exception error code is somewhat bothersome) or unknown hardware failure.
Don't forget that you have had at least one (1)
0x124 bugcheck BSOD - WHEA = a Machine Check Exception, which is about as bad as it gets for hardware failure. 0x124 is very serious.
THE DUMPS
2 more BSODs and 2 more bugchecks.
The first dump -
0x1e (0xc000001d,,,) = the kernel threw an exception; the exception =
0xc000001d = an attempt was made to execute an illegal instruction (for example - division by zero). I do not know what exact illegal instruction was involved with your BSOD. So either a driver or app suddenly issued an illegal instruction here (where it did not do so before that we know of) or there may be a CPU problem.
The probable cause of this BSOD -
intelppm.sys = Intel Processor driver -
Driver Reference Table (DRT) | intelppm.sys
This driver appears to be some kind of joint venture between Microsoft and Intel as the dumps do not list a timestamp for it, which is typical of Microsoft Windows drivers.
Please run this Intel CPU test -
CPU STRESS testing: Mersenne.org Prime95 and Intel Processor Diagnostic Tool (IPDT)
The second dump -
0x133 - DPC Watchdog Violation
From Microsoft -
DPC_WATCHDOG_VIOLATION bug check has a value of 0x00000133. This bug check indicates that the DPC watchdog executed, either because it detected a single long-running deferred procedure call (DPC), or because the system spent a prolonged time at an interrupt request level (IRQL) of DISPATCH_LEVEL or above. The value of Parameter 1 indicates whether a single DPC exceeded a timeout, or whether the system cumulatively spent an extended period of time at IRQL DISPATCH_LEVEL or above.
From Google -
DPC Watchdog Violation (error code: DPC_Watchdog_Violation) is a common issue in the Windows operating system. It's occurred due to some specific reasons, like unsupported SSD firmware, old SSD driver version, hardware incompatibility issues, or system files are corrupted.
The probable cause - your Roland audio driver -
Code:
RDWM1203.SYS Tue May 1 21:16:16 2018 (5AE93B90)
Check for a driver update -
Roland - Support - Updates & Drivers
Please also check on the SSD firmware.
System files generally are prone to corruption when they are being transferred back and forth between SSD/HDD and RAM. Before a driver or app can be executed, the system must load the module from the SSD into RAM. Then when no longer needed, it is unloaded from RAM and written back to the SSD. This process occurs every second that your system is powered on. Typically what happens is that a problem with RAM (or other underlying hardware failure that negatively affects RAM) and/or a problem with the SSD/HDD or other hardware part that can affect the hard drive fails and the complete file is not written back to the SSD/HDD or is not properly loaded into RAM. Then you end up with corrupted files.
Have you given any thought to my suggestion about running the system with just 1 RAM stick at a time?
We really do need to absolutely rule RAM itself in or out as a possible cause of the BSOD epidemic. Same with the SSDs.
I even replaced all of my HDDs with SSDs last month, so that rules that out.
No... it does not rule the SSD(s) out. SSDs are tantamount to RAM and therefore are prone to the same failures as RAM. I've seen many OPs with brand new RAM and SSDs that turn out to be bad. Also, the SSD(s) that you bought could have been sitting on a shelf somewhere for months or years; meanwhile the SSD manufacturer has released new firmware that has not been applied to your "new" SSDs. It is possible, so
PLEASE check for firmware updates.
Also, in Windows, "WATCHDOG" often refers to video. Please humor me and check in
C:\Windows\LiveKernelReports\WATCHDOG directory. Are there any dumps in there? I've got 130 WATCHDOG dumps on my system - video failure;
0x117 - video TDR timeout; the video driver was unable to reset itself in the time allotted (30 seconds), but ultimately did before the 30 seconds was up.
0x117 Live Kernel Events can easily turn into
0x116 BSODs - where the system BSODs because the video driver was not able to reset itself within 30 seconds and crashed the system. A driver update solved my video problem, but I had no idea at the time that these
0x116's were occurring.
Also, can I please get an updated Sysnative app output?
Just run this app -
SysnativeBSODCollectionApp - and upload and attach the output zip file to your next post. Thank you.
What I'm saying here is that I'll be more than happy to run every BSOD dump that you send to me. But if you are going to selectively implement my suggestions (or not do them at all - like the RAM tests), this is all pointless as I'm not really helping you to get any closer to actually solve these BSODs.
I can also guarantee you that you won't find BSOD Analysts as good and knowledgeable as you will here at Sysnative because more often than not, it is our staff members that go to the other forums and answer their BSOD threads! We also run the only BSOD Academy on the Internet.
All of our suggestions to you are of course yours to either do or not do. It is completely your call. But if you really want these BSODs solved, you should think about just following our lead and see where things end up.
Regards. . .
John