WoW BSoD

[Juggernaut]

While playing WoW i`m getting bsod (attachment). I`m on win 7 x64 RTM.
My PC cfg is:

Cpu: Intel e6550 @ 3.5ghz(OC)
MB: Gigabyte EP35C-DS3R
RAM: Corsair Dominator 2x2048 1000mhz(downclock from 1066)
Video: Gigabyte 8800gt 512/256

 

[Tews]

Restore your RAM to its default values...

 

[zigzag3143]

Could you go into c:\windows\minidump, zip the dump file (*.dmp) and upload it for us to take a look at?

Ken

 

[Juggernaut]

here you go

 

[AstaLaVista]

Restore your RAM to its default values...

+ 1

Make sure your Board has the correct Voltage and timings for it, I know my two last boards don't set this correctly when I have them on AUTO... set it Manually.

Some games don't play well with OC'd stuff... try resetting back to default.

Corrupt drivers can bring a lot of BSOD... perhaps a clean/fresh install is in order?

 

[Juggernaut]

Timings are correct, the voltage is 2.22v for the ram and 1.45 for the cpu. I`m currently testing with these settings. I`m still mainly interested if someone can ,,translate" that dump for me, because from what i`ve read there`s something related to the cpu.

 

[TGSoldier]

You are OCING and getting Blue Screens.. This is not rocket science.

Just because your computer is booting does not mean it is stable.

Reset your BIOS to default please.

You will probably need to jump the voltage on your RAM to 2.1v though.

If your problem does not persist after resetting to default, then we know where the problem is and I'll be here to help you with the overclocking if you wish.

If it does persist.. Then we know where the problem is as well.

 

[Juggernaut]

Thx for the advice, but this is the first time i`m getting bsod`s after almost half a year w/o blues. I`ve raised the cpu voltage to 1.46 and everything is flawless for the moment. I will post if anything goes wrong. Till then i`m waiting for the translation of my dump.

 

[zigzag3143]

Timings are correct, the voltage is 2.22v for the ram and 1.45 for the cpu. I`m currently testing with these settings. I`m still mainly interested if someone can ,,translate" that dump for me, because from what i`ve read there`s something related to the cpu.

While I dont have a true debugger I took a quick look at the dump. Ntoskrnl.exe is the faulting module and the trigger was not a driver but hardware. I encourage you to wait for someone with both the tools and experience for analyze this fully.

In the interim Here is the info I was able to get

Ken

 

[Juggernaut]

i`ll wait, no problem. thx for the new info.