Hello,

For a long time I have problems with the Window's stabillity and still I can
not identify what causes those blue screens. I will give you as much
information as I can and hope to help me to solve the problem.

Im with Windows XP Pro with the latest service packs and drivers, installed
on Duron 750Mhz, 2x128MB Ram, NVidia FX5200, MB Acorp (im not sure what
model is), HDD Maxtor 80GB 7200.

Often when I leave my PC (for example to dowlnad something from the
internet), later I find that it is crashed showing the BlueScreen (which I
have set to be shown on error). It crashes while Im working too.

In most of the cases the errors are different as well as the drivers in
which the error occur.
The last error was KERNEL_DATA_IN_PIPELINE_ERROR or something and the driver
in which the error occured was ATAPI.DLL. In the same day I saw the same
error but in a different driver KERNEL32.DLL (or something like this). Offen
the error occurs in the driver NV4_DISP.DLL too.

The first thing was to change the parts which probably cause the problem,
but even when I upgraded them my PC still crashes. The hardware changes I
made are:
1. New Video card
2. Added more RAM (1x128MB) - Also I have tried with only one simm on all
the slots.
3. New HDD (with fresh installation)

I have made a lot of preinstallations of Windows but without result.

If I missed some information, please ask me if you need.

I realy hope someone to help me solve this realy annoying problem!

Thanks in advance,
Bojidar Markov

You are probably using a Nvidia driver that your system dislikes. Go here
www.guru3d.com and try a few
different Nvidia drivers.
"Bojidar Markov" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hello,
>
> For a long time I have problems with the Window's stabillity and still I
can
> not identify what causes those blue screens. I will give you as much
> information as I can and hope to help me to solve the problem.
>
> Im with Windows XP Pro with the latest service packs and drivers,
installed
> on Duron 750Mhz, 2x128MB Ram, NVidia FX5200, MB Acorp (im not sure what
> model is), HDD Maxtor 80GB 7200.
>
> Often when I leave my PC (for example to dowlnad something from the
> internet), later I find that it is crashed showing the BlueScreen (which I
> have set to be shown on error). It crashes while Im working too.
>
> In most of the cases the errors are different as well as the drivers in
> which the error occur.
> The last error was KERNEL_DATA_IN_PIPELINE_ERROR or something and the
driver
> in which the error occured was ATAPI.DLL. In the same day I saw the same
> error but in a different driver KERNEL32.DLL (or something like this).
Offen
> the error occurs in the driver NV4_DISP.DLL too.
>
> The first thing was to change the parts which probably cause the problem,
> but even when I upgraded them my PC still crashes. The hardware changes I
> made are:
> 1. New Video card
> 2. Added more RAM (1x128MB) - Also I have tried with only one simm on all
> the slots.
> 3. New HDD (with fresh installation)
>
> I have made a lot of preinstallations of Windows but without result.
>
> If I missed some information, please ask me if you need.
>
> I realy hope someone to help me solve this realy annoying problem!
>
> Thanks in advance,
> Bojidar Markov
>
>

Could the error have been KERNEL_DATA_INPAGE_ERROR? If so, the most likely
culprit is the new drive you added, or less likely is the new memory. This
error indicates a page of kernel memory was not found in the paging file.

Next time it happens look at the parameters. The second parameter is the
status code.
0xC000009A means insufficient resources in paging file (too small)
0xC000009C means bad blocks on the disk
0xC000009D means bad cables (data or power), bad termination, or wrong
cables (should be 80 conductor)
0xC000016A means bad blocks on the disk
0xC0000185 means bad cables, bad configuration, or two devices using the
same resources.

You can test memory stability with memtest86. I would run it for at least
10 passes (about 2-3 hours).

- Robert -

"Bojidar Markov" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hello,
>
> For a long time I have problems with the Window's stabillity and still I
> can
> not identify what causes those blue screens. I will give you as much
> information as I can and hope to help me to solve the problem.
>
> Im with Windows XP Pro with the latest service packs and drivers,
> installed
> on Duron 750Mhz, 2x128MB Ram, NVidia FX5200, MB Acorp (im not sure what
> model is), HDD Maxtor 80GB 7200.
>
> Often when I leave my PC (for example to dowlnad something from the
> internet), later I find that it is crashed showing the BlueScreen (which I
> have set to be shown on error). It crashes while Im working too.
>
> In most of the cases the errors are different as well as the drivers in
> which the error occur.
> The last error was KERNEL_DATA_IN_PIPELINE_ERROR or something and the
> driver
> in which the error occured was ATAPI.DLL. In the same day I saw the same
> error but in a different driver KERNEL32.DLL (or something like this).
> Offen
> the error occurs in the driver NV4_DISP.DLL too.
>
> The first thing was to change the parts which probably cause the problem,
> but even when I upgraded them my PC still crashes. The hardware changes I
> made are:
> 1. New Video card
> 2. Added more RAM (1x128MB) - Also I have tried with only one simm on all
> the slots.
> 3. New HDD (with fresh installation)
>
> I have made a lot of preinstallations of Windows but without result.
>
> If I missed some information, please ask me if you need.
>
> I realy hope someone to help me solve this realy annoying problem!
>
> Thanks in advance,
> Bojidar Markov
>
>

Hi RobD,

I parsed (using dumpchk.exe) the minidump file and the second parameter
seems to be 0 (BugCheckParameter2).
Do you know where (and how) can I get more information about the error
codes?
Here's the parsed file contents:

----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 04b15000
PfnDataBase 8104a000
PsLoadedModuleList 80543530
PsActiveProcessHead 80545578
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 10000050
BugCheckParameter1 c535478c
BugCheckParameter2 00000000
BugCheckParameter3 bfa1fe40
BugCheckParameter4 00000000
PaeEnabled 00000000
KdDebuggerDataBlock 805353e0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000100
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002720
CallStackOffset 00002978
SizeOfCallStack 00000478
DriverListOffset 00003080
DriverCount 00000075
StringPoolOffset 00005340
StringPoolSize 00001010
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack f4f24b88
DebuggerDataOffset 00002df0
DebuggerDataSize 00000290
DataBlocksOffset 00006350
DataBlocksCount 00000003


Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
Debug session time: Mon Mar 22 01:04:41 2004
System Uptime: 0 days 3:21:33
start end module name
804d4000 806aa280 nt Checksum: 001E311B Timestamp: Thu
Apr 24 18:57:43 2003 (3EA80977)

Unloaded modules:
f320d000 f3234000 kmixer.sys Timestamp: unavailable (00000000)
f320d000 f3234000 kmixer.sys Timestamp: unavailable (00000000)
f4e26000 f4e4d000 kmixer.sys Timestamp: unavailable (00000000)
fa115000 fa116000 drmkaud.sys Timestamp: unavailable (00000000)
f607c000 f60a3000 kmixer.sys Timestamp: unavailable (00000000)
f6211000 f621e000 DMusic.sys Timestamp: unavailable (00000000)
f6221000 f622f000 swmidi.sys Timestamp: unavailable (00000000)
f60a3000 f60c6000 aec.sys Timestamp: unavailable (00000000)
f9f9f000 f9fa1000 splitter.sys Timestamp: unavailable (00000000)
f9c21000 f9c2b000 imapi.sys Timestamp: unavailable (00000000)
f9db1000 f9db6000 Cdaudio.SYS Timestamp: unavailable (00000000)
f9842000 f9845000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check

----------------------------------------------------------------------------
----------------------------
"RobD" wrote:
> Could the error have been KERNEL_DATA_INPAGE_ERROR? If so, the most
likely
> culprit is the new drive you added, or less likely is the new memory.
This
> error indicates a page of kernel memory was not found in the paging file.
>
> Next time it happens look at the parameters. The second parameter is the
> status code.
> 0xC000009A means insufficient resources in paging file (too small)
> 0xC000009C means bad blocks on the disk
> 0xC000009D means bad cables (data or power), bad termination, or wrong
> cables (should be 80 conductor)
> 0xC000016A means bad blocks on the disk
> 0xC0000185 means bad cables, bad configuration, or two devices using the
> same resources.
>
> You can test memory stability with memtest86. I would run it for at least
> 10 passes (about 2-3 hours).
>
> - Robert -

The error you list below is not the same bugcheck code. Below is code 0x50
(PAGE_FAULT_IN_NONPAGED_AREA) and the original code was 0x7a (if it is the
KERNEL_DATA_INPAGE_ERROR). Now, they may be related to the same problem,
but the parameter list is different. The error below says a read operation
faulted.

You can find more info on stop codes by going to www.msdn.microsoft.com, and
do a search on the code (e.g. 0x7a or 0x50). Usually, the first result in
the search list takes you to the "bugcheck codes" section of the DDK. The
documentation offers suggestions on how to identify or hopefully resolve the
problem.

- Robert -

"Bojidar Markov" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Hi RobD,
>
> I parsed (using dumpchk.exe) the minidump file and the second parameter
> seems to be 0 (BugCheckParameter2).
> Do you know where (and how) can I get more information about the error
> codes?
> Here's the parsed file contents:
>
> ----- 32 bit Kernel Mini Dump Analysis
>
> DUMP_HEADER32:
> MajorVersion 0000000f
> MinorVersion 00000a28
> DirectoryTableBase 04b15000
> PfnDataBase 8104a000
> PsLoadedModuleList 80543530
> PsActiveProcessHead 80545578
> MachineImageType 0000014c
> NumberProcessors 00000001
> BugCheckCode 10000050
> BugCheckParameter1 c535478c
> BugCheckParameter2 00000000
> BugCheckParameter3 bfa1fe40
> BugCheckParameter4 00000000
> PaeEnabled 00000000
> KdDebuggerDataBlock 805353e0
> MiniDumpFields 00000dff
>
> TRIAGE_DUMP32:
> ServicePackBuild 00000100
> SizeOfDump 00010000
> ValidOffset 0000fffc
> ContextOffset 00000320
> ExceptionOffset 000007d0
> MmOffset 00001068
> UnloadedDriversOffset 000010a0
> PrcbOffset 00001878
> ProcessOffset 000024c8
> ThreadOffset 00002720
> CallStackOffset 00002978
> SizeOfCallStack 00000478
> DriverListOffset 00003080
> DriverCount 00000075
> StringPoolOffset 00005340
> StringPoolSize 00001010
> BrokenDriverOffset 00000000
> TriageOptions 00000041
> TopOfStack f4f24b88
> DebuggerDataOffset 00002df0
> DebuggerDataSize 00000290
> DataBlocksOffset 00006350
> DataBlocksCount 00000003
>
>
> Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
> Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
> Debug session time: Mon Mar 22 01:04:41 2004
> System Uptime: 0 days 3:21:33
> start end module name
> 804d4000 806aa280 nt Checksum: 001E311B Timestamp: Thu
> Apr 24 18:57:43 2003 (3EA80977)
>
> Unloaded modules:
> f320d000 f3234000 kmixer.sys Timestamp: unavailable (00000000)
> f320d000 f3234000 kmixer.sys Timestamp: unavailable (00000000)
> f4e26000 f4e4d000 kmixer.sys Timestamp: unavailable (00000000)
> fa115000 fa116000 drmkaud.sys Timestamp: unavailable (00000000)
> f607c000 f60a3000 kmixer.sys Timestamp: unavailable (00000000)
> f6211000 f621e000 DMusic.sys Timestamp: unavailable (00000000)
> f6221000 f622f000 swmidi.sys Timestamp: unavailable (00000000)
> f60a3000 f60c6000 aec.sys Timestamp: unavailable (00000000)
> f9f9f000 f9fa1000 splitter.sys Timestamp: unavailable (00000000)
> f9c21000 f9c2b000 imapi.sys Timestamp: unavailable (00000000)
> f9db1000 f9db6000 Cdaudio.SYS Timestamp: unavailable (00000000)
> f9842000 f9845000 Sfloppy.SYS Timestamp: unavailable (00000000)
>
> Finished dump check
>
> ----------------------------------------------------------------------------
> ----------------------------
> "RobD" wrote:
>> Could the error have been KERNEL_DATA_INPAGE_ERROR? If so, the most
> likely
>> culprit is the new drive you added, or less likely is the new memory.
> This
>> error indicates a page of kernel memory was not found in the paging file.
>>
>> Next time it happens look at the parameters. The second parameter is the
>> status code.
>> 0xC000009A means insufficient resources in paging file (too small)
>> 0xC000009C means bad blocks on the disk
>> 0xC000009D means bad cables (data or power), bad termination, or wrong
>> cables (should be 80 conductor)
>> 0xC000016A means bad blocks on the disk
>> 0xC0000185 means bad cables, bad configuration, or two devices using the
>> same resources.
>>
>> You can test memory stability with memtest86. I would run it for at
>> least
>> 10 passes (about 2-3 hours).
>>
>> - Robert -
>
>

Hello Robert,

I think I found the problem but it is strange. In Event Viewer in the System
node there are some warnings and some errors.
The warnng says "An error was detected on device \Device\CdRom0 during a
paging operation." and in Help And Support it's description is "An
input/output (I/O) request to a memory-mapped file failed and the operation
was retried.".
The error says "The device, \Device\CdRom0, has a bad block." and in Help
And Support it's description is "The device has a bad block of memory, which
Windows attempted to read. The data might be missing or corrupted.".

If I change the CD-ROM will I fix the problem?
By the way in using CDs rarely and im sure that my PC hangs even when
there's not CD in the CD-ROM.

What could be the problem?

Thanks in advance.
I appreciate your help!

Best regards,
Bojidar Markov


"RobD wrote:
> The error you list below is not the same bugcheck code. Below is code
0x50
> (PAGE_FAULT_IN_NONPAGED_AREA) and the original code was 0x7a (if it is the
> KERNEL_DATA_INPAGE_ERROR). Now, they may be related to the same problem,
> but the parameter list is different. The error below says a read
operation
> faulted.
>
> You can find more info on stop codes by going to www.msdn.microsoft.com,
and
> do a search on the code (e.g. 0x7a or 0x50). Usually, the first result in
> the search list takes you to the "bugcheck codes" section of the DDK. The
> documentation offers suggestions on how to identify or hopefully resolve
the
> problem.
>
> - Robert -