Windows 10: Trying to investigate a Blue Screen, crashes when trying log to onto my windows user

Hi.I'm trying to fix a blue screen of death, i can't log onto my user on Windows 11 i get the BSoD.The stopcode is: DRIVER_IRQL_NOT_LESS_OR_EQUAL.When checking the Minidump file in no fail mode, it was an issue from ntoskrnl.exe and rtf64x64.sys, but i don't know how to fix thoses files.My config:CPU: Intel Core i5-10400RAM: G.Skill 8GB 2x4GB 2666MhzPSU: Corsair TX-650MGPU: Gigabyte GeForce RTX 3060 Eagle 12GBNetwork card WiFi-BT: Some Aorus thingMotherboard: Gigabyte B560M DS3H Ultra DurableIf you need more information, you can ask me.Thanks in advance for your answers :

:)

 

Trying to diagnose random blue screens

This is a Windows 10 Professional desktop, built seven years ago. It is starting to fail, with almost daily blue screens, and I'm trying to guess what part is failing. The candiates are naturally the motherboard, a RAM stick, or a video card.

The errors are almost always different, and there is almost never a culprit announced. Here are some examples:

• MEMORY_MMANAGEMENT
  
• IRQL_NOT_LESS_OR_EQUAL
  
• SYSTEM_SERVICE_EXCEPTION
  
• KMODE_EXCEPTION_NOT_HANDLED (mcdbus.sys)
  
• SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
  

Eventually I will have to start removing all parts one by one, but I was wondering if these errors might suggest which part to check first.

 

Crash/blue screen

Hi

I assume from the title of your post Crash/Blue Screen that the PC has crashed and produced a *BSOD=[Blue Screen Of Death] =Blue Screen; and that the PC recovered from this; if and when you see the Blue Screen write the Stop Code down; recover the PC or use one that is working to access the net and look up the Stop Code.

nb: You may be able to view this with a [*BlueScreenView] application, google for this.

Edit Link - Blue screen of death (STOP error) information in dump files.

Description
===========

BlueScreenView scans all your minidump files created during 'blue screen
of death' crashes, and displays the information about all crashes in one
table. For each crash, BlueScreenView displays the minidump filename, the
date/time of the crash, the basic crash information displayed in the blue
screen (Bug Check Code and 4 parameters), and the details of the driver
or module that possibly caused the crash (filename, product name, file
description, and file version).
For each crash displayed in the upper pane, you can view the details of
the device drivers loaded during the crash in the lower pane.
BlueScreenView also mark the drivers that their addresses found in the
crash stack, so you can easily locate the suspected drivers that possibly
caused the crash.

atb

Law-II

 

Blue screen trying to run the Bitlocker recovery mode

Hey there,

Thank you for using our Microsoft Community.

Bitlocker is not recommended for dual systems (especially non-primary systems) because the encryption will fail as it will interact with each other during the reboot encryption phase, causing the encryption to not complete all the way. We could first analyze the cause of the blue screen through the blue screen log. You can collect the log of your computer by the following steps:

Please check if there are .dmp files in the C:\Windows\Minidump directory.

• If so, package these files, upload them to OneDrive, and share them, and then include a link to share them in the next reply. Since these files detail exactly what happened when your system crashed, this helps us resolve your issue.
  
• If not, run the following command to try to enable it. Win logo key + Q, open the search box, type "cmd", then right-click Command Prompt, select Run as administrator), and then type the following command.
  

wmic recoveros set DebugInfoType=3

This is to enable blue screen logging. You need to try to access the C:\Windows\Minidump directory to see if there are .dmp files after the next blue screen appears.

Thank you for your time and effort working on this issue. If there are any updates or changes, please do not hesitate to let me know.

Have a nice day and stay safe!

Best regards,

| Microsoft Community Support Specialist