F5F Stay Refreshed Software Operating Systems Question sobre o BSOD com erro IRQL_NOT_LESS_OR_EQUAL e problema com webcam?

Question sobre o BSOD com erro IRQL_NOT_LESS_OR_EQUAL e problema com webcam?

Question sobre o BSOD com erro IRQL_NOT_LESS_OR_EQUAL e problema com webcam?

Pages (3): 1 2 3 Next
M
masterhamann8
Junior Member
48
04-25-2023, 09:49 PM
#1
Hello! I've encountered some problems with BSODs linked to corrupt .sys files from my Razer Basilisk V3 mouse. After swapping the mouse, everything functioned properly until today when another BSOD appeared with an IRQL_NOT_LESS_OR_EQUAL error.

What was happening at that time:
I was using a very old A4 Tech webcam. While typing the name of the webcam app (AMCap) into Start, it triggered the BSOD.

System details:
- MB: MSI Z790 Tomahawk WiFi (latest BIOS via USB flashback)
- CPU: Intel i5-14600KF + Thermalright Phantom Spirit 120 SE
- GPU: Gigabyte RTX 4070
- RAM: 32GB Kingston FURY DDR5 6000MHz CL30 (XMP)
- Storage: WD 2TB SN850X M.2 + 2TB WD Black HDD
- PSU: Seasonic Focus GX 750W Gold (used for 5 years)
- OS: Windows 10 (clean installs)
- XMP Profile 1 enabled, CPU undervolt -0.150V (temperatures dropped from 100 to 75 at max load)

My minidump file is corrupted, and BlueScreenView shows the error:
https://prnt.sc/9cjyrmJrKlTR
I couldn’t open the file because I lack permission, so I copied it to my desktop.

Here’s the link to download the dump file:
https://we.tl/t-sp6fMUwmTK
I’m feeling really confused and questioning everything—my SSD is fine, but I’m not sure what’s going on.
M
masterhamann8
04-25-2023, 09:49 PM #1

Hello! I've encountered some problems with BSODs linked to corrupt .sys files from my Razer Basilisk V3 mouse. After swapping the mouse, everything functioned properly until today when another BSOD appeared with an IRQL_NOT_LESS_OR_EQUAL error.

What was happening at that time:
I was using a very old A4 Tech webcam. While typing the name of the webcam app (AMCap) into Start, it triggered the BSOD.

System details:
- MB: MSI Z790 Tomahawk WiFi (latest BIOS via USB flashback)
- CPU: Intel i5-14600KF + Thermalright Phantom Spirit 120 SE
- GPU: Gigabyte RTX 4070
- RAM: 32GB Kingston FURY DDR5 6000MHz CL30 (XMP)
- Storage: WD 2TB SN850X M.2 + 2TB WD Black HDD
- PSU: Seasonic Focus GX 750W Gold (used for 5 years)
- OS: Windows 10 (clean installs)
- XMP Profile 1 enabled, CPU undervolt -0.150V (temperatures dropped from 100 to 75 at max load)

My minidump file is corrupted, and BlueScreenView shows the error:
https://prnt.sc/9cjyrmJrKlTR
I couldn’t open the file because I lack permission, so I copied it to my desktop.

Here’s the link to download the dump file:
https://we.tl/t-sp6fMUwmTK
I’m feeling really confused and questioning everything—my SSD is fine, but I’m not sure what’s going on.

O
Omer_Bamani
Member
78
04-26-2023, 06:03 AM
#2
CPU undervolt kann sich instabil verhalten. Prüfen Sie die Wärmeleitpaste und die Lüftergeschwindigkeit des Prozessors, wann erreicht er 100°C unter Belastung?
O
Omer_Bamani
04-26-2023, 06:03 AM #2

CPU undervolt kann sich instabil verhalten. Prüfen Sie die Wärmeleitpaste und die Lüftergeschwindigkeit des Prozessors, wann erreicht er 100°C unter Belastung?

S
SWAGGYTYALEX
Junior Member
6
04-26-2023, 02:25 PM
#3
Well, everything functions well in games and overall, but these small issues really bother me. Sorry, that was outdated information—I’m currently at -0.130V. The CPU throttled during unpacking some very compressed games; if you understand what I mean. Now it’s around 55 to 65 in the latest games at 1440p with Ultra settings.

I’ve already run sfc /scannow and found some corrupted files, which were fixed successfully. Should I also run DISM?

I’m also facing problems with Chrome—frequent Aw, Snap! errors. If I leave Chrome off for 2–3 hours, it blocks me from all websites and clears my cookies and sessions.

I plan to trigger a BSOD by interfering with my camera drivers. I’ll update you on what happens.

EDIT:
I’ve opened several instances of amcap software—no BSODs. I’m still confused. Chrome deleted my session again. Could it be a faulty SSD? I’ve tried all the tests, and my hardware looks fine. Maybe I should try reseating my m.2 SSD? ChatGPT mentioned a storport.sys driver issue. What’s that?
S
SWAGGYTYALEX
04-26-2023, 02:25 PM #3

Well, everything functions well in games and overall, but these small issues really bother me. Sorry, that was outdated information—I’m currently at -0.130V. The CPU throttled during unpacking some very compressed games; if you understand what I mean. Now it’s around 55 to 65 in the latest games at 1440p with Ultra settings.

I’ve already run sfc /scannow and found some corrupted files, which were fixed successfully. Should I also run DISM?

I’m also facing problems with Chrome—frequent Aw, Snap! errors. If I leave Chrome off for 2–3 hours, it blocks me from all websites and clears my cookies and sessions.

I plan to trigger a BSOD by interfering with my camera drivers. I’ll update you on what happens.

EDIT:
I’ve opened several instances of amcap software—no BSODs. I’m still confused. Chrome deleted my session again. Could it be a faulty SSD? I’ve tried all the tests, and my hardware looks fine. Maybe I should try reseating my m.2 SSD? ChatGPT mentioned a storport.sys driver issue. What’s that?

G
glenroi
Member
164
04-26-2023, 02:50 PM
#4
bugcheck happened while discord.exe was running. it looks like a heap corruption. it is unclear as to what driver caused the corruption. i would be looking at the dell driver and maybe this one DPMDriver.sys. Not sure what the Vimicro Corporation filter driver prototype is for.
System Uptime: 1 days 1:02:17.534
(most likely going to be a driver heap corruption bug, it will be hard to reproduce unless you use verifier.exe to force a bugcheck at the time of corruption)
Or you can just guess it is the dell dpmdriver.sys and remove it
you can download and run microsoft autoruns64.exe to delete or prevent drivers from loading.
Current Speed 3465MHz (strange number)
if you can not figure this out then:
I would turn off virtual memory, turn it back on to delete the pagefile.sys then turn on verifier flags. this should force windows to bugcheck when the heap is first corrupted rather than bugchecking later when the corrupted heap is passed to windows cleanup routines.
note: this assumes that your memory passes memory tests.
why is this driver running: (dell driver running on msi motherboard)
\SystemRoot\System32\drivers\DellInstrumentation.sys Wed Sep 18 23:53:04 2024
suspect drivers:
vvftav303.sys Fri Jun 22 22:46:10 2007
usbVM303.sys Sat Mar 24 21:26:25 2007
win32kfull.sys (checksum removed)
overclock driver installed:
C:\Program Files (x86)\MSI Afterburner\RTCore64.sys Sun Apr 14 04:53:16 2024
C:\Program Files (x86)\FanControl\FanControl.sys Sat Jul 26 06:29:37 2008
FocusritePCIeSwRoot.sys Thu Sep 19 06:07:05 2024
FocusriteUsb.sys Thu Sep 19 06:05:36 2024
FocusriteUsbAudio.sys Thu Sep 19 06:06:02 2024
FocusriteUsbSwRoot.sys Thu Sep 19 06:05:50 2024
DPMDriver.sys Wed Feb 21 15:58:01 2024
18: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 3494
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ Intel64 Family 6 Model 183 Stepping 1
ProcessorNameString = REG_SZ Intel® Core™ i5-14600KF
18: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.6, DMIVersion 0, Size=5202]
BiosMajorRelease = 5
BiosMinorRelease = 32
BiosVendor = American Megatrends International, LLC.
BiosVersion = H.G0
BiosReleaseDate = 04/09/2025
SystemManufacturer = Micro-Star International Co., Ltd.
SystemProductName = MS-7D91
SystemFamily = Default string
SystemVersion = 4.0
SystemSKU = Default string
BaseBoardManufacturer = Micro-Star International Co., Ltd.
BaseBoardProduct = MAG Z790 TOMAHAWK WIFI (MS-7D91)
BaseBoardVersion = 4.0
G
glenroi
04-26-2023, 02:50 PM #4

bugcheck happened while discord.exe was running. it looks like a heap corruption. it is unclear as to what driver caused the corruption. i would be looking at the dell driver and maybe this one DPMDriver.sys. Not sure what the Vimicro Corporation filter driver prototype is for.
System Uptime: 1 days 1:02:17.534
(most likely going to be a driver heap corruption bug, it will be hard to reproduce unless you use verifier.exe to force a bugcheck at the time of corruption)
Or you can just guess it is the dell dpmdriver.sys and remove it
you can download and run microsoft autoruns64.exe to delete or prevent drivers from loading.
Current Speed 3465MHz (strange number)
if you can not figure this out then:
I would turn off virtual memory, turn it back on to delete the pagefile.sys then turn on verifier flags. this should force windows to bugcheck when the heap is first corrupted rather than bugchecking later when the corrupted heap is passed to windows cleanup routines.
note: this assumes that your memory passes memory tests.
why is this driver running: (dell driver running on msi motherboard)
\SystemRoot\System32\drivers\DellInstrumentation.sys Wed Sep 18 23:53:04 2024
suspect drivers:
vvftav303.sys Fri Jun 22 22:46:10 2007
usbVM303.sys Sat Mar 24 21:26:25 2007
win32kfull.sys (checksum removed)
overclock driver installed:
C:\Program Files (x86)\MSI Afterburner\RTCore64.sys Sun Apr 14 04:53:16 2024
C:\Program Files (x86)\FanControl\FanControl.sys Sat Jul 26 06:29:37 2008
FocusritePCIeSwRoot.sys Thu Sep 19 06:07:05 2024
FocusriteUsb.sys Thu Sep 19 06:05:36 2024
FocusriteUsbAudio.sys Thu Sep 19 06:06:02 2024
FocusriteUsbSwRoot.sys Thu Sep 19 06:05:50 2024
DPMDriver.sys Wed Feb 21 15:58:01 2024
18: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 3494
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ Intel64 Family 6 Model 183 Stepping 1
ProcessorNameString = REG_SZ Intel® Core™ i5-14600KF
18: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.6, DMIVersion 0, Size=5202]
BiosMajorRelease = 5
BiosMinorRelease = 32
BiosVendor = American Megatrends International, LLC.
BiosVersion = H.G0
BiosReleaseDate = 04/09/2025
SystemManufacturer = Micro-Star International Co., Ltd.
SystemProductName = MS-7D91
SystemFamily = Default string
SystemVersion = 4.0
SystemSKU = Default string
BaseBoardManufacturer = Micro-Star International Co., Ltd.
BaseBoardProduct = MAG Z790 TOMAHAWK WIFI (MS-7D91)
BaseBoardVersion = 4.0

W
wahleno
Member
243
05-03-2023, 11:45 AM
#5
Hey johnbl, you also managed to fix the problem with your Razer mouse.
It was a corruption issue as well. Could this be due to a hardware fault or related to the drivers?

The webcam is connected to Vimicro Corporation, which is quite old—around 2006.
Current Speed 3465MHz (that’s an unusual number) — is this the speed of the CPU or RAM?

I deleted Dell’s software for my monitor; it saved the settings, but I think a corrupted file (DPMDriver.sys) was removed.
DellInstrumentation.sys was linked to the Dell Peripheral and Monitor app.
win32kfull.sys (checksum removed).
An overclock driver was installed:
C:\Program Files (x86)\MSI Afterburner\RTCore64.sys Sun Apr 14 04:53:16 2024
C:\Program Files (x86)\FanControl\FanControl.sys Sat Jul 26 06:29:37 2008

I need these files to manage the fans and temperatures.
Suspected drivers: vvftav303.sys (Fri Jun 22 22:46:10 2007), usbVM303.sys (Sat Mar 24 21:26:25 2007),
FocusritePCIeSwRoot.sys (Thu Sep 19 06:07:05 2024), FocusriteUsb.sys, FocusriteUsbAudio.sys, FocusriteUsbSwRoot.sys.

This one is confusing—I’m using a Focusrite Scarlett 2i2 3rd gen as my audio card and installed the drivers for it, then deleted all unnecessary files. It seems to be working fine now.
Also, how should I proceed?

If you can’t solve this, consider:
Turn off virtual memory, restart, then turn it back on to delete pagefile.sys, and enable verifier flags. This should force Windows to run bugcheck immediately when the heap is corrupted, rather than waiting until cleanup routines are triggered later.
Should I switch it off and on? Or perhaps restart your PC and then turn it back on?
W
wahleno
05-03-2023, 11:45 AM #5

Hey johnbl, you also managed to fix the problem with your Razer mouse.
It was a corruption issue as well. Could this be due to a hardware fault or related to the drivers?

The webcam is connected to Vimicro Corporation, which is quite old—around 2006.
Current Speed 3465MHz (that’s an unusual number) — is this the speed of the CPU or RAM?

I deleted Dell’s software for my monitor; it saved the settings, but I think a corrupted file (DPMDriver.sys) was removed.
DellInstrumentation.sys was linked to the Dell Peripheral and Monitor app.
win32kfull.sys (checksum removed).
An overclock driver was installed:
C:\Program Files (x86)\MSI Afterburner\RTCore64.sys Sun Apr 14 04:53:16 2024
C:\Program Files (x86)\FanControl\FanControl.sys Sat Jul 26 06:29:37 2008

I need these files to manage the fans and temperatures.
Suspected drivers: vvftav303.sys (Fri Jun 22 22:46:10 2007), usbVM303.sys (Sat Mar 24 21:26:25 2007),
FocusritePCIeSwRoot.sys (Thu Sep 19 06:07:05 2024), FocusriteUsb.sys, FocusriteUsbAudio.sys, FocusriteUsbSwRoot.sys.

This one is confusing—I’m using a Focusrite Scarlett 2i2 3rd gen as my audio card and installed the drivers for it, then deleted all unnecessary files. It seems to be working fine now.
Also, how should I proceed?

If you can’t solve this, consider:
Turn off virtual memory, restart, then turn it back on to delete pagefile.sys, and enable verifier flags. This should force Windows to run bugcheck immediately when the heap is corrupted, rather than waiting until cleanup routines are triggered later.
Should I switch it off and on? Or perhaps restart your PC and then turn it back on?

S
simon_allain
Junior Member
46
05-04-2023, 07:08 PM
#6
the usb from 2007 is quite outdated. if you need to use it, ensure the device is the sole component on its hub. specifications have evolved significantly for usb, so devices from before 2012 often encounter problems. these issues usually cause your usb port to malfunction, but newer machines route usb to the pci/e bus, which can render old drivers ineffective and disrupt connected devices.
S
simon_allain
05-04-2023, 07:08 PM #6

the usb from 2007 is quite outdated. if you need to use it, ensure the device is the sole component on its hub. specifications have evolved significantly for usb, so devices from before 2012 often encounter problems. these issues usually cause your usb port to malfunction, but newer machines route usb to the pci/e bus, which can render old drivers ineffective and disrupt connected devices.

X
xWaffleGaming
Member
69
05-19-2023, 09:36 AM
#7
I've removed my A4 Tech software, yet Device Manager still sees it and functions properly. I plan to purchase a new camera and install updated drivers. Are there other steps I can take while waiting?
X
xWaffleGaming
05-19-2023, 09:36 AM #7

I've removed my A4 Tech software, yet Device Manager still sees it and functions properly. I plan to purchase a new camera and install updated drivers. Are there other steps I can take while waiting?

B
Blue_Fox_Lady
Member
194
05-20-2023, 01:10 AM
#8
I think a heap corruption issue likely caused the previous bugcheck. You might enable verifier flags to try to identify the error and let the driver name be revealed by bugcheck. These problems usually arise when a program or service accesses kernel memory directly. This usually stops working until Windows adjusts how programs handle memory. (Assuming the old setup, you should restart before changes are made; now with sleep functions it happens more often)
B
Blue_Fox_Lady
05-20-2023, 01:10 AM #8

I think a heap corruption issue likely caused the previous bugcheck. You might enable verifier flags to try to identify the error and let the driver name be revealed by bugcheck. These problems usually arise when a program or service accesses kernel memory directly. This usually stops working until Windows adjusts how programs handle memory. (Assuming the old setup, you should restart before changes are made; now with sleep functions it happens more often)

R
RAToast
Junior Member
14
05-21-2023, 05:51 PM
#9
there are still concerns about a thermal issue with the CPU and undervolting might be the main problem. check the BIOS update and consider running an RMA for the CPU.
R
RAToast
05-21-2023, 05:51 PM #9

there are still concerns about a thermal issue with the CPU and undervolting might be the main problem. check the BIOS update and consider running an RMA for the CPU.

S
Sahrend
Member
55
05-25-2023, 08:58 PM
#10
I purchased my PC components 3-4 weeks ago, and even before setting up my CPU or starting up, I updated the BIOS to the newest version (using the MSI USB flash method). Therefore, it's a fresh CPU, and it has already booted with the latest BIOS. Could there still be problems?
S
Sahrend
05-25-2023, 08:58 PM #10

I purchased my PC components 3-4 weeks ago, and even before setting up my CPU or starting up, I updated the BIOS to the newest version (using the MSI USB flash method). Therefore, it's a fresh CPU, and it has already booted with the latest BIOS. Could there still be problems?

Pages (3): 1 2 3 Next