Assistance with debugging 0x3B caused by ntkrnlmp.exe - Windows 10

fireweed

fireweed

Active member
Joined
Oct 14, 2021
Posts
40
Location
Alberta, Canada
Hey all.

In a someone ironic event, my computer experienced it's first BSoD in the 9 months I've had it while I was poking around the public BSoD Academy files. Since it's only the first once I'm not too concerned, but I was considering joining the academy and would appreciate some assistance with troubleshooting, maybe some explanation of steps reached to discover the issue?

File collection attached, and here are answers to the questions.
  • A brief description of your problem (but you can also include the steps you tried)
A sudden BSoD out of nowhere. I have checked event log for events taking place around the time of the event and couldnt see anything that stood out to me. System is up to date, DISM and then SFC came out clean.
  • System Manufacturer?
Custom Built
  • Laptop or Desktop?
Desktop
  • OS ? (Windows 10, 8.1, 8, 7, Vista)
Win 10 21H1
  • x86 (32bit) or x64 (64bit)?
x64
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
Retail
  • Age of system? (hardware)
9 Months
  • Age of OS installation?
9 months
  • Have you re-installed the OS?
no
  • CPU
ryzen 5 3600
  • RAM (brand, EXACT model, what slots are you using?)
corsair vengeance pro RGB 32Gb kit, CMW32GX4M2C3200C16. installed in the recommended slots on the mobo
  • Video Card
nvidia geforce gtx 1660 super
  • MotherBoard - (if NOT a laptop)
rog strix B550-A gaming
  • Power Supply - brand & wattage (if laptop, skip this one)
Honestly, I cant remember and I dont see where to check it via system because it's not visible from the case.
  • Is driver verifier enabled or disabled?
disabled
  • What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth)
malwarebytes premium
  • Are you using proxy, vpn, ipfilters or similar software?
nordvpn and globalprotect occasionally
  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software)
no
  • Are you currently under/overclocking? Are there overclocking software installed on your system?
Yes, via BIOS but I was not the one to set it up. Memory is overclocked a bit, but that's all. Been like that for ~4 months and haven't had any issues yet.

There is an absolutely ridiculous amount of RGB and RGB management software installed which does give me issues sometimes, mainly just the programs crashing and my settings reverting to default.
 

Attachments

Update: Turned on driver verifier, restarted and immediate bsod. Didn't restart on its own so forced one. Turned on. Bsod. Restart. On. Bsod. Restart.

Now I'm using system restore to roll back.

So, driver issue perhaps? Haha
 
It seems like the issue was due to an unresolvable page fault. Were you unable to even reach Safe Mode when Driver Verifier was running?

fireweed said:
I was considering joining the academy and would appreciate some assistance with troubleshooting, maybe some explanation of steps reached to discover the issue?
Click to expand...
I've been considering to write some tutorials for the common bugchecks like Stop 0x3B and Stop 0x7E. They're very common bugchecks and it would be useful if there was some guidance for those who wish to attempt to debug their own crashes.
 
Is this the sort of thing that happens once in a blue moon or will this issue only start happening more frequently now?

And I didn't try anything other than a rollback from the windows startup recovery screen. I'm going to turn it on again and see what happens. I checked the dump from the verifier bsod and it was a driver for nordvpn so i've uninstalled it.

I would eagerly read a tutorial like that.
 
Well, no immediate BSoD this time, but upon logging in explorer didnt start so I had to use task manager to launch it and bring everything back. Hoping it's related to D.V being turned on and not just my computer bleeding from a second cut.

Things are also very slow. Verifier's fault?
 
The logs reported possible drive problems.

The BIOS is out of date.


Please perform the following steps:

1) Open administrative command prompt and type or copy and paste:
wmic recoveros set autoreboot = false
wmic recoveros set debuginfotype = 7
wmic computersystem where name="%computername%" set automaticmanagedpagefile=true


2) Run HD Tune: (free or trial version) (test all drives)
HD Tune website
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan


3) Sea Tools for Windows (test all drives)
SeaTools (Windows) | Seagate
long generic test


These tests can be performed overnight:
a) HD Tune full error scan
b) Sea Tools for Windows long generic test



4) Upgrade the BIOS: 1004 > 2423
BaseBoard Product ROG STRIX B550-A GAMING

Code: 
------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 36.6 GB
Total Space: 237.9 GB
File System: NTFS
      Model: KINGSTON SA2000M8250G

      Drive: D:
 Free Space: 204.9 GB
Total Space: 953.8 GB
File System: exFAT
      Model: Samsung PSSD T7 SCSI Disk Device

      Drive: E:
 Free Space: 1044.0 GB
Total Space: 1907.6 GB
File System: NTFS
      Model: ST2000DM008-2FR102
 
Last edited by a moderator:
zbook said:
The logs reported possible drive problems.
Click to expand...
Do you mind me asking what exactly in the logs reported that? I'm not doubting, I would just like to know.

Since my drives are so massive it will take some time but hopefully I have them done by tommorow.

Thank you for your advice.
 
I havent scanned my 1TB and 2TB drives yet, but I scanned my boot SSD and things seem fine. Here are the screenshots of the disk tools for the SSD, as well as a dump I got from when my explorer.exe crashed again.
ssd1.JPG[ssd2.JPGssd3.JPGssdpass.JPG
though I am not sure is I ran the health scan properly
1635381136716.png

bios update tonight...
 
These were some of the event viewer entries indicating possible drive problems:



Code: 
Event[2153]:
  Log Name: System
  Source: disk
  Date: 2021-10-14T20:37:23.4550000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x2 for Disk 2 (PDO name: \Device\0000004d) was retried.


Event[23154]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:33:25.8270000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x7eabdc for Disk 2 (PDO name: \Device\000000ab) was retried.

Event[23155]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:33:24.8120000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x7eaadc for Disk 2 (PDO name: \Device\000000ab) was retried.

Event[23156]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:33:07.3020000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x7ae49c for Disk 2 (PDO name: \Device\000000ab) was retried.

Event[23157]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:33:04.0600000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x78905c for Disk 2 (PDO name: \Device\000000ab) was retried.


Event[23161]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:32:12.9720000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x17f09c for Disk 2 (PDO name: \Device\000000ab) was retried.

Event[23162]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:32:12.6380000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x6e7f9c for Disk 2 (PDO name: \Device\000000ab) was retried.

Event[23163]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:32:10.2580000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x64a58 for Disk 2 (PDO name: \Device\000000ab) was retried.

Event[23164]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:32:09.9360000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x68e99c for Disk 2 (PDO name: \Device\000000ab) was retried.

Event[23165]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:32:07.4480000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x67009c for Disk 2 (PDO name: \Device\000000ab) was retried.

Event[23166]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:32:06.3450000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x669b9c for Disk 2 (PDO name: \Device\000000ab) was retried.

Event[23167]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:32:05.3140000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x669a9c for Disk 2 (PDO name: \Device\000000ab) was retried.

Event[23168]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:32:01.9500000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x655e9c for Disk 2 (PDO name: \Device\000000ab) was retried.

Event[23169]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:31:55.9540000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x59e59c for Disk 2 (PDO name: \Device\000000ab) was retried.

Event[23170]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:31:51.4420000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x50539c for Disk 2 (PDO name: \Device\000000ab) was retried.

Event[23171]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:31:49.7550000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x4e679c for Disk 2 (PDO name: \Device\000000ab) was retried.

Event[23172]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:31:48.7380000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x4e659c for Disk 2 (PDO name: \Device\000000ab) was retried.

Event[23173]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:31:40.8010000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x37639c for Disk 2 (PDO name: \Device\000000ab) was retried.

Event[23174]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:31:38.7750000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x37619c for Disk 2 (PDO name: \Device\000000ab) was retried.

Event[23175]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:31:34.5220000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x2c7e9c for Disk 2 (PDO name: \Device\000000ab) was retried.

Event[23176]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:31:33.4950000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x2c7c9c for Disk 2 (PDO name: \Device\000000ab) was retried.

Event[23177]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:31:27.0070000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x1b159c for Disk 2 (PDO name: \Device\000000ab) was retried.

Event[23178]:
  Log Name: System
  Source: disk
  Date: 2021-03-18T15:31:23.8880000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
The IO operation at logical block address 0x19339c for Disk 2 (PDO name: \Device\000000ab) was retried.




Code: 
Event[11]:
  Log Name: System
  Source: disk
  Date: 2021-10-25T14:46:02.7960000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[12]:
  Log Name: System
  Source: disk
  Date: 2021-10-25T14:46:02.7800000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.


Event[17]:
  Log Name: System
  Source: disk
  Date: 2021-10-25T14:46:00.0940000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[18]:
  Log Name: System
  Source: disk
  Date: 2021-10-25T14:46:00.0660000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[19]:
  Log Name: System
  Source: disk
  Date: 2021-10-25T14:46:00.0360000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[20]:
  Log Name: System
  Source: disk
  Date: 2021-10-25T14:46:00.0160000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.


Event[95]:
  Log Name: System
  Source: disk
  Date: 2021-10-25T14:28:36.4030000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[96]:
  Log Name: System
  Source: disk
  Date: 2021-10-25T14:28:36.2900000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.


Event[98]:
  Log Name: System
  Source: disk
  Date: 2021-10-25T14:28:36.1710000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[99]:
  Log Name: System
  Source: disk
  Date: 2021-10-25T14:28:36.0740000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.


Event[152]:
  Log Name: System
  Source: disk
  Date: 2021-10-25T09:56:49.5300000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[153]:
  Log Name: System
  Source: disk
  Date: 2021-10-25T09:56:49.4670000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.




Code: 
Event[1432]:
  Log Name: System
  Source: Volsnap
  Date: 2021-10-16T14:53:10.5620000Z
  Event ID: 14
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gay-Bomb
  Description: 
The shadow copies of volume C: were aborted because of an IO failure on volume C:.






After completing the steps in the earlier post also run:
Hard Disk Sentinel: (free or trial version)
Hard Disk Sentinel - HDD health and temperature monitoring

Post images of these tabs:
Overview
Temperature
SMART
 
fireweed said:
Things are also very slow. Verifier's fault?
Click to expand...
Yes, that'll be most likely due to DV running in the background.

fireweed said:
I checked the dump from the verifier bsod and it was a driver for nordvpn so i've uninstalled it.
Click to expand...
Good to hear, hopefully that was the main culprit for the crashes. If you don't have any more BSODs from DV, then I would disable it and then continue to use the system as you normally would.

zbook said:
These were some of the event viewer entries indicating possible drive problems:
Click to expand...
Most of those paging operation errors are likely due to the page fault issue pointed out in my previous post. Hopefully NordVPN was the culprit.
 
x BlueRobot said:
Good to hear, hopefully that was the main culprit for the crashes. If you don't have any more BSODs from DV, then I would disable it and then continue to use the system as you normally would.


Most of those paging operation errors are likely due to the page fault issue pointed out in my previous post. Hopefully NordVPN was the culprit.
Click to expand...
Unfortunately, I found another one. I was trying to use the Asus bios update utility and as soon as I opened it, crash. Reinstalled, downgraded, still no dice. I'm not feeling too great about using that utility now, so I was looking for another way to update bios but strangely in Armory Crate (updates and ect utility) it's not telling me I have any bios updates so I cant do it though there. I've become too busy in the next few days with assignments to really mess around with this for the next while unfortunately. As long as VMware runs and I can do my assignments I'm happy for now. I'll hopefully be able to get into the bios next week to check version and such.

I'm planning on trying to upgrade my boot drive and some other components and do a fresh reinstall by the new year, anyway. Hopefully with a new SSD, RAM and CPU cooler my system will behave better.

x BlueRobot said:
Page faults are a completely normal system operation. I've written about Stop 0x50 which is technically a different bugcheck, but it covers some details about unresolvable page faults - The Complete Debugging Guide to Stop 0x50
Click to expand...
That was pretty much the result of my research as well. I've seen some of the paging errors (event 51) since the computer was built and google pretty much told me to ignore it.
 
I'm assuming you mean the dump from the DV caused by the asus bios update utility? Here it is.

Since this whole debacle has started I have been getting many application errors that appear on startup. Windows that popup upon startup mostly to do with corsair and asus utilities. LogonUI failing because of reasons other than explorer.exe (which annoys me because i just turned on dumps for it). I'm going to turn on dumps for logonUI as im getting the most inconvenienced with it compared to all the others.
 

Attachments

fireweed said:
I'm assuming you mean the dump from the DV caused by the asus bios update utility? Here it is.
Click to expand...
Thanks and it certainly appear the the ASUS update utility caused the crash. If you haven't, then I would suggest removing the program altogether. Most of the ASUS utilities are junkware and can be removed.

Rich (BB code): 
0: kd> lmvm AsUpIO
Browse full module list
start             end                 module name
fffff800`66910000 fffff800`66919000   AsUpIO   T (no symbols)           
    Loaded symbol image file: AsUpIO.sys
    Image path: AsUpIO.sys
    Image name: AsUpIO.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon May 13 13:36:36 2019 (5CD964D4)
    CheckSum:         000111BE
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

fireweed said:
I'm going to turn on dumps for logonUI as im getting the most inconvenienced with it compared to all the others.
Click to expand...
Are these live kernel dumps?
 
Thanks for checking it out! Unfortunately I have to keep some of the asus and corsair crap around if I want to control my rgb but maybe I can find just one program that does all of it instead of two. I'm gonna uninstall all the bundled stuff and other utilities it automatically downloaded when I ran the update utility the first time.

They're user mode dumps. I followed these instructions but if there's a better way I'd gladly do it.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top