Solved BSOD every day , cant take it anymore

[kadulitis]

Hello... I get a BSOD allmost everday .. first i thougt i was my memory modules ( ram ) so i got me a some from a buddy , but it was the same problem , then he told me to change my HDD , so i did that and after 1 days the same problem came ( BSOD ) so now i dont know what to do , so i hope u can help me out...
Windows 7 ultimate x 64 , full retail , my system is about 3 years old , but my GX card is only 1 year.
If yoy need to know more plz tell me.

 

[zigzag3143]

These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[kadulitis]

Ok now i made theese things , run memtest86 for 13 passes with no error ... and them i made the driver thing to , and i got 2 BSOD today
Here is the new file , hope you can see the problem, so i can solve it. I will allso add a picture

 

[zigzag3143]

Since your ram appears ok please run this

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

http://support.microsoft.com/kb/244617

 

[kadulitis]

i did that , and got 2 crasches ....

 

[zigzag3143]

i did that , and got 2 crasches ....

Upload the dmps.

 

[kadulitis]

i hope this is the file

 

[zigzag3143]

Not verifier enabled and related to memory corruption. You sure you have run memtest for the required 6-8 passes?

 

[kadulitis]

Memtest was running from 21:00 to 07:30 this morning... it says 13 passes.
Do you want me to do anything again ? just let me know and ill do it

 

[zigzag3143]

Memtest was running from 21:00 to 07:30 this morning... it says 13 passes.
Do you want me to do anything again ? just let me know and ill do it

Memtest seems ok, now move on to verifier

 

[kadulitis]

Im doing the verifier now...
Could my problem be my Harddrive thats was split i 3 ? cause when i was using that drive the problem happend alot , now i have deleted it and maked it to 1 harddrive , hope that it will be better now...

 

[zigzag3143]

Im doing the verifier now...
Could my problem be my Harddrive thats was split i 3 ? cause when i was using that drive the problem happend alot , now i have deleted it and maked it to 1 harddrive , hope that it will be better now...

Probably not the HD but need the DMPS to find out.

 

[kadulitis]

So now i got 2 fresh BSOD ;( ... hope u can see something from this file

 

[zigzag3143]

So now i got 2 fresh BSOD ;( ... hope u can see something from this file

Still memory corruption. We may have to go back and run memtest again. Are you overclocking?

 

[kadulitis]

No im not overclocking ... so u need me to run memtest again ? for how many passes ?
I will run it from now to i wake up in the morning.....

 

[zigzag3143]

No im not overclocking ... so u need me to run memtest again ? for how many passes ?
I will run it from now to i wake up in the morning.....

Well verifier just keeps returning memory corruption so we need to look elsewhere. My gut feeling is that it is a driver issue but it isnt being found.

Lets try memtest again one stick at a time. 6-8 passes

 

[kadulitis]

Okay I'm trying to do that

 

[kadulitis]

Both stick´s tested for 9 passes with 0 error

 

[zigzag3143]

Both stick´s tested for 9 passes with 0 error

OK so it obviously isnt RAM.

If it isnt RAM, you arent overclocking, verifier keeps saying memory corruption it has to be a driver verifier isnt catching. Since it isnt, you may want to start thinking about a clean re-install.

 

[kadulitis]

its only about 2 weeks since i made a clean re-install....and you are sure it isent my harddrive ? because allmost every time i try to unzip a large file from it , the BSOD happens
When i look at bluescreen viewer dump it says caused by driver ntoskrl.exe