Checked build asserts

NTDEV
1

Hi,
As recommended by the experts in OSR, I started testing my driver with the
checked build version of windows. Since my test machine is connected to
remote storage, I had to install HBA drivers as well to work with the
storage.
Occassionally, I get an OS assert in places for which I don’t have any
source code. Is there some way to determine whether the assertion is caused
by my driver or by other installed driver?

Thanks,
Eran.

2

Well if you post the actual assert plus stack trace information here you
will probably get an accurate assesment. "I had to install HBA drivers " -
and are these 3rd party drivers associated with the assert?

One thing you can do is to turn verifier on both your driver and any other
drivers you might suspect.

=====================
Mark Roddy DDK MVP
Windows 2003/XP/2000 Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Eran Borovik
Sent: Thursday, August 18, 2005 5:11 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Checked build asserts

Hi,
As recommended by the experts in OSR, I started testing my
driver with the checked build version of windows. Since my
test machine is connected to remote storage, I had to install
HBA drivers as well to work with the storage.
Occassionally, I get an OS assert in places for which I don’t
have any source code. Is there some way to determine whether
the assertion is caused by my driver or by other installed driver?

Thanks,
Eran.

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as:
xxxxx@hollistech.com To unsubscribe send a blank email to
xxxxx@lists.osr.com

3

In the general case, no, there’s no way to know a priori. One has to
investigate each case.

–
James Antognini
Windows DDK and WDK Support

This posting is provided “AS IS” with no warranties, and confers no rights.

“Eran Borovik” wrote in message news:xxxxx@ntdev…
> Hi,
> As recommended by the experts in OSR, I started testing my driver with the
> checked build version of windows. Since my test machine is connected to
> remote storage, I had to install HBA drivers as well to work with the
> storage.
> Occassionally, I get an OS assert in places for which I don’t have any
> source code. Is there some way to determine whether the assertion is
> caused by my driver or by other installed driver?
>
> Thanks,
> Eran.
>
>