BSOD error code 0x0000001E keep crashing

batreky · Nov 27, 2013

ohhh no it's hard, long time configurations on this Software cause I used multi outputs Audio Speakers

, anyway did all the BSOD connected to each others ? cause the first one "0x0000001E" which is the only one that shows to me not those Via Driver Verifier !!!, can u Explain to me cause I'm starting to hate my PC

x BlueRobot · Nov 27, 2013

Code:

BugCheck D6, {fffff9800bd67018, 0, fffff88006602b15, 0}

Could not read faulting driver name
Probably caused by : portcls.sys ( portcls!GetMaxMapRegisters+5 )

This is quite a simple bugcheck, a driver has referenced and read memory beyond it's own pool allocation, and since this virtual memory is not part of the driver's address space, a invalid page fault has occurred.

Code:

0: kd> lmvm vrtaucbl

start             end                 module name
fffff880`067bd000 fffff880`067cba00   vrtaucbl T (no symbols)           
    Loaded symbol image file: vrtaucbl.sys
    Image path: \SystemRoot\system32\DRIVERS\vrtaucbl.sys
    Image name: vrtaucbl.sys
    Timestamp:        Mon Feb 15 17:07:10 2010 (4B797F3E)
    CheckSum:         0001BBDF
    ImageSize:        0000EA00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The above driver seems to be related to your Virtual Audio Cable (WDM) driver, I would suggest finding a updated version of the program it belongs to - Ventrilo - Download

Code:

.trap 0xfffff8800c0db090
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff9800bd66fc8
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88006602b15 rsp=fffff8800c0db228 rbp=fffffa8018963d90
 r8=0000000000000000  r9=fffff880067c6600 r10=fffff8800c0db2c0
r11=fffff8800c0db0f0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
portcls!GetMaxMapRegisters+0x5:
fffff880`06602b15 8b4150          mov     eax,dword ptr [rcx+50h] ds:fffff980`0bd67018=????????

Code:

0: kd> uf portcls!GetMaxMapRegisters+0x5
portcls!GetMaxMapRegisters+0x5:
fffff880`06602b15 8b4150          mov     eax,dword ptr [rcx+50h]
fffff880`06602b18 c3              ret

So, the instruction which has caused the problem, used a 64-bit integer pointer to point to the rcx register, and then move the address into the eax register.

Code:

0: kd> r.
Last set context:
eax=00000000`00000000  rcx=fffff980`0bd66fc8

x BlueRobot · Nov 27, 2013

Stop 0x1E indicates that exception (error) occurred which the exception handler couldn't handle.

batreky · Nov 27, 2013

So u mean the 0x1E is a multi BSOD errors that I catch them everything by Driver Verifier ?

batreky · Nov 27, 2013

Perfect I'll fix Virtual Audio Cable Soon :
Version 4.13 (23.07.13)

Fixed a bug preventing stream buffer watermark parameters from being loaded on restart.
Fixed bugs causing integer divide overflows in Audio Repeater (both MME and KS versions).
Added a workaround for PortCls bug causing BSOD (bugchecks 0x50 or 0xD6) in GetMaxMapRegisters function if Driver Verifier with the special pool is used for VAC driver verification.
Added peak signal level indicators to Control Panel.
Changed signal level indication in Audio Repeater from average to peak.
Fixed stream position timestamp error if PortCls is not used (occurred in Open Broadcaster Software).
Added a feature to control playback pin type (speaker or line out).
Fixed sleep/hibernate problems.
Added master volume control.

I used 4.10 Only

***New updates :

Version 4.10 (15.02.10) My Version

Added IPrefetchOffset interface support (more stable audio in XP/Vista/Server 2008/Win7).
Added a workaround to avoid Skype freezing and to stabilize streaming in heavy load cases. My problem
Changed voice reminder policy in trial version.
Added tray icon support to Audio Repeater.
Added Kernel Streaming version of Audio Repeater.
Added Wikipedia references in the user manual.
Fixed some bugs in volume control code.
Fixed a bug caused timer resolution restoration when a last cable stream was closed.
Added timer resolution correction on return from standby.
Added load splitting among CPUs/cores.
Added Authenticode digital signature from NTONYX.
Added instance closing feature to Audio Repeater.

***Version 4.11 (11.03.12)

Added cable multi-selection feature to Control Panel.
Clock correction precision increased to 0.0000001% (1E-8%). Now maybe it's the Only Problem from 4.10 Version :)
Added volume boost feature.
Fixed sampling rate change bug caused incorrect playback speed.
Rewritten data processing code from DPC to system thread set to minimize interlocked waiting and improve performance on multi-CPU/core systems.
Added stream buffer watermark control feature to improve stream stability.
Added "Reset counters" buttons (Control Panel) to reset cable/driver counters.
Minimum possible sampling rate increased from 200 to 1000.
Fixed a bug in KS Audio Repeater (device name string length was limited to 31 chars as in MME version).
Optimized KS Audio Repeater algorithms for more reliable transfer.
Added a feature to Audio Repeater: now command-line options can specify device number instead of its name to avoid name collisions if several adapters of the same type coexists.
Added several channel mixing/distribution schemes.
Added channel scatter/gather mode and cable channel mixing control.
Increased clock correction precision (registry value format is changed).
Added a privilege elevation manifest to Setup application to elevate privileges automatically.
Maximum sampling rate changed from 1000000 to 384000 in accordance with MS requirements.
Add "already installed" warning to Setup application.
Fixed some node property errors.
Fixed some minor bugs.

x BlueRobot · Nov 27, 2013

batreky said:
So u mean the 0x1E is a multi BSOD errors that I catch them everything by Driver Verifier ?

Driver Verifier only tests for certain conditions specified by the user, and supported by the Driver Verifier tool. A Stop 0x1E is a very general bugcheck, and can be caused by many different things. A exception is simply a error, or more specifically a type of data structure used to store information about an error, and is handled or caught by a exception handler, but in the case of a Stop 0x1E, the exception couldn't be handled with a try-catch statement.

Version 4.13 seems to address your problem :dsmile:

batreky · Nov 27, 2013

I'll Buy this Version as there is no Crack for it and will see what happens :), Thanks Patrick, X BlueRobot, jcgriff2 for all your help about my problem, So Soon I'll installed the V4.13 to fix my problem and will update this topic :), hope it will be the Only problem that cause the 0x1E BSOD...

x BlueRobot · Nov 27, 2013

Welcome, will look forward for an update.

batreky · Dec 1, 2013

Updates : I got an New BSOD via Driver Verifier after Fixing the old One with paid for a full Version of VAC 4.13 and now appears error 0x00000C4 addressed to Nvlddmkm.sys = NVidia Video drivers!!!!!!

Note : I installed the Latest Version 331.82 WHQL !!! Please What I can do then ? Also attached the Minidump

Patrick · Dec 1, 2013

The attached DMP file is of the DRIVER_VERIFIER_DETECTED_VIOLATION (c4) bug check.

This is the general bug check code for fatal errors found by Driver Verifier.

As you already noted, the driver it detected in violation was nvlddmkm.sys which is the nVidia video driver.

Given you're at the latest version right now, try installing a previous version or so, or possibly a beta if available. I actually just helped a friend with his BSOD's and I updated him to the beta driver and it fixed it. Give that a try if a beta is available for you.

Regards,

Patrick

batreky · Dec 1, 2013

NVIDIA Driver Downloads

Product	Current Installed Driver	Recommended Update
GeForce GTX 680	331.82	Your PC currently has the latest driver installed for your GPU. No driver update is necessary at this time.

Also No Beta's Found So may wait to the Next Update or Installing the previous version as u mention.

Thanks Patrick and will update this Topic Soon

TomasD · Dec 1, 2013

There actually is 331.93 Beta, though its changelog doesn't mention anything related to OS crashes.

batreky · Dec 1, 2013

TomasD said:
There actually is 331.93 Beta, though its changelog doesn't mention anything related to OS crashes.

Thanks So much for your reply, and also others previous version no Crashes So may I back to old Version ?

TomasD · Dec 1, 2013

batreky said:
Thanks So much for your reply, and also others previous version no Crashes So may I back to old Version ?

If there really are no crashes using the previous version, feel free to use it.

batreky · Dec 1, 2013

TomasD said:
batreky said:

Thanks So much for your reply, and also others previous version no Crashes So may I back to old Version ?

Click to expand...

If there really are no crashes using the previous version, feel free to use it.

Sorry for my English but not mean that. I mean that the last 10 Updates or more no Crashes fixes mentioned in there logs changes

Patrick · Dec 1, 2013

batreky said:
TomasD said:

batreky said:

Thanks So much for your reply, and also others previous version no Crashes So may I back to old Version ?

Click to expand...

If there really are no crashes using the previous version, feel free to use it.

Click to expand...

Sorry for my English but not mean that. I mean that the last 10 Updates or more no Crashes fixes mentioned in there logs changes

It's not so much that there are crash fixes mentioned in logs, but just potential system-specific issues and/or bugs with certain driver versions. If a user is crashing on the latest video card drivers, I always either recommend an install of a previous driver version to the latest (or a few behind), OR the beta driver. This way, if the user is still crashing, we know it's not on one specific driver version, or a possible buggy driver install to blame.

Regards,

Patrick

TomasD · Dec 1, 2013

batreky said:
Sorry for my English but not mean that. I mean that the last 10 Updates or more no Crashes fixes mentioned in there logs changes

Sorry for misunderstanding you. Anyhow, even official changelog for this Beta driver doesn't mention BSODs, there are users on forums reporting that this version fixed the BSODs they had. As Patrick suggested, give Beta driver a shot.

batreky · Dec 1, 2013

Thanks So much Patrick, TomasD for your help and will update this Soon

x BlueRobot · Dec 1, 2013

Code:

BugCheck C4, {f6, ac, fffffa8017bcb060, fffff8800f944879}

Probably caused by : nvlddmkm.sys ( nvlddmkm+9a879 )

I'm not sure if anyone has noticed, but that driver has caused the exact same problem, as seen in this thread - https://www.sysnative.com/forums/bs...eived-on-a-secondary-processor.html#post60154

batreky · Dec 1, 2013

x BlueRobot said:
We could have got more information about the registry key, by doing a !reg findkcb with the full path of the registry key, and then using the !reg kcb with the address provided by the !reg findkcb extension. I've demonstrated it in my latest blog post.

I'm Sorry but I'm too Scared now is it a bad problem ? in a hardware or what u mean as I don't know when I used those registrys

BSOD error code 0x0000001E keep crashing

Active member

Administrator

Administrator

Active member

Active member

Administrator

Active member

Administrator

Active member

Attachments

Sysnative Staff

Active member

Sysnative Staff, BSOD Kernel Dump Senior Analyst

Active member

Sysnative Staff, BSOD Kernel Dump Senior Analyst

Active member

Sysnative Staff

Sysnative Staff, BSOD Kernel Dump Senior Analyst

Active member

Administrator

Active member