The dreaded BSOD has started to strike me again Help please guys

[steve-pressman]

Can you Guys please let me know what is going on with my Rig and why I am getting these BSOD's.

I am aware of the USB and Samsung problem

Many thanks

Steve

 

[zigzag3143]

Can you Guys please let me know what is going on with my Rig and why I am getting these BSOD's.

I am aware of the USB and Samsung problem

Many thanks

Steve

Hi Steve and welcome

These crashes were caused by memory corruption (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!!!


1-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



2-Driver verifier

I'd suggest that you first backup your data 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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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"
- 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).

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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[steve-pressman]

Thanks Zig I will run the Mem test first and see what happens and then the Driver stress teat and get back to you all.

Steve

 

[steve-pressman]

Just to clarify on the Driver Stress test if and when I get the BSOD's do you want me to keep testing and then maybe in say 48 hours uploads the BSOD dumps ?

Steve

 

[zigzag3143]

Just to clarify on the Driver Stress test if and when I get the BSOD's do you want me to keep testing and then maybe in say 48 hours uploads the BSOD dumps ?

Steve

After a crash or two you can upload the dmps. No need to wait 36 hours and you can turn verifier off by typing verifier /reset.

 

[steve-pressman]

Ok ran the mem test for 24 hours solid and no errors. It then occurred to me that after a failed boot the system had reverted the bios back to original settings, I then went into the bios and put my custom OC settings in and saw that the ram timing were wrong previously so changed them to what they are meant to be and and so far after punishing the system for the last 12 hours no crash, no BSOD and all seems to be well again. So I guess it was the ram timings that were wrong.

Steve

 

[zigzag3143]

Ok ran the mem test for 24 hours solid and no errors. It then occurred to me that after a failed boot the system had reverted the bios back to original settings, I then went into the bios and put my custom OC settings in and saw that the ram timing were wrong previously so changed them to what they are meant to be and and so far after punishing the system for the last 12 hours no crash, no BSOD and all seems to be well again. So I guess it was the ram timings that were wrong.

Steve

Good Work Steve. If you agree you should ask them to mark this solved

 

[steve-pressman]

Looks like I spoke to soon although I don't think it is the ram. I ran the driver stress test and managed to get to the log in screen and it crashed to a BSOD so I tried once more and the same thing again so I guess it might well be driver related. Had to go to safe mode to get back in and stop the verifier so I could upload the latest dumps, I hope this will give us an insight as to what is wrong.


Steve

 

[zigzag3143]

Looks like I spoke to soon although I don't think it is the ram. I ran the driver stress test and managed to get to the log in screen and it crashed to a BSOD so I tried once more and the same thing again so I guess it might well be driver related. Had to go to safe mode to get back in and stop the verifier so I could upload the latest dumps, I hope this will give us an insight as to what is wrong.







Related to tdrpm273.sys Try&Decide Volume Filter Driver from Acronis

 

[steve-pressman]

What would be your recommendatory course of action ?

Steve

 

[zigzag3143]

What would be your recommendatory course of action ?

Steve

Steve I had the same problem with Acronis on windows 8 and had to end up removing it.

I would at least update to the newest version of Acronis.

 

[steve-pressman]

I have just updated it now to the latest version so will see what happens if not time to look for another solution.

Thanks

Steve