Blue Screen After Sleep Mode

I'm using Windows 7 Home Premium 64-bit, Service Pack 1. After coming
out of sleep mode, the computer always gets a blue screen displaying a
0x00000073 error, referring to stdriver64.sys. This problem seems to
have started after SP1, but I'm not sure there's a correlation. Any ideas?

On 4/11/2011 9:12 AM, Alias wrote:
> On 04/11/2011 03:00 PM, banjoistic wrote:
>> I'm using Windows 7 Home Premium 64-bit, Service Pack 1. After coming
>> out of sleep mode, the computer always gets a blue screen displaying a
>> 0x00000073 error, referring to stdriver64.sys. This problem seems to
>> have started after SP1, but I'm not sure there's a correlation. Any
>> ideas?
>
> Update your audio drivers.
>
I tried that. Windows reports they are the latest versions.

banjoistic wrote:
> I'm using Windows 7 Home Premium 64-bit, Service Pack 1. After coming
> out of sleep mode, the computer always gets a blue screen displaying a
> 0x00000073 error, referring to stdriver64.sys. This problem seems to
> have started after SP1, but I'm not sure there's a correlation. Any ideas?

http://www.vistax64.com/crashes-debu...rnl-fix-2.html

Description: stdriver.sys
Company: NCH Software

Possibly, "sound tap" program ? Inserts a shim in the audio stack and kaboom ?

http://www.nch.com.au/soundtap/index.html

This site ( http://aumha.org/a/stop.htm ) says the blue screen is:

0x00000073: CONFIG_LIST_FAILED

but doesn't offer an explanation.

OK, this gives a lead:

http://msdn.microsoft.com/en-us/library/ms819301.aspx

"It indicates the system configuration link list failed.

One of the core system hives is corrupted or unreadable,
or some critical Registry keys and values are not present."

In other words, some driver level code is attempting to access
the Registry. That sounds kinda crazy and dangerous ?!?

There is a forum for the product, but I don't see the developer
helping out. So asking a question here would likely be a waste of
time.

http://nch.invisionzone.com/index.php?showforum=27

A Realtek driver would be more likely to have an R at the
beginning of the driver name. A SigmaTel driver file might
begin with "st" but they generally don't bother including
the word "driver" in their files. So I'm guessing you've installed
Sound Tap, and now there is a problem. Sound Tap may be attempting
to access the Windows Registry, trying to find the registration
key purchased for Sound Tap.

Paul

On 4/11/2011 12:56 PM, Paul wrote:
> banjoistic wrote:
>> I'm using Windows 7 Home Premium 64-bit, Service Pack 1. After coming
>> out of sleep mode, the computer always gets a blue screen displaying a
>> 0x00000073 error, referring to stdriver64.sys. This problem seems to
>> have started after SP1, but I'm not sure there's a correlation. Any
>> ideas?
>
> http://www.vistax64.com/crashes-debu...rnl-fix-2.html
>
> Description: stdriver.sys
> Company: NCH Software
>
> Possibly, "sound tap" program ? Inserts a shim in the audio stack and
> kaboom ?
>
> A Realtek driver would be more likely to have an R at the
> beginning of the driver name. A SigmaTel driver file might
> begin with "st" but they generally don't bother including
> the word "driver" in their files. So I'm guessing you've installed
> Sound Tap, and now there is a problem. Sound Tap may be attempting
> to access the Windows Registry, trying to find the registration
> key purchased for Sound Tap.
>
> Paul
Thanks, Paul. I'll investigate that, as I do have some NCH software
installed.

On 4/11/2011 12:56 PM, Paul wrote:
> banjoistic wrote:
>> I'm using Windows 7 Home Premium 64-bit, Service Pack 1. After coming
>> out of sleep mode, the computer always gets a blue screen displaying a
>> 0x00000073 error, referring to stdriver64.sys. This problem seems to
>> have started after SP1, but I'm not sure there's a correlation. Any
>> ideas?
>
> http://www.vistax64.com/crashes-debu...rnl-fix-2.html
>
> Description: stdriver.sys
> Company: NCH Software
>
> Possibly, "sound tap" program ? Inserts a shim in the audio stack and
> kaboom ?
>
>
> Paul
I tried removing stdriver64.sys, and the problem goes away. However, I
then have no audio devices. I tried installing Windows' own audio
driver, but that didn't work. I put stdriver64.sys back, and sound
works, but the original problem also is back. So, back to square one.
- Gary

banjoistic wrote:
> On 4/11/2011 12:56 PM, Paul wrote:
>> banjoistic wrote:
>>> I'm using Windows 7 Home Premium 64-bit, Service Pack 1. After coming
>>> out of sleep mode, the computer always gets a blue screen displaying a
>>> 0x00000073 error, referring to stdriver64.sys. This problem seems to
>>> have started after SP1, but I'm not sure there's a correlation. Any
>>> ideas?
>>
>> http://www.vistax64.com/crashes-debu...rnl-fix-2.html
>>
>> Description: stdriver.sys
>> Company: NCH Software
>>
>> Possibly, "sound tap" program ? Inserts a shim in the audio stack and
>> kaboom ?
>>
>>
>> Paul
> I tried removing stdriver64.sys, and the problem goes away. However, I
> then have no audio devices. I tried installing Windows' own audio
> driver, but that didn't work. I put stdriver64.sys back, and sound
> works, but the original problem also is back. So, back to square one.
> - Gary

But this is caused by what Sound Tap has done to your audio protocol stack.
NCH should provide a proper uninstaller, that puts things back the way they
were.

Any software that places a "shim" between two other items in the stack,
will "break" it if the shim is removed improperly. The software must be
removed in such a way, that an upper item in the stack, talks directly
to a lower item. In the center case, the upper item tried to talk to "---"
but nobody is home. The non-existent shim, prevents the middle case from
working. The right-most case, is how the stack looked, before the software
with the shim was used. So there is more to cleaning up the mess, than
just deleting "stdriver.sys". Manually removing software, is fraught with
perils. (Note - this diagram is a generic concept of "shims". I don't
know the details of how it works for audio or storage in detail.)

Working Broken Original

upper upper upper
shim --- lower
lower lower

I've had this problem before. I had two audio cards, and each card had a
driver. One driver package, damaged a registry entry the other package needed.
And neither driver repaired the entry. I could detect what was happening,
with a Sysinternals program (watching for attempts to read the registry).
I had to go through about 100,000 log entries to find the thing that
was actually upsetting it and breaking working audio. (You could see the
driver attempting to access a non-existent registry key. I added the
key to the registry.)

If a software designer makes something that messes up the registry, or
adds filter drivers to a stack, they should clean up the mess with their
uninstaller later.

In some cases, using System Restore, to a point in time before the product
was installed, might fix it. But if you installed Sound Tap a long time
ago, that wouldn't be a viable option. System Restore is good for cases
where you noticed a problem happening a day or two after the bad software
was installed.

Paul

On 4/11/2011 3:38 PM, Paul wrote:

> But this is caused by what Sound Tap has done to your audio protocol stack.
> NCH should provide a proper uninstaller, that puts things back the way they
> were.
>
> Any software that places a "shim" between two other items in the stack,
> will "break" it if the shim is removed improperly. The software must be
> removed in such a way, that an upper item in the stack, talks directly
> to a lower item. In the center case, the upper item tried to talk to "---"
> but nobody is home. The non-existent shim, prevents the middle case from
> working. The right-most case, is how the stack looked, before the software
> with the shim was used. So there is more to cleaning up the mess, than
> just deleting "stdriver.sys". Manually removing software, is fraught with
> perils. (Note - this diagram is a generic concept of "shims". I don't
> know the details of how it works for audio or storage in detail.)
>

> Paul
Thanks. I guess I've got more work to do.

On Mon, 11 Apr 2011 09:00:27 -0400, banjoistic <>
wrote:

>I'm using Windows 7 Home Premium 64-bit, Service Pack 1. After coming
>out of sleep mode, the computer always gets a blue screen displaying a
>0x00000073 error, referring to stdriver64.sys. This problem seems to
>have started after SP1, but I'm not sure there's a correlation. Any ideas?


Maybe stdriver64.sys accesses components of the virtual storport
miniport driver.

This was necessary for me after installing SP1;
http://support.microsoft.com/kb/2320550

It certainly seems unrelated, but ya never know till ya try.

On 4/11/2011 5:40 PM, vortch wrote:
> On Mon, 11 Apr 2011 09:00:27 -0400, banjoistic<>
> wrote:
>
>> I'm using Windows 7 Home Premium 64-bit, Service Pack 1. After coming
>> out of sleep mode, the computer always gets a blue screen displaying a
>> 0x00000073 error, referring to stdriver64.sys. This problem seems to
>> have started after SP1, but I'm not sure there's a correlation. Any ideas?
>
>
> Maybe stdriver64.sys accesses components of the virtual storport
> miniport driver.
>
> This was necessary for me after installing SP1;
> http://support.microsoft.com/kb/2320550
>
> It certainly seems unrelated, but ya never know till ya try.
I installed updated AMD chipset driver for my motherboard, and it seems
to have done the trick. Thanks for your suggestion, though.
- Gary

On 4/11/2011 3:38 PM, Paul wrote:
> banjoistic wrote:
>> On 4/11/2011 12:56 PM, Paul wrote:
>>> banjoistic wrote:
>>>> I'm using Windows 7 Home Premium 64-bit, Service Pack 1. After coming
>>>> out of sleep mode, the computer always gets a blue screen displaying a
>>>> 0x00000073 error, referring to stdriver64.sys. This problem seems to
>>>> have started after SP1, but I'm not sure there's a correlation. Any
>>>> ideas?
>>>
>>> http://www.vistax64.com/crashes-debu...rnl-fix-2.html
>>>
>>> Description: stdriver.sys
>>> Company: NCH Software
>>>
>>> Possibly, "sound tap" program ? Inserts a shim in the audio stack and
>>> kaboom ?
>>>
>>>
>>> Paul
>> I tried removing stdriver64.sys, and the problem goes away. However, I
>> then have no audio devices. I tried installing Windows' own audio
>> driver, but that didn't work. I put stdriver64.sys back, and sound
>> works, but the original problem also is back. So, back to square one.
>> - Gary
>
> But this is caused by what Sound Tap has done to your audio protocol stack.
> NCH should provide a proper uninstaller, that puts things back the way they
> were.
>
> Any software that places a "shim" between two other items in the stack,
> will "break" it if the shim is removed improperly. The software must be
> removed in such a way, that an upper item in the stack, talks directly
> to a lower item. In the center case, the upper item tried to talk to "---"
> but nobody is home. The non-existent shim, prevents the middle case from
> working. The right-most case, is how the stack looked, before the software
> with the shim was used. So there is more to cleaning up the mess, than
> just deleting "stdriver.sys". Manually removing software, is fraught with
> perils. (Note - this diagram is a generic concept of "shims". I don't
> know the details of how it works for audio or storage in detail.)
>

> Paul
I installed updated drivers for the AMD chipset, and that seems to have
worked. Thanks for your suggestions, though. They encouraged me to dig
deeper.
- Gary