It is a computer that I built myself and it has constantly blue screened on me since it was built. Sometimes it will go a couple days in between and other times it will just be one after another after it reboots itself. I believe I correctly attached the dump files. Any help would be appreciative.
Last edited by Chris Hansen; 26 Jan 2013 at 23:47. Reason: Changed .rar to .zip
Hello Chris!
Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
InformationWhy Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.
How Can we know that DV is enabled:
It will make the system bit of slow, laggy.
WarningBefore enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.
If there is no points, make a System Restore Point manually before enabling DV.
Test your RAM modules for possible errors.Tip
- If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
- If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
Scan the system for possible virus infection.
Let us know the results.
I am back again with more issues. The original problem never got fixed and I seem to have even more now. I really hope that somebody here can assist me.
Recommend you follow up on previous advice.....don't leave it for 15 months, and then reply here hoping for a fix.
Counterfeit installations such as yours contains heavily modified code that causes the installation to behave it unexpected ways. Analysing BSOD's and determining their causes on these sorts of installations is very unreliable.Code:Host Name: CODY-PC OS Name: Microsoft Windows 7 Ultimate OS Version: 6.1.7601 Service Pack 1 Build 7601 OS Manufacturer: Microsoft Corporation OS Configuration: Standalone Workstation OS Build Type: Multiprocessor Free Registered Owner: CODY Registered Organization: Product ID: 00426-OEM-8992662-00173
My recommendation is to start with a clean slate, and install a genuine version of Windows. This will minimise the problems you are experiencing, and make subsequent diagnosis of BSOD's far more reliable. Once you are running a genuine Windows installation, and are still experiencing BSOD's, we will be happy to help you solve them.
The rules said not to make a new thread and to just post in your previous one... I didn't see a time limit anywhere. The original BSODs were fixed with that advice which is why I left it alone. I seem to have a whole new host of issues now.
