Bad Driver causing BSOD??? Any help appreciated

[Davonator]

Please help!

I am consistently getting a range of different BSODs, however they are all coming up as being due to Locale ID 2057, which I gather is causede by a corrupt or incompatible driver. Problem is trying to locate this troublesome driver.

I hope I have done the zipping of my Mini Dump correctly. Any help would be much appreciated.

My system

Win7 Home Premium 64 Bit
8GB DDR3 Ram
700 Watt PSU
AMD Phenom II x4 'Black edition' 3.2Ghz
ATI Radeon 5670 1GB RAM
600 GB Hard Drive

you need any more details please let me know

 

[zigzag3143]

Please help!

I am consistently getting a range of different BSODs, however they are all coming up as being due to Locale ID 2057, which I gather is causede by a corrupt or incompatible driver. Problem is trying to locate this troublesome driver.

I hope I have done the zipping of my Mini Dump correctly. Any help would be much appreciated.

My system

Win7 Home Premium 64 Bit
8GB DDR3 Ram
700 Watt PSU
AMD Phenom II x4 'Black edition' 3.2Ghz
ATI Radeon 5670 1GB RAM
600 GB Hard Drive

you need any more details please let me know

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


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.

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

 

[Davonator]

HI Zigzag thanks for your reply, I hesitate in getting back to you because I was carrying out Memtest. I did what you suggested and ran 7 sweeps (to be extra sure) of every block of ram individually, in all the memory slots. Thankfully no issues were detected, so i'm guessing that's not the issue.

The BSOD keeps saying that 'Windows has detected a corrupt driver on the Kernel Power stack' so i'm assuming thats it is in fact a bad driver. I will now go ahead with step 2, but i'm interested to know what does it mean when it says Windows has detected the bad driver. Does it mean detected in general or has it specifically detected the individual cause of the issue???

 

[Davonator]

Fingers crossed I think this issue is solved, the offending file was

Atikmag.sys

it's a ATIs Graphics driver, and a few people have reported problems with it. I've removed the file and haven't had a BSOD since (before a BSOD would take place within 10 minutes)

 

[zigzag3143]

HI Zigzag thanks for your reply, I hesitate in getting back to you because I was carrying out Memtest. I did what you suggested and ran 7 sweeps (to be extra sure) of every block of ram individually, in all the memory slots. Thankfully no issues were detected, so i'm guessing that's not the issue.

The BSOD keeps saying that 'Windows has detected a corrupt driver on the Kernel Power stack' so i'm assuming thats it is in fact a bad driver. I will now go ahead with step 2, but i'm interested to know what does it mean when it says Windows has detected the bad driver. Does it mean detected in general or has it specifically detected the individual cause of the issue???

Could be either and I am glad you are working.