Serious BSOD issues

Status
Not open for further replies.
kartikoli said:
The same set of hardware works perfectly fine when i use my other HD where as all these errors pop up when i try new SSD (NVMe or SATA), I am working on the same PC with same CPU and RAMs since morning and no crashes what so ever. Now that makes me believe that it might be Windows thats causing those errors but at this point in time I i just don't know whats the problem :banghead:
Click to expand...

This is only pointing to 1 direction - the memory controller issue is either on the board side or cpu since when you provide your system with high I/O ssd or nvme it’s crashing. Try changing the board or cpu once
 
  • Like
Reactions: kartikoli and GPMlore
nishthecooldude said:
This is only pointing to 1 direction - the memory controller issue is either on the board side or cpu since when you provide your system with high I/O ssd or nvme it’s crashing. Try changing the board or cpu once
Click to expand...
I am thinking the same since OP is pointing towards issue when using NVME / SSD. @kartikoli , could you try using the SSD and NVME on another system and check for issues?
 
  • Like
Reactions: kartikoli
To me, it seems like the problem might be with the drivers of hardware on this system. Since Windows was installed on another system, the drivers installed for components on that system will be different from the drivers required for the components of this system. That's why multiple crashes. Well, that's my guess... I could be wrong, but logically, it can be a reason.

About Windows not being able to install on the current system, is that maybe one of the hardware won't be agreeing with Windows 10, or again, some driver issue for one of the components.

You should try BlueScreenView to check the dump files, since it will point to the faulty driver file, by which you can search and identify the problem.

If you were able to install Windows 7, then you should have gone for the upgrade. That should have worked theoretically.

And you should have investigated the issue fully, before starting to replace components. 3 years is not a lot of time for a desktop.
 
  • Like
Reactions: kartikoli
To me it looks like window 10 is being funny with his SSD, few weeks ago latest update was causing BSOD for some printers of a company ( for my printer which is from HP it stopped printing anything after applying that update )
Trying other OS is to rule out hardware issue as you will be able to test the hardware on other OS like 7 or linux and its one of the easiest step and will take only 2-3 hours, if it ran fine on them then window 10 isn't happy with your hardware combo.
 
  • Like
Reactions: kartikoli
I don't have another system to test these SSD's but I will try W7 and see if it works and try to upgrade to W10 (not sure if that option still works now... will check though)

I think board is not at fault as I've used Asrock board to test and got errors
I prefer to keep components in warranty so if anything goes wrong we can get it repaired/replace. This is my main job PC so being extra cautious
 
Hi..I have a similar issue.. Upgraded my PC from an Intel i7 3rd gen to a R5 5600x and (shamelessly/lazily) did not reimage the system, everything worked great. Now, I got an NVME drive (From a fellow FM) and have installed the latest n greatest drivers, BIOS, Win 10 version and I get BSODs 2 - 10 mins after loading CP2077

Kernel Power Event 41 (63)

When I swap the NVME with the old SSD, it works great, no issues CP77 runs for hrs. Except the drives, all hardware remains the same.

SSD - Win 10 1909
NVME - Win 10 20H2

Any ideas?
 
Slayer88 said:
Hi..I have a similar issue.. Upgraded my PC from an Intel i7 3rd gen to a R5 5600x and (shamelessly/lazily) did not reimage the system, everything worked great. Now, I got an NVME drive (From a fellow FM) and have installed the latest n greatest drivers, BIOS, Win 10 version and I get BSODs 2 - 10 mins after loading CP2077

Kernel Power Event 41 (63)

When I swap the NVME with the old SSD, it works great, no issues CP77 runs for hrs. Except the drives, all hardware remains the same.

SSD - Win 10 1909
NVME - Win 10 20H2

Any ideas?
Click to expand...

If you have an option in bios to disable pcie gen4 mode and leave it as gen3 try that?
 
kartikoli said:
I don't have another system to test these SSD's but I will try W7 and see if it works and try to upgrade to W10 (not sure if that option still works now... will check though)

I think board is not at fault as I've used Asrock board to test and got errors
I prefer to keep components in warranty so if anything goes wrong we can get it repaired/replace. This is my main job PC so being extra cautious
Click to expand...
1. Try disabling PBO and see how it runs at base speed or below.
2. Try to install ubuntu linux on NVMe and see if this OS is stable. If this OS is stable, your CPU may not be the problem here and it could very well be the windows 10+nvme+b550+3500 combination.

If you were in Bangalore, I would have given my 3200G and A320 board to you to test your cpu on A320 board and my cpu on your board. If you can do this with any of your friends, try it out.
Slayer88 said:
Hi..I have a similar issue.. Upgraded my PC from an Intel i7 3rd gen to a R5 5600x and (shamelessly/lazily) did not reimage the system, everything worked great. Now, I got an NVME drive (From a fellow FM) and have installed the latest n greatest drivers, BIOS, Win 10 version and I get BSODs 2 - 10 mins after loading CP2077

Kernel Power Event 41 (63)

When I swap the NVME with the old SSD, it works great, no issues CP77 runs for hrs. Except the drives, all hardware remains the same.

SSD - Win 10 1909
NVME - Win 10 20H2

Any ideas?
Click to expand...
Let me check this particular issue with a friend who has same setup (5600X + NVMe SSD + win10).
 
Last edited:
  • Like
Reactions: Slayer88 and kartikoli
Wish I could do that but not possible as I am from Lucknow, anyways the RAMs are running without XMP profile since then and I am struggling with time due to very busy job schedule so haven't been able to boot from SSD, though on 26 March I've installed W10 one last time and got errors (now I am used to these errors lol) since then I haven't got time to try again, my next move will be to install W7 and see if it works and then upgrade to W10. Lastly install Linux (the reason I am avoiding Linux is no matter how good it is, I need Windows for job so have to stick)

The errors that I got on 26th are as follows
==================================================
Dump File : 032621-13781-01.dmp
Crash Time : 26-03-2021 16:10:20
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 : ndis.sys
Caused By Address : ndis.sys+18380
File Description : Network Driver Interface Specification (NDIS)
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.18362.1 (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\032621-13781-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 19041
Dump File Size : 842,044
Dump File Time : 26-03-2021 16:11:05
==================================================

==================================================
Dump File : 032621-14343-01.dmp
Crash Time : 26-03-2021 16:12:23
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000002
Parameter 2 : 00000000`001ab334
Parameter 3 : 00000000`0043f37f
Parameter 4 : 00000000`0000ffff
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\032621-14343-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 19041
Dump File Size : 762,628
Dump File Time : 26-03-2021 16:13:09
==================================================

==================================================
Dump File : 032621-14640-01.dmp
Crash Time : 26-03-2021 16:23:33
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff806`3d4efd71
Parameter 3 : ffffb008`53459f10
Parameter 4 : 00000000`00000000
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\032621-14640-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 19041
Dump File Size : 1,034,492
Dump File Time : 26-03-2021 16:24:19
==================================================

==================================================
Dump File : 032621-15328-01.dmp
Crash Time : 26-03-2021 16:27:22
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000002
Parameter 2 : 00000000`0024de1e
Parameter 3 : 00000000`0043f37f
Parameter 4 : 00000000`00000001
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\032621-15328-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 19041
Dump File Size : 1,089,340
Dump File Time : 26-03-2021 16:28:20
==================================================

==================================================
Dump File : 032621-15109-01.dmp
Crash Time : 26-03-2021 16:39:19
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff804`85bfc40a
Parameter 3 : fffffd05`c83ee8d0
Parameter 4 : 00000000`00000000
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+1c40a
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.18362.1 (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\032621-15109-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 19041
Dump File Size : 549,901
Dump File Time : 26-03-2021 16:40:00
==================================================
 
kartikoli said:
Wish I could do that but not possible as I am from Lucknow, anyways the RAMs are running without XMP profile since then and I am struggling with time due to very busy job schedule so haven't been able to boot from SSD, though on 26 March I've installed W10 one last time and got errors (now I am used to these errors lol) since then I haven't got time to try again, my next move will be to install W7 and see if it works and then upgrade to W10. Lastly install Linux (the reason I am avoiding Linux is no matter how good it is, I need Windows for job so have to stick)
Click to expand...
Not asking to install Linux and use it. If you get to install Linux in your NVMe SSD, you can create high I/O by trying to create huge set of files in parallel and also while you are doing these, you can monitor CPU speed, temperature etc.
Anyways, give W7 a try and see.
 
  • Like
Reactions: kartikoli
Today installed W7 and used it for 2.5h without any issues. Though first I had to struggle to get drivers for wifi and LAN so used my Phone in thethering mode and installing wifi drivers. After that installed all Windows updates which itself takes time and I was waiting for a crash

Next step, Install W10 using upgrade option and see how it goes
 
  • Like
Reactions: desiibond
kartikoli said:
Today installed W7 and used it for 2.5h without any issues. Though first I had to struggle to get drivers for wifi and LAN so used my Phone in thethering mode and installing wifi drivers. After that installed all Windows updates which itself takes time and I was waiting for a crash

Next step, Install W10 using upgrade option and see how it goes
Click to expand...
544qbb.jpg
 
  • Haha
Reactions: Kaleen Bhaiya and kartikoli
exactly thats what happened with me, upgraded and selected to remove everything and bingo... countless errors started poping up
I'll try again but this time use older version + select to keep my files and apps which I won't install on W7 anyways
 
Something in your system is not as per windows 10's liking i think, probably borrow an ssd from someone and see if its ssd that window 10 doesn't like (as HDD worked)
 
I'd like to thank everyone in this thread who have tried to help and spent time to figure out the problem. Finally after months of struggle I've gone to local store and bought a new processor (R5 3600) and wow everything worked great like I never had an issue :)
Since I was too scared to believe my luck I've waited around 10 days to see if everything is working fine and now can confirm that it does
 
  • Like
Reactions: Lozil, Stronk, Kaleen Bhaiya and 2 others
kartikoli said:
I'd like to thank everyone in this thread who have tried to help and spent time to figure out the problem. Finally after months of struggle I've gone to local store and bought a new processor (R5 3600) and wow everything worked great like I never had an issue :)
Since I was too scared to believe my luck I've waited around 10 days to see if everything is working fine and now can confirm that it does
Click to expand...
Told you so.
 
Status
Not open for further replies.
Top Bottom