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

Page 5 of 10 FirstFirst ... 34567 ... LastLast

  1. Posts : 53
    Windows 7 Home Premium x64
    Thread Starter
       #41

    BSOD again with two sticks in the first slots, will test the other sticks in the other slots.
      My Computer


  2. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #42

    Your memory should all be compatible based on the report and the motherboard memory compatibility check. My guess is you have a bad module or two. You will have to narrow it down with the two sticks at a time process and post back if you are able to fix it. You could also try the DRAM voltage recommended with a 0.1 Volt increase as before to see if it provides more stability. In the meantime, here is your crash report and some steps that resulted from the analysis of it (don't do anything with the RAM until after these steps are completed; if you have already swapped out the two modules, that is fine, but see if it is stable before doing the following steps).

    Code:
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Kapinoida\Windows_NT6_BSOD_jcgriff2\011712-11918-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`03212000 PsLoadedModuleList = 0xfffff800`03457670
    Debug session time: Tue Jan 17 22:21:02.936 2012 (UTC - 7:00)
    System Uptime: 0 days 0:26:03.512
    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 : memory_corruption
    
    Followup: memory_corruption
    ---------
    
    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: 
    +6465383861626634
    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:  CODE_CORRUPTION
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    EXCEPTION_RECORD:  fffff88002ffb588 -- (.exr 0xfffff88002ffb588)
    ExceptionAddress: fffff880053bbb3d (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:  fffff88002ffb630 -- (.trap 0xfffff88002ffb630)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=f7fffa8004d3f530 rbx=0000000000000000 rcx=fffffa8004008580
    rdx=fffffa8005a9e520 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880053bbb3d rsp=fffff88002ffb7c0 rbp=fffffa8006e35950
     r8=00000000000000b0  r9=fffffa8004128088 r10=fffffa8006597bd0
    r11=fffff88002ffbac8 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+0x7d:
    fffff880`053bbb3d f0834018ff      lock add dword ptr [rax+18h],0FFFFFFFFh ds:2bd0:f7fffa80`04d3f548=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800032865fe to fffff8000328ec10
    
    STACK_TEXT:  
    fffff880`02ffa668 fffff800`032865fe : 00000000`00000000 fffffa80`04faa000 fffff880`02ffade0 fffff800`032ba830 : nt!KeBugCheck
    fffff880`02ffa670 fffff800`032ba4fd : fffff800`0349871c fffff800`033d5c30 fffff800`03212000 fffff880`02ffb588 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff880`02ffa6a0 fffff800`032b92d5 : fffff800`033d90fc fffff880`02ffa718 fffff880`02ffb588 fffff800`03212000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`02ffa6d0 fffff800`032ca361 : fffff880`02ffb588 fffff880`02ffade0 fffff880`00000000 fffffa80`00000004 : nt!RtlDispatchException+0x415
    fffff880`02ffadb0 fffff800`0328e2c2 : fffff880`02ffb588 fffffa80`068ca9c0 fffff880`02ffb630 fffffa80`05a9e520 : nt!KiDispatchException+0x135
    fffff880`02ffb450 fffff800`0328cbca : fffffa80`05ad6a30 fffff880`00efbc98 fffffa80`05b05860 fffffa80`05b01e40 : nt!KiExceptionDispatch+0xc2
    fffff880`02ffb630 fffff880`053bbb3d : 00000000`00000000 00000000`00000000 fffffa80`06587af0 fffffa80`06597410 : nt!KiGeneralProtectionFault+0x10a
    fffff880`02ffb7c0 fffff880`053bf677 : fffffa80`068ca9c0 fffffa80`06e35950 fffffa80`04aee590 fffff880`0495d714 : dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+0x7d
    fffff880`02ffb7f0 fffff880`053bee00 : 00000000`00000000 fffff880`00000003 00000000`00000000 fffff880`048bdb9e : dxgmms1!VidSchiProcessDpcCompletedPacket+0x253
    fffff880`02ffb890 fffff880`053bec4c : fffffa80`05e22ef0 fffffa80`06597410 fffffa80`03c9c040 fffffa80`05e2f268 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
    fffff880`02ffb8e0 fffff880`052c51cf : fffffa80`05067040 fffffa80`05e32240 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94
    fffff880`02ffb930 fffff880`048ab3b4 : fffffa80`05cbb000 fffffa80`05cbb000 fffffa80`05e2f268 00000000`00000022 : dxgkrnl!DxgNotifyDpcCB+0x77
    fffff880`02ffb960 fffffa80`05cbb000 : fffffa80`05cbb000 fffffa80`05e2f268 00000000`00000022 fffffa80`05e22000 : atikmdag+0x4f3b4
    fffff880`02ffb968 fffffa80`05cbb000 : fffffa80`05e2f268 00000000`00000022 fffffa80`05e22000 fffff880`048be070 : 0xfffffa80`05cbb000
    fffff880`02ffb970 fffffa80`05e2f268 : 00000000`00000022 fffffa80`05e22000 fffff880`048be070 00000000`00000000 : 0xfffffa80`05cbb000
    fffff880`02ffb978 00000000`00000022 : fffffa80`05e22000 fffff880`048be070 00000000`00000000 c389470b`00000000 : 0xfffffa80`05e2f268
    fffff880`02ffb980 fffffa80`05e22000 : fffff880`048be070 00000000`00000000 c389470b`00000000 000000b5`000000a9 : 0x22
    fffff880`02ffb988 fffff880`048be070 : 00000000`00000000 c389470b`00000000 000000b5`000000a9 00000000`00000000 : 0xfffffa80`05e22000
    fffff880`02ffb990 00000000`00000000 : c389470b`00000000 000000b5`000000a9 00000000`00000000 00000000`00000000 : atikmdag+0x62070
    
    
    STACK_COMMAND:  kb
    
    CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
    3 errors : !nt (fffff8000328ec67-fffff8000328ef7f)
    fffff8000328ec60  00  00  00  48  8b  89  d8 *43  00  00  e8  61  06  00  00  65 ...H...C...a...e
    ...
    fffff8000328ec90  00  48  8b  44  24  40  49 *81  82  80  00  00  00  48  8b  44 .H.D$@I......H.D
    ...
    fffff8000328ef70  0f  20  c0  48  89  01  0f  20  d0  48  89  41  08  0f  20 *d0 . .H... .H.A.. .
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MEMORY_CORRUPTOR:  STRIDE
    
    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE
    
    BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE
    
    Followup: memory_corruption
    ---------

    Possible causes are Memory problems... Viruses... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Drivers...

    Yours was probably related to the RAM, but to rule out other possible causes, do the following steps.


    Thanks to JMH for helping with my understanding of the above steps.

    Also, considering you were missing a registry entry for the OS multiple times (you said you had to fix it in the past), where did you get your installation DVD for Windows 7?
      My Computer


  3. Posts : 53
    Windows 7 Home Premium x64
    Thread Starter
       #43

    I got the installation DVD from a retail store, It's an OEM version, I think I got it from Microcenter. So far all the scans came up with nothing, doing the verifier again now.
      My Computer


  4. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #44

    Alright, let us know if you get another crash.
      My Computer


  5. Posts : 53
    Windows 7 Home Premium x64
    Thread Starter
       #45

    System just froze with verifier running, but no dump. Could this be more then just memory, like the motherboard is bad or maybe the power supply is failing?
      My Computer


  6. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #46

    Kapinoida said:
    System just froze with verifier running, but no dump. Could this be more then just memory, like the motherboard is bad or maybe the power supply is failing?
    Try running Verifier with five non-Microsoft drivers at a time and see if you can get a crash report.

    It could be the motherboard or power supply. You can try to (carefully) do PSU Testing and see if your power supply is working as you would expect.
      My Computer


  7. Posts : 53
    Windows 7 Home Premium x64
    Thread Starter
       #47

    Had something weird happen, it ended up freezing on me, but the computer started beeping like crazy. No blue screen or anything, had verifier on with five drivers selected.
      My Computer


  8. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #48

    Kapinoida said:
    Had something weird happen, it ended up freezing on me, but the computer started beeping like crazy. No blue screen or anything, had verifier on with five drivers selected.
    That is not a good sign. Was there a pattern to the beep? Beeps are hardware alarms signifying overheating, voltage issues, etc.
      My Computer


  9. Posts : 53
    Windows 7 Home Premium x64
    Thread Starter
       #49

    Its was continuous repeating one tone beeps, very rapid. It happened as it froze while in game.
      My Computer


  10. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #50

    Kapinoida said:
    Its was continuous repeating one tone beeps, very rapid. It happened as it froze while in game.
    I believe that indicates a RAM failure. Recommend running the memory tests again.
      My Computer


 
Page 5 of 10 FirstFirst ... 34567 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 21:03.
Find Us