Getting ntoskrnl.exe STOP 0x0000000A BSOD since installing ATI 10.7

[Schfifty Five]

Ever since installing ATI Catalyst drivers 10.7 and 10.7a, I've been getting frequent BSOD Stop 0x0000000A ntoskrnl.exe errors while running SC2.

I'm not 100% sure if it's these drivers causing the issue or not.

My system:

i7 930 @ 3.8ghz
4gb corsair
Asus p6x58d-e

I used to run 10.4 drivers and things were fine. Does the ntoskrnl.exe have to do with anything related to the ati drivers? Is it not liking my i7 OC?

Any help is appreciated.

 

[Compddd]

I found that I BSODed often with 10.7 when I previously never had any BSODs, and it always said atikmag something or other was responsible. From my own experience and research on the web I've learned that 10.7 are giant pieces of sh**.

I went back to 10.5 and all was well again.

 

[Schfifty Five]

I found that I BSODed often with 10.7 when I previously never had any BSODs, and it always said atikmag something or other was responsible. From my own experience and research on the web I've learned that 10.7 are giant pieces of sh**.

I went back to 10.5 and all was well again.

I'm probably going to go back to 10.4 or try 10.5, but wanted to see first if there were any known solutions/fixes other than reverting back to old drivers.

Thanks for the input!

 

[Mem]

I'm probably going to go back to 10.4 or try 10.5, but wanted to see first if there were any known solutions/fixes other than reverting back to old drivers.

Thanks for the input!

10.7s working great for me,infact its not rocket science to have a stable system with any ATI or Nvidia drivers,overclocking may be causing the problem so try reducing that.

 

[OCGuy]

I think AMD's driver team has been having too many cocktails at lunch.

 

[Ualdayan]

Ever since installing ATI Catalyst drivers 10.7 and 10.7a, I've been getting frequent BSOD Stop 0x0000000A ntoskrnl.exe errors while running SC2.

I'm not 100% sure if it's these drivers causing the issue or not.

My system:

i7 930 @ 3.8ghz
4gb corsair
Asus p6x58d-e

I used to run 10.4 drivers and things were fine. Does the ntoskrnl.exe have to do with anything related to the ati drivers? Is it not liking my i7 OC?

Any help is appreciated.

You might try taking one stick of RAM out, seeing if the error happens at all, if it still does, then take that stick out and put the other one in and see if it still happens. I recently had some memory go bad and I saw variations of ntkernel all over the place. Swapped out the RAM for a kit of identical timings/speed/voltage and the BSODs went away. (FYI the kit that went bad on me was a 1600Mhz 8-8-8-24, 4GB kit).

Also, check your SATA cable. When I was trying to nail down my problem I also found the oddest thing - my SATA cable had gone hard and inflexible, like you see notebook power adapters do sometimes. Maybe try swapping your SATA cable if you happen to have a spare already and you rule out your memory. I know it seems like a bad SATA would definately cause data corruption, but it seemed like the data was only getting messed up on reads and not writes. Maybe because writes were at 80MB but reads were at 250MB/s.

 

[Schfifty Five]

You might try taking one stick of RAM out, seeing if the error happens at all, if it still does, then take that stick out and put the other one in and see if it still happens. I recently had some memory go bad and I saw variations of ntkernel all over the place. Swapped out the RAM for a kit of identical timings/speed/voltage and the BSODs went away. (FYI the kit that went bad on me was a 1600Mhz 8-8-8-24, 4GB kit).

Also, check your SATA cable. When I was trying to nail down my problem I also found the oddest thing - my SATA cable had gone hard and inflexible, like you see notebook power adapters do sometimes. Maybe try swapping your SATA cable if you happen to have a spare already and you rule out your memory. I know it seems like a bad SATA would definately cause data corruption, but it seemed like the data was only getting messed up on reads and not writes. Maybe because writes were at 80MB but reads were at 250MB/s.

Thanks for the suggestions. I may try the SATA stuff as a last resort. This system I'm using is pretty new, maybe 3 months old.

The RAM thing may be an issue, but again, the system is new and while running on 10.4 drivers, I had none of these problems.

I ran a chkdsk and also scanned the HDD for integrity and both came back with 0 errors. So that would have me think my SATA cables are ok.

 

[BD231]

When in doubt, disable catalyst AI. These are supposed to be performance optimization's but they're messing with stability in more than one title as of late.

10.7 drivers have given me some issue's with two title's thus far and both issue's were rectified when I disabled Catalyst AI. I can't say SC2 has seen a single crash with 10.7's on my hd4850/am3 setup though.

If your video card is overclocked you might have to reduce your clocks for certain title's as well. I'd also make sure your CPU overclock is stable.