Overclock.net banner

1 - 8 of 8 Posts

·
Registered
Joined
·
1,237 Posts
Discussion Starter #1
Just turned on my PC after an hour of it being shutdown and I am getting blue screens. BCCode 51. Turned my OCs to stock and still continuing. Ran a Chkdsk and no errors. Can anyone help me with this? Uploading my dump file to anyone that wants to help.

080813-21886-01.zip 22k .zip file
 

Attachments

·
Premium Member
Joined
·
14,173 Posts
Hi,

Moved to the proper forum.

In regards to your dump, it's of the REGISTRY_ERROR (51) bugcheck.

This indicates a Registry or Configuration Manager problem. An I/O error may have occurred while the Registry was trying to read one of its files (caused by hardware or file system corruption).

This is a very difficult bugcheck to solve as in most cases it's simply file system / registry corruption and best choice is to reinstall Windows. However, before that, we can try and salvage your current install.

Update to Service Pack 1 ASAP: http://windows.microsoft.com/en-us/windows7/install-windows-7-service-pack-1

1. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

2.

SFC /SCANNOW:
Quote:
What does running SFC /SCANNOW do?
The sfc /scannow command (System File Checker) scans the integrity of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible.
To run the SFC /SCANNOW command in Windows 7:
- Open an elevated command promt (run cmd as administrator).
- In elevated command prompt, type "sfc /scannow" without the quotes, and press enter. Do note this can take some time to finish.
To see and read only the "SFC" scan results from the CBS.log:
- Open an elevated command promt (run cmd as administrator).
- Copy and paste the following and then press enter:
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >C:\sfcdetails.txt
This will create a file called sfcdetails.txt at the root of your system (C:\) containing only the SFC scan results from the CBS.log.
Regards,

Patrick
 

·
Registered
Joined
·
1,237 Posts
Discussion Starter #3
Quote:
Originally Posted by pjBSOD View Post

Hi,

Moved to the proper forum.

In regards to your dump, it's of the REGISTRY_ERROR (51) bugcheck.

This indicates a Registry or Configuration Manager problem. An I/O error may have occurred while the Registry was trying to read one of its files (caused by hardware or file system corruption).

This is a very difficult bugcheck to solve as in most cases it's simply file system / registry corruption and best choice is to reinstall Windows. However, before that, we can try and salvage your current install.

Update to Service Pack 1 ASAP: http://windows.microsoft.com/en-us/windows7/install-windows-7-service-pack-1

1. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

2.

SFC /SCANNOW:
Regards,

Patrick
Thank you for moving this post and replying. After posting here I did a ton of stuff, Ran CCleaner, scanned with Malwarebytes and Spybot, and ran Advanced System Optimizer. Mainly registry fixer and optimizer. Apparently one of those things fixed it (knock on wood) because when I booted up this morning its doing fine. I will unistall Daemon Tools still though. Thanks for the heads up on that, never even use it anymore.

Kind of disappointing. Cuz if I had to reformat it would have given me an excuse to upgrade my SSD.
 

·
Premium Member
Joined
·
14,173 Posts
Hi,

Great to hear. I imagine of all the things the registry cleaner fixed it (which is a huge surprise as registry cleaners and fixers 99% of the time do the complete opposite). Keep me updated on the system behavior.

Regards,

Patrick
 

·
Engineer of Malcontent
Joined
·
5,770 Posts
Sorry I know this is an old thread but curious as to why you said registry cleaners like CCleaner 995 of the time actually hurt the registry. Can you explain? thanks in advance.
 

·
Premium Member
Joined
·
10,773 Posts
Quote:
Originally Posted by Dimaggio1103 View Post

Sorry I know this is an old thread but curious as to why you said registry cleaners like CCleaner 995 of the time actually hurt the registry. Can you explain? thanks in advance.
Its not that they HURT the registry (although they certainly can!) - its just that they don't do it any good either. There's no benefit to running one.
 

·
Premium Member
Joined
·
14,173 Posts
Quote:
Originally Posted by Dimaggio1103 View Post

Sorry I know this is an old thread but curious as to why you said registry cleaners like CCleaner 995 of the time actually hurt the registry. Can you explain? thanks in advance.
First off, one big thing about registry cleaning is it is by no means and should not be a computer maintenance task. Clearing your browser's cache and cookies every week? Great, no harm there. Running your favorite registry cleaner every week? NOT GREAT.

If we're being honest and straightforward here, cleaning the registry is an entirely unnecessary thing to do. So far, what I've said makes it sound like I despise registry cleaners. Do I? No, I don't despise them, but as I said, they are unnecessary and if used carelessly can render your Operating System a paperweight.

So why would you even use a registry cleaner in the first place? Well, they have to do something right or they wouldn't even be allowed to be sold (if paid for) or if they were free (CCleaner for example) there would be a huge backlash, more than what there already is in IT with regards to opinions based on registry cleaners.

Registry cleaning software is useful mainly for one thing, and it can be done very well depending on the algorithm the cleaner software itself is using, and that's removing remnants of old uninstalled software or entries with now invalid path names. At times, it can also possibly be useful for removing traces of malware that may have been stored in the registry that was not successfully removed after running a virus scan, etc.

Other than that, it's not going to do anything. It will not increase your system's performance by any means whatsoever. Nothing noticeable. A 'smaller registry' in theory would have one assume that things load faster, etc, but in reality there is no performance difference whatsoever.

For reference, take a look at this:

Mark Russinovich (Author of the "Bible", Windows Internals, co-founder of Winternals and Sysinternals, and since both companies were bought by Microsoft, now a senior Microsoft employee) was asked:





Hi Mark, do you really think that Registry junk left by uninstalled programs could severely slow down the computer? I would like to 'hear' your opinion.



His reply:


No, even if the registry was massively bloated there would be little impact on the performance of anything other than exhaustive searches.

On Win2K Terminal Server systems, however, there is a limit on the total amount of Registry data that can be loaded and so large profile hives can limit the number of users that can be logged on simultaneously.

I haven't and never will implement a Registry cleaner since it's of little practical use on anything other than Win2K terminal servers and developing one that's both safe and effective requires a huge amount of application-specific knowledge.

So, to sum all of this up:

Q: Will using a registry cleaner increase the speed and/or performance of my system?

A: No.

----

Q: Why would I even use a registry cleaner then?

A: I personally wouldn't use one whatsoever and would find the problem you're specifically having and take care of it manually. That is much safer. However, the main use of registry cleaners is to again as stated above, remove remnants of old uninstalled software or entries with now invalid path names. At times, it can also possibly be useful for removing traces of malware that may have been stored in the registry that was not successfully removed after running a virus scan, etc.

----

Q: What is the true danger of using a registry cleaner?

A: You have to remember what you're using is an automated tool that is not perfect by any means. You are putting your trust in an automated tool to be absolutely sure every key it is about to delete is 100% unnecessary. At times, and I have seen it personally myself PLENTY, it can delete a very important key that is necessary to the functionality of your Operating System in some form or another.

----

Q: What if my registry is corrupt, will running a registry cleaner help?

A: Absolutely not.
 

·
Engineer of Malcontent
Joined
·
5,770 Posts
Wow as a owner of a PC repair shop I am ashamed I ever vouched for its legitimacy. Just goes to show there is always something new to learn. Plus imaginary rep good sir.
 
1 - 8 of 8 Posts
Top