- Apr 21, 2022
- 5
- 0
- 10
First my system specs:
MB: b350m Gaming pro
CPU: Ryzen 3700x
OLD RAM that was causing issues: Patriot 2x8g 3200Mhz
RAM (that is giving BSODs I think): Corsair LPX 2666 2x16GB
Update: Minidumps here: https://files.catbox.moe/amfkka.zip
Ok to sum up what's happened so far...
Couple weeks ago, computer started rebooting/crashing bad. Then eventually it wouldn't even come back up until I removed one of the RAM sticks.
Figured one of the sticks was bad. Replaced the RAM and PC started fine. Setup XMP to right speeds, But then random, daily BSOD's would start with different errors below.
I've tried LOTS of things already:
Frustrating thing is how random it is... if it was a crash at startup or not even posting it'd be so much easier to troubleshoot.
Seems like the BSOD's below happen kinda ramdonly. Sometimes 12 hrs of uptime. Sometimes after an entire day. Sometimes an hour. Can be during use or when PC is pretty idle.
I'm running out of ideas.... Any help would be greatly appreciated.
Thinking of trying another ram kit... maybe this new one is faulty?
WhoCrashed logs:
Windows version:
Windows 10, 10.0, version 2009, build: 19044 (x64)
Windows dir:
C:\WINDOWS
Hardware:
MS-7A39, Micro-Star International Co., Ltd., MSI, B350M GAMING PRO (MS-7A39)
CPU:
AuthenticAMD AMD Ryzen 7 3700X 8-Core Processor 8664, level: 23
Processor count:
16 logical processors, active mask: 65535
RAM:
16334.5MB
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Thu 4/21/2022 12:44:44 PM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\Minidump\042122-5968-01.dmp (Minidump)
Bugcheck code:
0x7A(0x1, 0xFFFFFFFFC0000005, 0xFFFFD50F92072080, 0xFFFFC33FFA789000)
Bugcheck name:
KERNEL_DATA_INPAGE_ERROR
Bug check description:
This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
Analysis:
STATUS_ACCESS_VIOLATION was repoted. The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. This bugcheck indicates that the error is file system or disk related. If no offending driver is found, it is suggested that you run CHKDSK to check your drive(s) for errors. This is possibly a software problem. This is likely a case of memory corruption.
Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues
On Thu 4/21/2022 12:44:44 PM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\MEMORY.DMP (Kernel memory dump)
Bugcheck code:
0x7A(0x1, 0xFFFFFFFFC0000005, 0xFFFFD50F92072080, 0xFFFFC33FFA789000)
Bugcheck name:
KERNEL_DATA_INPAGE_ERROR
Bug check description:
This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
Analysis:
STATUS_ACCESS_VIOLATION was repoted. The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. This bugcheck indicates that the error is file system or disk related. If no offending driver is found, it is suggested that you run CHKDSK to check your drive(s) for errors. This is possibly a software problem. This is likely a case of memory corruption.
Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues
On Thu 4/21/2022 12:28:18 AM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\Minidump\042122-6171-01.dmp (Minidump)
Bugcheck code:
0x1A(0x41792, 0xFFFFA90168418C48, 0x4000000000000, 0x0)
Bugcheck name:
MEMORY_MANAGEMENT
Bug check description:
This indicates that a severe memory management error occurred.
Analysis:
A corrupted PTE has been detected. This is possibly a software problem. This is a typical case of memory corruption.
This bugcheck is often associated with overheating problems. Read this article on memory corruption. Read this article on thermal issues
On Wed 4/20/2022 4:42:39 PM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\Minidump\042022-6171-01.dmp (Minidump)
Bugcheck code:
0x1A(0x61941, 0x1AF777A9000, 0xF, 0xFFFFA88D51A29B00)
Bugcheck name:
MEMORY_MANAGEMENT
Bug check description:
This indicates that a severe memory management error occurred.
Analysis:
This is possibly a software problem. This is likely a case of memory corruption.
This bugcheck is often associated with overheating problems. Read this article on memory corruption. Read this article on thermal issues
On Tue 4/19/2022 5:31:58 PM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\Minidump\041922-7156-01.dmp (Minidump)
Bugcheck code:
0x1A(0x61941, 0x8001E5A9A10, 0xD, 0xFFFFCA8216A92B00)
Bugcheck name:
MEMORY_MANAGEMENT
Bug check description:
This indicates that a severe memory management error occurred.
Analysis:
This is possibly a software problem. This is likely a case of memory corruption.
This bugcheck is often associated with overheating problems. Read this article on memory corruption. Read this article on thermal issues
On Mon 4/18/2022 7:13:50 PM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\Minidump\041822-7000-01.dmp (Minidump)
Bugcheck code:
0xC9(0x21F, 0xFFFFF80EE75FB174, 0xFFFFCF0F236AAE50, 0x0)
Bugcheck name:
DRIVER_VERIFIER_IOMANAGER_VIOLATION
Driver or module in which error occurred:
ScpVBus.sys (ScpVBus+0xB174)
File path:
C:\WINDOWS\System32\drivers\ScpVBus.sys
Bug check description:
This is the bug check code for all Driver Verifier crashes.
Analysis:
This is a typical software problem. Most likely this is caused by a bug in a driver.
Google query:
scpvbus DRIVER_VERIFIER_IOMANAGER_VIOLATION
Conclusion
6 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
scpvbus.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the suggestions displayed in the bugcheck analysis above.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
The analysis process took 0:00:10 (h🇲🇲ss).
MB: b350m Gaming pro
CPU: Ryzen 3700x
OLD RAM that was causing issues: Patriot 2x8g 3200Mhz
RAM (that is giving BSODs I think): Corsair LPX 2666 2x16GB
Update: Minidumps here: https://files.catbox.moe/amfkka.zip
Ok to sum up what's happened so far...
Couple weeks ago, computer started rebooting/crashing bad. Then eventually it wouldn't even come back up until I removed one of the RAM sticks.
Figured one of the sticks was bad. Replaced the RAM and PC started fine. Setup XMP to right speeds, But then random, daily BSOD's would start with different errors below.
I've tried LOTS of things already:
- chkdsk for errors. Seem fine.
- Memory test (via windows... not thorough I know, but came out clean)
- Combinations of no overclocking, stock clocks, xmp, no xmp... same issue.
- increasing and decreasing voltage... (up to 1.35v) same problems
- Updating drivers (amd chipset, lan drivers, etc)
- Updating bios
- Windows update
- Removing scpv driver listed in the logs...
- Updating gpu drivers
- Other things... I'll updates as I remember.
Frustrating thing is how random it is... if it was a crash at startup or not even posting it'd be so much easier to troubleshoot.
Seems like the BSOD's below happen kinda ramdonly. Sometimes 12 hrs of uptime. Sometimes after an entire day. Sometimes an hour. Can be during use or when PC is pretty idle.
I'm running out of ideas.... Any help would be greatly appreciated.
Thinking of trying another ram kit... maybe this new one is faulty?
WhoCrashed logs:
Windows version:
Windows 10, 10.0, version 2009, build: 19044 (x64)
Windows dir:
C:\WINDOWS
Hardware:
MS-7A39, Micro-Star International Co., Ltd., MSI, B350M GAMING PRO (MS-7A39)
CPU:
AuthenticAMD AMD Ryzen 7 3700X 8-Core Processor 8664, level: 23
Processor count:
16 logical processors, active mask: 65535
RAM:
16334.5MB
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Thu 4/21/2022 12:44:44 PM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\Minidump\042122-5968-01.dmp (Minidump)
Bugcheck code:
0x7A(0x1, 0xFFFFFFFFC0000005, 0xFFFFD50F92072080, 0xFFFFC33FFA789000)
Bugcheck name:
KERNEL_DATA_INPAGE_ERROR
Bug check description:
This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
Analysis:
STATUS_ACCESS_VIOLATION was repoted. The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. This bugcheck indicates that the error is file system or disk related. If no offending driver is found, it is suggested that you run CHKDSK to check your drive(s) for errors. This is possibly a software problem. This is likely a case of memory corruption.
Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues
On Thu 4/21/2022 12:44:44 PM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\MEMORY.DMP (Kernel memory dump)
Bugcheck code:
0x7A(0x1, 0xFFFFFFFFC0000005, 0xFFFFD50F92072080, 0xFFFFC33FFA789000)
Bugcheck name:
KERNEL_DATA_INPAGE_ERROR
Bug check description:
This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
Analysis:
STATUS_ACCESS_VIOLATION was repoted. The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. This bugcheck indicates that the error is file system or disk related. If no offending driver is found, it is suggested that you run CHKDSK to check your drive(s) for errors. This is possibly a software problem. This is likely a case of memory corruption.
Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues
On Thu 4/21/2022 12:28:18 AM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\Minidump\042122-6171-01.dmp (Minidump)
Bugcheck code:
0x1A(0x41792, 0xFFFFA90168418C48, 0x4000000000000, 0x0)
Bugcheck name:
MEMORY_MANAGEMENT
Bug check description:
This indicates that a severe memory management error occurred.
Analysis:
A corrupted PTE has been detected. This is possibly a software problem. This is a typical case of memory corruption.
This bugcheck is often associated with overheating problems. Read this article on memory corruption. Read this article on thermal issues
On Wed 4/20/2022 4:42:39 PM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\Minidump\042022-6171-01.dmp (Minidump)
Bugcheck code:
0x1A(0x61941, 0x1AF777A9000, 0xF, 0xFFFFA88D51A29B00)
Bugcheck name:
MEMORY_MANAGEMENT
Bug check description:
This indicates that a severe memory management error occurred.
Analysis:
This is possibly a software problem. This is likely a case of memory corruption.
This bugcheck is often associated with overheating problems. Read this article on memory corruption. Read this article on thermal issues
On Tue 4/19/2022 5:31:58 PM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\Minidump\041922-7156-01.dmp (Minidump)
Bugcheck code:
0x1A(0x61941, 0x8001E5A9A10, 0xD, 0xFFFFCA8216A92B00)
Bugcheck name:
MEMORY_MANAGEMENT
Bug check description:
This indicates that a severe memory management error occurred.
Analysis:
This is possibly a software problem. This is likely a case of memory corruption.
This bugcheck is often associated with overheating problems. Read this article on memory corruption. Read this article on thermal issues
On Mon 4/18/2022 7:13:50 PM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\Minidump\041822-7000-01.dmp (Minidump)
Bugcheck code:
0xC9(0x21F, 0xFFFFF80EE75FB174, 0xFFFFCF0F236AAE50, 0x0)
Bugcheck name:
DRIVER_VERIFIER_IOMANAGER_VIOLATION
Driver or module in which error occurred:
ScpVBus.sys (ScpVBus+0xB174)
File path:
C:\WINDOWS\System32\drivers\ScpVBus.sys
Bug check description:
This is the bug check code for all Driver Verifier crashes.
Analysis:
This is a typical software problem. Most likely this is caused by a bug in a driver.
Google query:
scpvbus DRIVER_VERIFIER_IOMANAGER_VIOLATION
Conclusion
6 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
scpvbus.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the suggestions displayed in the bugcheck analysis above.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
The analysis process took 0:00:10 (h🇲🇲ss).
Facebook
Twitter
Instagram