MEMORY_MANAGEMENT BSOD

NTDEV
1

I have a Win NT 4.0 PCI card driver that deals with transferring data read
from hard disk on to a SDRAM across the PCI bus. When i run a program to
start and stop this data transmission, i sometimes get this
MEMORY_MANAGEMENT BSOD. The call stack varies with each occurance:

  1. only ntoskrnl.exe.

2)Sometimes it shows hal.dll in the call stack along with ntoskrnl.exe,
however the topmost two entries being ntoskrnl.exe

3)Sometimes it shows ntfs.sys in the call stack along with ntoskrnl.exe,
however the topmost two entries being ntoskrnl.exe

Any idea on what could be going wrong and when one gets this BSOD ??

Thanks,
Madhu

2

P1 to P4 values please, if you expect any help.

Dan

----- Original Message -----
From:
To: “NT Developers Interest List”
Sent: Thursday, October 03, 2002 5:45 PM
Subject: [ntdev] MEMORY_MANAGEMENT BSOD

> I have a Win NT 4.0 PCI card driver that deals with transferring data read
> from hard disk on to a SDRAM across the PCI bus. When i run a program to
> start and stop this data transmission, i sometimes get this
> MEMORY_MANAGEMENT BSOD. The call stack varies with each occurance:
> 1) only ntoskrnl.exe.
>
> 2)Sometimes it shows hal.dll in the call stack along with ntoskrnl.exe,
> however the topmost two entries being ntoskrnl.exe
>
> 3)Sometimes it shows ntfs.sys in the call stack along with ntoskrnl.exe,
> however the topmost two entries being ntoskrnl.exe
>
> Any idea on what could be going wrong and when one gets this BSOD ??
>
> Thanks,
> Madhu
>
> —
> You are currently subscribed to ntdev as: xxxxx@rdsor.ro
> To unsubscribe send a blank email to %%email.unsub%%
>

3

Hi Dan,

Here are the P’s:

p1 = 0x00041284
p2 = 0x5c5f9000
p3 = 0x00000000
p4 = 0xc0502000

The call stack is:

ntoskrnl.exe
ntoskrnl.exe
ntfs.sys
ntfs.sys
ntoskrnl.exe
ntoskrnl.exe
ntoskrnl.exe

Thanks in advance,
Madhu

4

The PTEs or working set database are corrupted. It can be from many causes.
Most likely, your driver slowly corrupts system memory. It might be hard to
track down why exactly happens. When you post a call stack, post it
completly, not only the module names, it usualy holds important clues.

----- Original Message -----
From:
To: “NT Developers Interest List”
Sent: Friday, October 04, 2002 4:58 PM
Subject: [ntdev] Re: MEMORY_MANAGEMENT BSOD

> Hi Dan,
>
> Here are the P’s:
>
> p1 = 0x00041284
> p2 = 0x5c5f9000
> p3 = 0x00000000
> p4 = 0xc0502000
>
> The call stack is:
>
> ntoskrnl.exe
> ntoskrnl.exe
> ntfs.sys
> ntfs.sys
> ntoskrnl.exe
> ntoskrnl.exe
> ntoskrnl.exe
>
> Thanks in advance,
> Madhu
>
> —
> You are currently subscribed to ntdev as: xxxxx@rdsor.ro
> To unsubscribe send a blank email to %%email.unsub%%
>