Bsod system_thread_exception_not_handled

Page 1 of 3 123 LastLast

  1. Posts : 14
    Windows 7 Ultimate 32bit
       #1

    Bsod system_thread_exception_not_handled


    (while i was writing here another BSOD appeared)

    computer is "old" (2009), after many BSOD at windows xp and windows 7 ultimate x64 I installed windows 7 ultimate x86 a week ago. I was prepared for BSOD and after my personal research I uninstalled the display driver, windows installed and installed by myself the original from ati site. all were fine (5-6 days now) since today.
    i had utorrent open downloading and when I returned i saw the minidump files open and everything closed.then after some minutes while i was writing here and everything was closed except firefox another BSOD!

    OS: Windows 7 ultimate x64
    CPU: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz 3.17GHz
    RAM: 4.00 GB (3.00 GB usable)* *first time I see that, last days I could use all 4GB! (?!)*
    GPU: ASUS EAH5850 1GB DDR5

    BlueScreenView says:
    Caused by driver atikmdag.sys
    atikmpag.sys
    dxgkrnl.sys
    NETIO.SYS
    ntkrnlpa.exe
    tcpip.sys

    I have my minidumps attached for you :)
    btw why I can't use all 4GB RAM ? I could some days ago
      My Computer


  2. Posts : 14
    Windows 7 Ultimate 32bit
    Thread Starter
       #2

    I could use all 4GB because I had windows ultimate x64 right ? silly me.. nevermind with that!

    Looking forward to your search
    George
      My Computer


  3. Posts : 14
    Windows 7 Ultimate 32bit
    Thread Starter
       #3

    anyone guys ? :/
      My Computer


  4. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #4

    BSODs caused by your display driver, the problem lies in your Graphics card or RAM, it is hardware related
    STOP 0x116: VIDEO_TDR_ERROR troubleshooting

    RAM - Test with Memtest86+
    If the RAM is ok then the cause is the HD5850, a RMA would be necessary
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {85188310, 90529d68, 0, 2}
    
    Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by : atikmpag.sys ( atikmpag+5d68 )
    
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: 85188310, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: 90529d68, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 00000002, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    atikmpag+5d68
    90529d68 8bff            mov     edi,edi
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    8eaefba4 906bac26 00000116 85188310 90529d68 nt!KeBugCheckEx+0x1e
    8eaefbc8 906bba45 90529d68 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
    8eaefbec 906eb92c 00000000 00000000 8eaefcb0 dxgkrnl!TdrIsRecoveryRequired+0xb8
    8eaefc64 90712c1d fffffcfb 0003a744 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
    8eaefc90 906f2993 871ca458 8eaefcb0 00000102 dxgmms1!VidSchWaitForCompletionEvent+0x16f
    8eaefd28 907173c9 00000000 82a793c1 871ca458 dxgmms1!VidSchiScheduleCommandToRun+0x14d
    8eaefd3c 90717485 871ca458 00000000 87290410 dxgmms1!VidSchiRun_PriorityTable+0xf
    8eaefd50 82c4b9df 871ca458 a0f4fb25 00000000 dxgmms1!VidSchiWorkerThread+0x7f
    8eaefd90 82afd219 90717406 871ca458 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmpag+5d68
    90529d68 8bff            mov     edi,edi
    
    SYMBOL_NAME:  atikmpag+5d68
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME:  atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4dae3541
    
    FAILURE_BUCKET_ID:  0x116_IMAGE_atikmpag.sys
    
    BUCKET_ID:  0x116_IMAGE_atikmpag.sys
    
    Followup: MachineOwner
    ---------
      My Computer


  5. Posts : 14
    Windows 7 Ultimate 32bit
    Thread Starter
       #5

    thanks yowanvista for your reply. I will run Memtest86+ now.
    I got another BSOD from my last visit here, I uploaded the minidump file.
    brb with the results from Memtest
      My Computer


  6. Posts : 14
    Windows 7 Ultimate 32bit
    Thread Starter
       #6

    Hello again yowanvista.
    Memtest was running for 16 hours yesterday as i fell asleep :P
    After 16 hours of testing and 14 passes found 1 error at 9th pass at the 3rd test I believe.
    So what should I do next ? Test each stick of RAM separately ?
      My Computer


  7. Posts : 507
    Windows 7 Ultimate x64 SP1
       #7

    Glaros said:
    Hello again yowanvista.
    Memtest was running for 16 hours yesterday as i fell asleep :P
    After 16 hours of testing and 14 passes found 1 error at 9th pass at the 3rd test I believe.
    So what should I do next ? Test each stick of RAM separately ?
    Yes test each stick individually.
    Also test each slot with a known good stick to find out whether there is any bad mobo slot.
      My Computer


  8. Posts : 14
    Windows 7 Ultimate 32bit
    Thread Starter
       #8

    wish said:
    Yes test each stick individually.
    Also test each slot with a known good stick to find out whether there is any bad mobo slot.
    Hello again!
    I am back with wierds news. My mb has 4 slots, 2 blue, 2 pink.. I checked both of my RAM at first slot(blue) and after 27 and 19 passes nothing showed up, no error. I was like damn.. motherboard must be the problem but at the third slot(second blue) memtest hasnt shown an error either after 17 passes now..
    How is that possible ? anyone experienced enough here with a theory ?
    what should I do next ?!
      My Computer


  9. Posts : 507
    Windows 7 Ultimate x64 SP1
       #9

    Glaros said:
    Hello again!
    I am back with wierds news. My mb has 4 slots, 2 blue, 2 pink.. I checked both of my RAM at first slot(blue) and after 27 and 19 passes nothing showed up, no error. I was like damn.. motherboard must be the problem but at the third slot(second blue) memtest hasnt shown an error either after 17 passes now..
    How is that possible ? anyone experienced enough here with a theory ?
    what should I do next ?!
    Did you have another BSOD since then?
    Would be better to follow this instruction and collect more files:
    https://www.sevenforums.com/crashes-d...tructions.html
      My Computer


  10. Posts : 14
    Windows 7 Ultimate 32bit
    Thread Starter
       #10

    hello again.
    I have only 1 stick of RAM connected since I don't spend so time with the computer nowadays and today I returned home to see that another BSOD had appeared.
    i have attached the minidump file can you please check it again ?
    its so annoying trying to find whats happening and can't find the actual problem :S
      My Computer


 
Page 1 of 3 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 17:38.
Find Us