Windows 10: Multiple BSOD over the last few days possibly after an update

Discus and support Multiple BSOD over the last few days possibly after an update in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi All, Having a bit of a mare with my laptop over the last few days. I have updated my drivers etc and took a look at the debugging files but over... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by skyblu3sk, Jan 29, 2016.

  1. SKYBLU3SK
    skyblu3sk Win User

    Multiple BSOD over the last few days possibly after an update


    Hi All,

    Having a bit of a mare with my laptop over the last few days.
    I have updated my drivers etc and took a look at the debugging files but over my head as I haven't needed to do it before.
    Anyone got any ideas it has BSOD around 10 times.
    I have attached the dump file.
    Any help gratefully received.

    Thanks,
    Daz

    :)
     
    skyblu3sk, Jan 29, 2016
    #1
  2. AAKL2227
    AAKL2227 Win User

    Multiple BSODs over the last few days (SYSTEM_SERVICE_EXCEPTION), minidump inside

    Over the past few days I've been getting frequent BSODs caused by the ntoskrnl.exe kernal. I suspect it may have something to do with my graphics drivers, my CPU or my memory. Can someone take a look through the minidump to see what
    it is?

    • *
    • 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: fffff8014f2d1b82, Address of the instruction which caused
    the bugcheck Arg3: ffffd0002380feb0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero.

    Debugging Details:
    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING: 10586.162.amd64fre.th2_release_sec.160223-1728

    SYSTEM_MANUFACTURER: MSI

    SYSTEM_PRODUCT_NAME: MS-7640

    SYSTEM_SKU: To be filled by O.E.M.

    SYSTEM_VERSION: 2.2

    BIOS_VENDOR: American Megatrends Inc.

    BIOS_VERSION: V11.13

    BIOS_DATE: 10/09/2012

    BASEBOARD_MANUFACTURER: MSI

    BASEBOARD_PRODUCT: 990FXA-GD80 (MS-7640)

    BASEBOARD_VERSION: 2.2

    DUMP_TYPE: 2

    BUGCHECK_P1: c0000005

    BUGCHECK_P2: fffff8014f2d1b82

    BUGCHECK_P3: ffffd0002380feb0

    BUGCHECK_P4: 0

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

    FAULTING_IP: nt!KxWaitForLockOwnerShipWithIrql+12 fffff801`4f2d1b82 48890a mov qword ptr [rdx],rcx

    CONTEXT: ffffd0002380feb0 -- (.cxr 0xffffd0002380feb0) rax=0000000000000000 rbx=ffffe0015b6c0680 rcx=ffffd00023810930 rdx=8000000000000000 rsi=0000000000000000 rdi=ffffd00023810930 rip=fffff8014f2d1b82 rsp=ffffd000238108d0 rbp=ffffe00153f26080
    r8=ffffd00023810990 r9=00000000f1e4e921 r10=0000000000000020 r11=ffffd00023810a88 r12=0000000000000000 r13=000000000008fda0 r14=0000000000000001 r15=0000000000010001 iopl=0 nv up di ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210086
    nt!KxWaitForLockOwnerShipWithIrql+0x12: fffff8014f2d1b82 48890a mov qword ptr [rdx],rcx ds:002b:8000000000000000=???????????????? Resetting default scope

    CPU_COUNT: 8

    CPU_MHZ: 1194

    CPU_VENDOR: AuthenticAMD

    CPU_FAMILY: 15

    CPU_MODEL: 2

    CPU_STEPPING: 0

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: 0x3B

    PROCESS_NAME: chrome.exe

    CURRENT_IRQL: 0

    ANALYSIS_SESSION_HOST: USERPC-8350970

    ANALYSIS_SESSION_TIME: 06-11-2016 14:04:25.0250

    ANALYSIS_VERSION: 10.0.10586.567 amd64fre

    LAST_CONTROL_TRANSFER: from fffff8014f284d6f to fffff8014f2d1b82

    STACK_TEXT:

    ffffd000238108d0 fffff8014f284d6f : ffffe0015b6c0680 000000000008fda0 0000000000000000 ffffe00153f26080 : nt!KxWaitForLockOwnerShipWithIrql+0x12 ffffd00023810900 fffff8014f284a4e : 000000000008fd02 ffffe00153f26080
    0000000000000000 0000000000000000 : nt!ExAcquireResourceExclusiveLite+0x1ef ffffd00023810990 fffff960ec3fca9d : 0000000000000000 0000000000000000 0000000000000000 0000000000000001 : nt!ExEnterPriorityRegionAndAcquireResourceExclusive+0x7e
    ffffd000238109c0 fffff960ec07df2d : ffffe00153f26080 ffffd00023810b80 0000000000000000 00000000ffffffff : win32kbase!EnterCrit+0x4d ffffd00023810a00 fffff8014f360fa3 : ffffe00153f26080 000000000008e688
    ffffd00023810aa8 000000000018f714 : win32kfull!NtUserPeekMessage+0x4d ffffd00023810a90 0000000062573784 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x13
    000000000008e668 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x62573784

    THREAD_SHA1_HASH_MOD_FUNC: 080ca959bc0f91ea3f13e0ac28a1802c40136cd6

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 83891a6d6820a44e3aa50a9677cdecf9b0028e88

    THREAD_SHA1_HASH_MOD: d38a0e80e29ac41d6c27da3d0bc8db7d9656fb38

    FOLLOWUP_IP: win32kbase!EnterCrit+4d fffff960`ec3fca9d 4885c0 test rax,rax

    FAULT_INSTR_CODE: 74c08548

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: win32kbase!EnterCrit+4d

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: win32kbase

    IMAGE_NAME: win32kbase.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 56cd500e

    IMAGE_VERSION: 10.0.10586.162

    STACK_COMMAND: .cxr 0xffffd0002380feb0 ; kb

    BUCKET_ID_FUNC_OFFSET: 4d

    FAILURE_BUCKET_ID: 0x3B_win32kbase!EnterCrit

    BUCKET_ID: 0x3B_win32kbase!EnterCrit

    PRIMARY_PROBLEM_CLASS: 0x3B_win32kbase!EnterCrit

    TARGET_TIME: 2016-06-11T20:24:30.000Z

    OSBUILD: 10586

    OSSERVICEPACK: 0

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 272

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2016-02-23 21:48:00

    BUILDDATESTAMP_STR: 160223-1728

    BUILDLAB_STR: th2_release_sec

    BUILDOSVER_STR: 10.0.10586.162.amd64fre.th2_release_sec.160223-1728

    ANALYSIS_SESSION_ELAPSED_TIME: 94e

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x3b_win32kbase!entercrit

    FAILURE_ID_HASH: {23f35199-491f-8e4d-7188-10b1051d8e7b}

    Followup: MachineOwner

    Thanks!

    Specs:

    AMD FX-8350 @ 4.5 GHz

    16GB DDR3 RAM @ 1600MHz

    MSI 990FXA-GD80 (MS-7640) MoBo

    Nvidia GTX 970

    120GB SSD

    2TB HDD
     
    AAKL2227, Jan 29, 2016
    #2
  3. XP ROCKS.
    XP ROCKS. Win User
    Multiple BSODs over the last few days (SYSTEM_SERVICE_EXCEPTION), minidump inside

    You need to upload and share copies of you crash dumps on you onedrive, and post a link to them, so we can analyze them.
     
    XP ROCKS., Jan 29, 2016
    #3
  4. AXE0
    axe0 New Member

    Multiple BSOD over the last few days possibly after an update

    Please try following command in an admin command prompt
    Code: DISM /Online /Cleanup-Image /RestoreHealth[/quote] If there are problems with RestoreHealth, please follow step 6 or 7 (depending on the file you have from the download) from the tutorial DISM - Repair Windows 10 Image - Tutorial





    Multiple BSOD over the last few days possibly after an update [​IMG]
    Diagnostics Test
    Multiple BSOD over the last few days possibly after an update [​IMG]
    System File Check
    Please try following:
    • Open an admin command prompt
    • Copy/paste "sfc/scannow" (without quotes) and press enter
    • When it finished reboot your system
    • Open again an admin command prompt
    • Enter sfc/scannow again
    If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
    System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

    In an admin command prompt run also following command
    Code: chkdsk C: /r[/quote]
     
    axe0, Jan 29, 2016
    #4
  5. SKYBLU3SK
    skyblu3sk Win User
    Hi, Thanks for the tips, nothing flagged up in the above rebooted computer and BSOD happened again with Registry issue.
    Any further thoughts?

    Thanks,
    D
     
    skyblu3sk, Jan 29, 2016
    #5
Thema:

Multiple BSOD over the last few days possibly after an update

Loading...

  1. Multiple BSOD over the last few days possibly after an update - Similar Threads - Multiple BSOD last

  2. multiple BSOD over few days

    in Windows 10 BSOD Crashes and Debugging
    multiple BSOD over few days: Hello,I've been experiencing multiple BSOD of the past couple of days. All of them had different error code. I am not an expert and so I had difficulty understanding what to do to fix my computer. I had the following issues:Code: 1000007eParamètre 1: ffffffffc0000005Paramètre...

  3. multiple BSOD over few days

    in Windows 10 Gaming
    multiple BSOD over few days: Hello,I've been experiencing multiple BSOD of the past couple of days. All of them had different error code. I am not an expert and so I had difficulty understanding what to do to fix my computer. I had the following issues:Code: 1000007eParamètre 1: ffffffffc0000005Paramètre...

  4. multiple BSOD over few days

    in Windows 10 Software and Apps
    multiple BSOD over few days: Hello,I've been experiencing multiple BSOD of the past couple of days. All of them had different error code. I am not an expert and so I had difficulty understanding what to do to fix my computer. I had the following issues:Code: 1000007eParamètre 1: ffffffffc0000005Paramètre...

  5. Windows 10 multiple BSODs last few days

    in Windows 10 Gaming
    Windows 10 multiple BSODs last few days: Hey guys,after already having stability issues and blue screens mid this year, I did a clean reinstall of windows a month back and everything was running smooth until a few days ago, I didn't change anything in my system when it started and I kept all drivers up to date. Here...

  6. Windows 10 multiple BSODs last few days

    in Windows 10 Software and Apps
    Windows 10 multiple BSODs last few days: Hey guys,after already having stability issues and blue screens mid this year, I did a clean reinstall of windows a month back and everything was running smooth until a few days ago, I didn't change anything in my system when it started and I kept all drivers up to date. Here...

  7. Windows 10 multiple BSODs last few days

    in Windows 10 BSOD Crashes and Debugging
    Windows 10 multiple BSODs last few days: Hey guys,after already having stability issues and blue screens mid this year, I did a clean reinstall of windows a month back and everything was running smooth until a few days ago, I didn't change anything in my system when it started and I kept all drivers up to date. Here...

  8. Multiple BSODs over the past few days.

    in Windows 10 BSOD Crashes and Debugging
    Multiple BSODs over the past few days.: I have been getting multiple different BSODs that happen randomly throughout the day. Let me know what information I can give to help find a solution.Minidumps for those crashes: https://www.mediafire.com/file/0ayep94lj710z6p/Minidumps.zip/file...

  9. Mutliple BSOD over the last few days

    in Windows 10 BSOD Crashes and Debugging
    Mutliple BSOD over the last few days: After checking the event viewer after a BSOD I see this error that I posted below not sure what it means exactly can anyone help? Using Windows 10 The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c4 (0x0000000000000083, 0x0000000018118000,...

  10. BSOD over the last few days

    in Windows 10 BSOD Crashes and Debugging
    BSOD over the last few days: I've noticed that over the last few days my machine has been crashing randomly. This machine is fairly static, software is very rarely added. It's mainly just Windows Updates. Any idea where to start?...