Before re-installing any drivers, it is a good idea to disable Verifier. It will generate false positives since it is trying to verify the drivers being re-installed. First, disable Verifier, and then re-install your graphics drivers again. Then re-enable Verifier and wait for more crashes.
Ok sorry for the delay but I was away from my the computer for most of last week so I haven't had time to try fix it.
Here are a few updates though. I was beginning to think this was a hardware issue so I borrowed my brother's computer which I had just built for him. It has the same motherboard only a different cpu, he only has an i3 instead of i5, I swapped the motherboards and cpus (I didn't feel like unmounting and remounting the cpu heatsinks) and now my brothers computer would get the BOSD even before loading windows so I of assumed it was the motherboard since I have already tried swapping out the ram as well. I ordered the new motherboard and installed it did a fresh install of windows installed all drivers but then I got the BOSD again. I hadn't setup the computer for mini numbers yet so I don't think I have those crash reports but I quickly set it up after that and got another BOSD while trying to installing some windows updates. I've swapped out the ram, the motherboard, used the graphics card in another computer and it worked fine. I tried using a different hard-drive but it I can't seem to install windows on it because every time it tries to expand finals I get an error message that says "Windows installation encountered an error verify that the installation sources are accessible" once I even got the BOSD before I got that error. and I just installed windows on this hard drive on another computer. I am completely clueless, if its not the motherboard, not the ram, hard drive or graphics card that means it could only be the psu or cpu. Can psu even cause a problem like this and I have never really heard of a bad cpu isn't that like a 1/100,000 chance. I was beginning to think they this was a hardware issue because I got the BOSD once while installing windows and once before drivers where even installed.
I have attached a few more dump finals.
Security Software: ??? Make sure to install security software. I recommend either of these:
- Microsoft Security Essentials - Free Antivirus for Windows coupled with Malwarebytes. Do not start the free trial of Malwarebytes. Just use the standalone version, update it, and scan your computer once a week with Malwarebytes and with Microsoft Security Essentials.
- Good and Free system security combination.
After installing your security software, update it, and then run full scans today with each program. Report back the results of the scans.
The following driver needs to be updated or the software removed:BIOS64.sys; This is probably aBIOSTAR I/O driver fileCode:BIOS64.sys Sat Jun 7 18:12:00 2003 (3EE27F50)
Let's check your RAM settings and compatibility:
- Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.
And yes, a CPU failure is rare, but not unheard of. I'd say it is more like 1/1000 chance. Your crashes point to memory, so it could be the memory controller at fault. It could also be that driver I keep mentioning that is really old.
I am a little confused about this motherboard driver, not sure which one I need to update because when I to the motherboard's driver page I don't see anything similar to it. Another question I have is why do they such an old driver on one of their newest motherboards? I am uploading my screenshots and getting ready to scan using the two programs you told about. I let you know what the results say.
You should set up your RAM to run with a command rate of 2/2T.
For the BIOSTAR driver, the date shown in another log is 8/8/2011. It may just be that BIOSTAR has a bad timestamp on that particular driver. A cursory Google search shows that driver a lot having the 2003 timestamp and none of the gurus have been able to get a more up to date driver or determine what that driver does, so I'll leave it be for now.
See if the RAM adjustment provides more stability. Almost all crashes point to memory issues.
If the RAM adjustment does not provide more stability, see if removing a RAM module does. Run with one module at a time in one slot at a time. Continue one module at a time in one slot at a time until you find a good module and good slot. Test remaining modules in the good slot, test good modules in other slots to find bad slots, etc.
Test by doing your normal routine in Windows for twice as long as it takes to get a crash or until you get a crash, whichever comes first. You can also test by doing the tasks that generally cause crashes.
As you add and remove hardware, follow these steps for ESD safety:
- Shut down and turn off your computer.
- Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
- Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
- Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
Once these steps have been followed, it is safe to remove and replace components within your computer.
Also, have you disabled Verifier since the last time you posted? If not, you should disable it prior to testing the RAM: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:verifier /reset-> Restart your computer.
I ran the scans and both came up with 0 problems how would I change the command rate to 2/2T? Thanks for you help so far.
There should be a setting in the BIOS. You will have to set your RAM timings/frequency settings to manual instead of auto. The first four timings should remain 9-9-9-24 and the command rate set to 2/2T
I managed to figure it out and switch it to 2/2t and it seemed to work fine for about a day but then I got the bsod again. I am still in the process of trying each piece of ram in each slot now but so far nothing has worked I am still getting the BSOD. Any other ideas. Thanks again
I just noticed you did not upload an image for each slot in the SPD tab for CPU-Z. Please do so to make sure the two modules are compatible.
Quote