• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Help with BSOD

erazor51

erazor51

erazor51

Associate
Joined
18 Dec 2010
Posts
597
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
 
No GPU was the only upgrade and the system was fine with no BSOD issues when i was on AMD 6970.

Will prime95 test determine if system OC is stable before changing anything? or my PSU might be too old?
 
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 guys.
 
You must log in or register to reply here.
Back
Top Bottom