[SOLVED] Random BSODs, Driver Verifier giving BSODs no matter what's tested. FIX: I removed Saitek drivers and daemon tools.

MingoMongo

MingoMongo

Well-known member
Joined
Oct 2, 2020
Posts
146
Location
UK
Stats:

Windows 7 64bit SP1, ASUS P8Z68 Deluxe/Gen3, Intel Core i5-2500K, Corsair Vengeance 8GB Dual Channel DDR3 Memory Kit (CMZ8GX3M2A1866C9), Asus Nvidia GeForce GTX 960, WDC WD1002FAEX (Windows drive), Corsair Force 3 SSD, Seagate ST2000DM006, Corsair Gold AX1200 (1200 Watts)

Hi people,

So I've been trying to upgrade to Windows 10 but the error (0xC1900101 - 0x40017, I believe coming from mid-way blue screens with no dumps) coming up during installation makes me feel like it's finally time to fix my drivers. I get BSODs every 3 weeks or something (not sure what I'm doing at the time), I've got issues with my audio interface garbling my audio, and putting my PC to sleep seems to put it in a state where I can't wake it or do anything but turn it off at the power (with some BSODs in the past). I've reinstalled the drivers for graphics and audio in the past but to no avail. I'm just a bit lost not knowing what's a problem and what's a symptom of a different problem

I've been running the Driver Verifier with no peripherals besides mouse and keyboard and no-antivirus installed. Turning off all Microsoft drivers brings up a BSOD during windows startup pointing to rskernelengine.sys. I'm not sure if it counts as a Microsoft driver as well, so when I don't test that one too I get the same BSOD but this time pointing to hidclass.sys which is a Microsoft driver. Testing less drivers on the verifier I got hidclass.sys several times, then a BSOD during startup pointing to Virtual CloneDrive, then after that one was turned off for the rest of the drivers I got crash on start-up even always giving BSODs with a IRQ_NOT_LESS_OR_EQUAL error and no dump. This happened even when testing random lone drivers so I'm not sure if verifier is even working as intended, I thought I could at least get the PC to log in to Windows.

Importantly, the random crashes I've got in the past usually point to ntoskrnl.exe (example of one is dump 092020-110355-01).
The rest of the dumps will be from Driver Verifier tests because I didn't save my old crash dumps, sorry.

Just fyi, Windows Memory Diagnostic has come up with nothing, and <sfc /scannow> in cmd comes up with no issues as well. I know I could try a clean install of Windows 10, but the prospect of redownloading all my programs I'm finding very unappealing. Focusing on fixing Windows 7 first.

Note: The SysnativeFileCollection app broke at the end "Waiting for Tasks to complete" for 15 mins and I had to stop it manually, didn't work on retry. Hopefully all the information is there.
 

Attachments

Please remove Daemon Tools or any associated software, it is known to cause issues with Windows 7 machines.

Rich (BB code): 
2: kd> lmvm dtsoftbus01
Browse full module list
start             end                 module name
fffff880`0586a000 fffff880`058b3000   dtsoftbus01 T (no symbols)           
    Loaded symbol image file: dtsoftbus01.sys
    Image path: \SystemRoot\system32\DRIVERS\dtsoftbus01.sys
    Image name: dtsoftbus01.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Jan 13 13:45:46 2012 (4F10358A)
    CheckSum:         00046D1E
    ImageSize:        00049000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Support: https://www.daemon-tools.cc/support
 
Rskernelengine.sys is a driver from Reason Software Corporation (Reason antivirus) antivirus software. Are you using it It is worth reporting it to its developer. As for Daemon Tools, it is enough to update it to the latest version, the error with Driver Verifier was fixed long ago. Also listed are the MBAMChameleon.sys driver (Malwarebytes driver, but I see that you removed all the company's products from your computer) and the gearaspiwdm.sys driver (driver from Apple iTunes, make sure iTunes is the latest version, but you need to update the driver manually - Driver updates - GEAR Software)
 
Mini-update:

Thanks for the replies people, I really appreciate the help! I've uninstalled DAEMON Tools for now since I don't need it and I've removed KMS from ProgramData and the KMS files Malwarebytes had in quarantine. Interesting to hear about Rskernelengine MrPepka, I installed Reason a month ago but didn't keep it for long and uninstalled it. Looks like it didn't uninstall properly, thanks for pointing it out. Also, I do have Malwarebytes, so it's odd that you don't see the program, should I get rid of it? iTunes I don't use any more but I will definitely update it, thanks.

Unfortunately, testing after these changes will have to wait a while. My PC has suddenly started taking huge amounts of time starting up Windows, with "Starting Windows" staying on the screen for 10-15 minutes before it prompts me for a password. This also applies to booting in safe mode, with it pausing after CLASSPNP.sys for 10-15 mins instead of the about 10 secs it would pause for usually. I've been changing a lot of things on my PC so I can't be sure what might have brought this on. In any case, it makes frequent restarting an issue. Additionally, I've realised that my Restore Points I've been making disappear after one reboot, making the prospect of getting stuck on a loading screen more scary. This might not be you guys' specialty, but if you have any ideas I'll gladly take them.

P.S. Just want to say Malwarebytes and a HDD scan of my boot drive detected no problems
 
Malwarebytes? When you use it, you can leave it as long as it is in the latest version. As for Reason, even in the latest memory dump there is his driver (although in the sense that you can see his timestamp, Malwarebytes driver cannot be so previewed)
 
Ok, solved the long boot time thing. THANKFULLY it was just a matter of readjusting my hardware connections. I was getting worried because if something gets past Safe Mode it can't be good.

Alright, back to testing!
 
Eeey so through some trial and error Driver Verifier-ing, no more blue screens!

Removing the drivers we talked about previously, I was still getting BSODs pointing to hidclass.sys, and my previous error IRQL_NOT_LESS_OR_EQUAL was replaced with SPECIAL POOL DETECTED MEMORY CORRUPTION. hidclass.sys I managed to track down to two Saitek drivers (saimini.sys and saibus.sys). I don't use any Saitek controllers so I got rid of them. Some searching around showed that old Saitek drivers can be unstable. The SPECIAL POOL DETECTED MEMORY CORRUPTION was from digitech.sys which is an Avid driver. I got Pro Tools from a friend and it never really worked, can only imagine it's around because of a dodgy install. I got rid of the driver and uninstalled the program, and it was all good.

Now, when I use the verifier with all non-windows drivers, I'm finally able to boot into Windows! Whether this is the end of my issues I'm not sure, but right now I'm feeling a lot better about my PCs stability.

So thanks everyone so much for your help!
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top