Serious BSOD issues

Status
Not open for further replies.
nRiTeCh said:
Dude, try latest iso from windows site.
In bios, memory controllers option, set it all to default esp. manual settings.
Also, try on a single stick only.
I will even say try it on a blank hdd or sdd initially to rule out issues stepwise..
Click to expand...
Yes it's the latest version on MS site I've also tried 1909.
While installing windows only SSD is connected so no other HD have anything to do with it, do you think I should remove wifi/bluetooth dongle as well?
Will try to work with single stick now also check memory controller options in BIOS

This is my main job PC so in order to be online and be productive I've to switch windows and work from old installed OS and as I get some free time, remove all HD and start trying again

Do you think that it might be SMPS which is at fault because what I see is I've changed everything but SMPS so this might be the case? I am excluding hardware that are new or brought from someone that worked well for them, not to mention all those work for me when I use OS from Seagate hard disk.
 
kartikoli said:
It is but I can't keep my PC off for even few hours so have to buy a new processor first then start with RMA process, that's the reason I want to try this at the end
Click to expand...
did you analyze the dump files as a step 1 before freaking out about processor and hardware?
 
booo said:
did you analyze the dump files as a step 1 before freaking out about processor and hardware?
Click to expand...
Not yet, can this be done using my other OS since this is stable and doing anything while booting from SSD is almost imposible due to restarts
 
You can copy the dump files to your other hard drive which has the other OS and open them with BlueScreenView to analyze them.

And yes, no need to worry until you find the culprit hardware or driver.
panther said:
It is the CPU get a new one from AMD
Click to expand...
Reason for saying so?
 
kartikoli said:
OMG I just checked Windows\Minidump\ and the folder is empty
Click to expand...
www.faqforge.com

How to Enable Minidump Logs in Windows 10

BSOD (Blue Screen of Death) is one of the worst errors in Windows. BSOD (Blue Screen of Death) error is that error which occurs after system error or
www.faqforge.com www.faqforge.com

tldr; win+pause/break->advanced settings->startup recovery->uncheck automatic restart and specify dump file location and blah...
i am getting old and seems you cant download standalone windbg without ddk so .... maybe use this https://www.microsoft.com/en-us/p/windbg/9pgjgd53tn86?rtc=1&activetab=pivot:overviewtab
 
Last edited:
  • Like
Reactions: kartikoli
==================================================
Dump File : 031321-2968-01.dmp
Crash Time : 13-03-2021 16:33:21
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000240
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff802`3d65900a
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f5210
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.18362.1440 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+3f5210
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\031321-2968-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 19041
Dump File Size : 799,804
Dump File Time : 13-03-2021 16:33:51
==================================================
This is the latest error report, I've installed totally new windows and as expected it crashed giving this error
 
CapriAnupam said:
You can copy the dump files to your other hard drive which has the other OS and open them with BlueScreenView to analyze them.

And yes, no need to worry until you find the culprit hardware or driver.

Reason for saying so?
Click to expand...
I have gone through it and have a first hand experience, Different BSOD error are a definitive Sign of CPU gone Bad.
 
Let's hope it is not as serious as that.

IRQL_NOT_LESS_OR_EQUAL can occur for a number of reasons... one of them being CPU overheating. So, OP can check for that, apart from other hardware like RAM.

Can also be because of antivirus software.

Or, the file system might be corrupt. Can run scan for that with SFC /scannow command.

OP has to work to find out the culprit behind the error.

Check the dump file with BlueScreenView too and see which driver/file it points to.
 
I will buy another CPU but before doing that I want to try one more option, Changing PSU because this is the only part of hardware I haven't changed (waiting for my RM1000 to come back from RMA)
 
Status
Not open for further replies.
Top Bottom