Hello,
Since getting this computer I have had issues. After running Windows updates, I started getting consistent BSOD. I rolled back the updates and turned off updating for awhile, but recently decided to give them a try again. Once again, I can hardly run the computer, let alone do anything demanding, without crashing in BSOD.
SFdebugFiles.zip
I gave up on the dm_log_collector zipping the files (it as it always came out empty) and zipped it myself.
Thank you all for your help!
The zip file you uploaded is empty.Can you try again?
I ended up zipping the files myself outside of the program, and have attached them to the original post. Thank you for your help with this!The zip file you uploaded is empty.Can you try again?
Somewhat better. The most recent one, 031016-26703-01.dmp is corrupt.
Others keep showing ETW minidump data unavailable.
Please make sure your pc is configured for small dump files How to configure minidump | Windows 10 tutorial.
Also, move all esiting mini dumps from C:Windowsminidump to another place to save them for now, so that only new dumps will show up there in the future.
DO some testing and when you get a BSOD, upload the dump here (zipped) please.
I have removed all of my previous dumps and have configured to collected minidumps. I am waiting for another crash.Somewhat better. The most recent one, 031016-26703-01.dmp is corrupt.
Others keep showing ETW minidump data unavailable.
Please make sure your pc is configured for small dump files How to configure minidump | Windows 10 tutorial.
Also, move all esiting mini dumps from C:Windowsminidump to another place to save them for now, so that only new dumps will show up there in the future.
DO some testing and when you get a BSOD, upload the dump here (zipped) please.
THANK YOU!!
Three BSOD today within using for an hour. Please find the dumps attached.
Thank you!
3-11 Dump.zip
The new dumps are all the same.which doesn't tell me much.Code:CRITICAL_PROCESS_DIED (ef) IMAGE_NAME: csrss.exe DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: csrss FAULTING_MODULE: 0000000000000000 PROCESS_NAME: csrss.exe
Let's see if doing a Clean Boot eliminates the BSOD. Clean Boot - Perform in Windows 10 to Troubleshoot Software
Test for awhile and if no BSODs then follow the directions To Troubleshoot Software Conflicts in a Clean Boot.
I've launched in a Clean Boot and will let you know how it goes.The new dumps are all the same.which doesn't tell me much.Code:CRITICAL_PROCESS_DIED (ef) IMAGE_NAME: csrss.exe DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: csrss FAULTING_MODULE: 0000000000000000 PROCESS_NAME: csrss.exe
Let's see if doing a Clean Boot eliminates the BSOD. Clean Boot - Perform in Windows 10 to Troubleshoot Software
Test for awhile and if no BSODs then follow the directions To Troubleshoot Software Conflicts in a Clean Boot.
Thank you
If that doesn't help then it's time to try running Driver Verifier and see if that gives us any useful info to work with.
See here: Driver Verifier - Enable and Disable in Windows 10
Take it step by step:
Part One: Run Driver Verifier
Part Two: Configure Driver Verifier Settings and Enable
Part Three: Disable Driver Verifier
No luck so far in getting a BSOD Clean Boot alone or in Clean Boot and trying for software conflicts. I have run driver verifier, please find the minidumps attached.If that doesn't help then it's time to try running Driver Verifier and see if that gives us any useful info to work with.
See here: Driver Verifier - Enable and Disable in Windows 10
Take it step by step:
Part One: Run Driver Verifier
Part Two: Configure Driver Verifier Settings and Enable
Part Three: Disable Driver Verifier
Driver Verifier 3-11.zip
Thank you.
