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

Kapinoida · 17 Jan 2012

Ran the memtest on each individual stick and slot and got no errors.

writhziden · 17 Jan 2012

Kapinoida said:

Ran the memtest on each individual stick and slot and got no errors.

Before I proceed with a troubleshooting step, I have some questions. Is your RAM made by the same manufacturer? Do all modules have the same timing? Were all modules bought at the same time?

Kapinoida · 17 Jan 2012

Yes, they are 4 sticks of 2gb Corsair xms3 and were all packaged together.

writhziden · 17 Jan 2012

Alright, try the following steps.

Find the voltage that is recommended for your RAM by checking with Corsair using the RAM part number.
Shut down and turn off your computer
Remove all power supplies from the computer (AC Adapter, battery, etc.)
Hold down the power button for 30 seconds to close the circuit and drain all residual power
Replace your RAM modules in the motherboard
Enter your BIOS
Go to your DRAM voltage settings
Change them from Automatic to Manual
Input the voltage that Corsair recommends.

See if it runs more stable. It is possible the automatic option was not setting the voltage correctly.

Kapinoida · 17 Jan 2012

Okay done and done. Looks good so far, will report any problems, but hopefully it was that, seems like it was undervolted a bit. Fingers crossed.

Kapinoida · 17 Jan 2012

And as if right on cue, another BSOD.

writhziden · 17 Jan 2012

Alright, try increasing the DRAM voltage by 0.1V and see if it is more stable. Sometimes the RAM needs a little more to work as a group.

Kapinoida · 17 Jan 2012

BSOD again after doing so.

writhziden · 17 Jan 2012

Code:

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Kapinoida\Windows_NT6_BSOD_jcgriff2\011712-12370-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02e53000 PsLoadedModuleList = 0xfffff800`03090e70
Debug session time: Tue Jan 17 13:26:59.504 2012 (UTC - 7:00)
System Uptime: 0 days 0:08:51.206
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d )

Followup: MachineOwner
---------

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+6565393563616337
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88002dfd588 -- (.exr 0xfffff88002dfd588)
ExceptionAddress: fffff88004605b3d (dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+0x000000000000007d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002dfd630 -- (.trap 0xfffff88002dfd630)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=f7fffa800700da20 rbx=0000000000000000 rcx=fffffa8007199300
rdx=fffffa8009bb6720 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004605b3d rsp=fffff88002dfd7c0 rbp=fffffa80070b0510
 r8=0000000000000060  r9=fffffa8009ed4908 r10=fffffa80094f57d0
r11=fffff88002dfdac8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+0x7d:
fffff880`04605b3d f0834018ff      lock add dword ptr [rax+18h],0FFFFFFFFh ds:efc0:f7fffa80`0700da38=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ebb2ee to fffff80002ec3590

STACK_TEXT:  
fffff880`02dfc678 fffff800`02ebb2ee : fffffa80`09eb9b60 fffffa80`09eb9c68 fffff880`02dfcdf0 fffff800`02ef0524 : nt!KeBugCheck
fffff880`02dfc680 fffff800`02ee92dd : fffff800`030d1b7c fffff800`0300be68 fffff800`02e53000 fffff880`02dfd588 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02dfc6b0 fffff800`02ef0950 : fffff800`03012b0c fffff880`02dfc728 fffff880`02dfd588 fffff800`02e53000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02dfc6e0 fffff800`02efd8cf : fffff880`02dfd588 fffff880`02dfcdf0 fffff880`00000000 fffffa80`00000004 : nt!RtlDispatchException+0x410
fffff880`02dfcdc0 fffff800`02ec2c02 : fffff880`02dfd588 fffffa80`094faf30 fffff880`02dfd630 fffffa80`09bb6720 : nt!KiDispatchException+0x16f
fffff880`02dfd450 fffff800`02ec150a : 00000000`00000202 fffff800`02ec809a fffff880`009e9180 fffffa80`095568c0 : nt!KiExceptionDispatch+0xc2
fffff880`02dfd630 fffff880`04605b3d : 00000000`00000000 00000000`00000000 fffffa80`071b1010 fffffa80`094f5010 : nt!KiGeneralProtectionFault+0x10a
fffff880`02dfd7c0 fffff880`04609677 : fffffa80`094faf30 fffffa80`070b0510 fffffa80`0a422c20 fffff880`0478d714 : dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+0x7d
fffff880`02dfd7f0 fffff880`04608e00 : 00000000`00000000 fffffa80`00000003 00000000`00000000 fffff880`046edb9e : dxgmms1!VidSchiProcessDpcCompletedPacket+0x253
fffff880`02dfd890 fffff880`04608c4c : fffffa80`0942def0 fffffa80`094f5010 fffffa80`0810c480 fffffa80`0943a268 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
fffff880`02dfd8e0 fffff880`050f51cf : fffffa80`0810c480 fffffa80`0943d240 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`02dfd930 fffff880`046db3b4 : fffffa80`093c7000 fffffa80`093c7000 fffffa80`0943a268 00000000`00000022 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff880`02dfd960 fffffa80`093c7000 : fffffa80`093c7000 fffffa80`0943a268 00000000`00000022 fffffa80`0942d000 : atikmdag+0x4f3b4
fffff880`02dfd968 fffffa80`093c7000 : fffffa80`0943a268 00000000`00000022 fffffa80`0942d000 fffff880`046ee070 : 0xfffffa80`093c7000
fffff880`02dfd970 fffffa80`0943a268 : 00000000`00000022 fffffa80`0942d000 fffff880`046ee070 00000000`00000000 : 0xfffffa80`093c7000
fffff880`02dfd978 00000000`00000022 : fffffa80`0942d000 fffff880`046ee070 00000000`00000000 6b9722af`00000000 : 0xfffffa80`0943a268
fffff880`02dfd980 fffffa80`0942d000 : fffff880`046ee070 00000000`00000000 6b9722af`00000000 000000b5`000000a9 : 0x22
fffff880`02dfd988 fffff880`046ee070 : 00000000`00000000 6b9722af`00000000 000000b5`000000a9 00000000`00000000 : 0xfffffa80`0942d000
fffff880`02dfd990 00000000`00000000 : 6b9722af`00000000 000000b5`000000a9 00000000`00000000 00000000`00000000 : atikmdag+0x62070


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d
fffff880`04605b3d f0834018ff      lock add dword ptr [rax+18h],0FFFFFFFFh

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d3fa174

FAILURE_BUCKET_ID:  X64_0x1E_0_dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d

BUCKET_ID:  X64_0x1E_0_dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d

Followup: MachineOwner
---------

Alright, the latest one is not memory related. Do the following and see if you still have problems.

Update to Service Pack 1

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [August 2011]

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011]

Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

Service Pack 1 Download site

Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH

Kapinoida · 17 Jan 2012

Install not successful, catastrophic failure, Error: E_UNEXPECTED(0x8000ffff)

It also showed that it was in windows update but also getting a 8000ffff error.