Question PC keeps getting BSODs ?

Toggle sidebar Toggle sidebar
B

Bluescreener97

Aug 18, 2024
28
0
30
Hey everyone... Not a big techy person and I'm at the point of frustration where i have no idea what's causing these BSOD anymore.. I've tried numerous things on youtube/google to solve the issues but they keep happening i would really appreciate some help if possible to try and solve this issue. I will randomly blue screen or my pc will restart sometimes when I'm gaming or even just watching a youtube video.

At first i thought it was just my ram so i went out and spent 150$ on new ram.... but it has continued to keep getting BSOD even after the new sticks went in. If I'm lucky i can go a few hours without a bluescreen but sometimes if i blue screen it will do it every 5 minutes or so until it gives up and lets me play for a while - Im not sure if there is a setting that's wrong in my pc or anything but i have tried many things to even check for outdated drivers and to my knowledge i have it all updated. I have even tried resetting my pc and keeping personal files..

Here is a list of my specs:
Motherboard: B450 Gaming Plus Max​
CPU: AMD Ryzen 5 5500​
GPU: NVIDIA GeForce RTX 3060 TI​
RAM: 32GB​

I'm not exactly sure how to send Dump files on here... but i copied the text of one of my dump files to paste here... ill post it below id appreciate any help ill have this open to reply as fast as i can...




************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 42

Microsoft (R) Windows Debugger Version 10.0.27668.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\081824-5562-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff802`66400000 PsLoadedModuleList = 0xfffff802`670134f0
Debug session time: Sun Aug 18 15:33:52.664 2024 (UTC - 4:00)
System Uptime: 0 days 2:16:46.268
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000eb`37308018). Type ".hh dbgerr001" for details
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`66815cb0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffe0f`75529660=000000000000000a
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8026671c7c2, address which referenced memory

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1624

Key : Analysis.Elapsed.mSec
Value: 1700

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 296

Key : Analysis.Init.Elapsed.mSec
Value: 7924

Key : Analysis.Memory.CommitPeak.Mb
Value: 90

Key : Bugcheck.Code.LegacyAPI
Value: 0xa

Key : Bugcheck.Code.TargetModel
Value: 0xa

Key : Dump.Attributes.AsUlong
Value: 1008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : Failure.Bucket
Value: AV_nt!MiGetProtoPteAddress

Key : Failure.Hash
Value: {a64e817a-4b50-300b-8b23-1b285f484094}


BUGCHECK_CODE: a

BUGCHECK_P1: 8

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8026671c7c2

FILE_IN_CAB: 081824-5562-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

FAULTING_THREAD: ffff880e8afc4040

READ_ADDRESS: fffff8026711c470: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
0000000000000008

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: sppsvc.exe

TRAP_FRAME: fffffe0f755297a0 -- (.trap 0xfffffe0f755297a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff880e862a5d30 rbx=0000000000000000 rcx=0000000000000481
rdx=ffff880e963a8920 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8026671c7c2 rsp=fffffe0f75529930 rbp=fffffe0f75529a80
r8=ffff880e862a5d30 r9=ffffa98147b47000 r10=00000007ff7616d0
r11=ffff880e963a8968 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiGetProtoPteAddress+0x82:
fffff802`6671c7c2 4d2b4808 sub r9,qword ptr [r8+8] ds:ffff880e`862a5d38=????????????????
Resetting default scope

STACK_TEXT:
fffffe0f`75529658 fffff802`6682bc29 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffe0f`75529660 fffff802`66827089 : ffff880e`862a5d68 fffff802`664ee1fc fffff802`66811bf0 fffff802`6689eb3e : nt!KiBugCheckDispatch+0x69
fffffe0f`755297a0 fffff802`6671c7c2 : fffffbfd`dffdd868 ffff880e`74d7e140 00000000`00000000 00007ff7`61b51000 : nt!KiPageFault+0x489
fffffe0f`75529930 fffff802`6671ba14 : 00000000`00000338 fffffe0f`75529a80 00000000`00000000 fffffe0f`75529a80 : nt!MiGetProtoPteAddress+0x82
fffffe0f`75529980 fffff802`6671e4db : ffff880e`96235740 fffffe0f`75529c18 00000000`00000001 00000000`00000000 : nt!MiQueryAddressState+0x564
fffffe0f`75529ba0 fffff802`66bc6adf : fffffe0f`00000000 00007ff7`6192d000 00000007`ff760000 ffff880e`963a8920 : nt!MiQueryAddressSpan+0x24b
fffffe0f`75529c60 fffff802`66bc6385 : 0017d838`000bc8ae fffffbe4`c0000000 00000000`00001000 ffff880e`74d7e140 : nt!MmQueryVirtualMemory+0x73f
fffffe0f`75529e00 fffff802`6682b308 : 00000000`00000001 fffff802`6667cfb2 fffff802`67069500 fffffbe4`c0bec1c8 : nt!NtQueryVirtualMemory+0x25
fffffe0f`75529e50 fffff802`6681b7a0 : fffff802`66b54315 000000c6`000000a8 000000d1`0000001e 00000000`00000001 : nt!KiSystemServiceCopyEnd+0x28
fffffe0f`7552a058 fffff802`66b54315 : 000000c6`000000a8 000000d1`0000001e 00000000`00000001 ffff880e`962350c0 : nt!KiServiceLinkage
fffffe0f`7552a060 fffff802`66b53af4 : ffffa981`5c5f73ec 00007ff7`6192d630 00000000`000002ea 00000000`00000018 : nt!WbReEncryptWarbirdEncryptionSegment+0xa9d
fffffe0f`7552a0f0 fffff802`66b538cd : 00000000`000000cc 00000000`00000000 00000000`00000000 00000000`00000030 : nt!WbReEncryptWarbirdEncryptionSegment+0x27c
fffffe0f`7552a170 fffff802`66b55387 : ffffa981`57dcfd68 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!WbReEncryptWarbirdEncryptionSegment+0x55
fffffe0f`7552a1a0 fffff802`66aaef03 : 00000000`00000000 00000000`00000030 00000000`00000030 ffffa981`57dcfd60 : nt!WbReEncryptEncryptionSegment+0x7f
fffffe0f`7552a1d0 fffff802`66aac62c : ffffa981`59f76410 000000eb`3797e420 ffffa981`5c7c3410 00000000`00000000 : nt!WbDispatchOperation+0x1c3
fffffe0f`7552a230 fffff802`66aac2ad : ffff880e`74d385a0 fffff802`6689eb3e 145b3c5d`c73faa50 00000000`00000019 : nt!ExpQuerySystemInformation+0x31c
fffffe0f`7552aa60 fffff802`6682b308 : 00007ff7`61910000 00000000`00000010 00000000`00000000 00007ff7`61ab08c0 : nt!NtQuerySystemInformation+0x5d
fffffe0f`7552aaa0 00007fff`bf370664 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000eb`3797e3f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`bf370664


SYMBOL_NAME: nt!MiGetProtoPteAddress+82

MODULE_NAME: nt

IMAGE_VERSION: 10.0.22621.4036

STACK_COMMAND: .process /r /p 0xffff880e962350c0; .thread 0xffff880e8afc4040 ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 82

FAILURE_BUCKET_ID: AV_nt!MiGetProtoPteAddress

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a64e817a-4b50-300b-8b23-1b285f484094}

Followup: MachineOwner
---------
 
bugcheck was in Microsoft Software Protection Platform
looks like a corruption in virtual memory to me.
check the smart status of the drive to make sure it is not having error.
(use a tool like crystaldiskinfo.exe)

update the motherboard bios and the CPU chipset drivers from your motherboard vendor.
(to fix any controller bugs)

I would delete the pagefile.sys (virtual memory) reboot and turn it back on. This will dump any saved memory corruptions from the virtual memory system.

then you want to check the integrity of the windows files. I would first update all of the windows files via windows update, be sure to install the optional updated from microsoft. After the updates you would want to check the system files.
try and google "how to check windows system files"

IE start cmd.exe as an admin and run
should be something like
DISM.exe /Online /Cleanup-image /Restorehealth

there is a chance that the error is caused by bad RAM and that would indicate you should
update the bios, set the memory setting correctly and run a memory testing tool (memtest86)
if you delete the pagefile.sys you should get different memory dumps if the ram is the problem.
(you can google "how to make windows delete the pagefile.sys at shutdown") this can prevent saving memory corruptions to the pagefile.sys (mostly due to malware or bad drivers)

Note: the bugcheck showed attempted access to memory address 8. I would not think this is a RAM defect more like a bad driver.
(you can use verifier.exe to find bad drivers but you should always just update all of your software drivers before trying to debug this)

note: any corruption in windows software protection service is assumed to be a malware attack or license hack.
dism.exe command listed above should remove the hack/modification. You should also look at the software license status
 
Last edited:
johnbl said:
bugcheck was in Microsoft Software Protection Platform
looks like a corruption in virtual memory to me.
check the smart status of the drive to make sure it is not having error.
(use a tool like crystaldiskinfo.exe)

update the motherboard bios and the CPU chipset drivers from your motherboard vendor.
(to fix any controller bugs)

I would delete the pagefile.sys (virtual memory) reboot and turn it back on. This will dump any saved memory corruptions from the virtual memory system.

then you want to check the integrity of the windows files. I would first update all of the windows files via windows update, be sure to install the optional updated from microsoft. After the updates you would want to check the system files.
try and google "how to check windows system files"

IE start cmd.exe as an admin and run
should be something like
DISM.exe /Online /Cleanup-image /Restorehealth

there is a chance that the error is caused by bad RAM and that would indicate you should
update the bios, set the memory setting correctly and run a memory testing tool (memtest86)
if you delete the pagefile.sys you should get different memory dumps if the ram is the problem.
(you can google "how to make windows delete the pagefile.sys at shutdown") this can prevent saving memory corruptions to the pagefile.sys (mostly due to malware or bad drivers)

Note: the bugcheck showed attempted access to memory address 8. I would not think this is a RAM defect more like a bad driver.
(you can use verifier.exe to find bad drivers but you should always just update all of your software drivers before trying to debug this)

note: any corruption in windows software protection service could be a malware attack or license hack.
dism.exe command listed above should remove the hack/modification. You should also look at the software license status
Click to expand...
Just read this really quickly - I appreciate all this info - based on the Ram its like Brand new i just purchased this 2 days ago.. Ill try and figure out how to do what you said above knowing me might take hours lol
 
new RAM should have about 3 % failure rate. first thing to do is update bios to get the best default RAM settings before you do any RAM testing. Mostly, because if you get a failure during RAM testing the next thing to do is update the BIOS anyway.

Also, if you installed windows with bad RAM, it can corrupt files during the copy. the dism command can fix some of these corruptions.

bios updates work very well for machines made in the last 10 to 15 years.
 
Ah gotcha.... will update soon here i will have to
johnbl said:
new RAM should have about 3 % failure rate. first thing to do is update bios to get the best default RAM settings before you do any RAM testing. Mostly, because if you get a failure during RAM testing the next thing to do is update the BIOS anyway.

Also, if you installed windows with bad RAM, it can corrupt files during the copy. the dism command can fix some of these corruptions.

bios updates work very well for machines made in the last 10 to 15 years.
Click to expand...
Ah gotcha... will have to update you soon here while i figure it out all i know is my BIOS is a 2023 version atm
 
Bluescreener97 said:
Ah gotcha.... will update soon here i will have to

Ah gotcha... will have to update you soon here while i figure it out all i know is my BIOS is a 2023 version atm
Click to expand...
note bios updated also require motherboard driver updates to be installed after the BIOS update.
(good for certain low level bug fixes that cause corruption)
(I would skip installing most custom motherboard utilities) (high failure rates)
 
johnbl said:
note bios updated also require motherboard driver updates to be installed after the BIOS update.
(good for certain low level bug fixes that cause corruption)
(I would skip installing most custom motherboard utilities) (high failure rates)
Click to expand...
So i did everything you said other then the pagefile.sys my computer apparently doesn't have that file...
 
I think we need a lot more troubleshooting data here. Can you please download and run the SysnativeBSODCollectionApp and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.
 
ubuysa said:
I think we need a lot more troubleshooting data here. Can you please download and run the SysnativeBSODCollectionApp and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.
Click to expand...
Hey there i just ran the app but im a bit confused where it puts the file? it just runs the program and says successful
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom