Question BSOD on every boot, can't access to windows, software or hardware issue ?

May 23, 2022
13
1
15
0
Hello guys,
I started to have some BSOD, with some recurrent errors like "KMODE EXECEPTION NOT HANDLED" or "IRQL NOT LESS OR EQUAL".
One day I had a BSOD and I entered in the infinite loop of BSOD on boot everytime, I no longer had access to windows but still my BIOS. After trying a lot ot things like Mem Test, update all drivers when I still had access to Windows, make change in BIOS, clear CMOS etc, I thought the problem was MB.

So I bought an other one, mount pc, and boom, I booted on my windows like magic ( removing Intel Turbo Boost in bios because it causes crash since day 1 on my PC). So I started my life again, without doing a windows reinstall as if nothing had happened. But since today I have the same BSOD on my new MB: BSOD on boot.

It crash EVERY time I want to boot on something (my Windows 11, LIVE-USB Windows Repair, Windows automatic, I even tried something called Active Boot Disk)

I tried to boot only with ram and CPU, with all my disk unplugged ( 2SSD 2HDD) and ONLY a live usb and it still crashed.
I got a lot of "SYSTEM THREAD EXCEPTION NOT HANDLED' when I try to boot on live usb
Don't know if its hardware or maybe a malware.
I'm quite desesperate, if someone can help me it would be lovely <3



MY STUFF:

MAG B365M MORTAL (old MB was MPG Z390I Gaming Edge AC)
I7 9700k 3.60Ghz
2x8go DDR4 3000mhz CORSAIR CMK16GX4M2B3000C15 ( set at 2333mhz in BIOS)
GTX 1060ti 6gb
Corsair CX650
SSD 1 TO
SSD 1TO NVME
2HDD 1TO
 

USAFRet

Titan
Moderator
Mar 16, 2013
154,750
11,279
176,090
24,155
I thought the problem was MB.

So I bought an other one, mount pc, and boom, I booted on my windows like magic ( removing Intel Turbo Boost in bios because it causes crash since day 1 on my PC). So I started my life again, without doing a windows reinstall as if nothing had happened. But since today I have the same BSOD on my new MB: BSOD on boot.
New motherboard, a fresh OS install is indicated here.
 
May 23, 2022
13
1
15
0
Then that indicates a hardware issue.

Strip it down to bare essentials, and run a bootable memtest (if possible)

Already try the memtest when I still have access to Windows like a week ago, I did the test with my two RAMS plugged and i got 0 error
 

dwd999

Honorable
Already try the memtest when I still have access to Windows like a week ago, I did the test with my two RAMS plugged and i got 0 error
Is this all with the gpu removed and intel cpu providing graphics and the BIOS set to default settings? You could also try booting from a usb with a live linux distro and see if that gives you any clues as to whether the hardware is fully functional. At least with that you should have access to the bios. Since BSOD is a Windows function you may not have to deal with that when you temporarily boot from linux and explore your hardware. Also is your motherboard one of those that allows bios updating from within the bios tool menu? You could download the lastest bios onto the usb and if you can access the existing bios use the built in update function.
 
Reactions: nakatey
May 23, 2022
13
1
15
0
Is this all with the gpu removed and intel cpu providing graphics and the BIOS set to default settings? You could also try booting from a usb with a live linux distro and see if that gives you any clues as to whether the hardware is fully functional. At least with that you should have access to the bios. Since BSOD is a Windows function you may not have to deal with that when you temporarily boot from linux and explore your hardware. Also is your motherboard one of those that allows bios updating from within the bios tool menu? You could download the lastest bios onto the usb and if you can access the existing bios use the built in update function.
Yes today I made all my tries without gpu, only CPU and RAM. I'm currently making a memtest only with one ram.

Yes I can try a Linux distro, do uyou know one good for testing my hardware? o

And about my motherboard I will try to flash it on last update, but on my last MB I did it and I had BSOD again...
 

dwd999

Honorable
Yes today I made all my tries without gpu, only CPU and RAM. I'm currently making a memtest only with one ram.

Yes I can try a Linux distro, do uyou know one good for testing my hardware? o

And about my motherboard I will try to flash it on last update, but on my last MB I did it and I had BSOD again...
You could try LinuxMint Mate or Ubuntu Mate and see if those will boot. The Ubuntu 21.10 version is the most up to date.
 
May 23, 2022
13
1
15
0
UPDATE: I create a live usb LinuxMint and I boot on it with no problem. I have access to my SSD with Windows on it so I'll try to dig files to find some clues
 
Reactions: dwd999

dwd999

Honorable
UPDATE: I create a live usb LinuxMint and I boot on it with no problem. I have access to my SSD with Windows on it so I'll try to dig files to find some clues
After you're finished rescuing any essential files from your Windows ssd you can use the Gparted app included with Mint to delete all of the old partitions on the ssd and verify the GPT identifier. Then with all of the ssd space unallocated a reinstall of Windows might be more successful than past repair attempts. If successful then you can carefully rebuild your computer, first by adding back in the all the memory, then the GPU without any drivers, then the latest GPU drivers, then the other stuff. Hopefully you won't have any BSODs with a new install.
 
Reactions: Mandark
May 23, 2022
13
1
15
0
I found in my Windows folder a folder named LiveKernelReports with a dmp file named 'NDIS-20220518-1049'. I open the minidump file on my laptop, here's the result:


***
  • *
  • Bugcheck Analysis *
  • *
***

BUGCODE_NDIS_DRIVER_LIVE_DUMP (15e)
The operating system recovered from an error in a networking driver.
NDIS has detected and recovered from a serious problem in another network
driver. Although the system was not halted, this problem may later cause
connectivity problems or a fatal BugCheck.
Arguments:
Arg1: 0000000000000025, NDIS_BUGCHECK_WATCHDOG
An attempt to manage the network stack has taken too
long. When NDIS calls out into other drivers, NDIS
starts a watchdog timer to ensure the call completes
promptly. If the call takes too long, NDIS injects a
BugCheck.
This can be caused by a simple deadlock -- look with
"!stacks 2 ndis!" or similar to see if any threads
look suspicious. Pay special attention to the
PrimaryThread from the NDIS_WATCHDOG_TRIAGE_BLOCK.
This can be caused by lost NBLs, in which case
!ndiskd.pendingnbls may help. Check for OIDs that are
stuck using !ndiskd.oid.
Arg2: 0000000000000023, NDIS_BUGCHECK_WATCHDOG_MINIPORT_OID
There was a timeout while delivering an OID request to a
miniport adapter.
Arg3: ffffe50f446fc418, Cast to ndis!_NDIS_WATCHDOG_TRIAGE_BLOCK. Interesting fields:
* StartTime shows what time the operation started,
in 100ns units, as returned by KeQueryInterruptTime.
* TimeoutMilliseconds shows how long NDIS waited, at a
minimum, before triggering this BugCheck.
Measured in milliseconds.
* TargetObject is a handle to the protocol, filter,
or miniport that NDIS is waiting on. Use with
!ndiskd.protocol, !ndiskd.filter, or !ndiskd.miniport.
* PrimaryThread is the thread on which NDIS initiated
the operation. Usually this is the first place to
look, although the thread may have gone elsewhere
if the operation is being handled asynchronously.
Arg4: 000000000101010a, The OID code of the stuck request. Use !ndiskd.help
or look in a header file to decode it.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 7358

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 22311

Key : Analysis.Init.CPU.mSec
Value: 6546

Key : Analysis.Init.Elapsed.mSec
Value: 50671

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

Key : Bugcheck.DumpVsMemoryMatch
Value: False

Key : Dump.Attributes.AsUlong
Value: 10

Key : WER.OS.Branch
Value: rs_prerelease

Key : WER.OS.Timestamp
Value: 2022-05-06T14:10:00Z

Key : WER.OS.Version
Value: 10.0.25115.1000


FILE_IN_CAB: NDIS-20220518-1049.dmp

DUMP_FILE_ATTRIBUTES: 0x10
Live Generated Dump

BUGCHECK_CODE: 15e

BUGCHECK_P1: 25

BUGCHECK_P2: 23

BUGCHECK_P3: ffffe50f446fc418

BUGCHECK_P4: 101010a

MODULE_NAME: wdiwifi

PROCESS_NAME: System

STACK_TEXT:
fffffd07fb8a7120 fffff80408c8a013 : 0000000000000000 fffffd07fb8a71f0 0000000000000000 0000000000000000 : nt!IopLiveDumpCollectPages+0xd9
fffffd07fb8a7170 fffff80408c9b5af : ffffffffffffffff ffffffffffffffff fffffd07fb8a71f0 0000000000000000 : nt!IopLiveDumpEndMirroringCallback+0x33
fffffd07fb8a71a0 fffff80408b4bc68 : 0000000000000000 0000000000000000 ffffe50f54de0890 fffffd07fb8a7390 : nt!MmDuplicateMemory+0x2ff
fffffd07fb8a7230 fffff80408c897f7 : ffffe50f0000000b fffffd07000120ad 000000000004b400 0000000001000000 : nt!IopLiveDumpCapture+0x78
fffffd07fb8a7290 fffff80408b49c89 : ffffe50f54de0890 ffffe50f54de0890 ffff9506bd2d3458 0000000000000000 : nt!IopLiveDumpCaptureMemoryPages+0x4b
fffffd07fb8a73d0 fffff80408b3a2e6 : 0000000000000000 ffff9506bd2d3440 ffff9506adf06c60 ffff9506adf06c60 : nt!IoCaptureLiveDump+0x3e1
fffffd07fb8a7610 fffff80408b3a8d8 : 0000000000000025 0000000000000000 0000000000000000 0000000000000000 : nt!DbgkpWerCaptureLiveFullDump+0x17e
fffffd07fb8a7680 fffff80408ae24c6 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!DbgkpWerProcessPolicyResult+0x30
fffffd07fb8a76b0 fffff80408a12be9 : ffffe50f4c2661a0 0000000000000038 0000000000000023 0000000000000000 : nt!DbgkWerCaptureLiveKernelDump2+0xcf8c6
fffffd07fb8a7710 fffff8040d18b099 : 0000000000000000 ffffe50f45570af0 0000000000000000 ffffe50f45570040 : nt!DbgkWerCaptureLiveKernelDump+0x69
fffffd07fb8a7790 fffff8040d26780a : fffffd07fb8a7850 fffff8040d2455f7 ffffe50f561cff40 0000000000000000 : ndis!ndisMLiveBugCheck+0x49
fffffd07fb8a77f0 fffff8040d2676a1 : 0000000000000000 ffffe50f42f3fe20 fffff8040d224c58 0000000000000000 : ndis!ndisReportTimeoutWaitingForExternalDriver+0xf6
fffffd07fb8a7830 fffff8040d267538 : ffffe50f561cfec0 ffffe50f561cff88 ffffe50f561cff40 0000000000000c00 : ndis!ndisFindSomeoneToBlame+0x111
fffffd07fb8a78a0 fffff8040d267969 : 0000000000000000 fffff80408f68b40 ffffe50f41f20c30 fffff80408e37f20 : ndis!NdisWatchdogState::ReportTimeout+0x68
fffffd07fb8a78d0 fffff80408571c45 : ffffe50f41f20c30 ffffe50f41f20c00 ffffe50f00000000 ffffe50f00000000 : ndis!ndisWatchdogTimeoutWorkerRoutine+0x9
fffffd07fb8a7900 fffff80408576817 : ffffe50f45570040 ffffac805d745180 ffffe50f45570040 fffff8056271ea80 : nt!ExpWorkerThread+0x155
fffffd07fb8a7af0 fffff80408635554 : ffffac805d745180 ffffe50f45570040 fffff804085767c0 0000000000000000 : nt!PspSystemThreadStartup+0x57
fffffd07fb8a7b40 0000000000000000 : fffffd07fb8a8000 fffffd07fb8a1000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME: wdiwifi!MPWrapperOidRequest+0

IMAGE_NAME: wdiwifi.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 0

FAILURE_BUCKET_ID: LKD_0x15E_MINI_StuckOID_101010A_wdiwifi!MPWrapperOidRequest

OS_VERSION: 10.0.25115.1000

BUILDLAB_STR: rs_prerelease

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {08946291-b108-d937-19b1-4c7a1138ac0b}

Followup: MachineOwner
---------
 
May 23, 2022
13
1
15
0
4: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common BugCheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff804663a26f7, The address that the exception occurred at
Arg3: ffff8d82952f72f8, Exception Record Address
Arg4: ffff8d82952f6b10, Context Record Address

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 7577

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 28020

Key : Analysis.Init.CPU.mSec
Value: 1233

Key : Analysis.Init.Elapsed.mSec
Value: 2869

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

Key : Bugcheck.DumpVsMemoryMatch
Value: False

Key : WER.OS.Branch
Value: rs_prerelease

Key : WER.OS.Timestamp
Value: 2022-05-06T14:10:00Z

Key : WER.OS.Version
Value: 10.0.25115.1000


FILE_IN_CAB: 052322-10140-01.dmp

BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc000001d

BUGCHECK_P2: fffff804663a26f7

BUGCHECK_P3: ffff8d82952f72f8

BUGCHECK_P4: ffff8d82952f6b10

EXCEPTION_RECORD: ffff8d82952f72f8 -- (.exr 0xffff8d82952f72f8)
ExceptionAddress: fffff804663a26f7 (vgk+0x00000000007326f7)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT: ffff8d82952f6b10 -- (.cxr 0xffff8d82952f6b10)
rax=ffff8d82952f7670 rbx=ffffffffffe5253d rcx=0000000000000001
rdx=0000000000000001 rsi=fffff80465d8bf31 rdi=fffff804663a26f7
rip=fffff804663a26f7 rsp=ffff8d82952f7530 rbp=ffff8d82952f7730
r8=0000000000044f37 r9=0000000000014be5 r10=0000000000000000
r11=fffffffffffe8d31 r12=0000000000000001 r13=fffff80465c7832c
r14=0000000000000008 r15=fffff80465c70000
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206
vgk+0x7326f7:
fffff804663a26f7 c5 ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Instruction non autoris e Tentative d ex cution d une instruction interdite.

EXCEPTION_CODE_STR: c000001d

MISALIGNED_IP:
vgk+7326f7
fffff804
663a26f7 c5 ???

EXCEPTION_STR: 0xc000001d

FAILED_INSTRUCTION_ADDRESS:
vgk+7326f7
fffff804663a26f7 c5 ???

STACK_TEXT:
ffff8d82
952f7530 0000000000000001 : 0000000e99224746 0000000000040282 ffffbb8bf1729de8 0000000000040202 : vgk+0x7326f7
ffff8d82
952f7538 0000000e99224746 : 0000000000040282 ffffbb8bf1729de8 0000000000040202 0000000000040286 : 0x1
ffff8d82
952f7540 0000000000040282 : ffffbb8bf1729de8 0000000000040202 0000000000040286 0000000000040246 : 0x0000000e99224746
ffff8d82952f7548 ffffbb8bf1729de8 : 0000000000040202 0000000000040286 0000000000040246 0000000000000001 : 0x40282
ffff8d82952f7550 0000000000040202 : 0000000000040286 0000000000040246 0000000000000001 0000000000000000 : 0xffffbb8bf1729de8
ffff8d82
952f7558 0000000000040286 : 0000000000040246 0000000000000001 0000000000000000 fffff80465c70000 : 0x40202
ffff8d82
952f7560 0000000000040246 : 0000000000000001 0000000000000000 fffff80465c70000 fffff80325c70000 : 0x40286
ffff8d82
952f7568 0000000000000001 : 0000000000000000 fffff80465c70000 fffff80325c70000 fffff80466054771 : 0x40246
ffff8d82
952f7570 0000000000000000 : fffff80465c70000 fffff80325c70000 fffff80466054771 00000000`00000008 : 0x1


SYMBOL_NAME: vgk+7326f7

STACK_COMMAND: .cxr 0xffff8d82952f6b10 ; kb

MODULE_NAME: hardware

IMAGE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED_vgk.sys

OS_VERSION: 10.0.25115.1000

BUILDLAB_STR: rs_prerelease

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c38582a8-fb68-6d00-6996-ec0ba0c44355}

Followup: MachineOwner
 
May 23, 2022
13
1
15
0
4: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000002, Stack cookie instrumentation code detected a stack-based
buffer overrun.
Arg2: fffffb09cb28e7c0, Address of the trap frame for the exception that caused the BugCheck
Arg3: fffffb09cb28e718, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4999

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 8724

Key : Analysis.Init.CPU.mSec
Value: 827

Key : Analysis.Init.Elapsed.mSec
Value: 6704

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

Key : Bugcheck.DumpVsMemoryMatch
Value: True

Key : FailFast.Name
Value: STACK_COOKIE_CHECK_FAILURE

Key : FailFast.Type
Value: 2

Key : WER.OS.Branch
Value: rs_prerelease

Key : WER.OS.Timestamp
Value: 2022-05-06T14:10:00Z

Key : WER.OS.Version
Value: 10.0.25115.1000


FILE_IN_CAB: 052322-6546-01.dmp

BUGCHECK_CODE: 139

BUGCHECK_P1: 2

BUGCHECK_P2: fffffb09cb28e7c0

BUGCHECK_P3: fffffb09cb28e718

BUGCHECK_P4: 0

TRAP_FRAME: fffffb09cb28e7c0 -- (.trap 0xfffffb09cb28e7c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000c0000016 rbx=0000000000000000 rcx=0000000000000002
rdx=ffff988f53419980 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8067adafcd5 rsp=fffffb09cb28e950 rbp=fffffb09cb28ea50
r8=000000000000038a r9=ffff988f53419848 r10=fffff806768989a0
r11=ffff988f5450ebd0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac pe cy
CLASSPNP!_report_gsfailure+0x5:
fffff8067adafcd5 cd29 int 29h
Resetting default scope

EXCEPTION_RECORD: fffffb09cb28e718 -- (.exr 0xfffffb09cb28e718)
ExceptionAddress: fffff8067adafcd5 (CLASSPNP!_report_gsfailure+0x0000000000000005)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000002
Subcode: 0x2 FAST_FAIL_STACK_COOKIE_CHECK_FAILURE

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

ERROR_CODE: (NTSTATUS) 0xc0000409 - Le syst me a d tect la saturation de la m moire tampon dans cette application. Cette saturation pourrait permettre un utilisateur mal intentionn de prendre le contr le de cette application.

EXCEPTION_CODE_STR: c0000409

EXCEPTION_PARAMETER1: 0000000000000002

EXCEPTION_STR: 0xc0000409

STACK_TEXT:
fffffb09
cb28e498 fffff80676a444a9 : 0000000000000139 0000000000000002 fffffb09cb28e7c0 fffffb09cb28e718 : nt!KeBugCheckEx
fffffb09
cb28e4a0 fffff80676a448f2 : ffffa7b265de2021 00000012965813ba 0000000000000002 fffffb09d06b6870 : nt!KiBugCheckDispatch+0x69
fffffb09
cb28e5e0 fffff80676a42b7a : ffff988f5c966440 0000000000000000 ffff988f53419000 ffff988f5c966010 : nt!KiFastFailDispatch+0xb2
fffffb09
cb28e7c0 fffff8067adafcd5 : fffff8067ada6fa2 ffff988f5450ebc0 fffffb09cb28ea50 ffff988f5450ebc0 : nt!KiRaiseSecurityCheckFailure+0x33a
fffffb09
cb28e950 fffff8067ada6fa2 : ffff988f5450ebc0 fffffb09cb28ea50 ffff988f5450ebc0 ffff988f5450ebc0 : CLASSPNP!_report_gsfailure+0x5
fffffb09
cb28e958 ffff988f67ec3203 : ffff988f67ec3010 ffff988f66a08080 ffffc0810b662100 0000000000000000 : CLASSPNP!TransferPktComplete+0x6e2
fffffb09
cb28eb28 ffff988f67ec3010 : ffff988f66a08080 ffffc0810b662100 0000000000000000 00000005cb28ee90 : 0xffff988f67ec3203
fffffb09cb28eb30 ffff988f66a08080 : ffffc0810b662100 0000000000000000 00000005cb28ee90 0000000000000005 : 0xffff988f67ec3010
fffffb09
cb28eb38 ffffc0810b662100 : 0000000000000000 00000005cb28ee90 0000000000000005 fffffb09cb28ef40 : 0xffff988f66a08080
fffffb09cb28eb40 0000000000000000 : 00000005cb28ee90 0000000000000005 fffffb09cb28ef40 0000000000000000 : 0xffffc081`0b662100


SYMBOL_NAME: CLASSPNP!_report_gsfailure+5

MODULE_NAME: CLASSPNP

IMAGE_NAME: CLASSPNP.SYS

IMAGE_VERSION: 10.0.25122.1000

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 5

FAILURE_BUCKET_ID: 0x139_MISSING_GSFRAME_CLASSPNP!_report_gsfailure

OS_VERSION: 10.0.25115.1000

BUILDLAB_STR: rs_prerelease

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {9b93f83c-0dc4-8fee-436a-2041488f57b3}

Followup: MachineOwner
---------
 
May 23, 2022
13
1
15
0
After you're finished rescuing any essential files from your Windows ssd you can use the Gparted app included with Mint to delete all of the old partitions on the ssd and verify the GPT identifier. Then with all of the ssd space unallocated a reinstall of Windows might be more successful than past repair attempts. If successful then you can carefully rebuild your computer, first by adding back in the all the memory, then the GPU without any drivers, then the latest GPU drivers, then the other stuff. Hopefully you won't have any BSODs with a new install.
it seems I can't delete one of the partition, the largest one named 'basic data protection'

EDIT: I can now interact with it after "unmount" it. My question now is do I need to "Delete" or to "Format to" partitions
 
Last edited:

dwd999

Honorable
it seems I can't delete one of the partition, the largest one named 'basic data protection'

EDIT: I can now interact with it after "unmount" it. My question now is do I need to "Delete" or to "Format to" partitions
All of the partitions should be deleted so that the drive shows all of its space as unallocated. When you reinstall windows the installer will handle all of the creating and formatting new partitions.
 
May 23, 2022
13
1
15
0
All of the partitions should be deleted so that the drive shows all of its space as unallocated. When you reinstall windows the installer will handle all of the creating and formatting new partitions.
I tryied to boot on Live usb windows 10 installation with all my hard-drive unplugged and I still had windows BDOS when I boot on it. Do you think erase my ssd partitions can resolve this issue ?

Why I have BSOD error when my ssd with the Os on it is unplugged (Electricity + Sata)
 

dwd999

Honorable
I tryied to boot on Live usb windows 10 installation with all my hard-drive unplugged and I still had windows BDOS when I boot on it. Do you think erase my ssd partitions can resolve this issue ?

Why I have BSOD error when my ssd with the Os on it is unplugged (Electricity + Sata)
Since you said that the linux usb booted and ran fine then the windows 10 install usb is most likely defective. If would be best if you used the media creation tool to create a new install usb and also check that your computer's bios settings are set to their default values.
 

ASK THE COMMUNITY