Windows 10: Random BSODs - can be a few per day, or a few days between BSODs

Hi,

I would really appreciate it if anyone could shed any light on this. The PC was originally Windows 7 and I upgraded to Windows 10 last year.

The crashes seem to be random, sometimes when it's sitting idle, sometimes whilst I'm working.

I have run METEST86+ for 11 passes (18 hours!) and got no errors.

Can anyone help?

Thanks

:)

 

BSOD every few days

Did you also check with Logitech Support and Forums to ask if this is a known issue.

Check that you also have the latest chipset drivers as well as the BIOS.

You could let it run the memory tests at night.

Also:

Troubleshoot blue screen errors <-- read this link

http://windows.microsoft.com/en-us/windows-10/troubleshoot-blue-screen-errors

Please do let us know the results and we are here to help if needed.

Rob - SpiritX

 

BSOD every few days

I am not yet sure if the problem is fixed.

I have not had errors since I posted the question but it can take more than a week to get one.

So far I've reinstalled cleanly the nvidia drivers a few times and I've kept the driver up to date for the past year so I doubt this is the problem.

The BIOS was updated a couple of weeks ago with the latest version and I reinstalled the Logitech software a day ago.

On the weekend I will reinstall all the other drivers, reseat the hardware and run driver verifier again.

 

Two of the latest dumpfiles are
Code: BugCheck 12B, {ffffffffc00002c4, 3e9, 38e5fd0, ffffe000181ee000} Probably caused by : hardware ( REGION_PAGED_OUT ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* FAULTY_HARDWARE_CORRUPTED_PAGE (12b) This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error. Arguments: Arg1: ffffffffc00002c4, virtual address mapping the corrupted page Arg2: 00000000000003e9, physical page number Arg3: 00000000038e5fd0, zero Arg4: ffffe000181ee000, zero Debugging Details: ------------------ DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_STR: PAGE_NOT_ZERO CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: MemCompression[/quote] To be sure run memtest 86+ again.
.Please start with diagnosing the system RAM first.
You can use the free tool "Memtest86+"to stress test the RAM.
MemTest86+ - Test RAM
Make sure you are using the latest version 5.01 - Memtest86+ - Advanced Memory DiagnosticTool
You can stop the test even if a single error is found during the test.Otherwise continue the test for 7-10 passes and post a screenshot with next reply. 7 passes is the recommended bare minimum but more passes will give better result.

If memtest 86+ gives no errors.
Please test your harddrive.
To check/analyse the integrity of your HDD you can use Sea Tools
Download from here SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Windows has this program chkdsk See for info and how to use
Drive Error Checking in Windows 10

 

Hi Lifetec,

Many thanks for looking at this for me.

I wasn't sure how to get some of the results in file formats so I've attached images - hope that is OK. In SeaDisk I couldn't see how to get more detailed results but I can easily run this again if needs be.

Thanks

Dave

 

Hello Daveben *Smile

I notice you are running Kaspersky. This has been known to trigger BSOD events. I would try running without it for a while and see if it makes a difference. You can safely use Windows Defender instead.

 

Thanks Phil,

I've turned off Kasperksy and turned on Windows Defender. I'll report back in due course.....

 

Don't turn off Kaspersky, uninstall it. Turning it off does not remove it's drivers and they can still cause problems.

 

Hi Ztruker,

Switched on the PC about 15 minutes ago and just had time to read your message before it crashed again - at least this confirms that switching off Kaspersky is not the answer.

It then suffered another crash a few minutes later - just as I'd got into the remove applications screen.

Third time lucky - Kaspersky has now been uninstalled. I'll report back later.

Thanks

Dave

 

So close....

Since removing Kasperksy I've had nearly four days of use without incident and was all set to come on here and report it fixed - until a couple of hours ago when it crashed again.*cry

I have attached the latest dump file.

Thanks

DaveAttachment 118217

 

Actually, if you can post a complete new set of log files it will be more helpful.

 

Hi,

File attached.

Thanks

 

There is something corrupting the memory - its either the RAM itself or a driver writing bad information to the memory.

As you have already tested the RAM I still think there is a rogue driver somewhere. We can use Driver Verifier to try and flush out the culprit.





Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please read and run driver verifier.

If you suspect a driver is causing a problem but do not have a clear idea which one it is then Driver Verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or until you have a bluescreen, whichever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset driver verifier from within safe mode, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

HELP!!!
I've enabled the driver verifier and now the machine won't boot - it's stuck with a windows logo and a spinning circle. I can't see how to get to any of the options to disable the driver verifier since it hasn't got past this screen. How do I disable the verifier?

Thanks

Dave

 

I don't know if it's still working and might not be the best approach so wait for more opinions and use this as last resort.
If you reset the PC right after you get the windows loading screen, after 3-5 times you should get the recovery screen.

I don't know why MS got rid of the old F8 option to boot in safe mod..