New
#21
That sounds great, thanks to Noel. I hope your good fortune continues.
So my good fortune lasted a few days. Then on a restart it did a system check and "fixed" a bunch of things that it found wrong. After it booted back up the BSOD's are back. I am attaching both the latest DM log output as well as the CBS.log file.
Kharma, You had 2 dump files for 5/26
Code:MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000000411, The subtype of the bugcheck. Arg2: fffff6fb831fd218 Arg3: 000000000000fa00 Arg4: fffff68000000003
You don't list what SSD you have, but please make sure you have the latest Firmware.Code:BAD_POOL_HEADER (19) The pool is already corrupt at the time of the current request. This may or may not be due to the caller. The internal pool links must be walked to figure out a possible cause of the problem, and then special pool applied to the suspect tags or the driver verifier to a suspect driver. Arguments: Arg1: 0000000000000003, the pool freelist is corrupt. Arg2: fffff8a0030e5840, the pool entry being checked. Arg3: fffff8a0030e5840, the read back flink freelist value (should be the same as 2). Arg4: fffff8a010cb63d0, the read back blink freelist value (should be the same as 2).
That is the second dump naming memory. With 32Gb of ram, it will take about 40 hours to run Memtest86+. From my perspective, a memory error is the worst error to have. When memory throws an error, the debugger will name almost any driver. So, that makes any dump file not reliable. I would like to try one other thing before you run memtest86+, however there is a possibility you will end up with a clean install of the OS. I have never had it happen to me, but it is still possible. I would suggest you back up all personal files to an external source.
The first thing is to make sure your SSD has the latest Firmware. I would also like you to run Seatools for DOS on your non SSD drive, both the long and the short test. SeaTools for DOS and Windows - How to Use Also please run check disk on it Disk Check
Next I would like you to create a restore point before going any further. The link for how to do that is below. When you are setting this up. Please sort the drivers by Provider and select all drivers NOT provided by Microsoft. Please run it for 24 hours of actual use. There are no restrictions. Do anything you want to. The test puts extra strain on the drivers in hopes that the bad driver will make the computer BSOD and the bad driver will be caught.
WarningBe sure to create a System Restore point before proceeding further System Restore Point - Create
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Information
What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.
What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.
Warning
Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. make a System Restore Point manually before enabling DV.
Tip
- If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
- If you cannot boot in Safe mode, do a System Restore to a point you made earlier.
Let us know the results, with the subsequent crash dumps, if any.
There are no errors in the background CBS data - and only the 'expected' errors in SFC.
Try uninstalling KB3022345 and hiding it.
Does that help?
I can confirm that removing KB3022345 has resolved the issue with CBS.log.
I am now working on taking the other steps provided.
Here is a breakdown of results so far:
Disk Check -- No issues found
SEATools for DOS -- No hard disks found
First run of Driver Verifier -- Cause a blue screen due to Razer Synapse driver.
I have removed the Razer Synapse program (and the associated driver) and am retesting now.
Will do tomorrow as the driver verifier is running currently and I want to give it the 24 hours to see if anything breaks.
Alright, it blue screened again this already (didn't even make it 3 hours
I have attached the information gathered from the DM Log Collector to this post.