Help with BSOD

[Erazor51]

I get BSOD playing crysis 3 within a few mins into the game. Just purchased the Sapphire Vapour-x 290x and installed 14.6 beta. Had a 6970 before and never got bsod but was using an old driver.



Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 01/06/2014 23:48:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060214-12734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x124 (0x0, 0xFFFFFA801112A028, 0xBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 01/06/2014 22:06:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060114-12546-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x5D5A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001CC9D5A, 0xFFFFF88006753940, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


First one by ndis.sys and 2nd time by ntoskrnl.exe.

Any ideas?


Thanks

 

[KaRLiToS]

Is you PC overclocked?

0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT)
0x3B = increase vcore


What kind of system do you have? What are the specs?

I would try to increase Vcore as first solution, then try to increase QPI voltages.

 

[Erazor51]

Is you PC overclocked?

0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT)
0x3B = increase vcore


What kind of system do you have? What are the specs?

I would try to increase Vcore as first solution, then try to increase QPI voltages.

i7 3770K @ 4.5ghz, Asus P8Z77-V, 16GB 1866Mhz CL9, Sapphire Vapor-X 290X, Crucial M4 128GB, Seagate 3TB, Enermax Galaxy 1000W DXX, Windows 7 Ultimate x64

System was completely fine before upgrading from 6970 to 290x. Will prime95 test determine if system OC is stable before changing anything?

 

[KaRLiToS]

i7 3770K @ 4.5ghz, Asus P8Z77-V, 16GB 1866Mhz CL9, Sapphire Vapor-X 290X, Crucial M4 128GB, Seagate 3TB, Enermax Galaxy 1000W DXX, Windows 7 Ultimate x64

System was completely fine before upgrading from 6970 to 290x. Will prime95 test determine if system OC is stable before changing anything?

I would try to increase the Vcore by 2 or 3 bumps then try to re-run the Crysis 3 game you were trying to play.

If it pass this time, you have your answer. Crysis 3 is a very demanding game, maybe your HD 6970 wasn't taxing your CPU that much but the 290x is.

You can also test with AMD Catalyst 14.4 WHQL drivers since they are certified... But bumping vcore would be my first test.

 

[Erazor51]

I would try to increase the Vcore by 2 or 3 bumps then try to re-run the Crysis 3 game you were trying to play.

If it pass this time, you have your answer. Crysis 3 is a very demanding game, maybe your HD 6970 wasn't taxing your CPU that much but the 290x is.

You can also test with AMD Catalyst 14.4 WHQL drivers since they are certified... But bumping vcore would be my first test.

Thanks i'll try bumping the vcore and see what happens.

 

[KaRLiToS]

Please keep us updated. I'll try to help when you come back .

 

[Erazor51]

Please keep us updated. I'll try to help when you come back .

Thanks, will do, will have to be tomorrow, 2:20am here.

Someone mentioned "Also possible with 16GB of RAM that you need to increase VTT/IMC(SA) a tad" will i need to?

Edit: my bad its the same thing.

 

[Erazor51]

Please keep us updated. I'll try to help when you come back .

I think I got the system stable now. Did a prime95 test and one of the threads failed around 30min mark.

I had offset set to -0.015 so I decreased that two notches and system is prime stables for a couple of hours now

Never knew a graphics upgrade can make the system OC unstable.


Thanks for the help

 

[KaRLiToS]

You are very welcome. I'm glad I could help.