Windows 10: My computer keeps giving me a BSOD Please help!

Discus and support My computer keeps giving me a BSOD Please help! in Windows 10 BSOD Crashes and Debugging to solve the problem; This is my Build: Asrock 970a-G/3.1 Amd FX 8350 DDR3 Gskill Ripjaw 16 GB 1333hz MSI GTX 970 EVGA Supernova 650w Corsair Case Coolermaster Hyper... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Omq111, Feb 4, 2021.

  1. OMQ111
    Omq111 Win User

    My computer keeps giving me a BSOD Please help!


    This is my Build:

    Asrock 970a-G/3.1

    Amd FX 8350

    DDR3 Gskill Ripjaw 16 GB 1333hz

    MSI GTX 970

    EVGA Supernova 650w

    Corsair Case

    Coolermaster Hyper 212 EVO CPU cooler



    Below are Mini Dumps I have collected from numerous crashes BSOD. There are only 4 minidumps below but there were many crashes before but most of them have been deleted Mini Dumps are labeled with date and time,I will try to provide every detail as well as everything I remember trying to solve the problem.


    Its happened once while i was watching YouTube and browsing the web. but mostly occurs when I am on Microsoft Flight Simulator, Elite Dangerous, GTA V, ect

    I uninstalled windows 10 then reinstalled it and that didn't work


    I tried uninstalling my gpu driver and reinstalling it in safe mode. Then returned to normal os and did another clean installation of the driver with GEFORCE Expirence


    I downloaed Memtest86 and let it run for 12hrs till it finaly completed with 0 errors found


    I have done command prompt commands thanks to a community thread I found Mr. Pedro Brungueras' reply to memesmafia27s' post and followed the steps below



    "Hi, memesmafia27

    Follow these steps, I hope you can solve the problem.

    Press the Start key and type the word CMD, right click on the command prompt and select Run as administrator, enter the following commands one by one followed by the Enter key:

    sfc /SCANNOW

    DISM.exe / Online / Cleanup-image / Scanhealth

    DISM.exe / Online / Cleanup-image / Restorehealth

    The execution of these processes may be delayed, do not forget to restart the computer to apply changes.

    If it works, follow these others.

    Any corrupt DLL files are best performed using built in utilities or using a repair upgrade method:

    Open Start, type: CMD
    Right click CMD
    Click Run as administrator

    Type in at the prompt OR Copy and Paste these one at a time : Hit enter after each

    Dism /Online /Cleanup-Image /CheckHealth

    Dism /Online /Cleanup-Image /ScanHealth

    Dism /Online /Cleanup-Image /RestoreHealth

    Also run the System File Checker utility:
    Open Start, type: CMD
    Right click CMD
    Click Run as administrator

    At the Command Prompt, type: sfc/scannow

    This will check for any integrity violations

    Restart your system" Pedro Brunguera

    THIS CRASH MINIDUMP BELOW OCCURED 1/25/2021 AT 11;51PM


    Microsoft R Windows Debugger Version 10.0.19041.685 AMD64

    Copyright c Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\Windows\Minidump\012521-9453-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available



    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 19041 MP 8 procs Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Machine Name:

    Kernel base = 0xfffff800`32a00000 PsLoadedModuleList = 0xfffff800`3362a2f0

    Debug session time: Mon Jan 25 23:50:30.870 2021 UTC - 6:00

    System Uptime: 0 days 7:42:34.640

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ................................................................

    .....

    Loading User Symbols

    Loading unloaded module list

    .........

    For analysis of this file, run !analyze -v

    2: kd> !analyze -v

    *******************************************************************************

    * *

    * 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: fffff80032c4c7f4, Address of the instruction which caused the bugcheck

    Arg3: fffff98be96de8e0, Address of the context record for the exception that caused the bugcheck

    Arg4: 0000000000000000, zero.



    Debugging Details:

    ------------------





    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.Sec

    Value: 7



    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on DESKTOP-INLR66U



    Key : Analysis.DebugData

    Value: CreateObject



    Key : Analysis.DebugModel

    Value: CreateObject



    Key : Analysis.Elapsed.Sec

    Value: 12



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 93



    Key : Analysis.System

    Value: CreateObject





    DUMP_FILE_ATTRIBUTES: 0x8

    Kernel Generated Triage Dump



    BUGCHECK_CODE: 3b



    BUGCHECK_P1: c0000005



    BUGCHECK_P2: fffff80032c4c7f4



    BUGCHECK_P3: fffff98be96de8e0



    BUGCHECK_P4: 0



    CONTEXT: fffff98be96de8e0 -- .cxr 0xfffff98be96de8e0

    rax=0000000000000005 rbx=ffff83c7c0602080 rcx=ffff83c7c6203180

    rdx=fffff80032a00000 rsi=ffff83c7c6203180 rdi=a2e64eada2e64ead

    rip=fffff80032c4c7f4 rsp=fffff98be96df2e0 rbp=0000000000000000

    r8=0000000000000000 r9=0000000000000000 r10=fffff800333b1010

    r11=ffff8afcfc600000 r12=0000000000000000 r13=0000000000003dff

    r14=ffff83c7c6203180 r15=fffff98be96df9d8

    iopl=0 nv up ei pl zr na po nc

    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246

    nt!ExFreeHeapPool+0x64:

    fffff800`32c4c7f4 0f11442540 movups xmmword ptr [rbp+40h],xmm0 ss:0018:00000000`00000040=????????????????????????????????

    Resetting default scope



    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXNTFS: 1 !blackboxntfs





    BLACKBOXWINLOGON: 1



    CUSTOMER_CRASH_COUNT: 1



    PROCESS_NAME: amtrucks.exe



    STACK_TEXT:

    fffff98b`e96df2e0 fffff800`333b1019 : fffff98b`e96df438 00000000`00000008 ffff83aa`d89c2cf0 ffff8afc`fc600000 : nt!ExFreeHeapPool+0x64

    fffff98b`e96df3c0 ffff83aa`d89c2d42 : fffff98b`e96df450 00000000`00000004 ffff0613`46e70364 fffff98b`e96df400 : nt!ExFreePool+0x9

    fffff98b`e96df3f0 ffff83aa`d862cfef : 00000000`00000000 ffff83c7`c6203180 ffff83c7`c0c08060 ffff83c7`c0e16048 : win32kfull!Win32FreePoolImpl+0x52

    fffff98b`e96df420 ffff83aa`d88e6698 : ffffffff`b47e0403 ffff83c7`c6203180 00000000`00000000 00000000`00000000 : win32kbase!HMFreeObject+0x12f

    fffff98b`e96df480 ffff83aa`d895aed7 : ffff83c7`c06c4010 fffff98b`e96dfb80 00000000`00000000 00000000`00000000 : win32kfull!FreeHidData+0x38

    fffff98b`e96df4b0 ffff83aa`d8959918 : fffff98b`e96df9d8 00000000`00000000 00000000`00000000 fffff98b`e96dfaa8 : win32kfull!xxxRealInternalGetMessage+0x1557

    fffff98b`e96df980 ffff83aa`d8fb71ad : ffffc00c`972ad080 000000f6`718ff7a8 fffff98b`e96dfaa8 00000000`00000000 : win32kfull!NtUserPeekMessage+0x158

    fffff98b`e96dfa40 fffff800`32e071b8 : fffff98b`e96dfb18 00000000`00000000 00000000`00000000 ffffc00c`eb29f170 : win32k!NtUserPeekMessage+0x29

    fffff98b`e96dfa90 00007fff`6be51064 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28

    000000f6`718ff788 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`6be51064





    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt

    fffff80032c4c7f7 - nt!ExFreeHeapPool+67

    [ 24:25 ]

    1 error : !nt fffff80032c4c7f7



    MODULE_NAME: memory_corruption



    IMAGE_NAME: memory_corruption



    MEMORY_CORRUPTOR: ONE_BIT



    STACK_COMMAND: .cxr 0xfffff98be96de8e0 ; kb



    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}



    Followup: memory_corruption


    THIS IS ANOTHER MINIDUMP FILE THAT OCCURED AT 3;51AM ON 1/24/2021


    Microsoft R Windows Debugger Version 10.0.19041.685 AMD64

    Copyright c Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\Windows\Minidump\012421-7531-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available



    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 19041 MP 8 procs Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Machine Name:

    Kernel base = 0xfffff806`72e00000 PsLoadedModuleList = 0xfffff806`73a2a2f0

    Debug session time: Sun Jan 24 03:50:37.912 2021 UTC - 6:00

    System Uptime: 0 days 6:26:09.595

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ...............................................................

    Loading User Symbols

    Loading unloaded module list

    ...................

    For analysis of this file, run !analyze -v

    4: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************



    STORE_DATA_STRUCTURE_CORRUPTION 1c7

    The store component detected a corruption in its data structures.

    Arguments:

    Arg1: 0000000000000000, A chunk heap buffer's hash doesn't match.

    Arg2: ffff830294475000, Chunk heap buffer whose hash didn't match.

    Arg3: 00000000f8e44161, Expected buffer hash.

    Arg4: 00000000003f020e, Page frame number of the corrupted page.



    Debugging Details:

    ------------------





    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.Sec

    Value: 3



    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on DESKTOP-INLR66U



    Key : Analysis.DebugData

    Value: CreateObject



    Key : Analysis.DebugModel

    Value: CreateObject



    Key : Analysis.Elapsed.Sec

    Value: 2



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 77



    Key : Analysis.System

    Value: CreateObject





    DUMP_FILE_ATTRIBUTES: 0x8

    Kernel Generated Triage Dump



    BUGCHECK_CODE: 1c7



    BUGCHECK_P1: 0



    BUGCHECK_P2: ffff830294475000



    BUGCHECK_P3: f8e44161



    BUGCHECK_P4: 3f020e



    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXNTFS: 1 !blackboxntfs





    BLACKBOXPNP: 1 !blackboxpnp





    BLACKBOXWINLOGON: 1



    CUSTOMER_CRASH_COUNT: 1



    PROCESS_NAME: MemCompression



    STACK_TEXT:

    fffff885`a32f4938 fffff806`73227e38 : 00000000`000001c7 00000000`00000000 ffff8302`94475000 00000000`f8e44161 : nt!KeBugCheckEx

    fffff885`a32f4940 fffff806`7303fd15 : 7fde9f1c`3df2d81b 00000000`003f020e 00000000`0000091a fffff885`a32f4a69 : nt!SmHpBufferProtectEx+0x1e8114

    fffff885`a32f49a0 fffff806`7303f348 : 00000000`ffffffff ffff324a`d7c66fa2 ffff8302`93bc11a8 00000000`2010e52f : nt!SmHpChunkUnprotect+0x2d

    fffff885`a32f49d0 fffff806`730c518c : 00000000`00000000 00000000`00000000 fffff885`a32f4a69 00000000`00000000 : nt!ST_STORE<SM_TRAITS>::StDmPageRecordUnprotect+0x1c

    fffff885`a32f4a00 fffff806`7303eda2 : 00000000`00000000 ffff8302`89bc5b90 00000000`00000000 fffff806`7303ec93 : nt!ST_STORE<SM_TRAITS>::StDmPageRemove+0x130

    fffff885`a32f4ad0 fffff806`7303e2ce : ffff8302`89b03000 fffff885`a32f4b98 00000000`00000001 ffff8302`89aee080 : nt!ST_STORE<SM_TRAITS>::StWorkItemProcess+0xc2

    fffff885`a32f4b20 fffff806`73122391 : fffff806`00000000 ffff8302`00000000 00000000`00000000 00000000`00000000 : nt!SMKM_STORE<SM_TRAITS>::SmStWorker+0x12a

    fffff885`a32f4be0 fffff806`73117e25 : ffff8302`89b03000 fffff806`73122380 fffff885`a31bf3a8 00078224`acbb3dfe : nt!SMKM_STORE<SM_TRAITS>::SmStWorkerThread+0x11

    fffff885`a32f4c10 fffff806`731fcdd8 : fffff806`70a02180 ffff8302`89aee080 fffff806`73117dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55

    fffff885`a32f4c60 00000000`00000000 : fffff885`a32f5000 fffff885`a32ef000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28





    SYMBOL_NAME: nt!SmHpBufferProtectEx+1e8114



    MODULE_NAME: nt



    IMAGE_NAME: ntkrnlmp.exe



    IMAGE_VERSION: 10.0.19041.746



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: 1e8114



    FAILURE_BUCKET_ID: 0x1C7_0_nt!SmHpBufferProtectEx



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {677f42d4-ea31-d924-1621-3373689c0a0a}



    Followup: MachineOwner




    THIS MINIDUMP BELOW BSOD OCCURED 1/24/2021 AT 7;41PM


    Microsoft R Windows Debugger Version 10.0.19041.685 AMD64

    Copyright c Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\Windows\Minidump\012421-7515-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available



    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 19041 MP 8 procs Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Machine Name:

    Kernel base = 0xfffff800`63600000 PsLoadedModuleList = 0xfffff800`6422a2f0

    Debug session time: Sun Jan 24 19:40:26.867 2021 UTC - 6:00

    System Uptime: 0 days 15:28:23.645

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ................................................................

    ....

    Loading User Symbols

    Loading unloaded module list

    ...................

    For analysis of this file, run !analyze -v

    2: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************



    UNEXPECTED_KERNEL_MODE_TRAP_M 1000007f

    This means a trap occurred in kernel mode, and it's a trap of a kind

    that the kernel isn't allowed to have/catch bound trap or that

    is always instant death double fault. The first number in the

    bugcheck params is the number of the trap 8 = double fault, etc

    Consult an Intel x86 family manual to learn more about what these

    traps are. Here is a *portion* of those codes:

    If kv shows a taskGate

    use .tss on the part before the colon, then kv.

    Else if kv shows a trapframe

    use .trap on that value

    Else

    .trap on the appropriate frame will show where the trap was taken

    on x86, this will be the ebp that goes with the procedure KiTrap

    Endif

    kb will then show the corrected stack.

    Arguments:

    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT

    Arg2: ffffe481c8d75e70

    Arg3: 0000000000000000

    Arg4: fffff800639fc98d



    Debugging Details:

    ------------------





    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.Sec

    Value: 6



    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on DESKTOP-INLR66U



    Key : Analysis.DebugData

    Value: CreateObject



    Key : Analysis.DebugModel

    Value: CreateObject



    Key : Analysis.Elapsed.Sec

    Value: 5



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 77



    Key : Analysis.System

    Value: CreateObject





    DUMP_FILE_ATTRIBUTES: 0x8

    Kernel Generated Triage Dump



    BUGCHECK_CODE: 7f



    BUGCHECK_P1: 8



    BUGCHECK_P2: ffffe481c8d75e70



    BUGCHECK_P3: 0



    BUGCHECK_P4: fffff800639fc98d



    BAD_STACK_POINTER: 0000000000000000



    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXNTFS: 1 !blackboxntfs





    BLACKBOXPNP: 1 !blackboxpnp





    BLACKBOXWINLOGON: 1



    CUSTOMER_CRASH_COUNT: 1



    PROCESS_NAME: System



    STACK_TEXT:

    00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext+0x1ad





    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt

    fffff800639fc8c7 - nt!SwapContext+e7

    [ ae:af ]

    1 error : !nt fffff800639fc8c7



    MODULE_NAME: memory_corruption



    IMAGE_NAME: memory_corruption



    MEMORY_CORRUPTOR: ONE_BIT



    STACK_COMMAND: .thread ; .cxr ; kb



    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}



    Followup: memory_corruption



    THIS BSOD MINIDUMP BELOW OCCURED 1/22/2021 AT 1;27AM





    Microsoft R Windows Debugger Version 10.0.19041.685 AMD64

    Copyright c Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\Windows\Minidump\012221-7203-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available



    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 19041 MP 8 procs Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Machine Name:

    Kernel base = 0xfffff805`85000000 PsLoadedModuleList = 0xfffff805`85c2a2f0

    Debug session time: Fri Jan 22 01:26:46.231 2021 UTC - 6:00

    System Uptime: 0 days 1:16:37.914

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ................................................................

    .......

    Loading User Symbols

    Loading unloaded module list

    ........

    For analysis of this file, run !analyze -v

    2: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************



    PAGE_FAULT_IN_NONPAGED_AREA 50

    Invalid system memory was referenced. This cannot be protected by try-except.

    Typically the address is just plain bad or it is pointing at freed memory.

    Arguments:

    Arg1: ffffb806ec71f8f1, memory referenced.

    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.

    Arg3: fffff805853f90c4, If non-zero, the instruction address which referenced the bad memory

    address.

    Arg4: 0000000000000002, reserved



    Debugging Details:

    ------------------





    Could not read faulting driver name



    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.Sec

    Value: 6



    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on DESKTOP-INLR66U



    Key : Analysis.DebugData

    Value: CreateObject



    Key : Analysis.DebugModel

    Value: CreateObject



    Key : Analysis.Elapsed.Sec

    Value: 5



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 80



    Key : Analysis.System

    Value: CreateObject





    DUMP_FILE_ATTRIBUTES: 0x8

    Kernel Generated Triage Dump



    BUGCHECK_CODE: 50



    BUGCHECK_P1: ffffb806ec71f8f1



    BUGCHECK_P2: 0



    BUGCHECK_P3: fffff805853f90c4



    BUGCHECK_P4: 2



    READ_ADDRESS: fffff80585cfa390: Unable to get MiVisibleState

    Unable to get NonPagedPoolStart

    Unable to get NonPagedPoolEnd

    Unable to get PagedPoolStart

    Unable to get PagedPoolEnd

    fffff80585c0f330: Unable to get Flags value from nt!KdVersionBlock

    fffff80585c0f330: Unable to get Flags value from nt!KdVersionBlock

    unable to get nt!MmSpecialPagesInUse

    ffffb806ec71f8f1



    MM_INTERNAL_CODE: 2



    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXNTFS: 1 !blackboxntfs





    BLACKBOXWINLOGON: 1



    CUSTOMER_CRASH_COUNT: 1



    PROCESS_NAME: dwm.exe



    TRAP_FRAME: ffffed8920f31c80 -- .trap 0xffffed8920f31c80

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=fffff805853f90c0 rbx=0000000000000000 rcx=0000009580f7f110

    rdx=0000000000000018 rsi=0000000000000000 rdi=0000000000000000

    rip=fffff805853f90c4 rsp=ffffed8920f31e10 rbp=ffffed8920f31ec0

    r8=0000000000000000 r9=0000000000000000 r10=0000fffff805853f

    r11=ffffaffbbe200000 r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0 nv up ei ng nz na pe nc

    nt!NtCallbackReturn+0x4:

    fffff805`853f90c4 654c8b1d25880100 mov r11,qword ptr gs:[nt!RtlpLookupUserFunctionTableInverted$filt$0+0x11 fffff805`854118f1] gs:fffff805`854118f1=404d894828558910

    Resetting default scope



    STACK_TEXT:

    ffffed89`20f319d8 fffff805`8541e8bb : 00000000`00000050 ffffb806`ec71f8f1 00000000`00000000 ffffed89`20f31c80 : nt!KeBugCheckEx

    ffffed89`20f319e0 fffff805`8520c960 : 00000000`000186a0 00000000`00000000 ffffed89`20f31d00 00000000`00000000 : nt!MiSystemFault+0x1f40ab

    ffffed89`20f31ae0 fffff805`8540395e : ffff9b84`d47eb1c0 ffffaffb`be200000 ffffab9e`04111010 00000000`00000000 : nt!MmAccessFault+0x400

    ffffed89`20f31c80 fffff805`853f90c4 : 00000067`9cf6e380 00000000`00da7a64 00000067`9cf6e810 00000000`00000000 : nt!KiPageFault+0x35e

    ffffed89`20f31e10 fffff805`854071b8 : ffff9b84`cd60b080 ffff9b84`cd4cf3e0 00000000`00000000 ffff9b84`00000000 : nt!NtCallbackReturn+0x4

    ffffed89`20f31e40 00007ffa`8606c054 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28

    00000095`80f7f0e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`8606c054





    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt

    fffff805853f90c7 - nt!NtCallbackReturn+7

    [ 1c:1d ]

    1 error : !nt fffff805853f90c7



    MODULE_NAME: memory_corruption



    IMAGE_NAME: memory_corruption



    MEMORY_CORRUPTOR: ONE_BIT



    STACK_COMMAND: .thread ; .cxr ; kb



    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}



    Followup: memory_corruption


    THIS BSOD MINIDUMP BELOW WAS ON 1/21/2021 AT 3;22 AM



    Microsoft R Windows Debugger Version 10.0.19041.685 AMD64

    Copyright c Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\Windows\Minidump\012121-7078-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available



    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 19041 MP 8 procs Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Machine Name:

    Kernel base = 0xfffff805`10e00000 PsLoadedModuleList = 0xfffff805`11a2a2f0

    Debug session time: Thu Jan 21 03:31:56.604 2021 UTC - 6:00

    System Uptime: 0 days 2:48:31.288

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ................................................................

    .....

    Loading User Symbols

    Loading unloaded module list

    ...............

    For analysis of this file, run !analyze -v

    3: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************



    UNEXPECTED_KERNEL_MODE_TRAP_M 1000007f

    This means a trap occurred in kernel mode, and it's a trap of a kind

    that the kernel isn't allowed to have/catch bound trap or that

    is always instant death double fault. The first number in the

    bugcheck params is the number of the trap 8 = double fault, etc

    Consult an Intel x86 family manual to learn more about what these

    traps are. Here is a *portion* of those codes:

    If kv shows a taskGate

    use .tss on the part before the colon, then kv.

    Else if kv shows a trapframe

    use .trap on that value

    Else

    .trap on the appropriate frame will show where the trap was taken

    on x86, this will be the ebp that goes with the procedure KiTrap

    Endif

    kb will then show the corrected stack.

    Arguments:

    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT

    Arg2: ffffd701ce1f5e70

    Arg3: 0000000000000000

    Arg4: fffff805111fc98d



    Debugging Details:

    ------------------





    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.Sec

    Value: 3



    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on DESKTOP-INLR66U



    Key : Analysis.DebugData

    Value: CreateObject



    Key : Analysis.DebugModel

    Value: CreateObject



    Key : Analysis.Elapsed.Sec

    Value: 3



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 79



    Key : Analysis.System

    Value: CreateObject





    DUMP_FILE_ATTRIBUTES: 0x8

    Kernel Generated Triage Dump



    BUGCHECK_CODE: 7f



    BUGCHECK_P1: 8



    BUGCHECK_P2: ffffd701ce1f5e70



    BUGCHECK_P3: 0



    BUGCHECK_P4: fffff805111fc98d



    BAD_STACK_POINTER: 0000000000000000



    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXNTFS: 1 !blackboxntfs





    BLACKBOXPNP: 1 !blackboxpnp





    BLACKBOXWINLOGON: 1



    CUSTOMER_CRASH_COUNT: 1



    PROCESS_NAME: System



    STACK_TEXT:

    00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext+0x1ad





    SYMBOL_NAME: ANALYSIS_INCONCLUSIVE



    MODULE_NAME: Unknown_Module



    IMAGE_NAME: Unknown_Image



    STACK_COMMAND: .thread ; .cxr ; kb



    FAILURE_BUCKET_ID: INVALID_KERNEL_CONTEXT_0x7f_8



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {7dec4a1f-e7bf-6cb5-680a-3c5c14a52b06}



    Followup: MachineOwner

    ---------

    :)
     
    Omq111, Feb 4, 2021
    #1
  2. MARVICHIBAN
    MarvIchiban Win User

    BSOD on new computer while gaming

    I just got a new computer about a month ago. Everything is new and I get BSOD (windows 10) while gaming mostly although it sometimes happens while I'm just using the computer. Sometimes the computer doesn't BSOD and just gives me a Access Violation Error. Not sure if related.

    Here is the link to download output files from the V2 script.

    Dropbox - windows crash - Simplify your life

    Any help is appreciated

    Steps I have taken:
    • Updated all drivers and bios to latest versions
    • Checked ram with windows memory test to see if ram is faulty. (A stick was and it was removed waiting for replacement)
    • Clean Installed Windows after finding faulty ram
    • I had 2 x 2080Ti installed, I removed one, tested and then swapped cards; issue still exist
     
    MarvIchiban, Feb 4, 2021
    #2
  3. GHEOTIC
    Gheotic Win User
    Computer laggs and gives BSOD kernel_data_inpage_error

    My computer have been crashing more and more often the last half year. It have been giving me two different error messages.

    and

    This can happen at any time, no matter if I'm playing games or just surfing the internet. In the same time period my computer have been getting lots of lagg spikes, in most games that freeze the game for ½-2 second, and then return to good steady FPS. When it crash my mouse freezes for about 1-2 seconds before showing BSOD. First few times when this happened it asked me to use the windows installation disk to repair the system, all though it some how skipped that part before I got the chance to do that.

    My computer specs are:

    • Windows 10 Home 64-bit
    • Samsung SSD 840 EVO 250GB ( With operation system )
    • 1863GB Western Digital WDC WD20EZRX-00D8PB0
    • 2x DDR3-1600 DC - 8GB
    • Intel Core i5 4590
    • Nvidia Geforce GTX 970
    • EVGA SuperNOVA 750W G2

    What I've tried:

    • Running a Chkdsk test on both my HDD and SDD (No errors)
    • Checked ram with memory diagnostic tool (No errors)

    I've also benchmarked my "HD Tune Hard Disk Utility" giving these results:

    • Minimum: 25.5 MB/sec
    • Mamximum: 418.3 MB/sec
    • Average: 214.7 MB/sec
    • Access Time: 0.1ms
    • Burst Rate: 133.3 MB/sec
    • CPU Usage: 31.9%

    Also during an error scan it showed no errors at all.

    Any suggestions how to fix this problem?
     
    Gheotic, Feb 4, 2021
    #3
  4. PROTOTYPE464XBL
    Prototype464XBL Win User

    My computer keeps giving me a BSOD Please help!

    Computer keeps crashing and having BSoD.

    So I tried the driver verifier, my computer hasn't crashed yet. I did it step by step, and I'm understanding that I need to wait for my computer to crash so I can find out this devious little driver?

    Edit: My PC just crashed, but it doesn't give me a BSoD. It simply... Crashes.
     
    Prototype464XBL, Feb 4, 2021
    #4
Thema:

My computer keeps giving me a BSOD Please help!

Loading...

  1. My computer keeps giving me a BSOD Please help! - Similar Threads - computer keeps giving

  2. Help me with bsods please

    in Windows 10 Gaming
    Help me with bsods please: Lately i got bsod more and more often, at start it always was kernel thread priority floor violation code41 0x8000400000000002 appered only at power off/sleep mode. Did everything update driver, turned off all energy saving. Now i got bsod without any reason i just watched...

  3. Help me with bsods please

    in Windows 10 Software and Apps
    Help me with bsods please: Lately i got bsod more and more often, at start it always was kernel thread priority floor violation code41 0x8000400000000002 appered only at power off/sleep mode. Did everything update driver, turned off all energy saving. Now i got bsod without any reason i just watched...

  4. My PC keeps BSOD. Please help me!

    in Windows 10 Gaming
    My PC keeps BSOD. Please help me!: Hello my PC has been blue screening for about a month now it got so bad that I couldn't boot and had to fresh install windows. Even after the fresh windows install I'm getting the same BSOD two to three times a day. Usually IRQL NOT LESS OR EQUAL or MEMORY MANAGEMENT or...

  5. My PC keeps BSOD. Please help me!

    in Windows 10 Software and Apps
    My PC keeps BSOD. Please help me!: Hello my PC has been blue screening for about a month now it got so bad that I couldn't boot and had to fresh install windows. Even after the fresh windows install I'm getting the same BSOD two to three times a day. Usually IRQL NOT LESS OR EQUAL or MEMORY MANAGEMENT or...

  6. My PC keeps BSOD. Please help me!

    in Windows 10 BSOD Crashes and Debugging
    My PC keeps BSOD. Please help me!: Hello my PC has been blue screening for about a month now it got so bad that I couldn't boot and had to fresh install windows. Even after the fresh windows install I'm getting the same BSOD two to three times a day. Usually IRQL NOT LESS OR EQUAL or MEMORY MANAGEMENT or...

  7. Please help me with bsod

    in Windows 10 Software and Apps
    Please help me with bsod: Here's the minidump folder https://1drv.ms/u/s!AlmAwivwCKwWjVOMr9jsmJXAiQTR?e=5wHJ1RThe system often crashes along with some games especially games made with UE4 , and both report something like exception_unhandled, followed by a memory address-like hexadecimal code.On the...

  8. BSOD,please help me

    in Windows 10 Customization
    BSOD,please help me: https://drive.google.com/file/d/1FlihnSIuHbVlVIyjUXYDfzlJZlEFMaLs/view?usp=sharing tb755655493thanks a lot https://answers.microsoft.com/en-us/windows/forum/all/bsodplease-help-me/351d0e88-446f-47e7-b6a9-d26dc783eb1b

  9. Give me help, please

    in Windows 10 Ask Insider
    Give me help, please: I wanted to know if windows defender, after uninstalling the third party antivirus and rebooting the system, would return to how it was before the third party antivirus installation. I have this doubt. submitted by /u/davide016 [link] [comments]...

  10. My PC is giving me BSODs very frequently,please help me

    in Windows 10 BSOD Crashes and Debugging
    My PC is giving me BSODs very frequently,please help me: Hello, my PC started to giving me BSODs very frequently, here are the minidumps : http://www.mediafire.com/file/mjag8lgv7dzoyqc/Minidump.rar/file Please help me. Thanks in advance....