Crash Logs Enabled but Not Being Generated.

Toggle sidebar Toggle sidebar
Soul Hacker

Soul Hacker

Distinguished
Oct 17, 2015
52
0
18,640
I've been trying to figure out the cause of some very erratic and rare BSODs but I'm not having any luck, so I'd love to post crash logs for someone to analyze but .. there aren't any.

I asked here quite awhile ago, how to enable those and followed his instructions and verified that this process does enable crash logs, however, there are still no crash logs being generated.

When I receive a BSOD, it says akin to:
Generating Crash Logs ..

However, even after leaving it sitting there for several minutes, it did not proceed with the process and the locations where dumps should be located, are devoid of such.

So, if anyone would be as so kind as to lend a hand, it would appreciated. If crash logs are truly enabled, which it says it is trying to generate them .. then why are there none being generated?

I've read somewhere that crash logs have problems being generated on a Solid State HD, is this true or untrue? If untrue, then what else would prevent crash logs from being generated?
 
Solution
nukemaster
Freezing before being able to dump memory or the drive not responding would prevent them from being written.

If you look at the stop code it may help you track them down.

SSD's write memory dumps just fine. I do not see a reason a SSHD would not, but I do not have one to test with.
Sort by date Sort by votes
nukemaster

nukemaster

Titan
Nov 23, 2004
19,626
6
74,965
Freezing before being able to dump memory or the drive not responding would prevent them from being written.

If you look at the stop code it may help you track them down.

SSD's write memory dumps just fine. I do not see a reason a SSHD would not, but I do not have one to test with.
 
Upvote 0 Downvote
Solution
Soul Hacker

Soul Hacker

Distinguished
Oct 17, 2015
52
0
18,640
Well, the sound jams prior to going to the BSOD. It goes to the BSOD after, so I have no idea if the system is completely jammed at that stage or not. I hadn't quite thought of that, but that might explain it. It's frustrating because I need to know what's happening but I can't get logs on it. And the errors and stop codes change constantly, or have been, so there's little consistency.

But thank you for the answer. If there's no other potential explanations, then that's all I needed to know for this question. I'll probably open a new forum topic soon, seeking additional help to track down these BSOD causes.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom