PC crashes on Windows 10/11 but not on Linux Mint

[Scrooloose]

I am not at my PC right now, but i did find some minidump files that i previously uploaded, would this be of any help?

Minidumps.zip

Compressed (zipped) Folder

1drv.ms

You need to run the tool yourself if you're going to learn how to troubleshoot stuff my dude.

 

[LordVoldetort_IV]

Driver Booster 11 Free: Official Free Driver Updater Tool for Windows 2023

The best free driver updater for Windows 11/10. Fully detect and update all your old drivers for graphics, USB, audio, display, network, printer, mouse, keyboard and scanner. Free check driver updates now.

www.iobit.com

after fresh windows install
Install Booster.
Update GPU drivers - if you have on board GFX do the above first without GPU installed and with 1 Dimm

GG WP - fact that you said its your first pc...........***...***.......

Yeah honestly not the greatest start to my PC experience😅 But, i am learning a lot and i am determined to get it sorted out

I'll try the above, thank you!

 

[LordVoldetort_IV]

You need to run the tool yourself if you're going to learn how to troubleshoot stuff my dude.

I have used that tool before, also Windbg, and whocrashed... but you see, it does not point to a specific driver, just to the kernel or NT (i think thats the kernel?)

I dont have enough experience to make sense of what the tool shows and so it does not help me too much

 

[LordVoldetort_IV]

I have used that tool before, also Windbg, and whocrashed... but you see, it does not point to a specific driver, just to the kernel or NT (i think thats the kernel?)

I dont have enough experience to make sense of what the tool shows and so it does not help me too much

As i understand, something is pushing the Kernel into fault, but it cannot determine from the dump files exactly *what* is pushing it into fault

 

[Scrooloose]

As i understand, something is pushing the Kernel into fault, but it cannot determine from the dump files exactly *what* is pushing it into fault

The useful error code that I asked for was this, which I got from your minidump files.

0x0000000A: IRQL_NOT_LESS_OR_EQUAL

This error almost always occurs when something asks the Windows kernel to write data to a read-only memory register. That something that can only be caused by a Windows bug or a developer-initiated instruction by way of drivers.
Where I see this rather often is when old drivers are used on more modern Operating Systems. Stuff like a Windows 10 driver written for the original release that gets loaded onto a 1909 build for example.

Other frequent causes include mismatched memory modules, incompatible memory modules (such as sticking non-certified modules into a Dell), outdated BIOS or overclock settings that are improperly configured.

I would start with the memory, make sure that the DIMMs are listed in your motherboard's supported hardware list. Then I'll move to ensuring that the modules are the same speed.

Next would be BIOS update, and ensuring that the BIOS configs match the CPU and Memory speeds exactly.

From there it's a clean install. Do one driver at a time, and reboot. You'll quickly find which driver is crashing your system.

 

[LordVoldetort_IV]

The useful error code that I asked for was this, which I got from your minidump files.

0x0000000A: IRQL_NOT_LESS_OR_EQUAL

This error almost always occurs when something asks the Windows kernel to write data to a read-only memory register. That something that can only be caused by a Windows bug or a developer-initiated instruction by way of drivers.
Where I see this rather often is when old drivers are used on more modern Operating Systems. Stuff like a Windows 10 driver written for the original release that gets loaded onto a 1909 build for example.

Other frequent causes include mismatched memory modules, incompatible memory modules (such as sticking non-certified modules into a Dell), outdated BIOS or overclock settings that are improperly configured.

I would start with the memory, make sure that the DIMMs are listed in your motherboard's supported hardware list. Then I'll move to ensuring that the modules are the same speed.

Next would be BIOS update, and ensuring that the BIOS configs match the CPU and Memory speeds exactly.

From there it's a clean install. Do one driver at a time, and reboot. You'll quickly find which driver is crashing your system.

Okay, I'll have a look at this, thank you!

 

[LordVoldetort_IV]

Driver Booster 11 Free: Official Free Driver Updater Tool for Windows 2023

The best free driver updater for Windows 11/10. Fully detect and update all your old drivers for graphics, USB, audio, display, network, printer, mouse, keyboard and scanner. Free check driver updates now.

www.iobit.com

after fresh windows install
Install Booster.
Update GPU drivers - if you have on board GFX do the above first without GPU installed and with 1 Dimm

GG WP - fact that you said its your first pc...........***...***.......

Okay i have an update!

so over the weekend i installed windows again and sure enough had another IRQL_NOT_LESS_OR_EQUAL BSOD... same as before...

So, i decided to debug it for clues without much hope since all previous times it said ntoskrnl.exe was the problem but could not see what pushed it to fault.. HOWEVER, this time it actually did name the driver!!! 😁

it was intelppm.sys so i did some research online and found a thread saying to edit something in the registry of this driver from 3 to 4 (I'll add a link to the thread below) and since ive done this on Saturday at round about 8pm, i have not had a crash since (used to be no less than 5 per day)

Now, i obviously need to test it further and longer, but the prelim results are promising!

link: Fix intelppm.sys Blue Screen error on Windows 11/10

 

[LordVoldetort_IV]

Okay i have an update!

so over the weekend i installed windows again and sure enough had another IRQL_NOT_LESS_OR_EQUAL BSOD... same as before...

So, i decided to debug it for clues without much hope since all previous times it said ntoskrnl.exe was the problem but could not see what pushed it to fault.. HOWEVER, this time it actually did name the driver!!! 😁

it was intelppm.sys so i did some research online and found a thread saying to edit something in the registry of this driver from 3 to 4 (I'll add a link to the thread below) and since ive done this on Saturday at round about 8pm, i have not had a crash since (used to be no less than 5 per day)

Now, i obviously need to test it further and longer, but the prelim results are promising!

link: Fix intelppm.sys Blue Screen error on Windows 11/10

Tested again yesterday for around 3-4 hours, so far so good

 

[LordVoldetort_IV]

Tested again yesterday for around 3-4 hours, so far so good

Yep, no issues so far, it seems the problem is resolved🙌