Solved BSOD playing Star Wars: The Old Republic, random reboots 0x00000024

[Kapinoida]

Another crash

 

[writhziden]

Another crash

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Kapinoida\Windows_NT6_BSOD_jcgriff2\012012-10077-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02c5b000 PsLoadedModuleList = 0xfffff800`02ea0e90
Debug session time: Fri Jan 20 14:49:08.037 2012 (UTC - 7:00)
System Uptime: 0 days 0:04:23.208
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff960006cb0f5}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff960006cb0f5

Debugging Details:
------------------


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002cdabe9 to fffff80002cdb640

STACK_TEXT:  
fffff880`02f6ace8 fffff800`02cdabe9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`02f6acf0 fffff800`02cd90b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f6ae30 fffff960`006cb0f5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`0a7d9ab0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : cdd!DrvCopyBits+0x9


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !cdd
    fffff960006cb0ef - cdd!DrvCopyBits+3
	[ 48:40 ]
1 error : !cdd (fffff960006cb0ef)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

Blames memory, but it appears it may blame the graphics driver as well. DrvCopyBits was in the stack. "This function translates between device-managed raster surfaces and graphics device interface (GDI) standard format bitmaps" (DrvCopyBits).

 

[Kapinoida]

Okay, well running FurMark right now, see what comes of it.

 

[Kapinoida]

Been running for 25 minutes and still stable

 

[writhziden]

Been running for 25 minutes and still stable

How is the GPU temperature?

 

[Kapinoida]

83c and 86c respectively, and steadily.

 

[Kapinoida]

Noticing that there is 0% on the mem load. Is that normal?

 

[writhziden]

Noticing that there is 0% on the mem load. Is that normal?

For FurMark, 0% mem load is common. That is why I gave you the second Graphics memory test.

 

[Kapinoida]

Okay will run that.

 

[writhziden]

I will be out for a bit. In case I do not get a chance to give instructions later, here is what I suggest: After you do the graphics test, post back the results. Then tonight, before going to bed, clear the BIOS software setting following steps 3-7 (you don't have to post back the results) in post #75. Then run Memtest86+ and see if you get errors overnight and let us know.

Right now, I am not sure whether you have bad RAM, a problem with the motherboard, or something wrong with a graphics card. The Memtest errors you have gotten in the past may have been due to RAM not being seated properly. It is odd that sometimes you get errors and other times you do not, but that could still indicate bad RAM/slots as it is not good to get errors at all in Memtest.

 

[Kapinoida]

No errors on the test.

 

[writhziden]

That most likely rules out the graphics card as the problem...

 

[Kapinoida]

Ran Memtest all night with no errors.

 

[writhziden]

Still having instability with gaming and obtaining your WEI?

If you are, try the Windows Memory Diagnostic tool in extended mode for five passes. Post back if memory passes there, too.

 

[Kapinoida]

Yeah still freezing with everything, the game wouldn't even fully load into it. Running the WMD and it's saying there was hardware problems detected.

 

[writhziden]

Yeah still freezing with everything, the game wouldn't even fully load into it. Running the WMD and it's saying there was hardware problems detected.

Looks like we are back to either the RAM or motherboard being damaged. We may have to wait until you are able to test the RAM in your friend's machine to see which it is.

 

[Kapinoida]

So my buddy had an older computer that didn't have the right type of memory slots, so I just went out and got a new motherboard, looks like it was the motherboard as everything seems to be working really good now. Time will tell and I might be speaking out of turn but I put it through a WEI test and it actually went through it. I believe what might have happened is the RAM I had before the RAM I currently have wasn't certified and probably clocked too high for the motherboard, and may have damaged it that way. Hence why I went with getting the motherboard first. Thank you so much, writhziden, for all your help and expertise. I really appreciate it, words can't describe. I will let you know within the next day about performance and what not.

 

[writhziden]

That is great news. Best of luck with the new board. Glad you will be keeping us updated on how it runs.

 

[flirno]

If you go to the SWTOR forum you will find a LOT of threads about this problem -- it apperas to be an optimization incompatibility with high end hardware/systems and at this point it is very well documented on the user end.

What appears to be happening is injected DX9 optimizations (possibly to solve low end hardware performance issues) causing high end video cards to exceed expected limits causing hard blue and black screen crashes.

This has reportedly resulted with corruption of video driver components and DX9 components so the problem appears to effect other games but it really starts with a SWTOR crash.

If you must keep playing this game (until bioware has fixed this) then you probably want to underclock your video card(s) for the time being which will lower the rate of BSOD/BLSOD although it will not remove them completely.

Be ready to reinstall/repair drivers/DX9/game/system files. Backup. Use restore points. Etc.

People ARE experiencing permanent hardware damage from this issue both from the BSODs and from the effect of repeated crash/reboot cycles.

I myself had to cold reset a fuse on a LCD because of a SWTOR BLSOD voltage spike.

Until bioware has fixed this I am not sure how wise it is to play SWTOR with a higher end system.