Windows 10: 2-5 BSOD's a day since August 2019

Hi guys back in August 2019 I did a major upgrade from a old system windows 7 home with Intel 2500K to an Ryzen 5 AMD 3600 along with a new motherboard ASRock X570 Phantom Gaming 4 and DDR4 ram with windows 10 64bit.

attached the V2 Log collector asked for as part of making a new BSOD post.

Currently contemplating Just buying a new motherboard and seeing if the issue goes away as really getting tired of issue. So would like to get advise if it's a hardware issue or software.


My old system was rock solid even with the CPU overclocked to 4.5GHz. My current system though is very rocky with 2 to 5 BSOD a day on average. No real pattern I could see as can happen while gaming or just browsing. Any help you can give would be great. I've gone though dmp files with windbg and whocrashed but can't narrow down what it causing issues at my knowledge level.



Few things I've tried:

I've swapped for a different kit of DDR4 ram anyway and ran memtest86 on those as well just in case still getting BSOD's


Bought a new PSU as my old one was about 6-7 years old current is a SeaSonic 850W



Took out 980ti I was using and put in an old card HD6950 but still had issues


Reinstalled Windows 10 onto a known working 500 SDD I was using before rather than the M.2 NVMe 500, still BSOD


Reinstalled windows 10 a few times just in case.


Tested CPU with Prime95 and OCCT -

Tested RAM with memtest86, hci memtest and windows own memory diagnostic

Tested disks with SeaTools and checked their S.M.A.R.T with CrystalDiskInfo -

Tested GPU with FurMark -

used Speccy to get specs.

http://speccy.piriform.com/results/P...g3nutF74iL1VMY

used V2 Log collector ( attached)

I also have a number of mini dmp files here: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Five most recent DMP files

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Not all the BSOD's seem to leave dmp files though I had 6-7 in the last 24 hours including one before even getting to signing into windows 10.


On Mon 2020-05-25 10:23:52 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052520-113046-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8061E7B16F9)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8061E7B16F9, 0xFFFF83880236FCA8, 0xFFFF83880236F4F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Mon 2020-05-25 9:15:23 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052520-109281-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF800461A8FD2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800461A8FD2, 0xFFFFC68DEB724BF8, 0xFFFFC68DEB724440)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Sun 2020-05-24 7:43:57 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052420-110750-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF806599A8FD2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF806599A8FD2, 0xFFFFCE09D43FDBF8, 0xFFFFCE09D43FD440)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Sat 2020-05-23 8:10:46 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052320-110203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xA (0x5E8B, 0xFF, 0x26, 0xFFFFF8018483C92B)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 2020-05-23 7:57:02 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052320-111750-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8077F1B16F9)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8077F1B16F9, 0xFFFFEF880265ECA8, 0xFFFFEF880265E4F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.

:)

 

Office 2019

Only supported on Win10. Sorry, 8.1 users, only 4 years old, gotta go.

Microsoft Office 2019 will only work on Windows 10

https://blogs.technet.microsoft.com...-to-office-and-windows-servicing-and-support/

Spoiler Office 2019
Last year at Ignite, we announced Office 2019 – the next perpetual version of Office that includes apps (including Word, Excel, PowerPoint, and Outlook, and Skype for Business) and servers (including Exchange, SharePoint, and Skype for Business). Today we’re pleased to share the following updates:

• Office 2019 will ship in H2 of 2018. Previews of the new apps and servers will start shipping in the second quarter of 2018.
• Office 2019 apps will be supported on:
  • Any supported Windows 10 SAC release
  • Windows 10 Enterprise LTSC 2018
  • The next LTSC release of Windows Server
• The Office 2019 client apps will be released with Click-to-Run installation technology only. We will not provide MSI as a deployment methodology for Office 2019 clients. We will continue to provide MSI for Office Server products.

 

windows updates not installed since august 2019

Hi

Not one update for Windows 10 has now installed since August 2019 other than
August 30, 2019 — KB4511555 Cumulative Update for .NET Framework 3.5, 4.8 for Windows 10, version 1903

I initially presumed this would be a known error and would eventually be resolved by a future update, but this clearly is not the case.

All updates are downloading without problem, but installation reached 98% and then starts to uninstall.

I've tried turning off my antivirus and firewall but that doesn't do anything either.

Any suggestions will be gratefully received.

Many thanks

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.