Blue screens are back

[xniosy]

Following this thread: Unexplained & Unresolved BSOD's. Desperate for help.

After a month or so of no crashes (After lowering the memory frequency) they've suddenly returned from the grave. 3 Crashes within a few days while doing everyday tasks.

Any help is appreciated.
Thanks!

Info here:
MEGA

 

[axe0]

Hi xniosy,

Please try the following
- Update or reinstall the wifi USB adapter drivers
- Reinstall or downgrade the nvidia display drivers

 

[xniosy]

Hi axe,

- Used DDU on the nvidia drivers to downgrade to a December release.

- Re-installed the WiFi adapter drivers. TP-Link's site displays the latest ones for 8.1 as "2015" however when they are installed they display in Device Manager as "2014". Some files in the "2015" zip have 2015 as the date of modification and others as 2014 so I'm guessing that's normal.

There is also a beta driver that was published in 2016 with even later files. Would you recommend me using this one instead?

 

[axe0]

I would only recommend beta version if it contains bugfixes that are specific to your problem.

 

[xniosy]

It doesn't.
I will post an update if anything changes.

Thanks.

 

[xniosy]

Two more out of nowhere. Playing Battlefield 3 and performing a scan on Windows Defender:

MEGA

do you think these are random? They seem to be different compared to the usual ones.

 

[axe0]

Since the dumps are a bit spread, could you upload them at once in a folder on MEGA and provide a share link for it.

For everything else, please upload anything requested directly unless it's too big, that would be easier for us both

 

[xniosy]

No problem,

FOLDER MEGA

 

[axe0]

Sorry for the delay in response.

Please run driver verifier using the following settings for 48 hours.

• Special Pool
• Force IRQL checking
• Pool Tracking
• Deadlock Detection
• Security Checks
• Miscellaneous Checks
• Power framework delay fuzzing
• DDI compliance checking

Warning: driver verifier can cause boot issues and/or performance issues.

• Make sure that you have recovery media, if needed you can create it.
• Configure a restore point prior enabling driver verifier.

Resetting driver verifier options (recommended in this order)

1. In normal mode open an administrator command prompt and enter the below command
2. In safe mode open an administrator command prompt and enter the below command
3. On 3 boot failures, you'll boot automatically to the recovery options,
   • click Troubleshoot
   • go to the advanced options
   • choose command prompt
   • enter the below command
4. Boot with the recovery media, see above 4 steps in option 3.
5. Via the recovery options or recovery media, select a restore point prior enabling driver verifier

verifier /reset

Crashed when running driver verifier

1. Reset driver verifier
2. Boot in normal mode if necessary
3. Follow Blue Screen of Death (BSOD) Posting Instructions to provide the requested logs

 

[xniosy]

Thanks^
Is there a specific type of dump I should let it make for this?

 

[axe0]

Standard configuration is good, standard configuration will make a kernel memory dump and small memory dump which is all that's needed.

 

[xniosy]

It's been running for just over an hour, minor mouse freezes at the start. No crashes yet.
I've set it to kernel memory dump.

Third party drivers listed during the verifier setup:

From the point of the last BSOD (18th Feb), I uninstalled the TP-Link drivers for my WiFi adapter and I've now been using a power line adapter instead, to rule that one out.

asio.sys is something from Asus which I will remove.
No idea what "mpksl7aacaa98.sys" is.

Had a quick look at driverquery, revealed this thing at the bottom:

Any ideas on what these could be?


I will leave Driver Verifier running up to 48 hours if no crashes have occurred up to that point.

Thanks.

 

[axe0]

asio.sys is part of ASUS PCProbe Utility
Driver Reference Table - AsIO.sys

mpksl7aacaa98.sys is a Windows Defender driver

 

[axe0]

FYI, any dump_*.sys drivers can be ignored. Those are copies of the original driver and reserved for accessing the RAM and disk when a dump is created.

 

[xniosy]

BSOD while playing Battlefield 3. I've uploaded the zip to the folder.

"SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION"

 

[axe0]

Could you upload the kernel dump (memory.dmp), the minidump contains too little data.

 

[xniosy]

That's the thing. It didn't create one.

It's not where it's supposed to be or anywhere else on my computer.

 

[axe0]

That would be due to lack of free space.

Standard Windows requires a partition to have 10-15% (10 on large drives) free space (for maintenance and performance), but with crashes Windows has the rule of at least 25GB free space to save dumps on the Windows drive.

 

[xniosy]

I thought that would be the cause. Only 19GB free on my OS drive. Total physical memory 24GB.

Would it work if I set the dump location to one of my other drives? Or will I have to clear space to 25GB?

And then begin on creating another crash..

 

[axe0]

Easiest would be to clear the space on the partition.