BSOD playing Neverwinter, Warframe, etc. BCCode: 1000007e

Page 1 of 5 123 ... LastLast

  1. Posts : 27
    Windows 7 Home Premium 64-Bit
       #1

    BSOD playing Neverwinter, Warframe, etc. BCCode: 1000007e


    So basically to say I've been rebooted alot while playing Neverwinter and Warframe and I recieve this message every time.

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.768.3
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 1000007e
    BCP1: FFFFFFFFC0000094
    BCP2: FFFFF8800F0EC1DD
    BCP3: FFFFF8800366CF38
    BCP4: FFFFF8800366C790
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1

    Files that help describe the problem:
    C:\Windows\Minidump\081614-20217-01.dmp
    C:\Users\user\AppData\Local\Temp\WER-95503-0.sysdata.xml

    I'm at my wits end to try and figure out a solution and could really use help on fixing this issue.

    Here's the basic specs:
    Model: HP Pavilion p6744Y

    Processor Type: Intel Dual-Core E5800 3.2GHz Processor

    Memory: 4 GB DDR3

    Hard Drive Capacity: 1 TB 7200 RPM

    AMD Radeon HD 6770 with 1 GB GDDR5 SDRAM

    Wireless 802.11 b/g/n

    Rocketfish 500 Watt Gaming Computer CPU Power Supply RF-500WPS2 600 Watt Peak

    Also added a file using the Log collector
    Last edited by Androshi; 17 Aug 2014 at 20:14. Reason: need to add a file
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Welcome to the forum Androshi,

    Please remove Advanced System Care & AVG from the system.

    System Optimisers
    Please remove the following software:

    This software can be cause of BSOD's. The windows 7 operating system does not require these registry cleaning software. They often tune-down rather than tune-up and can wreck the OS beyond repair. Microsoft have improved Windows 7 significantly and it is much better at organising and optimising itself than its predecessors. Check this, this and this thread for evidence.

    If you feel the need to use a registry cleaning or optimisation software, most of us recommend the use of CCleaner but make sure you back up the registry before making letting ccleaner delete anything.
    Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability
    compared to other antivirus or internet security software. It is free and lightweight:-

       Warning
    Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.


    Code:
    Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\admin\Downloads\USER-PC-Sun_08_17_2014_175703_80\081714-18049-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`02e4d000 PsLoadedModuleList = 0xfffff800`03090890
    Debug session time: Mon Aug 18 05:47:19.952 2014 (UTC + 6:00)
    System Uptime: 0 days 4:52:01.590
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................
    Loading User Symbols
    Loading unloaded module list
    ...........
    Unable to load image atikmdag.sys, Win32 error 0n2
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000094, fffff8800f1531dd, fffff88002ef7f38, fffff88002ef7790}
    
    Probably caused by : atikmdag.sys ( atikmdag+7c1dd )
    
    Followup: MachineOwner
    ---------
    
    1: kd> lmvm atikmdag
    start             end                 module name
    fffff880`0f0d7000 fffff880`0ffe7000   atikmdag   (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Fri Apr 18 08:13:16 2014 (53508A3C)
        CheckSum:         00EAEEE6
        ImageSize:        00F10000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Perform a Clean boot:

    Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

    Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:
    • Click on the
    • Type CMD on Search
    • Left click and Run as Administrator
    • Type SFC /scannow

    Full tutorial here:

    Check for heating issues using Speccy or HWMonitor. Upload a screen shot with either of the tools:

    Run Disk Check on your Hard Drive for file system errors and bad sectors on it:

    Upload a screenshot of your hard disk using Crystal Disk Info:
      My Computer


  3. Posts : 27
    Windows 7 Home Premium 64-Bit
    Thread Starter
       #3

    koolkat77 said:
    Welcome to the forum Androshi,

    Please remove Advanced System Care & AVG from the system.

    System Optimisers
    Please remove the following software:

    This software can be cause of BSOD's. The windows 7 operating system does not require these registry cleaning software. They often tune-down rather than tune-up and can wreck the OS beyond repair. Microsoft have improved Windows 7 significantly and it is much better at organising and optimising itself than its predecessors. Check this, this and this thread for evidence.

    If you feel the need to use a registry cleaning or optimisation software, most of us recommend the use of CCleaner but make sure you back up the registry before making letting ccleaner delete anything.
    Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability
    compared to other antivirus or internet security software. It is free and lightweight:-

       Warning
    Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.


    Code:
    Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\admin\Downloads\USER-PC-Sun_08_17_2014_175703_80\081714-18049-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`02e4d000 PsLoadedModuleList = 0xfffff800`03090890
    Debug session time: Mon Aug 18 05:47:19.952 2014 (UTC + 6:00)
    System Uptime: 0 days 4:52:01.590
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................
    Loading User Symbols
    Loading unloaded module list
    ...........
    Unable to load image atikmdag.sys, Win32 error 0n2
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000094, fffff8800f1531dd, fffff88002ef7f38, fffff88002ef7790}
    
    Probably caused by : atikmdag.sys ( atikmdag+7c1dd )
    
    Followup: MachineOwner
    ---------
    
    1: kd> lmvm atikmdag
    start             end                 module name
    fffff880`0f0d7000 fffff880`0ffe7000   atikmdag   (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Fri Apr 18 08:13:16 2014 (53508A3C)
        CheckSum:         00EAEEE6
        ImageSize:        00F10000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Perform a Clean boot:

    Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

    Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:
    • Click on the
    • Type CMD on Search
    • Left click and Run as Administrator
    • Type SFC /scannow

    Full tutorial here:

    Check for heating issues using Speccy or HWMonitor. Upload a screen shot with either of the tools:

    Run Disk Check on your Hard Drive for file system errors and bad sectors on it:

    Upload a screenshot of your hard disk using Crystal Disk Info:
    I followed your steps and the only things that were running were the microsoft stuff and steam used to play neverwinter and it lasted for about 3 hrs and then it froze. So I guess it was almost fixed but still ended up freezing.
      My Computer


  4. Posts : 27
    Windows 7 Home Premium 64-Bit
    Thread Starter
       #4

    Latest BSOD crash after about 4 hours

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.768.3
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 1000007e
    BCP1: FFFFFFFFC0000094
    BCP2: FFFFF8800F0EC1DD
    BCP3: FFFFF8800366CF38
    BCP4: FFFFF8800366C790
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1

    Files that help describe the problem:
    C:\Windows\Minidump\082214-21574-01.dmp
    C:\Users\user\AppData\Local\Temp\WER-78234-0.sysdata.xml
      My Computer


  5. Posts : 27
    Windows 7 Home Premium 64-Bit
    Thread Starter
       #5

    Anybody around to help? I mean Iv'e tried updating my drivers and checking my computer anyone got a solution?
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    The zip you uploaded in post #4 does not contain any crash dump.

    Follow it: Dump Files - Configure Windows to Create on BSOD
    Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

    Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

    Dont run any disc cleanup before you upload another zip.
      My Computer


  7. Posts : 27
    Windows 7 Home Premium 64-Bit
    Thread Starter
       #7

    Arc said:
    The zip you uploaded in post #4 does not contain any crash dump.

    Follow it: Dump Files - Configure Windows to Create on BSOD
    Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

    Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

    Dont run any disc cleanup before you upload another zip.
    So my computer crashed again after a couple hours and here's the minidump.
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #8

    Uninstall your installed version of the display driver.


    Then clean up any possible leftover.


    Then install version 13.9 WHQL only.


    When done, stress test the Graphics Card using Furmark. Let us know the result.

    Also, is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .
    ____________________________________
    Code:
    Unable to load image atikmdag.sys, Win32 error 0n2
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000094, fffff8800f1421dd, fffff880036c3f38, fffff880036c3790}
    
    Probably caused by : atikmdag.sys ( atikmdag+7c1dd )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    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.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000094, The exception code that was not handled
    Arg2: fffff8800f1421dd, The address that the exception occurred at
    Arg3: fffff880036c3f38, Exception Record Address
    Arg4: fffff880036c3790, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.
    
    FAULTING_IP: 
    atikmdag+7c1dd
    fffff880`0f1421dd 41f7f1          div     eax,r9d
    
    EXCEPTION_RECORD:  fffff880036c3f38 -- (.exr 0xfffff880036c3f38)
    ExceptionAddress: fffff8800f1421dd (atikmdag+0x000000000007c1dd)
       ExceptionCode: c0000094 (Integer divide-by-zero)
      ExceptionFlags: 00000000
    NumberParameters: 0
    
    CONTEXT:  fffff880036c3790 -- (.cxr 0xfffff880036c3790;r)
    rax=0000000000ad08e0 rbx=fffff880036c41c0 rcx=fffff880036c4200
    rdx=0000000000000000 rsi=fffffa8005e5e400 rdi=fffff8800f0c6000
    rip=fffff8800f1421dd rsp=fffff880036c4170 rbp=fffff880036c4220
     r8=0000000000ad08e0  r9=0000000000000000 r10=0000000000000186
    r11=fffff8800f3c3f60 r12=00000000000009dd r13=00000000000009de
    r14=0000000000000026 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    atikmdag+0x7c1dd:
    fffff880`0f1421dd 41f7f1          div     eax,r9d
    Last set context:
    rax=0000000000ad08e0 rbx=fffff880036c41c0 rcx=fffff880036c4200
    rdx=0000000000000000 rsi=fffffa8005e5e400 rdi=fffff8800f0c6000
    rip=fffff8800f1421dd rsp=fffff880036c4170 rbp=fffff880036c4220
     r8=0000000000ad08e0  r9=0000000000000000 r10=0000000000000186
    r11=fffff8800f3c3f60 r12=00000000000009dd r13=00000000000009de
    r14=0000000000000026 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    atikmdag+0x7c1dd:
    fffff880`0f1421dd 41f7f1          div     eax,r9d
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x7E
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff880036c41c0 to fffff8800f1421dd
    
    STACK_TEXT:  
    fffff880`036c4170 fffff880`036c41c0 : fffff880`036c4220 fffffa80`05e5e000 00000000`00000018 fffff880`036c4260 : atikmdag+0x7c1dd
    fffff880`036c4178 fffff880`036c4220 : fffffa80`05e5e000 00000000`00000018 fffff880`036c4260 fffff880`0f141172 : 0xfffff880`036c41c0
    fffff880`036c4180 fffffa80`05e5e000 : 00000000`00000018 fffff880`036c4260 fffff880`0f141172 00000000`00000027 : 0xfffff880`036c4220
    fffff880`036c4188 00000000`00000018 : fffff880`036c4260 fffff880`0f141172 00000000`00000027 00000000`00000000 : 0xfffffa80`05e5e000
    fffff880`036c4190 fffff880`036c4260 : fffff880`0f141172 00000000`00000027 00000000`00000000 00000000`00000000 : 0x18
    fffff880`036c4198 fffff880`0f141172 : 00000000`00000027 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`036c4260
    fffff880`036c41a0 00000000`00000027 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`036c4260 : atikmdag+0x7b172
    fffff880`036c41a8 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff880`036c4260 fffffa80`05e5e400 : 0x27
    
    
    FOLLOWUP_IP: 
    atikmdag+7c1dd
    fffff880`0f1421dd 41f7f1          div     eax,r9d
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  atikmdag+7c1dd
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmdag
    
    IMAGE_NAME:  atikmdag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53508a3c
    
    STACK_COMMAND:  .cxr 0xfffff880036c3790 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_atikmdag+7c1dd
    
    BUCKET_ID:  X64_0x7E_atikmdag+7c1dd
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x7e_atikmdag+7c1dd
    
    FAILURE_ID_HASH:  {2fe4d852-c614-c3ac-d02e-9ffc6a9bcc79}
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm atikmdag
    start             end                 module name
    fffff880`0f0c6000 fffff880`0ffd6000   atikmdag   (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Fri Apr 18 07:43:16 2014 (53508A3C)
        CheckSum:         00EAEEE6
        ImageSize:        00F10000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  9. Posts : 27
    Windows 7 Home Premium 64-Bit
    Thread Starter
       #9

    Arc said:
    Uninstall your installed version of the display driver.


    Then clean up any possible leftover.


    Then install version 13.9 WHQL only.


    When done, stress test the Graphics Card using Furmark. Let us know the result.

    Also, is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .
    ____________________________________
    Code:
    Unable to load image atikmdag.sys, Win32 error 0n2
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000094, fffff8800f1421dd, fffff880036c3f38, fffff880036c3790}
    
    Probably caused by : atikmdag.sys ( atikmdag+7c1dd )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    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.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000094, The exception code that was not handled
    Arg2: fffff8800f1421dd, The address that the exception occurred at
    Arg3: fffff880036c3f38, Exception Record Address
    Arg4: fffff880036c3790, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.
    
    FAULTING_IP: 
    atikmdag+7c1dd
    fffff880`0f1421dd 41f7f1          div     eax,r9d
    
    EXCEPTION_RECORD:  fffff880036c3f38 -- (.exr 0xfffff880036c3f38)
    ExceptionAddress: fffff8800f1421dd (atikmdag+0x000000000007c1dd)
       ExceptionCode: c0000094 (Integer divide-by-zero)
      ExceptionFlags: 00000000
    NumberParameters: 0
    
    CONTEXT:  fffff880036c3790 -- (.cxr 0xfffff880036c3790;r)
    rax=0000000000ad08e0 rbx=fffff880036c41c0 rcx=fffff880036c4200
    rdx=0000000000000000 rsi=fffffa8005e5e400 rdi=fffff8800f0c6000
    rip=fffff8800f1421dd rsp=fffff880036c4170 rbp=fffff880036c4220
     r8=0000000000ad08e0  r9=0000000000000000 r10=0000000000000186
    r11=fffff8800f3c3f60 r12=00000000000009dd r13=00000000000009de
    r14=0000000000000026 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    atikmdag+0x7c1dd:
    fffff880`0f1421dd 41f7f1          div     eax,r9d
    Last set context:
    rax=0000000000ad08e0 rbx=fffff880036c41c0 rcx=fffff880036c4200
    rdx=0000000000000000 rsi=fffffa8005e5e400 rdi=fffff8800f0c6000
    rip=fffff8800f1421dd rsp=fffff880036c4170 rbp=fffff880036c4220
     r8=0000000000ad08e0  r9=0000000000000000 r10=0000000000000186
    r11=fffff8800f3c3f60 r12=00000000000009dd r13=00000000000009de
    r14=0000000000000026 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    atikmdag+0x7c1dd:
    fffff880`0f1421dd 41f7f1          div     eax,r9d
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x7E
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff880036c41c0 to fffff8800f1421dd
    
    STACK_TEXT:  
    fffff880`036c4170 fffff880`036c41c0 : fffff880`036c4220 fffffa80`05e5e000 00000000`00000018 fffff880`036c4260 : atikmdag+0x7c1dd
    fffff880`036c4178 fffff880`036c4220 : fffffa80`05e5e000 00000000`00000018 fffff880`036c4260 fffff880`0f141172 : 0xfffff880`036c41c0
    fffff880`036c4180 fffffa80`05e5e000 : 00000000`00000018 fffff880`036c4260 fffff880`0f141172 00000000`00000027 : 0xfffff880`036c4220
    fffff880`036c4188 00000000`00000018 : fffff880`036c4260 fffff880`0f141172 00000000`00000027 00000000`00000000 : 0xfffffa80`05e5e000
    fffff880`036c4190 fffff880`036c4260 : fffff880`0f141172 00000000`00000027 00000000`00000000 00000000`00000000 : 0x18
    fffff880`036c4198 fffff880`0f141172 : 00000000`00000027 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`036c4260
    fffff880`036c41a0 00000000`00000027 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`036c4260 : atikmdag+0x7b172
    fffff880`036c41a8 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff880`036c4260 fffffa80`05e5e400 : 0x27
    
    
    FOLLOWUP_IP: 
    atikmdag+7c1dd
    fffff880`0f1421dd 41f7f1          div     eax,r9d
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  atikmdag+7c1dd
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmdag
    
    IMAGE_NAME:  atikmdag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53508a3c
    
    STACK_COMMAND:  .cxr 0xfffff880036c3790 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_atikmdag+7c1dd
    
    BUCKET_ID:  X64_0x7E_atikmdag+7c1dd
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x7e_atikmdag+7c1dd
    
    FAILURE_ID_HASH:  {2fe4d852-c614-c3ac-d02e-9ffc6a9bcc79}
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm atikmdag
    start             end                 module name
    fffff880`0f0c6000 fffff880`0ffd6000   atikmdag   (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Fri Apr 18 07:43:16 2014 (53508A3C)
        CheckSum:         00EAEEE6
        ImageSize:        00F10000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Well I ran Furmark and it lasted about 1000+ frames and said 7FPS and the temp reached about 90C at the bottom before the computer shutdown.

    Ran speccy and here's the URL.
    http://speccy.piriform.com/results/3...fo0zCgGuwl26Kf

    The temp. for cores so far:
    Core #0 32C min. 32C max. 38c
    Core #1 30C min. 28C max. 31c
    Last edited by Androshi; 08 Sep 2014 at 18:57. Reason: more information
      My Computer


  10. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #10

    It looks absurd.
    Try HWinfo to make it sure.

    You said ....
    the temp reached about 90C at the bottom before the computer shutdown.
    Did it shut down at its own?
      My Computer


 
Page 1 of 5 123 ... 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 00:25.
Find Us