[SOLVED] Mini Crash Dump/ BSOD

ssherjj

ssherjj

Sysnative Staff
Microsoft MVP
Contributor
Joined
Sep 28, 2017
Posts
501
Location
New York
Hello Sysnative! Long time without any BSODs. I believe my system crashed on 2 occassions. Could of been more in the last couple of days. I'd appreciate if someone could read the Mini Dumps and see what is causing these issues.
 

Attachments

Hi @zbook,

1) Upgraded the Bios as suggested:1.9.0 > 1.10.0

2) I will run the Driver Verifier as soon as I can.

Thank you so much for your quick assistance.
 
Not in the last couple days, but just to give an overview of the crashes since the last install date. Note that this 'install date' is changed with reinstalling Windows, a feature update or with an in-place upgrade.
Code: 
   2020-11-03T12:15:22.8070000Z        The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000139 (0x0000000000000003, 0xffff808904e4a280, 0xffff808904e4a1d8, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 521fce19-cd65-40fb-99f5-41261019b0c1.
   2021-03-29T10:04:31.6160000Z        The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000018 (0xffffa807088c34e0, 0xffff92899637b770, 0x0000000000000001, 0x0000000000000003). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: ace5dd1c-89b4-4624-8226-e5d62579373e.
   2021-04-01T18:26:59.6560000Z        The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0xffff960447b47b18, 0x0000000000000002, 0x0000000000000000, 0xfffff80050683145). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 873979ae-6036-498d-bcf4-3c6ba92657d7.
 
Hi there @axe0 ...I noticed crashes after the last 1 or 2 Windows updates. So I meant to mention that but over looked it I guess with uncertainty. I'm not at my computer right now but will be tonight! Thank you much for showing me that info.
 
Hello @zbook

I followed the instructions for Driver Verifier twice and twice I have had to use System Restore because Windows would not start back up. My system did go into Dell Support Assists (F8) and was checking the Memory Hardware. I hit escape and rebooted into Advanced/ System Restore and I am back to that restore point. But I want to mention upon rebooting after applying Driver Verifier settings the reboot froze up and I had to force a shut down on my system and restarted into System Restore.

Any ideas? Or just keep an eye on things?
 
From the two dump files that I've seen, the IRQL checks option is probably the only one which would be worth running in your situation. I would have suggested object tracing, however, we've only got a generic tag to use and therefore you'll probably end up tracing several different objects which are irrelevant.

Have you tried doing a clean boot? Disabling all programs which aren't necessary and then seeing if the crashes continue? I know WebRoot has caused BSOD problems in the past, but I'm a little reluctant to suggest remove it since we can't be certain that it is problem at this moment in time.
 
Thank you @x BlueRobot for chiming in. Yes, Webroot has caused a few BSODs in it's time but usually if Webroot causes a BSOD I would find it in the ProgramData Folder under WRData...usually but not always....but I'll definitely do a Clean Boot. That's simple enough. And will keep you all posted if that's ok? 😊
 
The tool is designed to keep producing BSOD until it is turned off.

There are multiple methods to turn off the tool.

The first method to turn off the tool is to open safe mode > run: verifier /reset

In case safe mode with command prompt verifier /reset does not turn off windows driver verifier then navigate in the windows advanced trouble shooting menu to command prompt.

This is where you will see X:\windows\system32\cmd.exe

Enter the command: verifier /bootmode resetonbootfail to turn off windows driver verifier.

If the above commands do not turn off the tool the use system restore.

If system restore fails the turn off the tool using the registry.



For any BSOD run the Sysnative log collector to collect new log files.
 
Hi,

The Tool is turned off. I did go into safe mode < run: verifier /reset. I have not had a BSOD since this morning. I am going to do a clean boot and try that now. But if I get a BSOD I will run the Sysnative log collector again for new logs. Thank you zbook!
 
x BlueRobot said:
Have you had any more crashes since?
Click to expand...
Good Morning! No I have not had anymore crashes since the last time I reported. Everything seems to be running great. (knock on wood). Thank you for asking! Perhaps the updated Bios sorted that out? Oh and I did a clean boot!
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top