Re: system freeze after memory access
- From: "Jodus" <RomanJordan@xxxxxx>
- Date: Mon, 2 Oct 2006 18:29:16 +0200
Hi,
it seams to be a hardware problem.
Best regards,
Roman
"Jodus" <RomanJordan@xxxxxx> schrieb im Newsbeitrag
news:eOeCJnh5GHA.940@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
i want resize a memory area of my selfmade PCI card.
I do the following:
- grap the IRP_MN_FILTER_RESOURCE_REQUIREMENTS request
- send it to the underlaying driver (synchronous)
- modify the size of one memory area (PCI told me there are 0x400 bytes, i
only want 0x200 bytes)
- complete the IRP
The IRP_MN_START_DEVICE request, which i receive later, gives me the
modified resources.
The whole driver works fine at three of my test machines.
One machine shows a strange behavior. I see, that the size of the memory
area is modified
(the length is 0x200 instead the original 0x400 bytes). The following call
to MmMapIoSpace
returns without error (returns pointer != NULL).
If i use this pointer, the system freezes.
In this case the revision and version numbers of the partial resource
list, which i get at IRP_MN_START_DEVICE request,
are 0 instead of 1.
All machines use Windows XP with service pack 2. The "error" machine uses
an english XP version.
The driver is compiled with the DDK version 3790.1830.
Some additional informations:
My PCI card uses more than one memory and i/o resources. At least there
are three device drivers,
to support the whole functionality of this card. The resources are divided
using MF.SYS.
Any ideas?
Thanks in advance,
Roman Jordan
.
- References:
- system freeze after memory access
- From: Jodus
- system freeze after memory access
- Prev by Date: Low-latency USB Isochronous transfers
- Next by Date: Re: Bugcheck FE, {8, 6, 5, 9445a000}
- Previous by thread: system freeze after memory access
- Next by thread: Re: system freeze after memory access
- Index(es):
Relevant Pages
|
