BSOD in games after last Nvidia update

Page 3 of 7 FirstFirst 12345 ... LastLast

  1. Posts : 41
    Windows 7 Ultimate x64
    Thread Starter
       #21

    I already did all that. PSU was amongst first things i suspected. All voltages were what they are supposed to be. I can recheck cables later. Also OCCT psu test didnt give me any errors. I let it run for couple hours. I im not sure how it works, but i think that it stresses PSU as much as it can while checking voltages.
      My Computer


  2. Posts : 7,050
    Windows 10 Pro
       #22

    Anything else you already have done but isn't mentioned here?
      My Computer


  3. Posts : 41
    Windows 7 Ultimate x64
    Thread Starter
       #23

    Because stuffs started after gpu drivers update and c++ error i have reinstalled all reditr packages.
    Then i reinstalled dx webinstaller. Rolled back drivers and keep rolling back i read that some might fix this stuff.
    Configured stuffs in nvidia panel. Uninstalled all nvidia "extras" like geforce experience / hd audio / 3d vision. I have now only latest physix and gpu drivers.

    And then i only did what ya asked and run tests i have mentioned above.

    Also i tried bunch of different games and none dx10/11 seems to work anymore.

    And then i reinstalled all dotNET files.

    I think thats all.

    One thing i havent tried is system restore. I read that it might help.
      My Computer


  4. Posts : 7,050
    Windows 10 Pro
       #24

    System restore indeed sometimes helps, it just gives you time to figure out what went wrong and prevent the problem.

    What GPU drivers were installed before you updated them?
    Have you tried clean installing them again?
      My Computer


  5. Posts : 41
    Windows 7 Ultimate x64
    Thread Starter
       #25

    Yeah several times. I even used nvidia uninstall tool. After that i cleaned registry to make sure that nothing is left. Even ones i was using arent working naymore.
    But before crashes started i was using 358.59
    Before that everything was fine and on those drivers everything worked fine.
    I preordered assassins creed syndicate so i got it 3 days earlier before release. So i played it without any problems for 3 days. Then on launch day nvidia released new drivers "day 1 drivers for syndicate" and while installing via geforce experience i got that error. I tried to install em again via geforce experience and got same error. Then i downloaded manually latest driver and installed it. It installed fine without problems. I launched syndicate and got my first BSOD.

    After boot i launched syndicate again and again got BSOD.
    I rerolled drivers back tried again and again BSOD.
    Then i though that problem has to be with syndicate and tried to play "Evil within" and again i got BSOD.
    Then later i tried to play "Zombie Army Trilogy" but again got BSOD.

    Some might have been just crashes. Also sometimes when game just crashed it exits to windows i get message that "video driver stopped working" and then 1-2 min later i get BSOD.

    After rerolling and cleaning drivers i no longer get video driver stopped working error, but i still cannot play anything.

    Now i get BSOD's less often. Now i get 90% just game crashes without bsod's but maybe 1/10 crashes is still bsod.
      My Computer


  6. Posts : 7,050
    Windows 10 Pro
       #26

    Thank you for the additional information :)

    Lunideth said:
    Alright ill do it and test it out. But thing is that sometimes games crashes without BSOD. What to do then?
    Back to this, do you usually have anything else open at time of the crash?
      My Computer


  7. Posts : 41
    Windows 7 Ultimate x64
    Thread Starter
       #27

    Yeah i have opera & winamp running at all times. Also i have steam running because most of my games are steam games. But during testing i have closed everything besides games. And it didnt help
      My Computer


  8. Posts : 7,050
    Windows 10 Pro
       #28

    Are any irrelevant background processes also closed when playing?
      My Computer


  9. Posts : 41
    Windows 7 Ultimate x64
    Thread Starter
       #29

    No nothing irrevelant.

    I downloaded Debugger and debugged all crash dumps i could find. Here they are from oldest to most resent one:

    Code:
    11.27.15
    *******************************************************************************
    *                                                                             *
    *                        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: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff800032c6954, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003500100
    GetUlongFromAddress: unable to read from fffff800035001c0
     0000000000000000 Nonpaged pool
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - K sky osoitteessa 0x%08lx viittasi muistiin osoitteessa 0x%08lx. Muisti ei voi olla %s.
    
    FAULTING_IP: 
    nt!SwapContext_PatchXRstor+0
    fffff800`032c6954 0fae09          fxrstor [rcx]
    
    BUGCHECK_STR:  0x1E_c0000005_R
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  NvStreamUserAg
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff80003343b02 to fffff800032c2c40
    
    STACK_TEXT:  
    fffff880`02626ee8 fffff800`03343b02 : 00000000`0000001e ffffffff`c0000005 fffff800`032c6954 00000000`00000000 : nt!KeBugCheckEx
    fffff880`02626ef0 fffff800`032c22c2 : fffff880`026276c8 fffff880`009b2180 fffff880`02627770 fffffa80`09ad29b0 : nt! ?? ::FNODOBFM::`string'+0x4805d
    fffff880`02627590 fffff800`032c0bca : fffffa80`00000007 00000000`00000000 fffffa80`0aad29b0 00001f80`6e000200 : nt!KiExceptionDispatch+0xc2
    fffff880`02627770 fffff800`032c6954 : 00000000`00000004 00000000`00000000 00000000`0c000000 00000000`03000000 : nt!KiGeneralProtectionFault+0x10a
    fffff880`02627900 fffff800`0a2c654a : 00000000`00000000 00000000`00000000 fffff880`03586180 fffffa80`0fcabb50 : nt!SwapContext_PatchXRstor
    fffff880`02627940 00000000`00000000 : 00000000`00000000 fffff880`03586180 fffffa80`0fcabb50 00000000`00000000 : 0xfffff800`0a2c654a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!SwapContext_PatchXRstor+0
    fffff800`032c6954 0fae09          fxrstor [rcx]
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  nt!SwapContext_PatchXRstor+0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5625815c
    
    IMAGE_VERSION:  6.1.7601.19045
    
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!SwapContext_PatchXRstor+0
    
    BUCKET_ID:  X64_0x1E_c0000005_R_nt!SwapContext_PatchXRstor+0
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x1e_c0000005_r_nt!swapcontext_patchxrstor+0
    
    FAILURE_ID_HASH:  {671230d7-e8c2-3f79-42f1-62befebb6419}
    
    Followup: MachineOwner
    ---------

    Code:
    11.30.15
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000005000, The subtype of the bugcheck.
    Arg2: fffff70001080000
    Arg3: 00000000a1000b58
    Arg4: 000000007a000d6e
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x1a_5000
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  NvStreamNetwor
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    TRAP_FRAME:  fffff880113cf8a0 -- (.trap 0xfffff880113cf8a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800fad4810
    rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800035c9aba rsp=fffff880113cfa30 rbp=fffffa800f984b10
     r8=fffffa800f9c2380  r9=00000000ffffffff r10=fffffa800bff5170
    r11=fffffa800f984f58 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!MmCreateTeb+0x6e:
    fffff800`035c9aba c74320001e0000  mov     dword ptr [rbx+20h],1E00h ds:00000000`00000020=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80003270e5e to fffff800032d5c40
    
    STACK_TEXT:  
    fffff880`113cf738 fffff800`03270e5e : 00000000`0000001a 00000000`00005000 fffff700`01080000 00000000`a1000b58 : nt!KeBugCheckEx
    fffff880`113cf740 fffff800`032d3d6e : 00000000`00000001 000007ff`fffa0020 fffffa80`0f984b00 000007ff`fffa0000 : nt! ?? ::FNODOBFM::`string'+0x425a3
    fffff880`113cf8a0 fffff800`035c9aba : fffffa80`0f984b10 00000000`00000000 00000004`00001818 fffff880`113cfac0 : nt!KiPageFault+0x16e
    fffff880`113cfa30 fffff800`035c3f7b : 000007ff`fffa0000 00000000`00001002 00000000`00000000 00000000`00001000 : nt!MmCreateTeb+0x6e
    fffff880`113cfac0 fffff800`035c3ae6 : fffffa80`0f984b10 fffff880`113d0928 fffffa80`096dea00 fffff880`113d0510 : nt!PspAllocateThread+0x35f
    fffff880`113cfce0 fffff800`035c919d : 00000000`00000000 00000000`00000000 00000000`00000001 fffff880`113d0510 : nt!PspCreateThread+0x1d2
    fffff880`113cff60 fffff800`032d4ed3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtCreateThreadEx+0x25d
    fffff880`113d06b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+425a3
    fffff800`03270e5e cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+425a3
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5625815c
    
    IMAGE_VERSION:  6.1.7601.19045
    
    FAILURE_BUCKET_ID:  X64_0x1a_5000_nt!_??_::FNODOBFM::_string_+425a3
    
    BUCKET_ID:  X64_0x1a_5000_nt!_??_::FNODOBFM::_string_+425a3
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x1a_5000_nt!_??_::fnodobfm::_string_+425a3
    
    FAILURE_ID_HASH:  {20848214-5c7f-d095-3d13-1335455dfdb5}
    
    Followup: MachineOwner
    ---------
    Code:
    12.02.15
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    BAD_POOL_CALLER (c2)
    The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
    Arguments:
    Arg1: 0000000000000099, Attempt to free pool with invalid address  (or corruption in pool header)
    Arg2: fffffa801055a9b0, Address being freed
    Arg3: 0000000000000000, 0
    Arg4: 0000000000000000, 0
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    USBPORT!USBPORT_Core_iCompleteDoneTransfer+b2f
    fffff880`0528a74b 4881c498000000  add     rsp,98h
    
    BUGCHECK_STR:  0xc2_99
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  ZAT.exe
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    DPC_STACK_BASE:  FFFFF88003322FB0
    
    LAST_CONTROL_TRANSFER:  from fffff8000375c4ec to fffff800032c6c40
    
    STACK_TEXT:  
    fffff880`03322b98 fffff800`0375c4ec : 00000000`000000c2 00000000`00000099 fffffa80`1055a9b0 00000000`00000000 : nt!KeBugCheckEx
    fffff880`03322ba0 fffff800`0337fd21 : fffffa80`0f808e4b 00000000`00000000 fffffa80`78dea180 00000000`00000050 : nt!VerifierBugCheckIfAppropriate+0x3c
    fffff880`03322be0 fffff800`033fdc83 : fffffa80`1055a9a0 00000000`00000660 00000000`0000007e 00000000`00000000 : nt!VerifierFreeTrackedPool+0x41
    fffff880`03322c20 fffff880`0528a74b : fffffa80`0cd4dc00 fffffa80`588c1810 fffffa80`0cd99002 00000000`00000000 : nt!ExFreePool+0xd4f
    fffff880`03322cd0 fffff880`0528ab0f : fffffa80`1055a902 fffffa80`0f808c10 00000000`ffffffff fffffa80`0cd99eb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xb2f
    fffff880`03322db0 fffff880`0528866f : fffffa80`0cd99eb0 fffffa80`0cd991a0 fffffa80`0cd9a050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
    fffff880`03322e10 fffff880`05279f89 : fffffa80`0cd99050 00000000`00000000 fffffa80`0cd99e02 fffffa80`0cd99eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
    fffff880`03322e50 fffff880`01088c74 : fffffa80`0cd63000 fffff880`05279db0 fffffa80`0cd99e00 fffff880`03322ef8 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
    fffff880`03322e80 fffffa80`0cd63000 : fffff880`05279db0 fffffa80`0cd99e00 fffff880`03322ef8 00000000`00000000 : sptd+0x1dc74
    fffff880`03322e88 fffff880`05279daf : fffffa80`0cd99e00 fffff880`03322ef8 00000000`00000000 fffff880`009e8180 : 0xfffffa80`0cd63000
    fffff880`03322e90 fffffa80`0cd99e00 : fffff880`03322ef8 00000000`00000000 fffff880`009e8180 fffff880`009ec9e8 : USBPORT!USBPORT_Xdpc_End+0x26f
    fffff880`03322e98 fffff880`03322ef8 : 00000000`00000000 fffff880`009e8180 fffff880`009ec9e8 00000000`75462450 : 0xfffffa80`0cd99e00
    fffff880`03322ea0 00000000`00000000 : fffff880`009e8180 fffff880`009ec9e8 00000000`75462450 00000000`00000000 : 0xfffff880`03322ef8
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    sptd+1dc74
    fffff880`01088c74 ??              ???
    
    SYMBOL_STACK_INDEX:  8
    
    SYMBOL_NAME:  sptd+1dc74
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: sptd
    
    IMAGE_NAME:  sptd.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5489afbc
    
    FAILURE_BUCKET_ID:  X64_0xc2_99_sptd+1dc74
    
    BUCKET_ID:  X64_0xc2_99_sptd+1dc74
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0xc2_99_sptd+1dc74
    
    FAILURE_ID_HASH:  {3ecd67c1-4e3a-b959-820d-912eba9855ce}
    
    Followup: MachineOwner
    ---------
    Code:
    12.04.15
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    BAD_POOL_HEADER (19)
    The pool is already corrupt at the time of the current request.
    This may or may not be due to the caller.
    The internal pool links must be walked to figure out a possible cause of
    the problem, and then special pool applied to the suspect tags or the driver
    verifier to a suspect driver.
    Arguments:
    Arg1: 0000000000000003, the pool freelist is corrupt.
    Arg2: fffff8a01a6b8010, the pool entry being checked.
    Arg3: fffff8a01a6b8010, the read back flink freelist value (should be the same as 2).
    Arg4: fffff8a0f16b8010, the read back blink freelist value (should be the same as 2).
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x19_3
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff800033f971f to fffff800032c2c40
    
    STACK_TEXT:  
    fffff880`039daab8 fffff800`033f971f : 00000000`00000019 00000000`00000003 fffff8a0`1a6b8010 fffff8a0`1a6b8010 : nt!KeBugCheckEx
    fffff880`039daac0 fffff800`033fb1b1 : 00000000`00000000 fffff8a0`0d878f60 00000000`00000000 00000000`00000000 : nt!ExFreePool+0x76b
    fffff880`039dab50 fffff880`044984b9 : fffffa80`5daafa50 fffff8a0`4355e270 00000000`41466153 00000000`00000162 : nt!ExFreePoolWithTag+0x411
    fffff880`039dac00 fffffa80`5daafa50 : fffff8a0`4355e270 00000000`41466153 00000000`00000162 fffff8a0`0d878f70 : SRTSP64+0x174b9
    fffff880`039dac08 fffff8a0`4355e270 : 00000000`41466153 00000000`00000162 fffff8a0`0d878f70 fffff880`04484b02 : 0xfffffa80`5daafa50
    fffff880`039dac10 00000000`41466153 : 00000000`00000162 fffff8a0`0d878f70 fffff880`04484b02 00000000`00000000 : 0xfffff8a0`4355e270
    fffff880`039dac18 00000000`00000162 : fffff8a0`0d878f70 fffff880`04484b02 00000000`00000000 fffff880`04499445 : 0x41466153
    fffff880`039dac20 fffff8a0`0d878f70 : fffff880`04484b02 00000000`00000000 fffff880`04499445 00000000`00000010 : 0x162
    fffff880`039dac28 fffff880`04484b02 : 00000000`00000000 fffff880`04499445 00000000`00000010 00000000`00000282 : 0xfffff8a0`0d878f70
    fffff880`039dac30 00000000`00000000 : fffff880`04499445 00000000`00000010 00000000`00000282 fffff8a0`1dad5930 : SRTSP64+0x3b02
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!ExFreePool+76b
    fffff800`033f971f cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!ExFreePool+76b
    
    FOLLOWUP_NAME:  Pool_corruption
    
    IMAGE_NAME:  Pool_Corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  6.1.7601.19045
    
    MODULE_NAME: Pool_Corruption
    
    FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExFreePool+76b
    
    BUCKET_ID:  X64_0x19_3_nt!ExFreePool+76b
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x19_3_nt!exfreepool+76b
    
    FAILURE_ID_HASH:  {ab733f4b-3d44-7e7f-b6aa-ca74429c9e0d}
    
    Followup: Pool_corruption
    ---------
    Code:
    12.05.15
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000061944, The subtype of the bugcheck.
    Arg2: 000000004f1b8a90
    Arg3: 00000000000051f5
    Arg4: fffffa8057e750b0
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x1a_61944
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  ACS.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff80003210165 to fffff80003274c40
    
    STACK_TEXT:  
    fffff880`0bda7ab8 fffff800`03210165 : 00000000`0000001a 00000000`00061944 00000000`4f1b8a90 00000000`000051f5 : nt!KeBugCheckEx
    fffff880`0bda7ac0 fffff800`03272d6e : 00000000`00000000 00000000`4f1b8a90 00000000`002faf01 00000000`06c3ccc0 : nt! ?? ::FNODOBFM::`string'+0x42905
    fffff880`0bda7c20 000007fe`f4417313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`1714f8a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`f4417313
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+42905
    fffff800`03210165 cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+42905
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5625815c
    
    IMAGE_VERSION:  6.1.7601.19045
    
    FAILURE_BUCKET_ID:  X64_0x1a_61944_nt!_??_::FNODOBFM::_string_+42905
    
    BUCKET_ID:  X64_0x1a_61944_nt!_??_::FNODOBFM::_string_+42905
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x1a_61944_nt!_??_::fnodobfm::_string_+42905
    
    FAILURE_ID_HASH:  {65217a76-d619-49e2-f639-9ba654b21552}
    
    Followup: MachineOwner
      My Computer


  10. Posts : 41
    Windows 7 Ultimate x64
    Thread Starter
       #30

    And last part that didnt fit in previous post

    Code:
    12.12.15
    *******************************************************************************
    *                                                                             *
    *                        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: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff800035f8a03, The address that the exception occurred at
    Arg3: fffff8800c4be148, Exception Record Address
    Arg4: fffff8800c4bd9a0, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - K sky osoitteessa 0x%08lx viittasi muistiin osoitteessa 0x%08lx. Muisti ei voi olla %s.
    
    FAULTING_IP: 
    nt!EtwpRealtimeDeliverBuffer+57
    fffff800`035f8a03 4d8b2424        mov     r12,qword ptr [r12]
    
    EXCEPTION_RECORD:  fffff8800c4be148 -- (.exr 0xfffff8800c4be148)
    ExceptionAddress: fffff800035f8a03 (nt!EtwpRealtimeDeliverBuffer+0x0000000000000057)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000000
    Attempt to read from address 0000000000000000
    
    CONTEXT:  fffff8800c4bd9a0 -- (.cxr 0xfffff8800c4bd9a0;r)
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800f3e6c01
    rdx=fffffa800c3e6dc0 rsi=fffffa800f3e6c80 rdi=fffff8800c4be410
    rip=fffff800035f8a03 rsp=fffff8800c4be380 rbp=0000000000000000
     r8=fffff8800c4be410  r9=0000000000000000 r10=000000000000000f
    r11=fffff8800c4bec90 r12=0000000000000000 r13=fffffa800f3e6dc0
    r14=0000000000000001 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe cy
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010203
    nt!EtwpRealtimeDeliverBuffer+0x57:
    fffff800`035f8a03 4d8b2424        mov     r12,qword ptr [r12] ds:002b:00000000`00000000=????????????????
    Last set context:
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800f3e6c01
    rdx=fffffa800c3e6dc0 rsi=fffffa800f3e6c80 rdi=fffff8800c4be410
    rip=fffff800035f8a03 rsp=fffff8800c4be380 rbp=0000000000000000
     r8=fffff8800c4be410  r9=0000000000000000 r10=000000000000000f
    r11=fffff8800c4bec90 r12=0000000000000000 r13=fffffa800f3e6dc0
    r14=0000000000000001 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe cy
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010203
    nt!EtwpRealtimeDeliverBuffer+0x57:
    fffff800`035f8a03 4d8b2424        mov     r12,qword ptr [r12] ds:002b:00000000`00000000=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - K sky osoitteessa 0x%08lx viittasi muistiin osoitteessa 0x%08lx. Muisti ei voi olla %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000000
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003515100
    GetUlongFromAddress: unable to read from fffff800035151c0
     0000000000000000 Nonpaged pool
    
    FOLLOWUP_IP: 
    nt!EtwpRealtimeDeliverBuffer+57
    fffff800`035f8a03 4d8b2424        mov     r12,qword ptr [r12]
    
    BUGCHECK_STR:  0x7E
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff8000331898d to fffff800035f8a03
    
    STACK_TEXT:  
    fffff880`0c4be380 fffff800`0331898d : 00000000`00000001 00000000`00000000 00000000`00000001 fffffa80`0f3e6c80 : nt!EtwpRealtimeDeliverBuffer+0x57
    fffff880`0c4be3d0 fffff800`035f8713 : fffffa80`0f3e0000 fffffa80`00000001 00000000`00000000 00000000`00000000 : nt!EtwpFlushActiveBuffers+0x13d
    fffff880`0c4becc0 fffff800`03571b86 : 01d1348d`5d516a95 fffffa80`0f3fd640 00000000`00000080 fffffa80`09744040 : nt!EtwpLogger+0x1ff
    fffff880`0c4bed40 fffff800`032c90e6 : fffff880`03364180 fffffa80`0f3fd640 fffffa80`0f3fdb50 fffff880`0c48d401 : nt!PspSystemThreadStartup+0x5a
    fffff880`0c4bed80 00000000`00000000 : fffff880`0c4bf000 fffff880`0c4b9000 fffff880`0c4be7f0 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!EtwpRealtimeDeliverBuffer+57
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5625815c
    
    IMAGE_VERSION:  6.1.7601.19045
    
    STACK_COMMAND:  .cxr 0xfffff8800c4bd9a0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_nt!EtwpRealtimeDeliverBuffer+57
    
    BUCKET_ID:  X64_0x7E_nt!EtwpRealtimeDeliverBuffer+57
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x7e_nt!etwprealtimedeliverbuffer+57
    
    FAILURE_ID_HASH:  {76afd303-2f65-9916-8f95-623cf80c10f9}
    
    Followup: MachineOwner
    ---------
      My Computer


 
Page 3 of 7 FirstFirst 12345 ... 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:39.
Find Us