Is my system SSD gone?

Page 1 of 2 12 LastLast

  1. Posts : 16
    Win 10 x64
       #1

    Is my system SSD gone?


    Hi.
    I noticed my PC is restarting itself this morning and I found two minidumps, here they are.


    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000006, Exception code that caused the bugcheck
    Arg2: fffff8061e09e972, Address of the instruction which caused the bugcheck
    Arg3: ffff9284a9379470, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.


    Debugging Details:
    ------------------


    *** WARNING: Unable to verify timestamp for win32k.sys


    KEY_VALUES_STRING: 1


    Key : Analysis.CPU.Sec
    Value: 3


    Key : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-NSHNSRQ


    Key : Analysis.DebugData
    Value: CreateObject


    Key : Analysis.DebugModel
    Value: CreateObject


    Key : Analysis.Elapsed.Sec
    Value: 48


    Key : Analysis.Memory.CommitPeak.Mb
    Value: 74


    Key : Analysis.System
    Value: CreateObject




    BUGCHECK_CODE: 3b


    BUGCHECK_P1: c0000006


    BUGCHECK_P2: fffff8061e09e972


    BUGCHECK_P3: ffff9284a9379470


    BUGCHECK_P4: 0


    CONTEXT: ffff9284a9379470 -- (.cxr 0xffff9284a9379470)
    rax=0000000000000000 rbx=ffff9284a9379ed0 rcx=0000000000000007
    rdx=000000000188aa58 rsi=0000000000000155 rdi=ffffdc04ac40b000
    rip=fffff8061e09e972 rsp=ffff9284a9379e78 rbp=ffffdc04ac40b000
    r8=000000000000001c r9=ffff80033836d080 r10=0000024d929fba58
    r11=0000000000000a58 r12=00000000a88ef046 r13=ffff9284a937a130
    r14=0000000000000155 r15=0000024d92a1e024
    iopl=0 nv up ei pl nz na pe nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202
    nt!HvpGetCellPaged+0xa2:
    fffff806`1e09e972 418b02 mov eax,dword ptr [r10] ds:002b:0000024d`929fba58=????????
    Resetting default scope


    BLACKBOXBSD: 1 (!blackboxbsd)




    BLACKBOXNTFS: 1 (!blackboxntfs)




    BLACKBOXPNP: 1 (!blackboxpnp)




    BLACKBOXWINLOGON: 1


    CUSTOMER_CRASH_COUNT: 1


    PROCESS_NAME: Registry


    STACK_TEXT:
    ffff9284`a9379e78 fffff806`1e01bf6f : 00000000`e9c5e935 ffff9284`a937a1f0 0000024d`92a18ff4 00000000`c0000034 : nt!HvpGetCellPaged+0xa2
    ffff9284`a9379e80 fffff806`1e021da5 : 00000001`ffffffff 00000000`a88ef046 00000000`e9c5e935 00000000`00000000 : nt!CmpDoCompareKeyName+0x2f
    ffff9284`a9379ed0 fffff806`1e024fc9 : ffffdc04`f866c320 00000000`00000006 ffff9284`a937a0d0 ffff9284`a937a150 : nt!CmpWalkOneLevel+0x6f5
    ffff9284`a9379fd0 fffff806`1e0238b3 : 00000000`0000001c ffff9284`a937a320 ffff9284`a937a2d8 ffff8003`3e652010 : nt!CmpDoParseKey+0x849
    ffff9284`a937a270 fffff806`1e02797e : fffff806`1e023501 00000000`00000000 ffff8003`3e652010 00000000`6d4e6201 : nt!CmpParseKey+0x2c3
    ffff9284`a937a410 fffff806`1dfeb27a : ffff8003`3e652000 ffff9284`a937a678 00000000`00000040 ffff8003`29af6c40 : nt!ObpLookupObjectName+0x3fe
    ffff9284`a937a5e0 fffff806`1dfeb05c : 00000000`00000000 00000000`00000000 00000000`00000000 ffff8003`29af6c40 : nt!ObOpenObjectByNameEx+0x1fa
    ffff9284`a937a710 fffff806`1dfeab81 : 0000003f`b64fe238 ffff9284`a937aa80 00000000`00000001 fffff806`1dc6119e : nt!ObOpenObjectByName+0x5c
    ffff9284`a937a760 fffff806`1dfea8af : 0000019e`82cdc3d0 00000000`00000000 00000000`00000000 00000000`00000002 : nt!CmOpenKey+0x2c1
    ffff9284`a937a9c0 fffff806`1de075b5 : 00000000`00500000 ffff8003`32c70080 ffff9284`a937aa80 0000019e`82b47050 : nt!NtOpenKeyEx+0xf
    ffff9284`a937aa00 00007ffc`a53ef004 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
    0000003f`b64fe158 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`a53ef004




    SYMBOL_NAME: nt!HvpGetCellPaged+a2


    MODULE_NAME: nt


    IMAGE_NAME: ntkrnlmp.exe


    IMAGE_VERSION: 10.0.19041.867


    STACK_COMMAND: .cxr 0xffff9284a9379470 ; kb


    BUCKET_ID_FUNC_OFFSET: a2


    FAILURE_BUCKET_ID: 0x3B_c0000006_nt!HvpGetCellPaged


    OS_VERSION: 10.0.19041.1


    BUILDLAB_STR: vb_release


    OSPLATFORM_TYPE: x64


    OSNAME: Windows 10


    FAILURE_ID_HASH: {68f3db38-ae8e-4bae-c37a-85819946495f}


    Followup: MachineOwner



    And the second one...

    UNEXPECTED_STORE_EXCEPTION (154)
    The store component caught an unexpected exception.
    Arguments:
    Arg1: ffffe10406db5000, Pointer to the store context or data manager
    Arg2: fffff582284b9f30, Exception information
    Arg3: 0000000000000002, Reserved
    Arg4: 0000000000000000, Reserved


    Debugging Details:
    ------------------


    *** WARNING: Unable to verify timestamp for win32k.sys


    KEY_VALUES_STRING: 1


    Key : Analysis.CPU.Sec
    Value: 3


    Key : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-NSHNSRQ


    Key : Analysis.DebugData
    Value: CreateObject


    Key : Analysis.DebugModel
    Value: CreateObject


    Key : Analysis.Elapsed.Sec
    Value: 8


    Key : Analysis.Memory.CommitPeak.Mb
    Value: 72


    Key : Analysis.System
    Value: CreateObject




    BUGCHECK_CODE: 154


    BUGCHECK_P1: ffffe10406db5000


    BUGCHECK_P2: fffff582284b9f30


    BUGCHECK_P3: 2


    BUGCHECK_P4: 0


    EXCEPTION_RECORD: fffff582284baeb8 -- (.exr 0xfffff582284baeb8)
    ExceptionAddress: fffff802318f49e0 (nt!RtlDecompressBufferXpressLz+0x0000000000000050)
    ExceptionCode: c0000006 (In-page I/O error)
    ExceptionFlags: 00000000
    NumberParameters: 3
    Parameter[0]: 0000000000000000
    Parameter[1]: 0000024e3bac4680
    Parameter[2]: 00000000c000000e
    Inpage operation failed at 0000024e3bac4680, due to I/O error 00000000c000000e


    EXCEPTION_PARAMETER1: 0000000000000000


    EXCEPTION_PARAMETER2: 0000024e3bac4680


    CONTEXT: fffff582284ba6f0 -- (.cxr 0xfffff582284ba6f0)
    rax=fffff802318f4990 rbx=ffffb9807fe73000 rcx=ffffb9807fe73000
    rdx=ffffb9807fe73000 rsi=0000000000000002 rdi=0000024e3bac4680
    rip=fffff802318f49e0 rsp=fffff582284bb0f8 rbp=0000024e3bac4732
    r8=0000024e3bac4680 r9=0000000000000108 r10=ffffb9807fe73ea0
    r11=0000024e3bac4788 r12=fffff582284bb368 r13=ffffe1040ced9000
    r14=ffffb9807fe74000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00050246
    nt!RtlDecompressBufferXpressLz+0x50:
    fffff802`318f49e0 418b08 mov ecx,dword ptr [r8] ds:002b:0000024e`3bac4680=????????
    Resetting default scope


    BLACKBOXBSD: 1 (!blackboxbsd)




    BLACKBOXNTFS: 1 (!blackboxntfs)




    BLACKBOXPNP: 1 (!blackboxpnp)




    BLACKBOXWINLOGON: 1


    CUSTOMER_CRASH_COUNT: 1


    PROCESS_NAME: MemCompression


    IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was specified.


    EXCEPTION_STR: 0xc0000006_c000000e


    ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.


    EXCEPTION_CODE_STR: c0000006


    EXCEPTION_PARAMETER3: 00000000c000000e


    STACK_TEXT:
    fffff582`284b9e78 fffff802`31b9415e : 00000000`00000154 ffffe104`06db5000 fffff582`284b9f30 00000000`00000002 : nt!KeBugCheckEx
    fffff582`284b9e80 fffff802`31a0f136 : ffffe104`06db5000 fffff582`284b9f30 fffff582`00000002 fffff582`284b9fe0 : nt!SMKM_STORE<SM_TRAITS>::SmStUnhandledExceptionFilter+0x7e
    fffff582`284b9ed0 fffff802`319cc04f : fffff802`00000002 fffff802`316d1244 fffff582`284b5000 fffff582`284bc000 : nt!`SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue'::`1'::filt$0+0x22
    fffff582`284b9f00 fffff802`319fe93f : fffff802`316d1244 fffff582`284ba4e0 fffff802`319cbfb0 00000000`00000000 : nt!_C_specific_handler+0x9f
    fffff582`284b9f70 fffff802`3192bf97 : fffff582`284ba4e0 00000000`00000000 fffff582`284bb3c0 fffff802`318c3359 : nt!RtlpExecuteHandlerForException+0xf
    fffff582`284b9fa0 fffff802`3192ab86 : fffff582`284baeb8 fffff582`284babf0 fffff582`284baeb8 0000024e`3bac4680 : nt!RtlDispatchException+0x297
    fffff582`284ba6c0 fffff802`31a07bac : ffffe104`06db7780 fffff802`319540e6 00000000`00010000 fffff582`284baf60 : nt!KiDispatchException+0x186
    fffff582`284bad80 fffff802`31a03d43 : ffffe104`1501da80 00000000`00000000 00000000`00000001 ffffcb85`e0491468 : nt!KiExceptionDispatch+0x12c
    fffff582`284baf60 fffff802`318f49e0 : ffffb980`7fe73000 ffffe104`06db5050 fffff802`318c42d0 ffffb980`7fe73000 : nt!KiPageFault+0x443
    fffff582`284bb0f8 fffff802`318c42d0 : ffffb980`7fe73000 ffffb980`7fe73000 00000000`00000002 0000024e`3bac4680 : nt!RtlDecompressBufferXpressLz+0x50
    fffff582`284bb110 fffff802`318c4018 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlDecompressBufferEx+0x60
    fffff582`284bb160 fffff802`318c3ea5 : 00000000`00000004 fffff802`318c3a0e 00000000`00000000 00000000`00000001 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x150
    fffff582`284bb220 fffff802`318c36dc : 00000000`00000001 00000000`00004680 ffffe104`06db5000 ffffe104`00001000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa5
    fffff582`284bb270 fffff802`318c350c : 00000000`ffffffff ffffe104`0ced9000 fffff582`284bb350 ffffe104`0cc02f10 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x180
    fffff582`284bb310 fffff802`318c3359 : fffff802`2f1ce730 00000000`00000001 00000000`00000000 00000000`00000000 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc8
    fffff582`284bb3c0 fffff802`318c3211 : ffffe104`06db5000 ffffe104`0cc02f10 ffffe104`0ced9000 ffffe104`06db69c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
    fffff582`284bb440 fffff802`31954488 : ffffe104`08721080 ffffe104`06db5000 00000000`00000000 ffffe104`0a4b0a00 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
    fffff582`284bb470 fffff802`3190a337 : fffff802`318c31f0 fffff582`284bb510 00000000`00000003 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78
    fffff582`284bb4e0 fffff802`3183e0b4 : fffff582`284bb5e0 00000000`31526d73 00000000`000003ff fffff802`323239c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xc7
    fffff582`284bb5b0 fffff802`3183dae8 : 00000000`0000000c 00000000`000003ff fffff582`284bb660 fffff802`323239c0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1ac
    fffff582`284bb600 fffff802`31909597 : 00000000`0000000c 00000000`00000001 ffffe104`0cc02f10 ffffe104`0a4b0a00 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xc0
    fffff582`284bb690 fffff802`3191d34b : ffffe104`00000001 ffffe104`0a4b0ac0 00000000`00000000 ffffe104`06db5000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x167
    fffff582`284bb700 fffff802`318b6f60 : 0000007f`00000100 00000000`00000000 fffff582`284bb958 fffff802`318b4eb0 : nt!SmPageRead+0x33
    fffff582`284bb750 fffff802`318b4a0d : 00000000`00000002 fffff582`284bb7e0 fffff582`284bb958 ffffe104`0a4b09b0 : nt!MiIssueHardFaultIo+0x10c
    fffff582`284bb7a0 fffff802`3180c9c8 : 00000000`c0033333 00000000`00000001 00007ff5`da75aaf0 ffffcb85`a211b1d0 : nt!MiIssueHardFault+0x29d
    fffff582`284bb860 fffff802`31a03c5e : 00007ff8`5fc9f400 00000000`00000000 fffff582`284bba80 00000218`c03bbc50 : nt!MmAccessFault+0x468
    fffff582`284bba00 00007ff8`6009c04e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
    000000bf`cd676ca8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`6009c04e




    MODULE_NAME: hardware_disk


    IMAGE_NAME: hardware_disk


    STACK_COMMAND: .thread ; .cxr ; kb


    FAILURE_BUCKET_ID: 0x154_c0000006_c000000e_IMAGE_hardware_disk


    OS_VERSION: 10.0.19041.1


    BUILDLAB_STR: vb_release


    OSPLATFORM_TYPE: x64


    OSNAME: Windows 10


    FAILURE_ID_HASH: {6ef1f8aa-ba96-513b-39a6-be53976d18b0}


    Followup: MachineOwner



    I am not sure is it my SSD, which is OS holder, or HDD which is my second disk, but seems something is wrong with one of the disks.
    Can someone throw some light on this, explain what it is, maybe which disk it is, and is it really an disk hardware.
      My Computer


  2. Posts : 35,400
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #2

    If you wish to check your disks, you can, of course.
    E.g. Crystal Diskinfo (free) - basic SMART check.

    Hard Disk Sentinel (SSDs too) is great - portable version available too- trial version..
    - best in class instant appraisal right on its GUI.
    Download Hard Disk Sentinel

    If your PC restarts too frequently, you may need to try booting from a live boot disk (freely available e.g. Kyhi's, Bob Omb's...)

    I am not sure is it my SSD, which is OS holder, or HDD which is my second disk, but seems something is wrong with one of the disks.
    You could, of course, if you wished, disconnect your HDD.

    And the restarts may have absolutely nothing to do with your disks or even your O/S...and that needs further analysis.

    Once you know your disks are good, you can run basic checks e.g.
    chkdsk c: /scan
    from an admin command or Powershell Prompt
    and then similarly
    SFC /SCANNOW

    Still random restarts?
    Check your RAM
    PSU

    What changes have you made recently that may have led to this?
    Any recent updates? (See your Update History).
      My Computers


  3. Posts : 39,994
    windows 10 professional version 1607 build 14393.969 64 bit
       #3

    See posting instructions: Run both V2 and DM
    BSOD - Posting Instructions



    Run: Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.




    For all steps / tests make sure images are posted into the thread:


    Take Screenshot in Windows 10
    https://support.microsoft.com/en-gb/...re-screenshots

    How to Upload and Post Screenshots and Files at Ten Forums
      My Computer


  4. Posts : 16
    Win 10 x64
    Thread Starter
       #4

    dalchina said:
    If you wish to check your disks, you can, of course.
    E.g. Crystal Diskinfo (free) - basic SMART check.

    Hard Disk Sentinel (SSDs too) is great - portable version available too- trial version..
    - best in class instant appraisal right on its GUI.
    Download Hard Disk Sentinel

    If your PC restarts too frequently, you may need to try booting from a live boot disk (freely available e.g. Kyhi's, Bob Omb's...)


    You could, of course, if you wished, disconnect your HDD.

    And the restarts may have absolutely nothing to do with your disks or even your O/S...and that needs further analysis.

    Once you know your disks are good, you can run basic checks e.g.
    chkdsk c: /scan
    from an admin command or Powershell Prompt
    and then similarly
    SFC /SCANNOW

    Still random restarts?
    Check your RAM
    PSU

    What changes have you made recently that may have led to this?
    Any recent updates? (See your Update History).
    Thanks for the answer.

    I ran...
    Hard Disk Sentinel
    Crystal Diskinfo
    HD Tune Pro Trial
    chkdsk c: /scan
    chkdsk d: /scan
    chkdsk e: /scan
    sfc /scannow (some errors were fixed )
    Hashes for file member [l:12]'mscormmc.dll' do not match.


    I did not find single problem, althought I still believe it is a disk problem.
    However, I will see how to run memtest from usb, and leave it over night as I have 32GB of RAM.
      My Computer


  5. Posts : 35,400
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #5

    Great basic start.. the thread is now in @zbook's hands as usual. Good luck.
      My Computers


  6. Posts : 16
    Win 10 x64
    Thread Starter
       #6

    zbook said:
    See posting instructions: Run both V2 and DM
    BSOD - Posting Instructions



    Run: Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.




    For all steps / tests make sure images are posted into the thread:


    Take Screenshot in Windows 10
    https://support.microsoft.com/en-gb/...re-screenshots

    How to Upload and Post Screenshots and Files at Ten Forums
    Google Drive: Sign-in
    Google Drive: Sign-in

    I will picture and post Tuneup.bat result, because I don't understand way described to save it as log, like at all, I just closed CMD for no reason following instructions.
      My Computer


  7. Posts : 35,400
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #7

    Please also confirm you are not overclocking and no sign of overheating.

    What changes have you made recently that may have led to this?
    Any recent updates? (See your Update History).

    What is your build number?

    Thanks.
      My Computers


  8. Posts : 16
    Win 10 x64
    Thread Starter
       #8

    dalchina said:
    Please also confirm you are not overclocking and no sign of overheating.

    What changes have you made recently that may have led to this?
    Any recent updates? (See your Update History).

    Thanks.
    No overclocking.
    No overheating.

    The BSOD actually occurred while I was not using PC, both times.

    I noticed it by remembering that I left Chrome opened, and than I have seen it is asking to restore tabs, so I knew PC was having an update or was restarted by bug, and than event viewer showed bug, so I discovered minidump.

    Problems occured at these times by WhoCrashed.

    On Tue 3/16/2021 6:09:11 AM your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\Minidump\031621-14765-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C50)
    Bugcheck code: 0x3B (0xC0000006, 0xFFFFF8061E09E972, 0xFFFF9284A9379470, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    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 Wed 3/10/2021 11:01:52 PM your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\Minidump\031021-7765-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
    Bugcheck code: 0x154 (0xFFFFE10406DB5000, 0xFFFFF582284B9F30, 0x2, 0x0)
    Error: UNEXPECTED_STORE_EXCEPTION
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that the store component caught an unexpected exception.
    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.


    - - - Updated - - -

    Fixed Google Drive Links.
      My Computer


  9. Posts : 39,994
    windows 10 professional version 1607 build 14393.969 64 bit
       #9

    Please make share links available without sign-in.
      My Computer


  10. Posts : 7,483
    Windows 10 Home 20H2
       #10

    dalchina said:
    Great basic start.. the thread is now in @zbook's hands as usual. Good luck.
    All threads are open to all members rather than in any particular member's hands.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:28.
Find Us




Windows 10 Forums