F5F Stay Refreshed Hardware Desktop No worries, everything looks good. Just a routine check yesterday.

No worries, everything looks good. Just a routine check yesterday.

No worries, everything looks good. Just a routine check yesterday.

S
Skro74
Junior Member
37
07-01-2016, 07:27 AM
#1
While capturing my desktop with Camtasia, I encountered this BSOD (error code 0x0000003b) right away when I stopped recording. I kept doing many retakes because it was hard to speak clearly, and I’m wondering if the recording conflicted with previous ones or if something unexpected happened. I hope my computer is working properly and everything is stable.
S
Skro74
07-01-2016, 07:27 AM #1

While capturing my desktop with Camtasia, I encountered this BSOD (error code 0x0000003b) right away when I stopped recording. I kept doing many retakes because it was hard to speak clearly, and I’m wondering if the recording conflicted with previous ones or if something unexpected happened. I hope my computer is working properly and everything is stable.

V
vilkkuPVP
Junior Member
8
07-02-2016, 07:42 PM
#2
From my perspective, a single blue screen isn't something to stress over. When multiple ones appear one after another, it's time to look into the matter.
V
vilkkuPVP
07-02-2016, 07:42 PM #2

From my perspective, a single blue screen isn't something to stress over. When multiple ones appear one after another, it's time to look into the matter.

J
julien190901
Member
192
07-08-2016, 10:30 PM
#3
Occasional BSODs are acceptable, but repeated occurrences within a short time frame suggest a problem that requires investigation.
J
julien190901
07-08-2016, 10:30 PM #3

Occasional BSODs are acceptable, but repeated occurrences within a short time frame suggest a problem that requires investigation.

I
IceBjornn
Member
98
07-13-2016, 09:02 PM
#4
bsod indicates a hardware problem with the driver, specifically overclocking. It often appears under unusual circumstances such as Windows issues, especially if the system isn't compatible with the current Windows version. This type of error is rare and usually documented. Using a main system for Windows development builds is discouraged by Microsoft. The error code shown is in all caps and can be analyzed using tools like Microsoft WinDgb or Nirsoft Blue Screen View. Documentation exists for BSODs, and if you have the hex code, Microsoft provides guidance. BSODs should never happen on any system and are not considered normal.
I
IceBjornn
07-13-2016, 09:02 PM #4

bsod indicates a hardware problem with the driver, specifically overclocking. It often appears under unusual circumstances such as Windows issues, especially if the system isn't compatible with the current Windows version. This type of error is rare and usually documented. Using a main system for Windows development builds is discouraged by Microsoft. The error code shown is in all caps and can be analyzed using tools like Microsoft WinDgb or Nirsoft Blue Screen View. Documentation exists for BSODs, and if you have the hex code, Microsoft provides guidance. BSODs should never happen on any system and are not considered normal.

R
ricby
Senior Member
681
07-13-2016, 10:45 PM
#5
XMP is activated in your BIOS, but it might be linked to the issue. The article suggests it could affect RAM or HDD performance, though your drive info looks normal.
R
ricby
07-13-2016, 10:45 PM #5

XMP is activated in your BIOS, but it might be linked to the issue. The article suggests it could affect RAM or HDD performance, though your drive info looks normal.

G
Gabokazu
Posting Freak
814
07-14-2016, 06:36 AM
#6
Sorry for the disappointment, but my C drive root contained this crash dump file. I hope you can examine it and continue with DumpStack.log.
G
Gabokazu
07-14-2016, 06:36 AM #6

Sorry for the disappointment, but my C drive root contained this crash dump file. I hope you can examine it and continue with DumpStack.log.

S
Shibouh
Senior Member
369
07-15-2016, 04:49 PM
#7
Find the generated mini dump in the specified folder: C:\Windows\Minidump
S
Shibouh
07-15-2016, 04:49 PM #7

Find the generated mini dump in the specified folder: C:\Windows\Minidump

F
FoxRidgePonies
Junior Member
4
07-24-2016, 04:52 AM
#8
110522-9734-01.dmp
F
FoxRidgePonies
07-24-2016, 04:52 AM #8

110522-9734-01.dmp

T
Tuzuu
Junior Member
19
07-25-2016, 01:19 PM
#9
The mini-dump indicates you were using Windows 10 Build 22621 - 64-bit. Your system operated for about 54 minutes before the crash started. The BSOD happened while the computer was active, not during sleep or shutdown. Error code: SYSTEM_SERVICE_EXCEPTION with details provided. The cause appears to be an Nvidia audio driver file, specifically nvrtxvad64v.sys. The process running at the time was NVIDIA RTX Voice, likely trying to access your microphone. No disk read/write errors were recorded. This information comes from Microsoft's WinDbg tool. You can find more details here: https://www.microsoft.com/store/productId/9PGJGD53TN86
T
Tuzuu
07-25-2016, 01:19 PM #9

The mini-dump indicates you were using Windows 10 Build 22621 - 64-bit. Your system operated for about 54 minutes before the crash started. The BSOD happened while the computer was active, not during sleep or shutdown. Error code: SYSTEM_SERVICE_EXCEPTION with details provided. The cause appears to be an Nvidia audio driver file, specifically nvrtxvad64v.sys. The process running at the time was NVIDIA RTX Voice, likely trying to access your microphone. No disk read/write errors were recorded. This information comes from Microsoft's WinDbg tool. You can find more details here: https://www.microsoft.com/store/productId/9PGJGD53TN86

U
UltiPig
Member
55
07-25-2016, 01:42 PM
#10
It doesn't seem related to my hardware. I'm glad you're sure, though it could be a bug with the RTX voice feature—since it runs in the background and has access to my microphone.
U
UltiPig
07-25-2016, 01:42 PM #10

It doesn't seem related to my hardware. I'm glad you're sure, though it could be a bug with the RTX voice feature—since it runs in the background and has access to my microphone.