Re: CIPE-Win32 (2.0-pre7) BSOD|
"Damion K. Wilson" <dkw,AT,rcm,DOT,bm>|
Thu, 5 Apr 2001 20:57:28 +0200|
Thanks, Any help at all would be appreciated. I wasn't a driver writer
either when I started this. Indeed, most of my more recent development
experience has been on Solaris and Linux than Win32.
If you snag a copy of WinDbg and load up the memory.dmp, you may be able to
pinpoint where it's happening. I'm unable to force the crash on my boxes so
I don't have one to debug.
*********** REPLY SEPARATOR ***********
On 4/5/01 at 8:23 PM Erik Wallin wrote:
>Erik Wallin wrote:
>> It does produce a memory.dmp, but no bluescreen. Am I missing
>> something here?
>It seems that the Video driver is crappy on the machine I'm testing on.
>Starting W2K in VGA mode produces a proper BSOD. If there is such a
>thing as a proper BSOD. :-)
>> The only useful information I found was this entry in the system log:
>> The computer has rebooted from a bugcheck. The bugcheck was:
>> 0x000000b8 (0x00000000, 0x00000000, 0x00000000, 0x00000000). Microsoft
>> Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\MEMORY.DMP.
>The BSOD I get on screen has the same information but with the addition
>of the following message:
>"A wait operation, attach process, or yield was attempted from a DPC
>Right now I get this BSOD if I start the machine with the CIPE interface
>disabled and enable it. The service refuses to start.
>Do I understand it correctly that the cipdrvr runs in kernel space and
>cipsrvr runs in user space? If so only cipdrvr should be able to crash
>the OS. (I'm not a Windows hacker.) That would be good since the driver
>is only about 15 pages of code.
>Let me know if I can be of any further assistance. I've looked at the
>code. It seems fairly readble so maybe I'll take a look at it to see if
>I can pinpoint anything. I do have quite a lot of experience in C/C++,
>but I don't have a clue about windows drivers so I would be looking for