BSOD Out of the blue when surfing net. ERROR: System_Service_Exception


  1. Posts : 6
    64
       #1

    BSOD Out of the blue when surfing net. ERROR: System_Service_Exception


    Hello i suddenly received this error on my custom built PC and i need help as i intend to give this PC to my cousin for his birthday in 3 days time... i cant seem to fix the error as it keeps popping up.

    Here is the minidump file

    https://www.dropbox.com/s/lygohte517...2-16614-01.dmp
      My Computer


  2. Posts : 851
    Windows 8 Professional x64
       #2

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff80002ca0284, Address of the instruction which caused the bugcheck
    Arg3: fffff880098d7c30, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    nt!SwapContext_PatchXRstor+0
    fffff800`02ca0284 0fae29          xrstor  [rcx]
    
    CONTEXT:  fffff880098d7c30 -- (.cxr 0xfffff880098d7c30)
    rax=0000000000000005 rbx=fffff88003502180 rcx=fffff880098d8cc0
    rdx=0000000000000000 rsi=fffffa8011e8c860 rdi=fffff8800350d0c0
    rip=fffff80002ca0284 rsp=fffff880098d8610 rbp=fffff880098d8c70
     r8=fffffa8010fb3bb8  r9=0000000000000000 r10=ffffffffffffffbf
    r11=fffff88003502180 r12=0000000000000000 r13=0000000000000000
    r14=fffffa8010fb3b30 r15=fffff88003507040
    iopl=0         nv up ei pl nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
    nt!SwapContext_PatchXRstor:
    fffff800`02ca0284 0fae29          xrstor  [rcx]
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  csrss.exe
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80002c9fe7a to fffff80002ca0284
    
    STACK_TEXT:  
    fffff880`098d8610 fffff800`02c9fe7a : fffff880`098d88f0 fffff800`02f8446b fffff8a0`00000001 fffffa80`15477060 : nt!SwapContext_PatchXRstor
    fffff880`098d8650 fffff800`02c92a32 : 00000000`00000000 fffffa80`11e8c860 000007fe`fd3be880 00000000`00000009 : nt!KiSwapContext+0x7a
    fffff880`098d8790 fffff800`02ca3d8f : 00000000`00000000 00000000`00000000 ffffcd49`00000000 fffff880`098d88f0 : nt!KiCommitThreadWait+0x1d2
    fffff880`098d8820 fffff800`02fa5169 : 00000000`746c6600 fffff880`00000010 00000000`00000001 00000000`00000400 : nt!KeWaitForSingleObject+0x19f
    fffff880`098d88c0 fffff800`02fa4bec : 00000000`00000000 00000000`00000201 00000000`00000000 00000000`00010000 : nt!AlpcpReceiveMessagePort+0x189
    fffff880`098d8920 fffff800`02fa5f86 : fffffa80`111038f0 00000000`00010000 00000000`00010000 fffffa80`111038f0 : nt!AlpcpReceiveMessage+0x2d9
    fffff880`098d89c0 fffff800`02c9c253 : fffffa80`11e8c860 fffff880`098d8b60 00000000`028efb48 00000000`002d3620 : nt!NtAlpcSendWaitReceivePort+0x1e6
    fffff880`098d8a70 00000000`76f21b6a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`028efb28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f21b6a
    
    
    FOLLOWUP_IP: 
    nt!SwapContext_PatchXRstor+0
    fffff800`02ca0284 0fae29          xrstor  [rcx]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!SwapContext_PatchXRstor+0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be
    
    STACK_COMMAND:  .cxr 0xfffff880098d7c30 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_nt!SwapContext_PatchXRstor+0
    
    BUCKET_ID:  X64_0x3B_nt!SwapContext_PatchXRstor+0
    
    Followup: MachineOwner
    ---------

    Have you updated all your drivers??

    Try this and post back the dumps

    Driver Verifier - Enable and Disable
      My Computer


  3. Posts : 6
    64
    Thread Starter
       #3

    There was a BSOD after followwing the steps, and i am on safemode now.
    Here is the new dump
    https://www.dropbox.com/s/nbfx383t9z...2-10873-01.dmp
      My Computer


  4. Posts : 851
    Windows 8 Professional x64
       #4

    Good.

    The dump blames GEAR Software Inc for the BSOD.

    1. Uninstall Gear software
    2.Uninstall DAEMON Tools Virtual Bus Driver

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C9, {23e, fffff88001998324, fffff98004c88ee0, 0}
    
    *** WARNING: Unable to verify timestamp for GEARAspiWDM.sys
    *** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys
    Unable to load image dtsoftbus01.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for dtsoftbus01.sys
    *** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
    Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1324 )
    
    Followup: MachineOwner
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    The IO manager has caught a misbehaving driver.
    Arguments:
    Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
    Arg2: fffff88001998324, The address in the driver's code where the error was detected.
    Arg3: fffff98004c88ee0, IRP address.
    Arg4: 0000000000000000, Status code.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc9_23e
    
    DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23e
    
    FAULTING_IP: 
    dtsoftbus01+1324
    fffff880`01998324 4053            push    rbx
    
    FOLLOWUP_IP: 
    dtsoftbus01+1324
    fffff880`01998324 4053            push    rbx
    
    IRP_ADDRESS:  fffff98004c88ee0
    
    DEVICE_OBJECT: fffffa8012155d50
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff800031203dc to fffff80002c99fc0
    
    STACK_TEXT:  
    fffff880`037a0508 fffff800`031203dc : 00000000`000000c9 00000000`0000023e fffff880`01998324 fffff980`04c88ee0 : nt!KeBugCheckEx
    fffff880`037a0510 fffff800`0312a47a : fffff800`0311e9f0 fffff880`01998324 fffff980`04c88ee0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
    fffff880`037a0550 fffff800`0312b34e : 00000000`0000023e 00000000`00000000 fffff980`04c88ee0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
    fffff880`037a05a0 fffff800`0313671f : fffffa80`112b2870 fffffa80`118a1930 fffffa80`118a19e8 fffff880`0199c228 : nt!VfErrorReport6+0x6e
    fffff880`037a0670 fffff800`03136b63 : fffffa80`118a1930 00000000`00000002 fffffa80`12155d50 fffff880`019983f4 : nt!IovpCallDriver2+0x13f
    fffff880`037a06d0 fffff800`0313cc2e : fffff980`04c88ee0 fffff980`04c88ee0 00000000`00000002 fffffa80`12155d50 : nt!VfAfterCallDriver+0x353
    fffff880`037a0720 fffff880`00f01d3b : fffff880`00f93d20 fffff880`037a07f0 00000000`00000025 fffffa80`118a1930 : nt!IovCallDriver+0x57e
    fffff880`037a0780 fffff880`00f03d65 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`118a68a0 : Wdf01000!FxIoTarget::SubmitSync+0x24b
    fffff880`037a0830 fffff880`04619e95 : fffffa80`00000020 fffffa80`118a68a0 fffffa80`117f8810 fffffa80`112ac280 : Wdf01000!imp_WdfRequestSend+0x2d1
    fffff880`037a08c0 fffff880`0461a2f4 : 00000000`00000000 00000000`00000024 00000000`00000001 fffff880`037a0a80 : cdrom!DeviceSendRequestSynchronously+0xc9
    fffff880`037a0920 fffff880`04618f04 : 0000057f`ee808fd8 fffff880`037a0a80 fffffa80`0d9273b0 00000000`00000024 : cdrom!DeviceSendSrbSynchronously+0x3ec
    fffff880`037a0a50 fffff880`04617825 : fffffa80`00000002 fffffa80`117f72d0 fffff880`0460f3b8 0000057f`ee808fd8 : cdrom!DeviceCacheDeviceInquiryData+0xbc
    fffff880`037a0b20 fffff880`00f34ef0 : 00000000`00000000 00000000`00000010 00000000`0000000c fffff880`00f940c0 : cdrom!DeviceEvtSelfManagedIoInit+0x105
    fffff880`037a0b60 fffff880`00f17faa : fffffa80`117f7a50 00000000`0000000c fffff880`00f940c0 00000000`00000002 : Wdf01000!FxSelfManagedIoMachine::Init+0x34
    fffff880`037a0b90 fffff880`00f235db : 00000000`00000000 00000000`00000000 fffff880`037a0d30 fffff880`00f940c0 : Wdf01000!FxSelfManagedIoMachine::ProcessEvent+0x14a
    fffff880`037a0c00 fffff880`00f0ec3c : 00000000`00000312 fffff880`037a0d30 00000000`ffff7fff fffffa80`117f7ae0 : Wdf01000!FxPkgPnp::PowerD0StartingStartSelfManagedIo+0x2f
    fffff880`037a0c30 fffff880`00f0f106 : fffff880`00f93e80 fffffa80`117f7c98 fffffa80`117f7ae0 fffffa80`117f7ae0 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1d8
    fffff880`037a0d90 fffff880`00f0ee9f : 00000000`00000000 fffff880`037a0e70 fffffa80`117f7c80 fffffa80`117f7ae0 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
    fffff880`037a0e00 fffff880`00f24afe : 00000000`00000000 00000000`00000501 00000000`00000501 fffff800`031280ce : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1b3
    fffff880`037a0ea0 fffff880`00f18e99 : 00000000`00000501 fffff880`037a0f40 00000000`00000500 fffffa80`117f7ae0 : Wdf01000!FxPkgPnp::NotPowerPolOwnerStarting+0xe
    fffff880`037a0ed0 fffff880`00f0fa9b : fffffa80`117f7d48 fffffa80`117f7d50 fffffa80`117f7ae0 fffffa80`117f7d48 : Wdf01000!FxPkgPnp::NotPowerPolicyOwnerEnterNewState+0x1c9
    fffff880`037a0f70 fffff880`00f0f595 : 00000000`00000000 fffff880`037a1050 fffffa80`117f7d38 fffffa80`117f7ae0 : Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x3df
    fffff880`037a0fe0 fffff880`00f239c1 : 00000000`00000000 fffffa80`117fa2a0 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x1c1
    fffff880`037a1080 fffff880`00f2381d : 00000000`00000101 00000000`00000108 00000000`00000108 fffffa80`117f7ae0 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x111
    fffff880`037a10c0 fffff880`00f24032 : 00000000`00000002 fffffa80`117f7c08 fffffa80`117f7ae0 fffffa80`117f7ae0 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a1
    fffff880`037a1160 fffff880`00f23cdd : 00000000`00000000 fffff880`037a1240 fffffa80`117f7bf0 fffffa80`117f7ae0 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
    fffff880`037a11d0 fffff880`00f23b3e : 00000000`00000000 fffffa80`117f7ae0 fffffa80`116c6940 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x18d
    fffff880`037a1270 fffff880`00f0cecf : fffffa80`109f5410 fffff880`037a12f0 00000000`00000000 fffffa80`120981c8 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x1e
    fffff880`037a12a0 fffff880`00f049da : fffff980`04c5cd80 00000000`00000051 fffff980`04c5cd80 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x18f
    fffff880`037a1300 fffff880`00f04aa6 : fffff980`04c5cd80 00000000`00000002 fffffa80`117f8e10 fffffa80`117f8e10 : Wdf01000!FxDevice::Dispatch+0x19a
    fffff880`037a1340 fffff800`0313cc16 : fffff980`04c5cd80 00000000`00000002 fffffa80`117f8e10 fffff800`0313837e : Wdf01000!FxDevice::DispatchWithLock+0xa6
    fffff880`037a1380 fffff800`0313f52a : fffff980`04c5cee0 fffffa80`117f8e10 fffffa80`117fa040 fffffa80`112b22e0 : nt!IovCallDriver+0x566
    fffff880`037a13e0 fffff800`0313cc16 : fffff980`04c5cd80 00000000`00000002 fffffa80`117fa040 fffffa80`1217af40 : nt!ViFilterDispatchPnp+0x13a
    fffff880`037a1410 fffff880`07ca5082 : fffffa80`117fa040 00000000`00000000 fffffa80`117fa630 fffffa80`1217af40 : nt!IovCallDriver+0x566
    fffff880`037a1470 fffffa80`117fa040 : 00000000`00000000 fffffa80`117fa630 fffffa80`1217af40 fffff980`04c5cfb8 : GEARAspiWDM+0x4082
    fffff880`037a1478 00000000`00000000 : fffffa80`117fa630 fffffa80`1217af40 fffff980`04c5cfb8 fffffa80`120982b8 : 0xfffffa80`117fa040
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    SYMBOL_NAME:  dtsoftbus01+1324
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dtsoftbus01
    
    IMAGE_NAME:  dtsoftbus01.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4f10358a
    
    FAILURE_BUCKET_ID:  X64_0xc9_23e_dtsoftbus01+1324
    
    BUCKET_ID:  X64_0xc9_23e_dtsoftbus01+1324
    
    Followup: MachineOwner
    ---------
    After uninstalling check if the BSOD persists.

    If yes post back the dumps
      My Computer


  5. Posts : 6
    64
    Thread Starter
       #5

    I can't seem to find the GEAR Software in my uninstall list
      My Computer


  6. Posts : 851
    Windows 8 Professional x64
       #6

    Please check the install/uninstall program list again.

    Did you uninstall daemon tools?
      My Computer


  7. Posts : 6
    64
    Thread Starter
       #7

    Checked the list already, i uninstalled daemon tools already but i still dont see the gear software
      My Computer


  8. Posts : 851
    Windows 8 Professional x64
       #8

    Ok.
    Do you still get BSOD?
      My Computer


  9. Posts : 6
    64
    Thread Starter
       #9

    Just enabled the verifier thing and so far restart and running for about 5 mins no BSOD, should i let it run to test for any BSOD?
      My Computer


  10. Posts : 851
    Windows 8 Professional x64
       #10

    Yes,

    In the tutorial it is instructed to run for 24 hrs.
      My Computer


 

  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 06:03.
Find Us