Windows 8 and 8.1 Forums


Frequent BSODs = no obvious trigger

  1. #1


    Posts : 12
    Windows 10 Pro 10586

    Frequent BSODs = no obvious trigger


    My Dell XPS8700 running Windows 8.1 is giving me frequent (2 or 3 times a week) BSODs. There's no obvious trigger that I can ascertain, and running WhoCrashed just says "Possibly this problem is caused by another driver on your system that cannot be identified at this time."

    I believe that I am running the latest BIOS, drivers and patches for Windows and all my aplications (but could be proven wrong).

    ZIP file is attached below, and any suggestions appreciated!

    Attachment 62535

      My System SpecsSystem Spec

  2. #2


    Posts : 12
    Windows 10 Pro 10586


    Another BSOD tonight, so would really appreciate any assistance that may be available.

    Log files attached.
      My System SpecsSystem Spec

  3. #3



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro


    If nobody else response, I'll take a look when I'm home within a few hours.
      My System SpecsSystem Spec

  4. #4



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro


    There are a couple of issues.

    1. Your Intel(R) USB 3.0 eXtensible Host Controller driver has been flagged, please update this driver.

    2. Your NVIDIA GeForce GTX 650 Ti graphics card has been flagged, please update this driver

    3. There are a few things flagged to your windows update, I recommend to open an admin command prompt (windows + x, press a, press enter 2x) and copy & paste(right click > paste) this:
    Dism.exe /online /Cleanup-Image /StartComponentCleanup&sfc/scannow&Dism /Online /Cleanup-Image /RestoreHealth&sfc/scannow&pause
    It may take a while to finish these commands & it'll look like its stuck, just let it run.
    Reboot when finished, try sfc/scannow and reboot again.

    There is one other thing also flagged, ntoskrnl.exe ntkrnlmp.exe, but I do not really understand these dumps.


    Code:
    ********************************************************************************                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
    An attempt was made to execute non-executable memory.  The guilty driver
    is on the stack trace (and is typically the current instruction pointer).
    When possible, the guilty driver's name (Unicode string) is printed on
    the bugcheck screen and saved in KiBugCheckDriver.
    Arguments:
    Arg1: ffffe000bccf55c0, Virtual address for the attempted execute.
    Arg2: 8000000103a009e3, PTE contents.
    Arg3: fffff800a90cd240, (reserved)
    Arg4: 0000000000000003, (reserved)
    
    
    Debugging Details:
    ------------------
    
    
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    BUGCHECK_STR:  0xFC
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  2
    
    
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
    
    
    DPC_STACK_BASE:  FFFFF800A90D4FB0
    
    
    TRAP_FRAME:  fffff800a90cd240 -- (.trap 0xfffff800a90cd240)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffff80163b001a0
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=ffffe000bccf55c0 rsp=fffff800a90cd3d0 rbp=fffff800a90cd4e0
     r8=0000000000000000  r9=ffffe000bccf70e0 r10=0000000000000000
    r11=fffff800a90cd3b0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    ffffe000`bccf55c0 0300            add     eax,dword ptr [rax] ds:00000000`00000000=????????
    Resetting default scope
    
    
    LAST_CONTROL_TRANSFER:  from fffff800a762a5fa to fffff800a75cc9a0
    
    
    STACK_TEXT:  
    fffff800`a90ccff8 fffff800`a762a5fa : 00000000`000000fc ffffe000`bccf55c0 80000001`03a009e3 fffff800`a90cd240 : nt!KeBugCheckEx
    fffff800`a90cd000 fffff800`a767b4ad : ffffe000`bccbc090 ffffe000`bcd5bc01 ffffe000`bcc758a0 fffff800`a777f180 : nt! ?? ::FNODOBFM::`string'+0x4d74a
    fffff800`a90cd040 fffff800`a75f744d : ffffe000`e4edaaf0 fffff800`a90cd100 00000000`00000000 00000000`00000000 : nt!MiRaisedIrqlFault+0xf5
    fffff800`a90cd080 fffff800`a75d6c2f : 00000000`00000008 ffffe000`e4edaaf0 ffffe000`bfc31a00 fffff800`a755ccd7 : nt! ?? ::FNODOBFM::`string'+0x1a59d
    fffff800`a90cd240 ffffe000`bccf55c0 : ffffe000`e4edaf6b fffff800`a751d36a ffffe000`e4edaaf0 fffff800`a90cd4e0 : nt!KiPageFault+0x12f
    fffff800`a90cd3d0 ffffe000`e4edaf6b : fffff800`a751d36a ffffe000`e4edaaf0 fffff800`a90cd4e0 00000000`00000000 : 0xffffe000`bccf55c0
    fffff800`a90cd3d8 fffff800`a751d36a : ffffe000`e4edaaf0 fffff800`a90cd4e0 00000000`00000000 ffffe000`e4edaf23 : 0xffffe000`e4edaf6b
    fffff800`a90cd3e0 fffff801`602fc8fc : 00000000`ffffff00 00000000`00000000 00000000`00000004 ffffe000`bd19e6a0 : nt!IopfCompleteRequest+0x2ea
    fffff800`a90cd520 fffff801`60309364 : ffffe000`bcd5ea40 00000000`00000000 fffff800`00000001 ffffe000`bcd5e802 : Wdf01000!FxRequest::CompleteInternal+0x23c
    fffff800`a90cd5e0 fffff801`62d45efe : ffffe000`bcd5ea40 fffff800`a90c0000 ffffe000`bcd5e8a0 ffffe000`bcd5e8a0 : Wdf01000!imp_WdfRequestComplete+0x8c
    fffff800`a90cd650 fffff801`62d46e74 : ffffe000`bcd5ea40 00000000`00000001 ffffe000`bcd5eac0 fffff800`a90cd7d0 : USBXHCI!Bulk_Transfer_CompleteCancelable+0x15a
    fffff800`a90cd6b0 fffff801`62d34013 : 00000000`00000780 ffffe000`bd1c8210 00000000`00000000 fffff801`623c8d70 : USBXHCI!Bulk_ProcessTransferEventWithED1+0x3a8
    fffff800`a90cd760 fffff801`60394c81 : 00000000`00000000 00000000`00000000 00001fff`42e37fd8 00000000`00000046 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0x427
    fffff800`a90cd860 fffff800`a7530d50 : fffff800`a7781f00 fffff800`a90cdb20 ffffe000`bd1c8020 fffff800`a77845c0 : Wdf01000!FxInterrupt::DpcHandler+0xc1
    fffff800`a90cd890 fffff800`a7530007 : ffffe000`bd392080 fffff800`a90cdae0 fffff800`a777f180 fffff800`a777f180 : nt!KiExecuteAllDpcs+0x1b0
    fffff800`a90cd9e0 fffff800`a75d04ea : fffff800`a777f180 fffff800`a777f180 fffff800`a77d8a00 ffffe000`bcc42880 : nt!KiRetireDpcList+0xd7
    fffff800`a90cdc60 00000000`00000000 : fffff800`a90ce000 fffff800`a90c8000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    USBXHCI!Bulk_Transfer_CompleteCancelable+15a
    fffff801`62d45efe 488d4d58        lea     rcx,[rbp+58h]
    
    
    SYMBOL_STACK_INDEX:  a
    
    
    SYMBOL_NAME:  USBXHCI!Bulk_Transfer_CompleteCancelable+15a
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: USBXHCI
    
    
    IMAGE_NAME:  USBXHCI.SYS
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  54337388
    
    
    IMAGE_VERSION:  6.3.9600.17393
    
    
    BUCKET_ID_FUNC_OFFSET:  15a
    
    
    FAILURE_BUCKET_ID:  0xFC_USBXHCI!Bulk_Transfer_CompleteCancelable
    
    
    BUCKET_ID:  0xFC_USBXHCI!Bulk_Transfer_CompleteCancelable
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:0xfc_usbxhci!bulk_transfer_completecancelable
    
    
    FAILURE_ID_HASH:  {a9e2c251-6842-47a2-071c-5f5701f7c4ba}
    Code:
    ********************************************************************************                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: ffffd000daa3e095, memory referenced
    Arg2: 0000000000000006, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffff800aa813e32, address which referenced memory
    
    
    Debugging Details:
    ------------------
    
    
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8027f17f138
    unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSizeOfNonPagedPoolInBytes
     ffffd000daa3e095 
    
    
    CURRENT_IRQL:  6
    
    
    FAULTING_IP: 
    nvlddmkm+187e32
    fffff800`aa813e32 488bfb          mov     rdi,rbx
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    BUGCHECK_STR:  AV
    
    
    PROCESS_NAME:  System
    
    
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
    
    
    TRAP_FRAME:  ffffd000daa4dac0 -- (.trap 0xffffd000daa4dac0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=ffffd000daa4dc84 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800aa813e32 rsp=ffffd000daa4dc50 rbp=ffffd000daa4dd09
     r8=0000000000000020  r9=ffffd000daa4dc50 r10=fffff800aa9de808
    r11=ffffd000daa4db60 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nvlddmkm+0x187e32:
    fffff800`aa813e32 488bfb          mov     rdi,rbx
    Resetting default scope
    
    
    LAST_CONTROL_TRANSFER:  from fffff8027ef787e9 to fffff8027ef6cca0
    
    
    STACK_TEXT:  
    ffffd000`daa4d978 fffff802`7ef787e9 : 00000000`0000000a ffffd000`daa3e095 00000000`00000006 00000000`00000001 : nt!KeBugCheckEx
    ffffd000`daa4d980 fffff802`7ef7703a : 00000000`00000001 ffffe001`0a0a5000 00000000`00000000 fffff800`aa845854 : nt!KiBugCheckDispatch+0x69
    ffffd000`daa4dac0 fffff800`aa813e32 : ffffe001`00000017 ffffe001`0a0a5000 ffffe001`0a0ae000 ffffe001`0a1373d0 : nt!KiPageFault+0x23a
    ffffd000`daa4dc50 ffffe001`00000017 : ffffe001`0a0a5000 ffffe001`0a0ae000 ffffe001`0a1373d0 00000000`00000000 : nvlddmkm+0x187e32
    ffffd000`daa4dc58 ffffe001`0a0a5000 : ffffe001`0a0ae000 ffffe001`0a1373d0 00000000`00000000 00000000`00000000 : 0xffffe001`00000017
    ffffd000`daa4dc60 ffffe001`0a0ae000 : ffffe001`0a1373d0 00000000`00000000 00000000`00000000 00000020`da010000 : 0xffffe001`0a0a5000
    ffffd000`daa4dc68 ffffe001`0a1373d0 : 00000000`00000000 00000000`00000000 00000020`da010000 00000000`00000004 : 0xffffe001`0a0ae000
    ffffd000`daa4dc70 00000000`00000000 : 00000000`00000000 00000020`da010000 00000000`00000004 ffffe001`0a0a5108 : 0xffffe001`0a1373d0
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    nvlddmkm+187e32
    fffff800`aa813e32 488bfb          mov     rdi,rbx
    
    
    SYMBOL_STACK_INDEX:  3
    
    
    SYMBOL_NAME:  nvlddmkm+187e32
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: nvlddmkm
    
    
    IMAGE_NAME:  nvlddmkm.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  54d3b001
    
    
    FAILURE_BUCKET_ID:  AV_nvlddmkm+187e32
    
    
    BUCKET_ID:  AV_nvlddmkm+187e32
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:av_nvlddmkm+187e32
    
    
    FAILURE_ID_HASH:  {1db79247-cf4b-450a-6fee-4e28a6655491}
    Last edited by axe0; 03 Jul 2015 at 16:02.
      My System SpecsSystem Spec

  5. #5


    Posts : 12
    Windows 10 Pro 10586


    Thank you very much for your help!
    Quote Originally Posted by axe0 View Post
    1. Your Intel(R) USB 3.0 eXtensible Host Controller driver has been flagged, please update this driver.
    I have read this page, but it doesn't seem to mention any way in which I can update the driver.
    Quote Originally Posted by axe0 View Post
    2. Your NVIDIA GeForce GTX 650 Ti graphics card has been flagged, please update this driver
    Now done, thanks. Nvidia do seem to release updates to this driver very frequently.
    Quote Originally Posted by axe0 View Post
    3. There are a few things flagged to your windows update, I recommend to open an admin command prompt (windows + x, press a, press enter 2x) and copy & paste(right click > paste) this:
    Dism.exe /online /Cleanup-Image /StartComponentCleanup&sfc/scannow&Dism /Online /Cleanup-Image /RestoreHealth&sfc/scannow&pause
    It may take a while to finish these commands & it'll look like its stuck, just let it run.
    Reboot when finished, try sfc/scannow and reboot again.
    Not sure what pressing Enter x 2 was meant to do (after <Windows>X and then A, I got a PowerShell window, and the Enter x 2 didn't really do anything).

    The lines in bold gave an error when pasted - "The ampersand (&) character is not allowed", so I ran the commands as 4 separate commands:
    Dism.exe /online /Cleanup-Image /StartComponentCleanup
    sfc/ scannow
    Dism /Online /Cleanup-Image /RestoreHealth
    sfc/ scannow

    I then rebooted and ran sfc/scannow again. In each case sfc gave the following error on completion:
    "Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios."

    I have looked in the CBS.log file but it doesn't mean a lot o me - it's attached below in case you can get any useful information from it.
      My System SpecsSystem Spec

  6. #6



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro


    Forgot to mention that your usb 3.0 port only get updates via Windows Update.
    The link I gave you is just for information about it.

    After I press windows logo + x and then a, I have to press twice enter, one for choosing admin prompt and the other to confirm.
    I'd say try sfc/scannow again, it could take a couple of tries and reboots before the errors are solved.

    I saw you have update KB3022345, that update gives a false positive, unfortunately its not yet clear if there are other problems then the false positive from KB3022345.
    Last edited by axe0; 04 Jul 2015 at 13:54. Reason: Extra information
      My System SpecsSystem Spec

  7. #7



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro


    You may ignore the sfc/scannow errors.
    Those errors are the false positives from KB3022345.
      My System SpecsSystem Spec

  8. #8


    Posts : 12
    Windows 10 Pro 10586


    Thank you very much again.

    I'll monitor things for a week or so before I mark this as "solved", and If I get any further BSODs, I'll post the logs.
      My System SpecsSystem Spec

  9. #9


    Posts : 12
    Windows 10 Pro 10586


    Sorry to report that I have had 2 more BSODs this evening.

    WhoCrashed again says:

    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


    which is less than useful :-(

    I'm hoping that perhaps Windows 10 will cure it when it comes out on 29th (though I doubt it), so any additional jelp appreciated.

    Log files attached.Attachment 63528
      My System SpecsSystem Spec

  10. #10



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro


    Please update or remove the following drivers
    Code:
    Western Digital SCSI Arcitecture Model (SAM) WDM driver
    wdcsam64.sys Wed Apr 16 10:39:08 2008 (4805BB2C) 
    WD Support / Downloads
    
    Blackberry Device Driver
    RimUsb_AMD64.sys Mon May 14 18:06:16 2007 (464888F8)
    Smartphones - New BlackBerry Phones - Latest Smartphones from BlackBerry - Canada
    
    EnTech softEngine x64 kernel-mode driver
    se64a.sys Thu May 3 07:50:31 2007 (46397827) 
    EnTech Taiwan | Utilities
    Please remove avast temporarily Avast uninstall utility
    Please run memtest86+, 8 passes per stick.

    Usual causes for these BSOD's (could be there are some double):
    Code:
      Device driver,
    hardware, 
    System service, 
    compatibility,
     Remote control programs, 
    memory,
    Kernel mode driver,
    Windows, 
    Virus scanner, 
    Backup tool, 
    Defective hardware (particularly memory - but not just RAM), 
    Faulty system service,
    Antivirus, 
    NTFS corruption,
    BIOS






    The following is for information purposes only.

    Code:
     The following information contains the relevant information from the blue screen analysis: 
    **************************Mon Jul 6 00:07:46.405 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 5:12:55.000 
    
    *** WARNING: Unable to verify timestamp for win32k.sys 
    
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys 
    
    Probably caused by :NETIO.SYS ( NETIO!RtlGetNextExpirationTimerWheelTick+0 ) 
    
    BugCheck 1E, {ffffffffc0000005, fffff8014151a310, 0, ffffffffffffffff} 
    BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e) 
    
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled 
    Arg2: fffff8014151a310, The address that the exception occurred at 
    Arg3: 0000000000000000, Parameter 0 of the exception 
    Arg4: ffffffffffffffff, Parameter 1 of the exception 
    BUGCHECK_STR: 0x1E_c0000005_R 
    
    PROCESS_NAME: System 
    
    FAILURE_BUCKET_ID: 0x1E_c0000005_R_NETIO!RtlGetNextExpirationTimerWheelTick 
    
    CPUID: "Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz" 
    
    MaxSpeed: 3400 
    
    CurrentSpeed: 3392 
    
    BIOS Version A10 
    
    BIOS Release Date 12/08/2014 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Sun Jul 5 18:50:24.453 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 6:14:05.277 
    
    Probably caused by :ntkrnlmp.exe ( nt!PerfInfoLogInterrupt+28 ) 
    
    BugCheck A, {36ad1bb5, 6, 0, fffff80034f1ac00} 
    BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a) 
    
    Arguments: 
    Arg1: 0000000036ad1bb5, memory referenced 
    Arg2: 0000000000000006, IRQL 
    Arg3: 0000000000000000, bitfield : 
    bit 0 : value 0 = read operation, 1 = write operation 
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) 
    Arg4: fffff80034f1ac00, address which referenced memory 
    BUGCHECK_STR: AV 
    
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT 
    
    PROCESS_NAME: System 
    
    FAILURE_BUCKET_ID: AV_nt!PerfInfoLogInterrupt 
    
    CPUID: "Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz" 
    
    MaxSpeed: 3400 
    
    CurrentSpeed: 3392 
    
    BIOS Version A10 
    
    BIOS Release Date 12/08/2014 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Mon Jun 29 20:34:41.696 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 0:18:09.572 
    
    Probably caused by :ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 ) 
    
    BugCheck 139, {3, ffffd00155874050, ffffd00155873fa8, 0} 
    BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139) 
    
    Arguments: 
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove). 
    Arg2: ffffd00155874050, Address of the trap frame for the exception that caused the bugcheck 
    Arg3: ffffd00155873fa8, Address of the exception record for the exception that caused the bugcheck 
    Arg4: 0000000000000000, Reserved 
    BUGCHECK_STR: 0x139 
    
    DEFAULT_BUCKET_ID: LIST_ENTRY_CORRUPT 
    
    PROCESS_NAME: nvSCPAPISvr.ex 
    
    FAILURE_BUCKET_ID: 0x139_3_nt!KiFastFailDispatch 
    
    CPUID: "Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz" 
    
    MaxSpeed: 3400 
    
    CurrentSpeed: 3392 
    
    BIOS Version A10 
    
    BIOS Release Date 12/08/2014 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Sun Jun 28 22:01:51.966 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 8:22:18.908 
    
    Probably caused by :win32k.sys ( win32k!EnterCritAvoidingDitHitTestHazard+13 ) 
    
    BugCheck 139, {3, ffffd00022cf1630, ffffd00022cf1588, 0} 
    BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139) 
    
    Arguments: 
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove). 
    Arg2: ffffd00022cf1630, Address of the trap frame for the exception that caused the bugcheck 
    Arg3: ffffd00022cf1588, Address of the exception record for the exception that caused the bugcheck 
    Arg4: 0000000000000000, Reserved 
    BUGCHECK_STR: 0x139 
    
    DEFAULT_BUCKET_ID: LIST_ENTRY_CORRUPT 
    
    PROCESS_NAME: explorer.exe 
    
    FAILURE_BUCKET_ID: 0x139_3_win32k!EnterCritAvoidingDitHitTestHazard 
    
    CPUID: "Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz" 
    
    MaxSpeed: 3400 
    
    CurrentSpeed: 3392 
    
    BIOS Version A10 
    
    BIOS Release Date 12/08/2014 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Wed Jun 10 12:34:56.193 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 2:09:32.938 
    
    Probably caused by :ntkrnlmp.exe ( nt!KeAccumulateTicks+1e6 ) 
    
    BugCheck A, {fffff80376f08f1c, d, 0, fffff80356c42d76} 
    BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a) 
    
    Arguments: 
    Arg1: fffff80376f08f1c, memory referenced 
    Arg2: 000000000000000d, IRQL 
    Arg3: 0000000000000000, bitfield : 
    bit 0 : value 0 = read operation, 1 = write operation 
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) 
    Arg4: fffff80356c42d76, address which referenced memory 
    BUGCHECK_STR: AV 
    
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT 
    
    PROCESS_NAME: iTunes.exe 
    
    FAILURE_BUCKET_ID: AV_nt!KeAccumulateTicks 
    
    CPUID: "Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz" 
    
    MaxSpeed: 3400 
    
    CurrentSpeed: 3392 
    
    BIOS Version A10 
    
    BIOS Release Date 12/08/2014 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Tue Jun 9 15:40:40.237 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 5:32:05.312 
    
    Probably caused by :USBXHCI.SYS ( USBXHCI!WPP_RECORDER_SF_ddddxdLL+c7 ) 
    
    BugCheck D1, {fffff8006cecd748, 2, 1, fffff801f69b529f} 
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) 
    
    Arguments: 
    Arg1: fffff8006cecd748, memory referenced 
    Arg2: 0000000000000002, IRQL 
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation 
    Arg4: fffff801f69b529f, address which referenced memory 
    BUGCHECK_STR: AV 
    
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT 
    
    PROCESS_NAME: System 
    
    FAILURE_BUCKET_ID: AV_USBXHCI!WPP_RECORDER_SF_ddddxdLL 
    
    CPUID: "Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz" 
    
    MaxSpeed: 3400 
    
    CurrentSpeed: 3392 
    
    BIOS Version A10 
    
    BIOS Release Date 12/08/2014 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Sun Jun 7 12:52:58.382 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 0:45:00.376 
    
    Probably caused by :ntkrnlmp.exe ( nt!PpmCheckRecordAllUtility+1ef ) 
    
    BugCheck A, {400000000004, 2, 0, fffff8023674195f} 
    BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a) 
    
    Arguments: 
    Arg1: 0000400000000004, memory referenced 
    Arg2: 0000000000000002, IRQL 
    Arg3: 0000000000000000, bitfield : 
    bit 0 : value 0 = read operation, 1 = write operation 
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) 
    Arg4: fffff8023674195f, address which referenced memory 
    BUGCHECK_STR: AV 
    
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT 
    
    PROCESS_NAME: System 
    
    FAILURE_BUCKET_ID: AV_nt!PpmCheckRecordAllUtility 
    
    CPUID: "Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz" 
    
    MaxSpeed: 3400 
    
    CurrentSpeed: 3392 
    
    BIOS Version A10 
    
    BIOS Release Date 12/08/2014 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Sat May 30 11:26:22.781 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 0:51:06.492 
    
    Probably caused by :fileinfo.sys ( fileinfo!FIPreCloseCallback+3a ) 
    
    BugCheck 50, {fffff802b1490a04, 8, fffff802b1490a04, 2} 
    BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50) 
    
    Arguments: 
    Arg1: fffff802b1490a04, memory referenced. 
    Arg2: 0000000000000008, value 0 = read operation, 1 = write operation. 
    Arg3: fffff802b1490a04, If non-zero, the instruction address which referenced the bad memory 
    address. 
    Arg4: 0000000000000002, (reserved) 
    BUGCHECK_STR: AV 
    
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT 
    
    PROCESS_NAME: System 
    
    FAILURE_BUCKET_ID: AV_BAD_IP_fileinfo!FIPreCloseCallback 
    
    CPUID: "Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz" 
    
    MaxSpeed: 3400 
    
    CurrentSpeed: 3392 
    
    BIOS Version A10 
    
    BIOS Release Date 12/08/2014 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Sat May 30 00:29:21.276 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 4:50:04.778 
    
    Probably caused by :hardware ( nt!KeClockInterruptNotify+41f ) 
    
    BugCheck A, {8, d, 1, fffff8015e049bff} 
    BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a) 
    
    Arguments: 
    Arg1: 0000000000000008, memory referenced 
    Arg2: 000000000000000d, IRQL 
    Arg3: 0000000000000001, bitfield : 
    bit 0 : value 0 = read operation, 1 = write operation 
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) 
    Arg4: fffff8015e049bff, address which referenced memory 
    BUGCHECK_STR: AV 
    
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT 
    
    PROCESS_NAME: System 
    
    FAILURE_BUCKET_ID: IP_MISALIGNED 
    
    CPUID: "Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz" 
    
    MaxSpeed: 3400 
    
    CurrentSpeed: 3392 
    
    BIOS Version A10 
    
    BIOS Release Date 12/08/2014 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Fri May 29 15:21:32.234 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 4:58:45.170 
    
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys 
    
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys 
    
    Probably caused by :hardware ( nvlddmkm+19ac37 ) 
    
    BugCheck D1, {ffffffffffffff8b, e, 1, fffff800645eec37} 
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) 
    
    Arguments: 
    Arg1: ffffffffffffff8b, memory referenced 
    Arg2: 000000000000000e, IRQL 
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation 
    Arg4: fffff800645eec37, address which referenced memory 
    BUGCHECK_STR: AV 
    
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT 
    
    PROCESS_NAME: System 
    
    FAILURE_BUCKET_ID: IP_MISALIGNED_nvlddmkm.sys 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Sun May 24 01:59:25.658 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 1:20:29.736 
    
    Probably caused by :ntkrnlmp.exe ( nt!KiRetireDpcList+292 ) 
    
    BugCheck A, {100000209, 2, 0, fffff8022c6c2072} 
    BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a) 
    
    Arguments: 
    Arg1: 0000000100000209, memory referenced 
    Arg2: 0000000000000002, IRQL 
    Arg3: 0000000000000000, bitfield : 
    bit 0 : value 0 = read operation, 1 = write operation 
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) 
    Arg4: fffff8022c6c2072, address which referenced memory 
    BUGCHECK_STR: AV 
    
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT 
    
    PROCESS_NAME: System 
    
    FAILURE_BUCKET_ID: AV_nt!KiRetireDpcList 
    
    CPUID: "Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz" 
    
    MaxSpeed: 3400 
    
    CurrentSpeed: 3392 
    
    BIOS Version A10 
    
    BIOS Release Date 12/08/2014 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Sat May 23 23:15:14.437 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 5:04:49.717 
    
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys 
    
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys 
    
    Probably caused by :nvlddmkm.sys ( nvlddmkm+187e32 ) 
    
    BugCheck D1, {ffffd000daa3e095, 6, 1, fffff800aa813e32} 
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) 
    
    Arguments: 
    Arg1: ffffd000daa3e095, memory referenced 
    Arg2: 0000000000000006, IRQL 
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation 
    Arg4: fffff800aa813e32, address which referenced memory 
    BUGCHECK_STR: AV 
    
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT 
    
    PROCESS_NAME: System 
    
    FAILURE_BUCKET_ID: AV_nvlddmkm+187e32 
    
    CPUID: "Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz" 
    
    MaxSpeed: 3400 
    
    CurrentSpeed: 3392 
    
    BIOS Version A10 
    
    BIOS Release Date 12/08/2014 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Mon Apr 13 19:44:22.894 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 0:01:15.591 
    
    Probably caused by :ntkrnlmp.exe ( nt!KeAccumulateTicks+194 ) 
    
    BugCheck 3D, {ffffd000dfc46260, 0, 0, fffff8004d466774} 
    BugCheck Info: INTERRUPT_EXCEPTION_NOT_HANDLED (3d) 
    
    Arguments: 
    Arg1: ffffd000dfc46260 
    Arg2: 0000000000000000 
    Arg3: 0000000000000000 
    Arg4: fffff8004d466774 
    BUGCHECK_STR: 0x3D 
    
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT 
    
    PROCESS_NAME: SearchIndexer. 
    
    FAILURE_BUCKET_ID: 0x3D_nt!KeAccumulateTicks 
    
    CPUID: "Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz" 
    
    MaxSpeed: 3400 
    
    CurrentSpeed: 3392 
    
    BIOS Version A10 
    
    BIOS Release Date 12/08/2014 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Mon Apr 13 19:40:41.202 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 9:53:48.984 
    
    Probably caused by :ntkrnlmp.exe ( nt!KiRetireDpcList+5ea ) 
    
    BugCheck A, {ffffe02097e9e198, 2, 0, fffff802eb13951a} 
    BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a) 
    
    Arguments: 
    Arg1: ffffe02097e9e198, memory referenced 
    Arg2: 0000000000000002, IRQL 
    Arg3: 0000000000000000, bitfield : 
    bit 0 : value 0 = read operation, 1 = write operation 
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) 
    Arg4: fffff802eb13951a, address which referenced memory 
    BUGCHECK_STR: AV 
    
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT 
    
    PROCESS_NAME: System 
    
    FAILURE_BUCKET_ID: AV_nt!KiRetireDpcList 
    
    CPUID: "Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz" 
    
    MaxSpeed: 3400 
    
    CurrentSpeed: 3392 
    
    BIOS Version A10 
    
    BIOS Release Date 12/08/2014 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Sun Apr 12 18:05:30.287 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 2:49:05.019 
    
    Probably caused by :ntkrnlmp.exe ( nt!KiPageFault+23a ) 
    
    BugCheck D1, {fffff8006adc0790, 2, 8, fffff8006adc0790} 
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) 
    
    Arguments: 
    Arg1: fffff8006adc0790, memory referenced 
    Arg2: 0000000000000002, IRQL 
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation 
    Arg4: fffff8006adc0790, address which referenced memory 
    BUGCHECK_STR: AV 
    
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT 
    
    PROCESS_NAME: System 
    
    FAILURE_BUCKET_ID: AV_CODE_AV_BAD_IP_nt!KiPageFault 
    
    CPUID: "Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz" 
    
    MaxSpeed: 3400 
    
    CurrentSpeed: 3392 
    
    BIOS Version A10 
    
    BIOS Release Date 12/08/2014 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Fri Apr 10 00:41:22.956 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 3:21:54.146 
    
    Probably caused by :USBXHCI.SYS ( USBXHCI!Bulk_Transfer_CompleteCancelable+15a ) 
    
    BugCheck FC, {ffffe000bccf55c0, 8000000103a009e3, fffff800a90cd240, 3} 
    BugCheck Info: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc) 
    
    Arguments: 
    Arg1: ffffe000bccf55c0, Virtual address for the attempted execute. 
    Arg2: 8000000103a009e3, PTE contents. 
    Arg3: fffff800a90cd240, (reserved) 
    Arg4: 0000000000000003, (reserved) 
    BUGCHECK_STR: 0xFC 
    
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT 
    
    PROCESS_NAME: System 
    
    FAILURE_BUCKET_ID: 0xFC_USBXHCI!Bulk_Transfer_CompleteCancelable 
    
    CPUID: "Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz" 
    
    MaxSpeed: 3400 
    
    CurrentSpeed: 3392 
    
    BIOS Version A10 
    
    BIOS Release Date 12/08/2014
      My System SpecsSystem Spec

Frequent BSODs = no obvious trigger
Related Threads
[Random/Frequent BSODs] DPC_WATCHDOG_VIOLATION in BSOD Crashes and Debugging
I am at a standstill ever since I recieved this BSOD. At first I thought it was just a random crash and that I would've resolved it later, however it became frequent in just a matter of minutes. Playing a game, browsing the internet, listening to music, anything I do will result in another BSOD...
Frequent BSODs in BSOD Crashes and Debugging
Hi I'm getting pretty frequent BSODs when I'm using my computer. Attached is the file I got after going through all the steps and using the diagnostic tool. As a note every time it crashes and goes to the blue error screen where it says it's collecting information it goes to 100% but never restarts...
Frequent BSOD, no specific trigger in BSOD Crashes and Debugging
So I am having something like 6 BSOD┤s a day atm, I get stated two reasons. Either kernel data inpage error or Critical Process Died. The BSOD is usually preceded by the disappearance of the taskbar. So far as I am aware the windows 8.1 installation is up to date. I hope this information is...
Frequent BSODs in BSOD Crashes and Debugging
In the last months I have been experiencing many BSODs, with no particular pattern. Sometimes, the BSOD happens when I have left the computer alone for some minutes. Others, the system crashes when I am using it, primarily for work. Here I attach my diagnostic file. Thank you for your support.
Frequent BSODs in BSOD Crashes and Debugging
I've been getting pretty frequent BSODs, doesn't seem to be related to any particular activity or period of time... Sometimes they'll happen every 1-2 days, othertimes it'll be 3 times in an hour :( I'm attached data from the SF tool, if anybody could take a look and let me know what you think...
Frequent yet, seemingly random BSODs in BSOD Crashes and Debugging
Hi, At the recommendation of one of the moderators on the Seven Forums, I am re-posting my problem here following a an upgrade to Windows 8 Pro. (original posts here: BSOD Memory Management Error - On Boot and in-game (GW2) - Windows 7 Support Forums) Basically, I am getting frequent BSODs in...
I built my first gaming rig in january 2013, and everything went well. However about 2 days later i recieved my first BS0Ds, which was very dissapointing. I neglected to fix the issues and now all these BSODS are driving me crazy. I don't know how to analyze dmp files so any help would be...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook