Windows 11 ntoskrnl.exe BSODs will not stop, even with new hardware

  • Thread starter Thread starter Jason Varni
  • Start date Start date
J

Jason Varni

A couple months ago, I started getting persistent BSODs, all linking back to driver and memory errors. At the time, my PC could stand a fresh install of Windows, so I just went ahead and did a full reset. The BSODs were so persistent and constant, it took nearly 10 tries to get Windows installed. With a fresh install, the BSODs continued. They were mostly random, happening both during idle and active states, but I figured out that trying to install the MSI Control Panel app would cause a crash, so I started forcing crashes and checking BlueScreenView. Every error linked back to ntoskrnl.exe. S

Continue reading...
 
You must log in or register to reply here.

Similar threads

D
Windows 11 Multiple BSODs for different reasons
Replies
0
Views
10
Dylan Van Der Westhuizen
D
I
Windows 10 Persistent unknown cause of BSODs "IRQL NOT EQUAL" and "KMODE EXCEPTION"
Replies
0
Views
27
IRQL Not Equal KMODE nightmare
I
T
Windows 10 Constant BSOD, even after new Windows 10 install
Replies
0
Views
5
Timde Boer1
T
T
Windows 10 Constant BSODs - Minidump Analysis Help Please! - storport.sys, PSHED.dll, ntoskrnl.exe.
Replies
0
Views
13
TimRaynor
T
T
Windows 10 Constant BSOD, also after new Windows 10 install. Tried Driver Verifier. Can someone help with Debug?
Replies
0
Views
4
Timde Boer1
T
Back
Top