BSOD Nightmare

zbook · Sep 11, 2025

For any BSOD please run the V2 log collector > post a new share link into the newest post

BSOD - Posting Instructions

BSOD - Posting Instructions This will show you how to help provide needed information about your system and dump files. It will not contain any personal or sensitive information about you or your data. To get better help with your Windows BSOD issue, please read these instructions and follow...

www.elevenforum.com

Rev_88 · Sep 11, 2025

Prime95 running all day so far. BSOD log attached.

zbook · Sep 11, 2025

The latest crashes were debugged.

1E
1A
A
D1

Multiple drivers were seen in the crashes.

Please place the computer into continuous safe mode (the longer the continuous duration the better the testing conditions) > for any BSOD run V2 > post a new V2 share link into the newest post

1E
1A
D1
124
7F
A
1A8

RJARRRPCGP · Sep 11, 2025

Rev_88 said:
Prime95 running all day so far. BSOD log attached.

That Prime95 run, looks very good. Usually, Prime95 would have failed at the 2 hour mark, especially if core(s) unstable.

RJARRRPCGP · Sep 11, 2025

RJARRRPCGP said:
That Prime95 run, looks very good. Usually, Prime95 would have failed at the 2 hour mark, especially if core(s) unstable.

Just in case, now run Prime95 with strictly small FFTs! Run that for at least 2 hours. Even though giving it 3 hours won't hurt.

Rev_88 · Sep 11, 2025

zbook said:
zbook said:

The latest crashes were debugged.

1E
1A
A
D1

Multiple drivers were seen in the crashes.

Please place the computer into continuous safe mode (the longer the continuous duration the better the testing conditions) > for any BSOD run V2 > post a new V2 share link into the newest post

1E
1A
D1
124
7F
A
1A8

Click to expand...

The latest crashes were debugged.

1E
1A
A
D1

Multiple drivers were seen in the crashes.

Please place the computer into continuous safe mode (the longer the continuous duration the better the testing conditions) > for any BSOD run V2 > post a new V2 share link into the newest post

1E
1A
D1
124
7F
A
1A8

The computer is stable, i've been running on currently with Prime95 for 10 hours now. The BSOD is only upon wake from sleep. If i don't do that i won't trigger a BSOD. I can try this in Safe but it doesn't crash if that's what you mean.

Rev_88 · Sep 11, 2025

Rev_88 said:
The computer is stable, i've been running on currently with Prime95 for 10 hours now. The BSOD is only upon wake from sleep. If i don't do that i won't trigger a BSOD. I can try this in Safe but it doesn't crash if that's what you mean.

Oops no sleep in safe!

zbook · Sep 11, 2025

Rev_88 said:
The computer is stable, i've been running on currently with Prime95 for 10 hours now. The BSOD is only upon wake from sleep. If i don't do that i won't trigger a BSOD. I can try this in Safe but it doesn't crash if that's what you mean.

The goal is to see the continuous duration of stability in safe mode.

The longer the testing period the better the testing conditions.

Rev_88 · Sep 12, 2025

zbook said:
The goal is to see the continuous duration of stability in safe mode.

The longer the testing period the better the testing conditions.

I know I'm being stupid, but since it runs indefinitely in normal mode can I not just leave it powered up to do the same test but actually use it?

I suppose I'm asking is there a difference in me messaging you next Friday after a week of being left on in normal mode vs next Friday of it running a week in safe mode?

zbook · Sep 12, 2025

1) Please read this link on Windows Driver Verifier (WDV):

Enable and Disable Driver Verifier in Windows 10

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

2) Create a new restore point

Create System Restore Point in Windows 11

This tutorial will show you how to manually create a restore point in Windows 11. Turning on system protection for a drive allows System Restore to include the drive when restore points are created so you can undo undesired system changes by reverting to a previous point in time. System...

www.elevenforum.com

3) 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

(option nine and seven)

Boot to Advanced Startup (WinRE) in Windows 11

This tutorial will show you how to boot to the advanced startup (WinRE) in Windows 11. The Windows Recovery Environment (WinRE) is a companion operating system installed alongside Windows 11, typically in a separate partition, that can help with troubleshooting, recovery, or booting from...

www.elevenforum.com

4) 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

5) 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.

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.

Rev_88 · Nov 7, 2025

Help

zbook · Nov 8, 2025

There were approximately two months without thread activity.

What was done?

What happened?

Are important files backed up for GoFlex Home?

Are you planning to run WDV as per post #30?

Code:

Event[1010]
  Log Name: Application
  Source: Chkdsk
  Date: 2025-10-15T02:30:20.5740000Z
  Event ID: 26228
  Task: None
  Level: Information
  Opcode: Info 
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: DESKTOP-8AUP7VP
  Description:
Chkdsk was executed in verify mode on a volume snapshot. 

Checking file system on \Device\HarddiskVolume12
Volume label is GoFlex Home.

Examining 1 corruption record ...

Record 1 of 1: Corrupt File "<0xfc,0xf22>" ... Attribute list entry with type code 80 in file F22 is corrupt.
Unable to find child frs 0xa844 with sequence number 0x426.
Attribute list entry with type code 80 in file F22 is corrupt.
Unable to find child frs 0xa845 with sequence number 0x427.
Attribute list entry with type code 80 in file F22 is corrupt.
Unable to find child frs 0xa846 with sequence number 0x428.
Attribute list entry with type code 80 in file F22 is corrupt.
Unable to find child frs 0xa847 with sequence number 0x429.
Attribute list entry with type code 80 in file F22 is corrupt.
Unable to find child frs 0xa848 with sequence number 0x42a.
Attribute list entry with type code 80 in file F22 is corrupt.
Unable to find child frs 0xa849 with sequence number 0x42b.
Attribute list entry with type code 80 in file F22 is corrupt.
Unable to find child frs 0xa84a with sequence number 0x42c.
Attribute list entry with type code 80 in file F22 is corrupt.
Unable to find child frs 0xa84b with sequence number 0x42d.
Attribute list entry with type code 80 in file F22 is corrupt.
Unable to find child frs 0xa84c with sequence number 0x42e.
Attribute list entry with type code 80 in file F22 is corrupt.
Unable to find child frs 0xa84d with sequence number 0x42f.
Attribute list entry with type code 80 in file F22 is corrupt.
Unable to find child frs 0xa84e with sequence number 0x430.
Attribute list entry with type code 80 in file F22 is corrupt.
Unable to find child frs 0xa84f with sequence number 0x431.
The attribute of type 0x80 and instance tag 0x0 in file 0xf22
has allocated length of 0xc249000 instead of 0x2bf2000.
Deleted corrupt attribute list entry
with type code 80 in file F22.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x41900000000a837.  The expected attribute type is 0x80.
Attribute record (80, "") from file record segment A837
is corrupt.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x41a00000000a838.  The expected attribute type is 0x80.
Attribute record (80, "") from file record segment A838
is corrupt.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x41e00000000a83c.  The expected attribute type is 0x80.
Attribute record (80, "") from file record segment A83C
is corrupt.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x42100000000a83f.  The expected attribute type is 0x80.
Attribute record (80, "") from file record segment A83F
is corrupt.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x42200000000a840.  The expected attribute type is 0x80.
Attribute record (80, "") from file record segment A840
is corrupt.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x42300000000a841.  The expected attribute type is 0x80.
Attribute record (80, "") from file record segment A841
is corrupt.
corruption found.

1 corruption record processed in 0.1 seconds.

Windows has examined the list of previously identified potential issues and found problems.
Please run chkdsk /scan to fully analyze the problems and queue them for repair.

Rev_88 · Nov 8, 2025

There were approximately two months without thread activity.

What was done?
As per previous posts, i found the computer was stable until i restarted it/shutdown. To be honest, it was easier to leave it running than risk the continuous boot loops. Like i found it difficult to even run the BSOD compiler.

What happened?
I've been redecorated, the PC was off for a about 3 weeks.

Are important files backed up for GoFlex Home?
The above might as well be chinese to me, the go flex is a USB attached storage device i remove and plug in. It doesn't have anything important.

Are you planning to run WDV as per post #30?
I'm running it now on all Microsoft drivers, no BSOD

Microsoft Windows [Version 10.0.26100.6899]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\System32>verifier /querysettings

Verifier Flags: 0x00100610

Standard Flags:

[ ] 0x00000001 Special pool.
[ ] 0x00000002 Force IRQL checking.
[ ] 0x00000008 Pool tracking.
[X] 0x00000010 I/O verification.
[ ] 0x00000020 Deadlock detection.
[ ] 0x00000080 DMA checking.
[ ] 0x00000100 Security checks.
[ ] 0x00000800 Miscellaneous checks.
[ ] 0x00020000 DDI compliance checking.

Additional Flags:

[ ] 0x00000004 Randomized low resources simulation.
[X] 0x00000200 Force pending I/O requests.
[X] 0x00000400 IRP logging.
[ ] 0x00002000 Invariant MDL checking for stack.
[ ] 0x00004000 Invariant MDL checking for driver.
[ ] 0x00008000 Power framework delay fuzzing.
[ ] 0x00010000 Port/miniport interface checking.
[ ] 0x00040000 Systematic low resources simulation.
[ ] 0x00080000 DDI compliance checking (additional).
[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.

Internal Flags:

[X] 0x00100000 Extended Verifier flags (internal).

[X] Indicates flag is enabled.

Active Rule Classes:

5 - I/O verification.
10 - Force pending I/O requests.
11 - IRP logging.
21 - Extended Verifier flags (internal).
34 - WDF verfication.
37 - File system filter verification.

Boot Mode:

Persistent

Rules:

All rules are using default settings

Verified Drivers:

mcupdate_genuineintel.dll
globmerger.sys
iastoravc.sys
amdkmdag.sys
amdfendr.sys
igdkmd64.sys
teedriverw10x64.sys
amdfendrmgr.sys
intcdaud.sys
dump_diskdump.sys
dump_iastoravc.sys
dump_dumpfve.sys
googledrivefs31931.sys
bedaisy.sys

zbook · Nov 8, 2025

How come Qcamain10x64.sys was not selected / tested?

When selecting non-Microsoft drivers:

a) click on the column heading so that it sorts
b) scroll up a down
c) select all non-Microsoft drivers

Rev_88 · Nov 10, 2025

zbook said:
How come Qcamain10x64.sys was not selected / tested?

When selecting non-Microsoft drivers:

a) click on the column heading so that it sorts
b) scroll up a down
c) select all non-Microsoft drivers

I didn't realise there were letters after M apparently in the alphabet. This may be it:

Microsoft Windows [Version 10.0.26100.6899]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\System32>verifier /querysettings

Verifier Flags: 0x00100610

Standard Flags:

[ ] 0x00000001 Special pool.
[ ] 0x00000002 Force IRQL checking.
[ ] 0x00000008 Pool tracking.
[X] 0x00000010 I/O verification.
[ ] 0x00000020 Deadlock detection.
[ ] 0x00000080 DMA checking.
[ ] 0x00000100 Security checks.
[ ] 0x00000800 Miscellaneous checks.
[ ] 0x00020000 DDI compliance checking.

Additional Flags:

[ ] 0x00000004 Randomized low resources simulation.
[X] 0x00000200 Force pending I/O requests.
[X] 0x00000400 IRP logging.
[ ] 0x00002000 Invariant MDL checking for stack.
[ ] 0x00004000 Invariant MDL checking for driver.
[ ] 0x00008000 Power framework delay fuzzing.
[ ] 0x00010000 Port/miniport interface checking.
[ ] 0x00040000 Systematic low resources simulation.
[ ] 0x00080000 DDI compliance checking (additional).
[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.

Internal Flags:

[X] 0x00100000 Extended Verifier flags (internal).

[X] Indicates flag is enabled.

Active Rule Classes:

5 - I/O verification.
10 - Force pending I/O requests.
11 - IRP logging.
21 - Extended Verifier flags (internal).
34 - WDF verfication.
37 - File system filter verification.

Boot Mode:

Persistent

Rules:

All rules are using default settings

Verified Drivers:

mcupdate_genuineintel.dll
globmerger.sys
iastoravc.sys
amdkmdag.sys
amdfendr.sys
igdkmd64.sys
teedriverw10x64.sys
qcamain10x64.sys
amdfendrmgr.sys
intcdaud.sys
dump_diskdump.sys
dump_iastoravc.sys
dump_dumpfve.sys
googledrivefs31931.sys

C:\Windows\System32>

zbook · Nov 10, 2025

Please restart WDV with these groups of customized tests:

Group a

Code:

    [ ] 0x00000010 I/O verification.
    [ ] 0x00000200 Force pending I/O requests.
    [ ] 0x00000400 IRP logging.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00000001 Special pool.
    [ ] 0x00000002 Force IRQL checking

Group b

Code:

    [ ] 0x00000008 Pool tracking.
    [ ] 0x00000020 Deadlock detection.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.
    [ ] 0x00200000 NDIS/WIFI verification.

Group c

Code:

    [ ] 0x00000080 DMA checking.
    [ ] 0x00000100 Security check.
    [ ] 0x00000800 Miscellaneous checks.
    [ ] 0x00020000 DDI compliance checking.
    [ ] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x00040000 Systematic low resources simulation.[/COLOR]




For each group if there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.



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

Rev_88 · Nov 15, 2025

Using the same set of drivers as before? (Non-Microsoft)

zbook · Nov 15, 2025

Rev_88 said:
Using the same set of drivers as before? (Non-Microsoft)

Yes, please select all non-Microsoft drivers for each WDV run.

BSOD Nightmare

Well-known member

My Computer My Computer

At a glance

Member

Attachments

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Member

My Computer My Computer

At a glance

Member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Member

Attachments

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computers

My Computers

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer