Results 1 to 2 of 2

Thread: - /

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Registered User seeYa's Avatar
    Join Date: Jun:2012
    Location: blagoewgrad
    Posts: 27

    - /

    , 2-3 , GTA V, BSOD (CRITICAL_PROCESS_DIED) ( Batman AK, WoW etc).

    WhoCrashed report:

    BSOD report

    On Tue 1/12/2016 4:45:11 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\011216-3375-01.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0xEF (0xFFFFE000D0E0D7C0, 0x0, 0x0, 0x0)
    Error: CRITICAL_PROCESS_DIED
    Bug check description: This indicates that a critical system process died.
    There is a possibility this problem was caused by a virus or other malware.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Tue 1/12/2016 4:45:11 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    This was probably caused by the following module: kernelbase.sys (KERNELBASE!GetLastError+0x9)
    Bugcheck code: 0xEF (0xFFFFE000D0E0D7C0, 0x0, 0x0, 0x0)
    Error: CRITICAL_PROCESS_DIED
    Bug check description: This indicates that a critical system process died.
    There is a possibility this problem was caused by a virus or other malware.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: kernelbase.sys .
    Google query: kernelbase.sys CRITICAL_PROCESS_DIED


    Report
    Windows Defender, . sfc /scannow Command Promt , GTA V 30
    WhoCrashed :

    Crash dump directory: C:\WINDOWS\Minidump

    Crash dumps are enabled on your computer.

    On Tue 1/12/2016 6:34:49 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\011216-3265-01.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80045E63C08)
    Error: IRQL_NOT_LESS_OR_EQUAL
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Tue 1/12/2016 6:34:49 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80045E63C08)
    Error: IRQL_NOT_LESS_OR_EQUAL
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    :
    i5-6600k @ 4.6Ghz
    R9 390 Sapphire Nitro @ 1100/1600
    RAM 8GB Kingston HyperX Fury @ 2666Mhz
    PSU EVGA G2 650W Gold 80+
    Define S

  2. #2

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Copyright © 1999-2011 . .
iskamPC.com | mobility.BG | Bloody's Techblog | | 3D Vision Blog |