Windows 10: BSOD (Critical_Structure_Corruption) once every few days or so

Sounds good! If a new BSOD does happen, make sure you post the new files.

 

Yeah, will do. In the meantime, I edited my last post so can you take a look at it? It has all the non-Microsoft drivers listed with some questions.

 

ahh i didn't see this when i replied!

Let me take a look.....

RivaTuner. It is a known BSOD causer in Win7. Lets uninstall Rivatuner for now, and if it appears not to be the problem then you can always reinstall it.

You can always check for an update at Drivers & Software

As for this, I had to google a solution for it. I found it, but only do it if you feel comfortable manually deleting files from your system folder. Here is the link https://dottech.org/101997/how-to-un...rs-on-windows/ I suggest ONLY removing the files and do not touch your systems registry.

 

I have W10, so I'd say it shouldn't be the issue especially as it's been fine for a long time with no BSODs (only recently they started appearing). However, I'll uninstall it.

For the Intel Driver Update Utility, it gives me: "Windows can't open this type of file (.bat)". I suppose the associations are messed up? How do I set Windows to open .bat files normally?

As for xqhdrv.sys, I followed that advice before and indeed those files (the ones the website mentioned) were there and I deleted them, but the website doesn't say anything about xqhdrv.sys.

EDIT: Nevermind about Intel Driver Update Utility, found the fix. Regedit folder in HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.bat and set Default to batfile.

EDIT2: Uninstalled Rivatuner, however its driver file still persists and it can be seen in Driver Verifier even after turning off Driver Verifier and turning it on again (deleting settings, and rebooting).

EDIT3: I was able to get rid of the RivaTuner driver file, it seems uninstalling RivaTuner was not enough. I also had to uninstall MSI Afterburner.

 

It might not be the issue. I am not forcing you to uninstall it, I am just trying to narrow down an issue.

.bat is normally ran with cmd as batch is a type of coding language for command line. Did you try this install? Download Intel® Management Engine Consumer Driver for Intel® NUC

I will take a look more at this driver, and reply with what I find.

 

The Intel Driver Update Utility kept failing once I tried updating, instead I downloaded and installed this: Download Intel® Chipset Device Software (INF Update Utility)

Not sure about the Intel driver you linked, the one I linked might be more appropriate?

 

Looks solid to me. For now we can standby until there is a new BSOD.

 

But we still haven't fixed the xqhdrv.sys issue. Should I delete it or what?

There's also e2xw10x64.sys and bcmsmbsp.sys which I had questions about above.

 

Our main focus is the BSODs. On the side I will see what I can figure out about these drivers. But we won't know if they are causing the BSODs until the next one.

 

I deleted xqhdrv.sys, since it seems to be related to VirtualBox and shouldn't hurt at all since I've already uninstalled it.

Regarding the network drivers (e2xw10x64.sys), I updated them as, conveniently, it seems the last drivers were released on 15 August: Killer Networking - Standard Drivers

Now I'm going to turn on Driver Verifier again and keep searching for bcmsmbsp.sys to find out why I actually have it.

 

Just got a BSOD again, but this time it was "WORKER INVALID". Here are the debug files.

 

I apologize for the late reply!

The type of errors I am getting from your dump files are starting to point more towards memory. I would suggest doing a MemTest86+ - Test RAM - Windows 10 Forums just to be safe.

Please let it run for a minimum of 8 passes! Once it is done with it's 8th pass. Post back results, and we will go from there.

 

Hey,

I'll get to the memory test soon.

However, I have one more question. Before, I had the "Write debugging information" in "Startup and Recovery" set to "Small memory dump", but "Automatic memory dump" seems to be better, so I set it to that. It did however, warn me that I need 800 MB at least page file or something, but I set my C: drive (the SSD, and where I have my operating system of course) to system managed and no page file on the rest. What should I set these to?

 

Are you talking about setting the dump files to the correct settings? This tutorial should help you with that: BSOD Minidump - Configure to Create in Windows 10 - Windows 10 Forums

 

I looked at that, but it doesn't give the necessary information that I need.

1. It doesn't recommend which one to use, merely states how you can change the settings.
2. It doesn't tell me how the page file should be set up.