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

Yeah just a hard reboot, so far only from the game, has happened twice. Screen goes black and then bios loads.

Download and install HWiNFO64 Download and run in sensor only mode. Start logging, save in a place that you will remember, and post the CSV log next time after it reboots.

Had a Blue screen but no dump. Here is the sensor log

Temperatures are within acceptable limits. Don't see too much change in the voltage. I think it is time to try updating your chipset drivers and BIOS through your motherboard website: ASUSTeK Computer Inc. - Motherboards- ASUS M4A88TD-V EVO/USB3.

BSOD after flashing the BIOS. Again it happened while in the game. Have the dump and the sensor log.

Code:

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Kapinoida\Windows_NT6_BSOD_jcgriff2\011712-15366-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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0324e000 PsLoadedModuleList = 0xfffff800`03493670
Debug session time: Tue Jan 17 21:30:28.945 2012 (UTC - 7:00)
System Uptime: 0 days 0:06:40.115
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff280088d5238, 0, fffff800033cbb2c, 7}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiEmptyPageAccessLog+dc )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff280088d5238, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800033cbb2c, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034fd100
 fffff280088d5238 

FAULTING_IP: 
nt!MiEmptyPageAccessLog+dc
fffff800`033cbb2c 488b08          mov     rcx,qword ptr [rax]

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800998e6b0 -- (.trap 0xfffff8800998e6b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff280088d5238 rbx=0000000000000000 rcx=0000000000000018
rdx=fffff8a003b67230 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800033cbb2c rsp=fffff8800998e840 rbp=0000000000000000
 r8=fffffa8008410004  r9=fffffa8009081048 r10=fffffa80088d5180
r11=fffffa800993a640 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!MiEmptyPageAccessLog+0xdc:
fffff800`033cbb2c 488b08          mov     rcx,qword ptr [rax] ds:2004:fffff280`088d5238=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003275347 to fffff800032cac40

STACK_TEXT:  
fffff880`0998e548 fffff800`03275347 : 00000000`00000050 fffff280`088d5238 00000000`00000000 fffff880`0998e6b0 : nt!KeBugCheckEx
fffff880`0998e550 fffff800`032c8d6e : 00000000`00000000 fffff280`088d5238 fffffa80`04a55600 00000000`011db404 : nt! ?? ::FNODOBFM::`string'+0x44711
fffff880`0998e6b0 fffff800`033cbb2c : 00000000`6bb22001 fffffa80`088d51c0 fffff880`0998e8f0 fffff800`033b0976 : nt!KiPageFault+0x16e
fffff880`0998e840 fffff800`0333f4d5 : fffffa80`08412b30 00000003`00000000 00000000`01383404 fffff280`088d5238 : nt!MiEmptyPageAccessLog+0xdc
fffff880`0998e8b0 fffff800`035e2221 : fffffa80`0830f340 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x3b9a6
fffff880`0998e9d0 fffff800`035e2623 : 0000007f`00000000 00000000`6b8d0000 fffffa80`00000001 fffffa80`088d5180 : nt!MiUnmapViewOfSection+0x1b1
fffff880`0998ea90 fffff800`032c9ed3 : ffffffff`ffffffff 00000000`02bfe878 fffffa80`08412b30 00000000`00008000 : nt!NtUnmapViewOfSection+0x5f
fffff880`0998eae0 00000000`77ab15ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02bfea58 fffff800`032c2210 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ab15ba
fffff880`0998eec0 00000000`00000000 : 00000000`00000000 ffffffff`fffffb80 fffff680`00010d80 fffffa80`0a0d4fe0 : nt!KiCallUserMode


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiEmptyPageAccessLog+dc
fffff800`033cbb2c 488b08          mov     rcx,qword ptr [rax]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiEmptyPageAccessLog+dc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiEmptyPageAccessLog+dc

BUCKET_ID:  X64_0x50_nt!MiEmptyPageAccessLog+dc

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

memory_corruption is back. Try resetting BIOS settings to default to reset the CMOS and put the DRAM voltage back to automatic.

If that does not work, try to determine which RAM module(s) is/are bad by running with two at a time and doing your normal routine in Windows.

Also, AMD is very finicky with RAM. Please do the following at your convenience:

1. Start HWINFO with the box unchecked for sensor only
2. Click Save Report
3. Choose a destination by clicking browse
4. Save as an html file and upload here

I will check your RAM to see if it is compatible with your motherboard and CPU.

Actually all of the BIOS settings are in default, I set them back to default to flash the bios. So I will do the memory thing.

Kapinoida said:

Actually all of the BIOS settings are in default, I set them back to default to flash the bios. So I will do the memory thing.

Sometimes you want to set them back to default again after flashing the BIOS to clear the CMOS afterward, too. In some instances, this has to be done two or three times to get stability after a flash.

Here's the report, I only have 2 sticks in right now. Also did a default set again to the bios.