Re: Bugcheck 101

Tech-Archive recommends: Fix windows errors by optimizing your registry

Daniel,

Thanks for the suggestion! I got a few more entries to refer to. Still,
sorry to say, none of them helped in this particular case.

I did some more digging into this problem, and this is what I found.

My chip has a hw dma queue and a hw render queue. The chip fetches command
streams from these queues, which can be placed on host or board memory .
These commands are set up by the driver to move data and tables in and out of
the board, or to perform the rendering.

In this case, we're fetching from host memory. I preallocate a large (the
default is 4 megabytes) contiguous slab of memory at initialization time,
which becomes a buffer pool from where the driver suballocates queue command
buffers.

I found that the problem goes away if I force the physical address of this
memory slab to be under 4Gb. If I let the command buffer pool to go beyond
4Gb, every once in a blue moon I either get a Bugcheck 101 or I get a hard
machine freeze where not even the keyboard LEDs are functional.

Now, this can be an issue with my hardware's PCI Express implementation, or
it can have something to do with the way Vista 64-bit handles physical
memory. I faintly recall to have read some warning somewhere on the Web, but
I cannot locate it any longer.

Meanwhile, I'll double check to make sure my chip isn't mistreating the PCI
Express bus. And thanks to all of you who pitched in!


Alberto.

===========

"daniel@xxxxxxxxxxxxxxxx" wrote:

Now that I am thinking about it, the driver where I have seen this bugcheck
was doing exotic experiments in an attempt to achieve a real time
environment by "liberating" CPUs from any workload.

For this purpose, I was setting affinity for all processes and threads in
the system (KeSetSystemAffinityThread) and dequeueing DPCs which were not
mine (with KeSetTargetProcessorDpc) from the CPU I wanted to liberate.

//Daniel





<daniel@xxxxxxxxxxxxxxxx> wrote in message
news:C8BBC04B-1A83-4A12-9EC2-0D5CEE1AE617@xxxxxxxxxxxxxxxx
Through the years I have had a few of these bugchecks in my software only
drivers, but they were never reproduceable and always while running under
VmWare.

I hate to make such a silly suggestion but have you considered Googling
for "CLOCK_WATCHDOG_TIMEOUT" and "bugcheck 0x101" rather than "bucheck
101", these do yield some results.

//Daniel


"Alberto" <moreira@xxxxxxxxxxxxx> wrote in message
news:38960766-493e-4629-8459-02f4e82d662f@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

My question is, do any of you have any experience with this Bugcheck
you might be willing to share ? At this point, any information,
however minor, will be highly appreciated!

Thanks,


Alberto.


.

Relevant Pages