HCT12.1 DrverPath Test got 0x000000C4(0x00000090...) Bluescreen

Hello Everyone:

I run HCT12.1 DevicePath Test for my smartcard reader driver, it got
bluescreen with 0x000000C4(0x00000090..) message. But if I run DDK tool
dc2.exe in command line for my driver, like: dc2 /hct /dr drivername. It
PASSED. What's the different between these two kinds of tests??

When I got BS, how to use the dump file ? I have tried to open dump file in
windbg, it returned"symbol not found", I have added pdb file into the "symbol
path". Any more setting I need ?

Thank you for everyone's attention!

Alexander
Tue May 16 08:13:18 CDT 2006

See DDK documentation. Bugcheck C4 is DRIVER_VERIFIER_DETECTED_VIOLATION.
The subcode means:

"The driver switched stacks, and the current stack is neither a thread stack
nor a DPC stack.
(Typically, the driver doing this should be on the stack obtained by the KB
debugger command.) "

When the test is started from HCT, it runs with driver verifier enabled.
When you run it yourself, the driver verifier is not active.


"Haikun" <Haikun@discussions.microsoft.com> wrote in message
news:92800AAA-85D4-4671-85E1-F23A6C545231@microsoft.com...
> Hello Everyone:
>
> I run HCT12.1 DevicePath Test for my smartcard reader driver, it got
> bluescreen with 0x000000C4(0x00000090..) message. But if I run DDK tool
> dc2.exe in command line for my driver, like: dc2 /hct /dr drivername. It
> PASSED. What's the different between these two kinds of tests??
>
> When I got BS, how to use the dump file ? I have tried to open dump file
> in
> windbg, it returned"symbol not found", I have added pdb file into the
> "symbol
> path". Any more setting I need ?
>
> Thank you for everyone's attention!

Mark
Tue May 16 08:14:09 CDT 2006

Haikun wrote:
> Hello Everyone:
>
> I run HCT12.1 DevicePath Test for my smartcard reader driver, it got
> bluescreen with 0x000000C4(0x00000090..) message.

That is a bit of an unusual bug check:

"The driver switched stacks, and the current stack is neither a thread
stack nor a DPC stack.

(Typically, the driver doing this should be on the stack obtained by
using the kb (Display Stack Backtrace) debugger command.)"

Doing something a bit unusual in your driver with respect to stacks perhaps?

> But if I run DDK tool
> dc2.exe in command line for my driver, like: dc2 /hct /dr drivername. It
> PASSED. What's the different between these two kinds of tests??
>
> When I got BS, how to use the dump file ? I have tried to open dump file in
> windbg, it returned"symbol not found", I have added pdb file into the "symbol
> path". Any more setting I need ?

Follow the instructions for setting up windbg to use the microsoft
symbol server and add a path for your diver's pdb file.

Your system should be set up for either full or kernel dumps, not mini
dumps.

Maxim
Tue May 16 09:55:13 CDT 2006

"!analyze -v" debugger command is the first mean of dealing with BSODs.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

"Haikun" <Haikun@discussions.microsoft.com> wrote in message
news:92800AAA-85D4-4671-85E1-F23A6C545231@microsoft.com...
> Hello Everyone:
>
> I run HCT12.1 DevicePath Test for my smartcard reader driver, it got
> bluescreen with 0x000000C4(0x00000090..) message. But if I run DDK tool
> dc2.exe in command line for my driver, like: dc2 /hct /dr drivername. It
> PASSED. What's the different between these two kinds of tests??
>
> When I got BS, how to use the dump file ? I have tried to open dump file in
> windbg, it returned"symbol not found", I have added pdb file into the "symbol
> path". Any more setting I need ?
>
> Thank you for everyone's attention!