BSOD Problems again!

Hello,

I'm sorry if I have posted this incorrectly or in the wrong space, I'm blinded by pain & anxiety. I got a message & I link to post here so many thanks to you Sir.
Here goes.
Here are the logs from V2, I created a link with one drive follow that tutorial just and is as follows:
GS-GAMER-(2025-02-02_11-16-56).zip

I have been plagued with this BSOD like all of a sudden. Over the last week I've been getting it & there are 2 things that show up in my investigations. 1 on the BSOD itself it's says BAD_POOL_CALLER & 2/ I computer management in Event logs> System it says 0x000000002 ( i just guessed on the zeros) & other notes online say this is almost always a driver related issue, now. I did see in a post here that there were some notes regarding Driver Verifier which I know nothing about. In that post at the bottom it said "noone has visited this post in 30 days, consider making another thread. Still I'm sorry if I have done the wrong thing I am so sick off banging my head into the keyboard & spraying blood everywhere lol.

I bought new RAM & a new motherboard & thought I was home yesterday. Started out today to check the system & it was BSOD. Oh the pain, oh the pain.

That link will give you access to the output of V2 & I noticed in one of the logs that it said no drivers are verified & as above I have seen that topic before but I need guidance cos I'm getting old, to old for the BSOD crap! Grrrrrrrr!

I am hopeful you guys can help after glancing some of the posts here.

Thanks in advance, all my spec are in my profile if you need anything else please let me know, I'll be here for a while.

Smitster :)

Please perform the following steps:



1) Run Tuneup plus > post a share link







2) Turn off Windows fast startup





3) Create a new restore point






4) Read this link on Windows Driver Verifier (WDV):

Enable and Disable Driver Verifier in Windows 10




5) Learn the methods to recover from BSOD caused by WDV by booting into safe mode and running one or more of these commands:

verifier /reset

verifier /bootmode resetonbootfail








6) Plan to run the tool with various customized test settings.

a) Test all non-Microsoft drivers

b) Test no Microsoft drivers

c) For the first run of WDV select the 3 customized tests displayed in the TF tutorial






7) Whenever the WDV tool is started if there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.





8) Customized tests will then be posted for the next run of WDV.





WDV can run continuously during the testing.



For any BSOD post a new V2 share link into the newest post.

Tuneup log!

Microsoft Windows 11 Pro Version 22H2 (OS Build 22621.4751)

==================================================================

Started on Sun 02/02/2025 at 17:30:57.95

[SFC /ScanNow]

Beginning system scan. This process will take some time.

Results:

Windows Resource Protection did not find any integrity violations.

==================================================================

Started on Sun 02/02/2025 at 17:33:21.11

[DISM /online /cleanup-image /ScanHealth]

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22621.4751

No component store corruption detected.

The operation completed successfully.

==================================================================

Started on Sun 02/02/2025 at 17:36:24.35

[DISM /online /cleanup-image /RestoreHealth]

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22621.4751

The restore operation completed successfully.

The operation completed successfully.

==================================================================

The second "SFC /ScanNow" was skipped, as the first output the following:

Windows Resource Protection did not find any integrity violations.

==================================================================

Started on Sun 02/02/2025 at 17:38:38.75

[ChkDsk /Scan]

The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
561408 file records processed.
File verification completed.
Phase duration (File record verification): 2.93 seconds.
5539 large file records processed.
Phase duration (Orphan file record recovery): 3.02 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.04 milliseconds.

Stage 2: Examining file name linkage ...
10528 reparse records processed.
659610 index entries processed.
Index verification completed.
Phase duration (Index verification): 5.21 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 315.15 milliseconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.11 milliseconds.
10528 reparse records processed.
Phase duration (Reparse point and Object ID verification): 20.81 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 29.21 milliseconds.
49102 data files processed.
Phase duration (Data attribute verification): 0.04 milliseconds.
CHKDSK is verifying Usn Journal...
36805448 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 130.29 milliseconds.

Windows has scanned the file system and found no problems.

No further action is required.

487641040 KB total disk space.
91452332 KB in 167526 files.
115808 KB in 49103 indexes.
0 KB in bad sectors.
687156 KB in use by the system.
65536 KB occupied by the log file.
395385744 KB available on disk.

4096 bytes in each allocation unit.
121910260 total allocation units on disk.
98846436 allocation units available on disk.
Total duration: 8.65 seconds (8652 ms).

==================================================================

Started on Sun 02/02/2025 at 17:38:53.85

AutoReboot

TRUE

==================================================================

[Set AutoReboot = False]

Updating property(s) of '\\GS-GAMER\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.
==================================================================

AutoReboot

FALSE

==================================================================

DebugInfoType

7

==================================================================

[Set DebugInfoType = 7]

Updating property(s) of '\\GS-GAMER\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.
==================================================================

DebugInfoType

7

==================================================================

[WMIC PageFile list]

AllocatedBaseSize=2944
CurrentUsage=5
Description=C:\pagefile.sys
InstallDate=20250201164123.911474+480
Name=C:\pagefile.sys
PeakUsage=5
Status=
TempPageFile=FALSE

==================================================================

AutomaticManagedPagefile

TRUE

==================================================================

[Set AutomaticManagedPagefile = True]

Updating property(s) of '\\GS-GAMER\ROOT\CIMV2:Win32_ComputerSystem.Name="GS-GAMER"'
Property(s) update successful.
==================================================================

AutomaticManagedPagefile

TRUE

==================================================================

[BcdEdit /enum {badmemory}]

RAM Defects
-----------
identifier {badmemory}

==================================================================

Finished on Sun 02/02/2025 at 17:38:55.58
It took 7 minutes and 58 seconds to complete the operations.

Am I reading that right like "Bad Memory" The RAM I bought yesterday, It's brand new!

Tune up bat.

Microsoft Windows 11 Pro Version 22H2 (OS Build 22621.4751)

==================================================================

Started on Sun 02/02/2025 at 17:30:57.95

[SFC /ScanNow]

Beginning system scan. This process will take some time.

Results:

Windows Resource Protection did not find any integrity violations.

==================================================================

Started on Sun 02/02/2025 at 17:33:21.11

[DISM /online /cleanup-image /ScanHealth]

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22621.4751

No component store corruption detected.

The operation completed successfully.

==================================================================

Started on Sun 02/02/2025 at 17:36:24.35

[DISM /online /cleanup-image /RestoreHealth]

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22621.4751

The restore operation completed successfully.

The operation completed successfully.

==================================================================

The second "SFC /ScanNow" was skipped, as the first output the following:

Windows Resource Protection did not find any integrity violations.

==================================================================

Started on Sun 02/02/2025 at 17:38:38.75

[ChkDsk /Scan]

The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
561408 file records processed.
File verification completed.
Phase duration (File record verification): 2.93 seconds.
5539 large file records processed.
Phase duration (Orphan file record recovery): 3.02 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.04 milliseconds.

Stage 2: Examining file name linkage ...
10528 reparse records processed.
659610 index entries processed.
Index verification completed.
Phase duration (Index verification): 5.21 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 315.15 milliseconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.11 milliseconds.
10528 reparse records processed.
Phase duration (Reparse point and Object ID verification): 20.81 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 29.21 milliseconds.
49102 data files processed.
Phase duration (Data attribute verification): 0.04 milliseconds.
CHKDSK is verifying Usn Journal...
36805448 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 130.29 milliseconds.

Windows has scanned the file system and found no problems.

No further action is required.

487641040 KB total disk space.
91452332 KB in 167526 files.
115808 KB in 49103 indexes.
0 KB in bad sectors.
687156 KB in use by the system.
65536 KB occupied by the log file.
395385744 KB available on disk.

4096 bytes in each allocation unit.
121910260 total allocation units on disk.
98846436 allocation units available on disk.
Total duration: 8.65 seconds (8652 ms).

==================================================================

Started on Sun 02/02/2025 at 17:38:53.85

AutoReboot

TRUE

==================================================================

[Set AutoReboot = False]

Updating property(s) of '\\GS-GAMER\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.
==================================================================

AutoReboot

FALSE

==================================================================

DebugInfoType

7

==================================================================

[Set DebugInfoType = 7]

Updating property(s) of '\\GS-GAMER\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.
==================================================================

DebugInfoType

7

==================================================================

[WMIC PageFile list]

AllocatedBaseSize=2944
CurrentUsage=5
Description=C:\pagefile.sys
InstallDate=20250201164123.911474+480
Name=C:\pagefile.sys
PeakUsage=5
Status=
TempPageFile=FALSE

==================================================================

AutomaticManagedPagefile

TRUE

==================================================================

[Set AutomaticManagedPagefile = True]

Updating property(s) of '\\GS-GAMER\ROOT\CIMV2:Win32_ComputerSystem.Name="GS-GAMER"'
Property(s) update successful.
==================================================================

AutomaticManagedPagefile

TRUE

==================================================================

[BcdEdit /enum {badmemory}]

RAM Defects
-----------
identifier {badmemory}

==================================================================

Finished on Sun 02/02/2025 at 17:38:55.58
It took 7 minutes and 58 seconds to complete the operations.

No way, it's brand new RAM, but it is what it is I guess. Am I reading that right zbook?

Hmmmmmmmm after scratching my head & looking at the results of those bat files I decided to check out my RAM more closely & the "person" I bought the new motherboard & RAM via said "I will check that the RAM matches your motherboard" so I said to myself "Oh good I won't have to look it up at Gigabytes website for supported "Memory"! Turns out that the Memory I bought, the number sticker on the back of the RAM is not supported! Which was....
CMK16GX4M2E3200C16, so I had some RAM lying around CMK16GX4M2Z2666C16 so I have loaded it into my new motherboard B550M DS3H AC Rev 1.7 hoping that though the speed is not supported the part number is most significantly CMK16GX "4M2Z" component of the overall number which is supported on the Gigabyte website for memory support!

I'll be taking that CMK16GX4M2E3200C16 Corsair RAM back tomorrow & give that young geek a rocket while I'm picking up my new. I hope this works, truIy I think you guys helped me out a great deal & I have found the problem for me. If you have anything to add I would appreciate it, thanks zbook. and if this hasn't been the fix then I'll be back until we find solution for any other BSOD sufferers out there :). I think all will be well.

The section for bad memory was empty.

Having RAM displayed on the QVL makes troubleshooting easier.

zbook said:

The section for bad memory was empty.

Having RAM displayed on the QVL makes troubleshooting easier.

Code:

[BcdEdit /enum {badmemory}]

RAM Defects
-----------
identifier {badmemory}

Click to expand...

yeah but since I put in the right RAM I left in on all night & it hasn't debugged once?
(sorry about the wrong section for posting this, my bad)

There was only one BSOD.

If that ends up being the fix then that will complete the troubleshooting.
(monitor for one week)

zbook said:

There was only one BSOD.

If that ends up being the fix then that will complete the troubleshooting.
(monitor for one week)

Click to expand...

Roger! Thanks so much, iza crossing my fingerz!

Monitor using:

It's still happening. Screenshot attached.

Please see the steps in post #2.

Ok, I ran the Reliability monitor & the line is not dotted & it's says the 74 critical events !
I do a screenshot.

zbook said:

Please see the steps in post #2.

Click to expand...

I must tell you, that I saw something about BSOD from Lacie Kelly? She had a hard time with it like me & she was advised to uninstall her anti virus & she came back & said "after un-installing her anti virus she hasn't experienced BSOD at all". So I did that too, Total AV were not happy but after 2 motherboards and a new CPU & new RAM, I'm glad I un-installed it "so far". Microsoft Defender is good enough they reckon but the guy coaching Lacie does recommend 3 anti virus providers. Now I'm going to play "Risk" & see if it happens again, if you don't here from me in 30 days, I'm good lol.

Love your work

<< Lacie Kelly link