Main Forum > General Computer Support

(SOLVED)BSOD out of the blue (pun intended)

<< < (4/5) > >>

Boggin:
With the free version of CCleaner you have more control over what you remove.

https://www.piriform.com/ccleaner/download

While it has a Registry Cleaner which is one of the safest, there's no real need to clean the registry and you can negate the need to use it to remove any residue following using Windows to uninstall a program, when you use a 3rd party uninstaller program.

https://www.piriform.com/docs/ccleaner/using-ccleaner

I'm always wary of these commercial "mechanic" programs as indiscriminate use of them can screw a system and quite often, the unwary/inexperienced let them loose on the registry where they clean indiscriminately.

While I don't know the program you are using, Advanced System Care and Uniblue Power Suite are two to steer clear of.

Shane:
I use the WhoCrashed program every time I am fixing a customers machine and there is a blue screen. It does a good job on letting me know what crashed.

But if it wasn't a driver or something specific that caused it and is something more general then it is normally due to hardware, such as failing hardware, bad hardware and even heat.

I looked over the posts but didnt see if you where able to run whocrashed and post what it said.

Shane

Boggin:
I think he'd run a cleaner before using BlueScreenView and WhoCrashed so neither found any dump files to analyse (Post#10).

Shane:
I have had that happen on a customers machine. The reason on the customers machine that there was no dump file was because the blue screen couldn't write it.

In this case, the blue screen was being caused by bad hardware not by something in Windows. In this case it turned out to be the hard drive was cutting out and so Windows couldn't write to it if it wanted to. Other times it was the motherboard that was going out and the sata channel was of course not responding and so windows couldn't write the dump file either.

As for the one customer their hard drive was dieing and when it got to a certain temp the drive would just cut out. I had to try and get their data off of it, so I put ice in two zip lock bags, then wrapped small towels around the bags and had the hard drive sit in between the two making a sandwich with it and keeping the drive as cold as possible. I was able to get the data off the drive without it dieing on me since I could keep the temp down.

As for the other user who had a bad motherboard, there was nothing I could do there but replace the board. I knew it was the board because I hard swapped out everything else lol, cables, power supply (in case it was simply dropping power to the drive) and even the drive itself and it still happened. Once the motherboard was replaced it was good to go.

Point being that if Windows didn't write the dump file, then there is a serious reason why it couldn't.

Shane

Tacotardis42:
Hello Shane! Boggin is right, I acciently deleted junk files before I ran WhoCrashed, I verified that it was there after the crash, but I had no idea how to view it. And also, as far as I can tell the computer is fine a couple days after the shutdown. I also ran recuvva from piriform, but it did not find the dump file, so there is nothing more I can do as of right now. Should I mark this topic as solved, or is there some miracle that can be done :) Thanks in advance!

Navigation

[0] Message Index

[#] Next page

[*] Previous page