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

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

Jason Varni

Guest
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

S
Extremely difficult Windows BSODs caused by "ntoskrnl.exe"
Replies
0
Views
3
saltcruise
S
S
Extremely difficult Windows BSODs caused by "ntoskrnl.exe"
Replies
0
Views
5
saltcruise
S
I
Persistent unknown cause of BSODs "IRQL NOT EQUAL" and "KMODE EXCEPTION"
Replies
0
Views
9
IRQL Not Equal KMODE nightmare
I
K
Various BSODs with error driver code as ntoskrnl.exe. Unsure how to fix
Replies
0
Views
8
KingCosmicNick
K
A
Driver Power State Failure BSODs
Replies
0
Views
13
Adam13377
A
Back
Top