BSOD Issue

Superwooper10 · April 15, 2022

OS - Windows: 10
64 Bit
What OS was originaly installed on the system? Windows 10
Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from a retailer)? Came pre-installed
Age of system (hardware) 1 Year, 3 Months
Age of OS installation - have you re-installed the OS? Yes. March 11th of this year(3 months)
CPU model: AMD Ryzen 7 4800H with Radeon Graphics @ 2.90 GHz
Video Card model: Nvidia GeForce RTX 2060
~~MotherBoard - (if NOT a laptop)~~
~~Power Supply - brand & wattage (if laptop, skip this)~~
System Manufacturer: ASUS
Exact model number (if OEM or laptop): ASUS TUF Gaming A15 FA506IV_FA506IV
Laptop or Desktop? Laptop.

So i've had this issue for almost a whole year when I purchased the laptop and it doesn't seem to like VR. I've crashed multiple times, and i've even logged mostly everything manually to what the crash was, but I rarely got a reasion as to why it crashed. Sometimes it'd just crash with "irql_not_less_or_equal", "kmode_exception_not_handled", "system_service_exception", and a few other annoying issues. IRQL it the most frequent, but this time when i'm just using it as normal, i'll sometimes get a blue screen for no reason. I'm just wondering, is there any idea on how to even fix this? At this point I was going to mark this laptop as obsolete and just get a new one, or something like that. This has crashed too much on me whenever i'm in VR and I don't even think this laptop is even VR Ready like it was listed. Paying 1200$ for this laptop for nothing? Egh. I hate it now. As a matter of fact, i'll put the recent crash it gave and i'll include a crash that happened a while ago whenever i'm in VR. Also I tried the system diagnostics, but it didn't give the file after 20 minutes.

https://drive.google.com/file/d/1mTgu2Vvju42HJa4bWAJD0g5JcZlxU2L7/view?usp=sharing

Bombastinator · April 15, 2022

50 minutes ago, Superwooper10 said:

OS - Windows: 10

64 Bit

What OS was originaly installed on the system? Windows 10

Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from a retailer)? Came pre-installed

Age of system (hardware) 1 Year, 3 Months

Age of OS installation - have you re-installed the OS? Yes. March 11th of this year(3 months)

CPU model: AMD Ryzen 7 4800H with Radeon Graphics @ 2.90 GHz

Video Card model: Nvidia GeForce RTX 2060

~~MotherBoard - (if NOT a laptop)~~

~~Power Supply - brand & wattage (if laptop, skip this)~~

System Manufacturer: ASUS

Exact model number (if OEM or laptop): ASUS TUF Gaming A15 FA506IV_FA506IV

Laptop or Desktop? Laptop.

So i've had this issue for almost a whole year when I purchased the laptop and it doesn't seem to like VR. I've crashed multiple times, and i've even logged mostly everything manually to what the crash was, but I rarely got a reasion as to why it crashed. Sometimes it'd just crash with "irql_not_less_or_equal", "kmode_exception_not_handled", "system_service_exception", and a few other annoying issues. IRQL it the most frequent, but this time when i'm just using it as normal, i'll sometimes get a blue screen for no reason. I'm just wondering, is there any idea on how to even fix this? At this point I was going to mark this laptop as obsolete and just get a new one, or something like that. This has crashed too much on me whenever i'm in VR and I don't even think this laptop is even VR Ready like it was listed. Paying 1200$ for this laptop for nothing? Egh. I hate it now. As a matter of fact, i'll put the recent crash it gave and i'll include a crash that happened a while ago whenever i'm in VR. Also I tried the system diagnostics, but it didn't give the file after 20 minutes.

https://drive.google.com/file/d/1mTgu2Vvju42HJa4bWAJD0g5JcZlxU2L7/view?usp=sharing

A. Which VR software?

B. Do you run anything besides VR software on it? If so what? VR software can push machines really hard. Is it the only thing you do that does that?

C. Is anything overclocked?

Superwooper10 · April 15, 2022

10 hours ago, Bombastinator said:

A. Which VR software?

B. Do you run anything besides VR software on it? If so what? VR software can push machines really hard. Is it the only thing you do that does that?

C. Is anything overclocked?

A: Oculus. I'm using a Oculus Rift CV1 to use the Oculus Software.

B: Nothing I can think of. Whenever I start VR, SteamVR starts up with it and I have usually space calibrator on as well for my tracking.

C: Nope. I don't think so.

Also I forgot abotu putting an additional bit in for another crash that is a different thing, but it always crashes whenever I start it up regardless.

Bombastinator · April 15, 2022

4 hours ago, Superwooper10 said:

A: Oculus. I'm using a Oculus Rift CV1 to use the Oculus Software.

B: Nothing I can think of. Whenever I start VR, SteamVR starts up with it and I have usually space calibrator on as well for my tracking.

C: Nope. I don't think so.

Also I forgot abotu putting an additional bit in for another crash that is a different thing, but it always crashes whenever I start it up regardless.

If that’s all you run it could be it just does this. Your system might be unstable generally. Without an unstable overclock to screw things up my first two hardware suspect (might not be hardware) are memory and PSU. Memory is at least easy to check. The Microsoft memory tester is famous for sucking, so memtest86+ may be your best initial bet. It can throw false negatives too, but far less of them. The gold standard test (which takes even longer than memtest86+ which isn’t quick) is an old school thing that only works on multiple ram sticks and runs under the assumption that bad memory is so rare that the chances of both sticks being bad approaches zero. You put in just one ram stick (yes it will run very slowly) and see if you get crashes. Either way you then stick in the other. If crashes stop when you remove sticks, the stick you did not remove is the one that is bad. If it cleans up on both you had a badly installed stick and if it cleans up on neither it’s a different problem.

Superwooper10 · April 16, 2022

2 hours ago, Bombastinator said:

If that’s all you run it could be it just does this. Your system might be unstable generally. Without an unstable overclock to screw things up my first two hardware suspect (might not be hardware) are memory and PSU. Memory is at least easy to check. The Microsoft memory tester is famous for sucking, so memtest86+ may be your best initial bet. It can throw false negatives too, but far less of them. The gold standard test (which takes even longer than memtest86+ which isn’t quick) is an old school thing that only works on multiple ram sticks and runs under the assumption that bad memory is so rare that the chances of both sticks being bad approaches zero. You put in just one ram stick (yes it will run very slowly) and see if you get crashes. Either way you then stick in the other. If crashes stop when you remove sticks, the stick you did not remove is the one that is bad. If it cleans up on both you had a badly installed stick and if it cleans up on neither it’s a different problem.

Well, this is a laptop, and I just got two new sticks of 8GB Kingston RAM, so I doubt it could be that. I don't even know what else is causing it. Sometimes it's IRQL all the time. Does it identify my headset's version and pretty much just crashes over that? I was gonna roll back the BIOS to where it never crashed at all, but really I just wanna sell this laptop and buy a newer one. It's exactly like this one, but it has a nvidia and intel core in it, so I don't know if that's better than what I have. As for the power, it's using a 100~240V input/19.5v=11.8A 230w power brick.

Bombastinator · April 16, 2022

30 minutes ago, Superwooper10 said:

Well, this is a laptop, and I just got two new sticks of 8GB Kingston RAM, so I doubt it could be that. I don't even know what else is causing it. Sometimes it's IRQL all the time. Does it identify my headset's version and pretty much just crashes over that? I was gonna roll back the BIOS to where it never crashed at all, but really I just wanna sell this laptop and buy a newer one. It's exactly like this one, but it has a nvidia and intel core in it, so I don't know if that's better than what I have. As for the power, it's using a 100~240V input/19.5v=11.8A 230w power brick.

Did the problem exist before the new ram was installed? There are only two things there: hardware and software. If it’s not hardware it’s software so there is a corruption or a conflict. (Tiny chance of malware but considering the behavior even that is a conflict) Corruptions need to be rewritten with clean code, conflicts need to be resolved, usually by removing one of the conflicting items. Corruptions don’t always have to be found, they can just be wholesale rewritten. Conflicts can be more annoying if you don’t want to simply remove everything which often defeats the purpose of even having the thing. If it’s a conflict the issue will have started immediately after something was loaded, though corruptions can do that too. Memory boogers just happen randomly. Sometimes in memory that has been good for years. Something about cosmic rays or I don’t know what. Memory boogers have a pattern though which your issue may fit. Boogered memory works fine until the boogered point is accessed, and then blue screens happen. If it’s high up in the address stack and one doesn’t normally use that much memory, one may never see them. This is part of what the single stick thing does. It fills up the memory because there’s less of it.

Superwooper10 · April 16, 2022

2 hours ago, Bombastinator said:

Did the problem exist before the new ram was installed? There are only two things there: hardware and software. If it’s not hardware it’s software so there is a corruption or a conflict. (Tiny chance of malware but considering the behavior even that is a conflict) Corruptions need to be rewritten with clean code, conflicts need to be resolved, usually by removing one of the conflicting items. Corruptions don’t always have to be found, they can just be wholesale rewritten. Conflicts can be more annoying if you don’t want to simply remove everything which often defeats the purpose of even having the thing. If it’s a conflict the issue will have started immediately after something was loaded, though corruptions can do that too. Memory boogers just happen randomly. Sometimes in memory that has been good for years. Something about cosmic rays or I don’t know what. Memory boogers have a pattern though which your issue may fit. Boogered memory works fine until the boogered point is accessed, and then blue screens happen. If it’s high up in the address stack and one doesn’t normally use that much memory, one may never see them. This is part of what the single stick thing does. It fills up the memory because there’s less of it.

Yup. It still stuck around even when I completely deleted the Windows OS and reinstalled it, resetting it, and nothing still worked. Does the crash log bring up anything? I don't even know what it's fussing over and I don't know what to do at this point.

Bombastinator · April 16, 2022

2 hours ago, Superwooper10 said:

Yup. It still stuck around even when I completely deleted the Windows OS and reinstalled it, resetting it, and nothing still worked. Does the crash log bring up anything? I don't even know what it's fussing over and I don't know what to do at this point.

So hardware not software apparently. And probably not cpu memory. Generally hardware problems mean a machine won’t even post though as they affect the bios as well as windows. The impression I get is the thing works fine until you try to run something. Could be heat. Are you getting high temps? You could confirm the hardware theory by running a liveCD off a USB key if you have one around. If it crashes then it not only has to be hardware it’s not the drive. You’ve got an APU apparently, so you could check gpu memory by pulling the video card and see if the problem goes away. AGPs use cpu memory.

Superwooper10 · April 16, 2022

8 minutes ago, Bombastinator said:

So hardware not software apparently. And probably not cpu memory. Generally hardware problems mean a machine won’t even post though as they affect the bios as well as windows. The impression I get is the thing works fine until you try to run something. Could be heat. Are you getting high temps? You could confirm the hardware theory by running a liveCD off a USB key if you have one around. If it crashes then it not only has to be hardware it’s not the drive. You’ve got an APU apparently, so you could check gpu memory by pulling the video card and see if the problem goes away. AGPs use cpu memory.

Usually playing Beat Saber or VRChat, the Nvidia's temp caps at 86c while AMD is right behind it at about 79c. Even if I lift it off the table to get proper cooling, it still fails to keep the system cool. Some people say these ASUS TUF laptops have poor cooling since the bottom casing for these are choking off a lot of cooling. And last time it crashed, I was just minding my own buisiness watching videos and it just blue screened out of nowhere. It's done this twice this week, so I guess the computer itself is just bad. And I can't pull the video card out. It's in a laptop. Everything's sorta connected in, unless i'm seeing that wrong.

Bombastinator · April 16, 2022

8 hours ago, Superwooper10 said:

Usually playing Beat Saber or VRChat, the Nvidia's temp caps at 86c while AMD is right behind it at about 79c. Even if I lift it off the table to get proper cooling, it still fails to keep the system cool. Some people say these ASUS TUF laptops have poor cooling since the bottom casing for these are choking off a lot of cooling. And last time it crashed, I was just minding my own buisiness watching videos and it just blue screened out of nowhere. It's done this twice this week, so I guess the computer itself is just bad. And I can't pull the video card out. It's in a laptop. Everything's sorta connected in, unless i'm seeing that wrong.

That’s not all that hot for a laptop. My suspicion would be “no” to heat then. Next step would be to check for conflicts then. Do you run any less common software? I don’t remember where win10 keeps it’s logs. It’s an app in administrative tools but I don’t remember which one.

Superwooper10 · April 16, 2022

1 hour ago, Bombastinator said:

That’s not all that hot for a laptop. My suspicion would be “no” to heat then. Next step would be to check for conflicts then. Do you run any less common software? I don’t remember where win10 keeps it’s logs. It’s an app in administrative tools but I don’t remember which one.

Would that be the Event Viewer? The only thing that comes to mind is my Open Space Calibrator for my full body tracking since I only have one base station, and I have to manually put it to where I am. Then I have a Voicemeter to amplify my mic since it's been sounding more quiet.

Bombastinator · April 16, 2022

1 hour ago, Superwooper10 said:

Would that be the Event Viewer? The only thing that comes to mind is my Open Space Calibrator for my full body tracking since I only have one base station, and I have to manually put it to where I am. Then I have a Voicemeter to amplify my mic since it's been sounding more quiet.

That’s one. My memory is there are two. One has to be started though as it’s a recording thing and default is do not record. Apparently it’s not often needed and the recording files eventually get large. The voice meter thing would have gone on later. Did it’s installation coincide with the start of problems? These symptoms are very common with unstable overclocks or memory issues. This whole occasional blue screen but otherwise works fine thing implies something is functioning but only barely. I hope open space calibrator isn’t the problem as that may be hard to do without.

Superwooper10 · April 16, 2022

1 hour ago, Bombastinator said:

That’s one. My memory is there are two. One has to be started though as it’s a recording thing and default is do not record. Apparently it’s not often needed and the recording files eventually get large. The voice meter thing would have gone on later. Did it’s installation coincide with the start of problems? These symptoms are very common with unstable overclocks or memory issues. This whole occasional blue screen but otherwise works fine thing implies something is functioning but only barely. I hope open space calibrator isn’t the problem as that may be hard to do without.

At the moment, I don't know. I have to manually start it up since I disabled everything from starting up when I login. But really all i'm saying is, I have no idea what's causing the crashing issue to come up.

Superwooper10 · April 17, 2022

7 hours ago, Superwooper10 said:

At the moment, I don't know. I have to manually start it up since I disabled everything from starting up when I login. But really all i'm saying is, I have no idea what's causing the crashing issue to come up.

I'm just gonna put this with it to show you what i'm dealing with. I tried everything, and this is all its giving. At this point, i'm going to just scrap it and wait to save up for a new laptop, because I have no clue at the moment on what to resolve, and i'm too livid. I just need an answer to WHO'S crashing my computer, not resolving multiple things on what's open and closed. This crashed while in VRChat.

Spoiler

*******************************************************************************
* *
* 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: ffffffffffffff8b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80178e885d5, address which referenced memory

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1781

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 1789

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

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

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

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: a

BUGCHECK_P1: ffffffffffffff8b

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff80178e885d5

WRITE_ADDRESS: fffff801798fb390: 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
ffffffffffffff8b

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: VRChat.exe

TRAP_FRAME: ffff888736dfe4f0 -- (.trap 0xffff888736dfe4f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=000000000000000c rsi=0000000000000000 rdi=0000000000000000
rip=fffff80178e885d5 rsp=ffff888736dfe680 rbp=ffff888736dfe761
r8=0000000000001200 r9=fffff80179925440 r10=000000000000ffff
r11=ffffc8004d0e0180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiChooseTargetProcessor+0x265:
fffff801`78e885d5 00488b add byte ptr [rax-75h],cl ds:ffffffff`ffffff8b=??
Resetting default scope

MISALIGNED_IP:
nt!KiChooseTargetProcessor+265
fffff801`78e885d5 00488b add byte ptr [rax-75h],cl

STACK_TEXT:
ffff8887`36dfe3a8 fffff801`79009869 : 00000000`0000000a ffffffff`ffffff8b 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffff8887`36dfe3b0 fffff801`79005b69 : ffff4548`5525ab58 00000000`00000000 00000000`0001201f 00000000`00000001 : nt!KiBugCheckDispatch+0x69
ffff8887`36dfe4f0 fffff801`78e885d5 : ffffc800`4d066180 ffffc800`4d066180 ffff8887`36dfe761 fffff801`78ffeab2 : nt!KiPageFault+0x469
ffff8887`36dfe680 fffff801`78e876db : 00000000`00000000 ffffa002`af1f4080 00000000`00000009 55555555`55555555 : nt!KiChooseTargetProcessor+0x265
ffff8887`36dfe7c0 fffff801`78e87191 : 00000000`00000000 fffff801`791f6d01 ffffc800`4d066180 00000000`00000001 : nt!KiDeferredReadySingleThread+0x28b
ffff8887`36dfe9b0 fffff801`78f28080 : 00000000`00000000 00000000`00000000 ffffa002`af10ec60 ffffa002`b11b31c0 : nt!KiExitDispatcher+0x141
ffff8887`36dfea20 fffff801`792d77db : 00000000`00000000 00000000`00000000 ffff8887`36dfeb80 ffffa002`af10ec60 : nt!KeReleaseSemaphore+0x110
ffff8887`36dfeaa0 fffff801`790092b8 : ffffa002`ac382080 00000000`000000b0 00000000`00000000 ffff8887`36dfeb01 : nt!NtReleaseSemaphore+0x9b
ffff8887`36dfeb00 00007ffe`321cceb4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000001b`7b6edf58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`321cceb4

SYMBOL_NAME: nt!KiChooseTargetProcessor+265

IMAGE_NAME: hardware

IMAGE_VERSION: 10.0.19041.1620

STACK_COMMAND: .thread ; .cxr ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {201b0e5d-db2a-63d2-77be-8ce8ff234750}

Followup: MachineOwner
---------

Bombastinator · April 17, 2022

Reading that it looks like a driver corruption.

Superwooper10 · April 17, 2022

7 hours ago, Bombastinator said:

Reading that it looks like a driver corruption.

Welp! Any idea who's causing the issue?

Bombastinator · April 17, 2022

23 minutes ago, Superwooper10 said:

Welp! Any idea who's causing the issue?

As in which driver? I don’t remember if the thing said or not.

Superwooper10 · April 17, 2022

Just now, Bombastinator said:

As in which driver? I don’t remember if the thing said or not.

Ah, okay. Yeahh that's kinda what i'm getting sometimes. When I blue screen, they don't give a reason as to why it crashed. It just give s a random crash error, and then I had to restart. The only things it rarely gave for a reason was afd.sys, Dxgmms2.sys, Wdf01000.sys, Amdppm.sys, and Wpprecorder.sys. These all crashed around 3/11/22-4/12/22. I have the whole manual listing I typed out.

Bombastinator · April 18, 2022

3 hours ago, Superwooper10 said:

Ah, okay. Yeahh that's kinda what i'm getting sometimes. When I blue screen, they don't give a reason as to why it crashed. It just give s a random crash error, and then I had to restart. The only things it rarely gave for a reason was afd.sys, Dxgmms2.sys, Wdf01000.sys, Amdppm.sys, and Wpprecorder.sys. These all crashed around 3/11/22-4/12/22. I have the whole manual listing I typed out.

The way I myself would probably go with this one (not that it’s the best way, it’s merely what I would personally do if I found myself in this situation is in the words of Ripley:” nuke the site from orbit. It’s the only way to be sure” try booting in safe mode and see if it’s still unstable. Safe mode deactivates all drivers and replaces them with well known ol vanilla things that are known to work. If this works it’s a corrupt driver.

Superwooper10 · April 18, 2022

21 hours ago, Bombastinator said:

The way I myself would probably go with this one (not that it’s the best way, it’s merely what I would personally do if I found myself in this situation is in the words of Ripley:” nuke the site from orbit. It’s the only way to be sure” try booting in safe mode and see if it’s still unstable. Safe mode deactivates all drivers and replaces them with well known ol vanilla things that are known to work. If this works it’s a corrupt driver.

I tried a special thing that lets me start it up via just the drivers, and it gave me a blue screen loop. I saw this far below. Guess my audios' the fault. This crash was "Driver Verifier Detected Violation"

Spoiler

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000002000, Code Integrity Issue: The caller specified an executable pool type. (Expected: NonPagedPoolNx)
Arg2: fffff800007f91ba, The address in the driver's code where the error was detected.
Arg3: 0000000000000000, Pool Type.
Arg4: 0000000072436350, Pool Tag (if provided).

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

*** WARNING: Unable to verify timestamp for vbaudio_vmvaio64_win10.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2312

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 2749

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

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

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

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: c4

BUGCHECK_P1: 2000

BUGCHECK_P2: fffff800007f91ba

BUGCHECK_P3: 0

BUGCHECK_P4: 72436350

BLACKBOXNTFS: 1 (!blackboxntfs)

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff9e8d`48f44898 fffff801`36fd0e24 : 00000000`000000c4 00000000`00002000 fffff800`007f91ba 00000000`00000000 : nt!KeBugCheckEx
ffff9e8d`48f448a0 fffff801`36b9f235 : fffff801`37214c8c 00000000`00002000 fffff800`007f91ba 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0xe0
ffff9e8d`48f448e0 fffff801`36fc7de4 : 00000000`72436350 fffff801`37214c8c fffff800`007f91ba 003b0025`0065006d : nt!VfReportIssueWithOptions+0x101
ffff9e8d`48f44930 fffff801`36fd5032 : 00000000`00000000 ffffca0a`308c58e0 00000000`00000050 00000000`00000000 : nt!VfCheckPoolType+0x90
ffff9e8d`48f44970 fffff800`007f91ba : 00000000`00000050 00000000`00000000 ffffca0a`308d3050 01000000`00100000 : nt!VerifierExAllocatePoolWithTag+0x62
ffff9e8d`48f449c0 00000000`00000050 : 00000000`00000000 ffffca0a`308d3050 01000000`00100000 fffff801`36fb4140 : vbaudio_vmvaio64_win10+0x91ba
ffff9e8d`48f449c8 00000000`00000000 : ffffca0a`308d3050 01000000`00100000 fffff801`36fb4140 fffff80f`f5a12553 : 0x50

SYMBOL_NAME: vbaudio_vmvaio64_win10+91ba

MODULE_NAME: vbaudio_vmvaio64_win10

IMAGE_NAME: vbaudio_vmvaio64_win10.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 91ba

FAILURE_BUCKET_ID: 0xc4_2000_vbaudio_vmvaio64_win10!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e9a1b15c-1205-9fe4-156e-b5dd9896f1e8}

Followup: MachineOwner
---------

Superwooper10 · April 20, 2022

I fixed the constant crash loop, but it still crashes at this point.

Superwooper10 · April 21, 2022

On 4/17/2022 at 8:01 PM, Bombastinator said:

The way I myself would probably go with this one (not that it’s the best way, it’s merely what I would personally do if I found myself in this situation is in the words of Ripley:” nuke the site from orbit. It’s the only way to be sure” try booting in safe mode and see if it’s still unstable. Safe mode deactivates all drivers and replaces them with well known ol vanilla things that are known to work. If this works it’s a corrupt driver.

So seeing as how it crashes in VR without the headset, this is what it threw. Looks like it's just software issues...

Spoiler

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8042f7f7108, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 00000000001f0002, Parameter 1 of the exception

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2093

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 3309

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

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

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

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8042f7f7108

BUGCHECK_P3: 1

BUGCHECK_P4: 1f0002

WRITE_ADDRESS: fffff8042fefb390: 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
00000000001f0002

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 00000000001f0002

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: VRChat.exe

TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

STACK_TEXT:
fffffd87`1d778f48 fffff804`2f65a5cb : 00000000`0000001e ffffffff`c0000005 fffff804`2f7f7108 00000000`00000001 : nt!KeBugCheckEx
fffffd87`1d778f50 fffff804`2f6099ac : 00000000`00001000 fffffd87`1d7797f0 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x174bbb
fffffd87`1d779610 fffff804`2f605b43 : ffffe309`3f28b080 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x12c
fffffd87`1d7797f0 fffff804`2f7f7108 : 00000000`00000000 ffffe309`3f28b1c0 fffffd87`1d7799e0 00000000`00000000 : nt!KiPageFault+0x443
fffffd87`1d779980 00000000`00000000 : ffffe309`3f28b1c0 fffffd87`1d7799e0 00000000`00000000 00000000`00040000 : nt!ExpLookupHandleTableEntry+0x48

SYMBOL_NAME: nt!ExpLookupHandleTableEntry+48

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1645

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 48

FAILURE_BUCKET_ID: 0x1E_c0000005_W_nt!ExpLookupHandleTableEntry

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d53fa430-2ad8-0df0-1b21-db9495ba137b}

Followup: MachineOwner
---------

Bombastinator · April 21, 2022

32 minutes ago, Superwooper10 said:

So seeing as how it crashes in VR without the headset, this is what it threw. Looks like it's just software issues...

Hide contents

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8042f7f7108, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 00000000001f0002, Parameter 1 of the exception

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2093

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 3309

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

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

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

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8042f7f7108

BUGCHECK_P3: 1

BUGCHECK_P4: 1f0002

WRITE_ADDRESS: fffff8042fefb390: 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
00000000001f0002

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 00000000001f0002

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: VRChat.exe

TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

STACK_TEXT:
fffffd87`1d778f48 fffff804`2f65a5cb : 00000000`0000001e ffffffff`c0000005 fffff804`2f7f7108 00000000`00000001 : nt!KeBugCheckEx
fffffd87`1d778f50 fffff804`2f6099ac : 00000000`00001000 fffffd87`1d7797f0 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x174bbb
fffffd87`1d779610 fffff804`2f605b43 : ffffe309`3f28b080 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x12c
fffffd87`1d7797f0 fffff804`2f7f7108 : 00000000`00000000 ffffe309`3f28b1c0 fffffd87`1d7799e0 00000000`00000000 : nt!KiPageFault+0x443
fffffd87`1d779980 00000000`00000000 : ffffe309`3f28b1c0 fffffd87`1d7799e0 00000000`00000000 00000000`00040000 : nt!ExpLookupHandleTableEntry+0x48

SYMBOL_NAME: nt!ExpLookupHandleTableEntry+48

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1645

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 48

FAILURE_BUCKET_ID: 0x1E_c0000005_W_nt!ExpLookupHandleTableEntry

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d53fa430-2ad8-0df0-1b21-db9495ba137b}

Followup: MachineOwner
---------

That’s why a nuclear option works. It’s not that critical to find where the problem is if you just replace stuff wholesale. If the safe mode thing throws problems you replace windows. If it doesn’t you replace all the drivers. Or you could just go and replace all of it. The standard way to replace corrupt software is to write over it with uncorrupted stuff.

Superwooper10 · April 21, 2022

13 hours ago, Bombastinator said:

That’s why a nuclear option works. It’s not that critical to find where the problem is if you just replace stuff wholesale. If the safe mode thing throws problems you replace windows. If it doesn’t you replace all the drivers. Or you could just go and replace all of it. The standard way to replace corrupt software is to write over it with uncorrupted stuff.

This is gonna be hard. I heard of those Bloatwares and such that "download" the latest drivers and replace them. I don't even know if those work, or are they just fake programs that give bloatware.

innoBius · April 21, 2022

1 hour ago, Superwooper10 said:

This is gonna be hard. I heard of those Bloatwares and such that "download" the latest drivers and replace them. I don't even know if those work, or are they just fake programs that give bloatware.

Go to the source. For nvidia drivers, go to nvidia etc

Sign In

BSOD Issue

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites