Serious BSOD issues

Status
Not open for further replies.
CapriAnupam said:
Don't be hasty in changing the CPU. If the problem is somewhere else, you will be unnecessary buying a CPU.
Click to expand...
Yes thats the reason I am desperately waiting for SMPS to come back, but i won't lie that i didn't had a temptation to go get a new Antec HCG750 or order online almost daily.
chetansha said:
One of us should invest in a basic cpu and keep foe standby purpose and share with genuine members who need a stop gap till they get a replacement
Click to expand...
I doubt this would work but if someone actually willing to do this then its a welcome move
I had all the components to build a new PC and yesterday I was talking to a member from my company and she told why not build another PC, I was like YES Components for 2 PC but none works lol
 
kartikoli said:
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)
Click to expand...
Try if you can borrow from someone else or do a memtest for the ram, but i don't think there will be any problem there.
kartikoli said:
Yes thats the reason I am desperately waiting for SMPS to come back, but i won't lie that i didn't had a temptation to go get a new Antec HCG750 or order online almost daily.

I doubt this would work but if someone actually willing to do this then its a welcome move
I had all the components to build a new PC and yesterday I was talking to a member from my company and she told why not build another PC, I was like YES Components for 2 PC but none works lol
Click to expand...
Test your current SMPS with a multimeter, so you can remove the doubt
 
panther said:
Try if you can borrow from someone else or do a memtest for the ram, but i don't think there will be any problem there.

Test your current SMPS with a multimeter, so you can remove the doubt
Click to expand...
I don't think RAMs will be faulty since I have 5 sticks to test also don't have multimeter to test SMPS
 
Well CPU is not bad .Its how bios is configured to use NVME so that windows can be installed and can be boot from it.

i hope you have a good copy of windows 10 ,secondly in your Bios setting make sure you have enabled AHCI for all the HDD and in boot options you have UEFI option checked if you use NVME as boot drive or use UEFi+ legacy


Disable Quick boot/Fast boot as well as secure boot if configured option in BIOS. nvidia does have a problem with this.

make following changes in power plan
1615671376648.png



chkdsk : drive letters /f /r on all the partitions with admin rights

If above doesn't help than do a clean install ,with minimum components .
CPU ,RAM,NVME SSD and gpu no other additional hdd .You can addon them later on

but prior to clean install , use your old hdd to scan all you storage for adware malware as memory related/ leak related issue occurs due to virus malware etc.

those IRQL`s indicate two HW issue mostly on driver side
 
Last edited:
  • Like
Reactions: CapriAnupam and Futureized
kartikoli said:
Windows installation have never been so stressful and it hurts personal pride saying i can install dam windows lol
Click to expand...
You : Installing windows is piece of cake for me.
Windows 10 : Hold my updates.

Try installing Linux on that ssd in same system. If it runs fine then you know its not hardware problem.
Also try Installing windows 10 with bare minimum hardware connected ( not even internet cable ).
 
  • Like
Reactions: Kaleen Bhaiya
truegenius said:
You : Installing windows is piece of cake for me.
Windows 10 : Hold my updates.

Try installing Linux on that ssd in same system. If it runs fine then you know its not hardware problem.
Also try Installing windows 10 with bare minimum hardware connected ( not even internet cable ).
Click to expand...
Lol so true :)
I had plans to work on installation today but turned out a Monday is more stressful than other working days
 
Last edited:
  • Like
Reactions: burntwingzZz
go to the bios and disable quick boot. and the maybe enable full ram test. also, try to capture more dumps. sometimes it doesn’t exactly say what failed.
 
Here is something which I faced,
I had BSOD issues with my Ryzen 2700X and Asus F-Gaming 470 MB. They were random. To fix, I had to run the RAM's at the voltages specified for the frequency in the XMP profile. You may want to check the "Auto" setting in the bios for voltage and run it on the voltage XMP profile mentions just for testing.
I have 4 Sticks running now, The issue was there when there were 2 sticks in it got very prominent when I added 2 more of same make model, Voltage bump fixed it.
 
  • Like
Reactions: vishalrao and booo
feedtaleten said:
Damm even I am having a similar kind of issue, I have searched all over the internet and even have posted on number of threads on different forum, no solution seems to work. I am really frustrated, can anyone of you here help me resolve this issue, I am very much tired now.
Click to expand...
start your own thread!
 
feedtaleten said:
Damm even I am having a similar kind of issue, I have searched all over the internet and even have posted on number of threads on different forum, no solution seems to work. I am really frustrated, can anyone of you here help me resolve this issue, I am very much tired now.
Click to expand...
For me I've changed almost everything and now ordered SMPS too so will work on installation during weekend and post the results here, you can check the suggestions in this thread also the steps I've taken to pin point the problem (still unsuccessful)
 
I am also having such BSOD problems and i dont know what to do even after updating all the drivers it happens.Windows 10 has been pretty bad for me.
 
Today got Antec HCG750 SMPS so tried to install fresh windows using minimum hardware
Processor+Mobo+NVME+SATA SSD (used SATA SSD to install windows)+Mouse+KB+USB WiFi dongle
After installation I got several BSOD but I've managed to update everything using MS update
Here are the logs from reports
==================================================
Dump File : 032221-14515-01.dmp
Crash Time : 23-03-2021 04:52:37
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff801`18e439ac
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f5a80
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+3f5a80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\032221-14515-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 19041
Dump File Size : 848,140
Dump File Time : 23-03-2021 04:53:23
==================================================
Dump File : 032221-13500-01.dmp
Crash Time : 23-03-2021 04:54:47
Bug Check String : APC_INDEX_MISMATCH
Bug Check Code : 0x00000001
Parameter 1 : 00007ffa`291ec804
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000001
Parameter 4 : ffff998f`48f95b80
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f5a80
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+3f5a80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\032221-13500-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 19041
Dump File Size : 1,304,052
Dump File Time : 23-03-2021 04:55:31
==================================================
Dump File : 032221-14171-01.dmp
Crash Time : 23-03-2021 05:02:43
Bug Check String : ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug Check Code : 0x000000be
Parameter 1 : fffff806`1e78411d
Parameter 2 : 09000004`3b58a121
Parameter 3 : ffffd78a`a8637450
Parameter 4 : 00000000`0000000a
Caused By Driver : amdppm.sys
Caused By Address : amdppm.sys+411d
File Description : Processor Device Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.18362.1049 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+3f5a80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\032221-14171-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 19041
Dump File Size : 847,924
Dump File Time : 23-03-2021 05:03:27
==================================================
Dump File : 032221-15281-01.dmp
Crash Time : 23-03-2021 05:05:09
Bug Check String :
Bug Check Code : 0x00000139
Parameter 1 : 00000000`00000003
Parameter 2 : ffffa505`50c457d0
Parameter 3 : ffffa505`50c45728
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f5a80
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+3f5a80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\032221-15281-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 19041
Dump File Size : 752,532
Dump File Time : 23-03-2021 05:05:55
==================================================
Dump File : 032221-13968-01.dmp
Crash Time : 23-03-2021 05:07:14
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : 00000000`00000001
Parameter 3 : 00000000`00000008
Parameter 4 : 00000000`00000001
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+1f9230
File Description : TCP/IP Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.18362.1377 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+3f5a80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\032221-13968-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 19041
Dump File Size : 863,012
Dump File Time : 23-03-2021 05:15:32
==================================================
Dump File : 032221-16187-01.dmp
Crash Time : 23-03-2021 05:18:36
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffcb80`1673f088
Parameter 2 : 00000000`00000000
Parameter 3 : fffff804`603fb22b
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f5a80
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+3f5a80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\032221-16187-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 19041
Dump File Size : 1,192,180
Dump File Time : 23-03-2021 05:19:23
==================================================
Dump File : 032221-15171-01.dmp
Crash Time : 23-03-2021 05:22:33
Bug Check String :
Bug Check Code : 0x00000162
Parameter 1 : ffff8581`b4710040
Parameter 2 : ffffe302`5fc9cd18
Parameter 3 : 00000000`ffffffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f5a80
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+3f5a80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\032221-15171-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 19041
Dump File Size : 960,076
Dump File Time : 23-03-2021 05:23:19
==================================================
 
ntoskrnl is crashing all the time. means windows kernel itself. in the past i saw this on my desktop while fiddling with ram xmp profiles. system became stable after disabling xmp profile totally and then was usable with xmp1 profile on my asus mobo.
are you overclocking ram?
 
Have you run full memtest? I suspect the RAM or RAM slot(s) to be faulty looking at the error messages. Other hardware fault also cannot be ruled out. Try booting with single stick of RAM and see if you face issues. Repeat the step with 2nd stick if you don't get any error. If you get error try using different RAM the slots.

Check the link below where one if your issues is listed.

 
GPMlore said:
Have you run full memtest? I suspect the RAM or RAM slot(s) to be faulty looking at the error messages. Other hardware fault also cannot be ruled out. Try booting with single stick of RAM and see if you face issues. Repeat the step with 2nd stick if you don't get any error. If you get error try using different RAM the slots.

Check the link below where one if your issues is listed.

Click to expand...
Sure I'll try with another stick and see if there is an error.

Didn't run any test as this is a new kit also the motherboard is new as well. Infact everything is new leaving processor/gpu which I bought second hand.
I can rule out motherboard slots issue as I've also tested same hardware with another Asrock b550 board and got errors, upto now I was thinking all these errors were due to SMPS but that's changed as well.
 
kartikoli said:
Sure I'll try with another stick and see if there is an error.

Didn't run any test as this is a new kit also the motherboard is new as well. Infact everything is new leaving processor/gpu which I bought second hand.
I can rule out motherboard slots issue as I've also tested same hardware with another Asrock b550 board and got errors, upto now I was thinking all these errors were due to SMPS but that's changed as well.
Click to expand...
I bet it's your memory. These all errors sound like memory related. Memtest86 would reveal your memory is indeed bad. Might wanna get it replaced from seller if it's new or RMA, upto you.
 
Status
Not open for further replies.
Top Bottom