Bluescreen Error code 1003 Category: (102)

Hi. I'm from Norway so exuse my (eventual) bad English.
Sometimes when i run a program my computer freezes and this is what i get in
the event viewer.

Date: 25.04.2007
Source: System error
Time: 19:37:53
Category: (102)
Type: Error
Event Id: 1003
User: N/A
Computer: Mine

Error code 100000ea, parameter1 88651970, parameter2 88158910, parameter3
bacf3cb4, parameter4 00000001.

And the second time

Date: 30.04.2007
Source: System error
Time: 16:00:53
Category: (102)
Type: Error
Event Id: 1003
User: N/A
Computer: Mine

Error code 000000cb, parameter1 a9a1e8c0, parameter2 88d2de10, parameter3
8853fc70, parameter4 00000005.

These crashes only happen when i use the computer for something that demands
some CPU power or so.

Hardware Spec. :

Mainboard : NEC COMPUTERS INTERNATIONAL P5S800-VM
Chipset : SiS 661FX
Processor : Intel Pentium 4 519J @ 3066 MHz
Physical Memory : 2048 MB (2 x 1024 DDR-SDRAM )
Video Card : ATI Technologies Inc Radeon 9600 Series (V350)
Hard Disk : ST3160021A (160 GB)
Hard Disk : ST3160021A (160 GB)
Network Card : Realtek Semiconductor RT8139 (A/B/C/810x/813x/C+) Fast
Ethernet Adapter
Operating System : Microsoft Windows XP Home Edition 5.01.2600 Service Pack 2


I looked at speedfan and the CPU temperature was 60 degrees celcius. And i
had no programs running! Also the CPU fan was running kind of slow even at
this temperature. I have had a little dustbunny massacre in the cabinet a
couple of days ago but the temperature was still the same. Does the high
temperature cause these error messages?

What can i do?
Thanks in advance
Erlend

Erlend Olsen <Erlend Olsen@discussions.microsoft.com> wrote:

>Hi. I'm from Norway so exuse my (eventual) bad English.
>Sometimes when i run a program my computer freezes and this is what i get in
>the event viewer.
>
>Date: 25.04.2007
>Source: System error
>Time: 19:37:53
>Category: (102)
>Type: Error
>Event Id: 1003
>User: N/A
>Computer: Mine
>
>Error code 100000ea, parameter1 88651970, parameter2 88158910, parameter3
>bacf3cb4, parameter4 00000001.
>

STOP 0x000000EA: THREAD_STUCK_IN_DEVICE_DRIVER
(from http://aumha.org/a/stop.htm) "A device driver problem has caused
the system to pause indefinitely (hang). Typically, this is caused by
a display driver waiting for the video hardware to enter an idle
state. This might indicate a hardware problem with the video adapter,
or a faulty video driver."

See http://support.microsoft.com?kbid=293078

In your instance the error is being caused by the device driver that
is using memory address 88651970 (parameter 1).


>And the second time
>
>Date: 30.04.2007
>Source: System error
>Time: 16:00:53
>Category: (102)
>Type: Error
>Event Id: 1003
>User: N/A
>Computer: Mine
>
>Error code 000000cb, parameter1 a9a1e8c0, parameter2 88d2de10, parameter3
>8853fc70, parameter4 00000005.
>

STOP 0x000000CB: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
Again, from aumha "This is related to Stop Code 0x76. It appears
instead of 0x76 if diagnostic tracking is enabled as described in the
General Discussion article below. It indicates that a driver or the
I/O manager failed to release locked pages after an I/O operation.
Note the name of the problem driver on the blue error screen."

In your instance the culprit is probably whatever item (application,
windows component, device driver) that is using memory address
88d2de10. (parameter 2).

Note that the two suspect memory addresses are fairly close together,
so it may be the same driver that is causing both.

Here is a procedure that may help you to identify the specific driver
involved:

******
Identifying the cause of STOP errors using PSTAT & Excel

Many times when a STOP error occurs the information provided does not
specifically identify the application, device driver, or other
component file where the error occurred. However the 4 parameters
associated with the STOP (bugcheck) code will very often include one
that is the address where the error occurred. You first need to look
up the detailed information about the specific STOP code in order to
determine if the address is included and if so which of the 4
parameters has the address.

You can identify the meaning of each of the parameters for your
specific STOP code at:
http://msdn2.microsoft.com/en-us/library/ms789516.aspx

The second step in the procedure is to identify the addresses that
each active process is being loaded at. The PSTAT utility will
provide this information. On some systems the PSTAT utility may
already be present. Check this by opening a Command Prompt window
(Start - Run - CMD) and entering the following command:

PSTAT /?

If PSTAT is not on your computer you can download it free from
Microsoft. The download is called "Windows XP Service Pack 2 Support
Tools" and it is available from
http://www.microsoft.com/downloads/d...displaylang=en
With PSTAT installed on your computer the next step is to open a
Command Prompt window again (Start - Run - CMD) and generate a report
with PSTAT. Because you need to copy part of the information from
this report (and only part) it is best to create the report as a text
file. In the Command Prompt window enter the following command:

PSTAT > C:\JUNK\PSTAT.TXT

You may change C:\JUNK\ to whatever drive and folder that you want to
save the report into.

Now open the saved file in Notepad. Start - Run - NOTEPAD
C:\JUNK\PSTAT.TXT

Scroll down the file, about 80% of the way to the end of the file and
you will find a head line:

ModuleName Load Addr Code Data Paged LinkDate

It is the information from this line to the end of the file that we
want to copy from this file and save as a separate file. Select the
block of text and copy it to the clipboard. Open a new notepad window
and paste the clipboard contents into it. Save this file under a
different name. I use PSTAT2.TXT and put it into the same C:\JUNK
folder.

Now launch Microsoft Excel and use File - Open to bring the PSTAT2.TXT
file into Excel. Excel will automatically parse the file into
columns. Once this is done use DATA - SORT to sort the entire
spreadsheet based on the value in Column B (Load Addr).

It is now a simple task to read down the addresses until you find the
highest value that is less than the address where the error occurred.
That module (name in column A) is the prime suspect for the cause of
your error.

******

Good luck




Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

Okay, I will do but i got the bluescreen one more time and i took a picture
of it. It said that the file most likely to be the problem was "rdwm1046.sys"
and this is the driver to my USB soundcard (Edirol UA-25) What should i do?

Erlend Olsen <ErlendOlsen@discussions.microsoft.com> wrote:

>Okay, I will do but i got the bluescreen one more time and i took a picture
>of it. It said that the file most likely to be the problem was "rdwm1046.sys"
>and this is the driver to my USB soundcard (Edirol UA-25) What should i do?

Go to the soundcard manufacturer's web site and download their latest
drivers for your specific model and install them. Also check their
tech support section for any information regarding this error problem.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

Okay. Done. But those bluescreens still doesn't go away. Can it have
something with the temperature?

Erlend Olsen <ErlendOlsen@discussions.microsoft.com> wrote:

>Okay. Done. But those bluescreens still doesn't go away. Can it have
>something with the temperature?

Have you contacted the sound card manufacturer's tech support yet? It
is their hardware and therefore they have the primary responsibility
for resolving errors that it causes?

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."