Blue screen - Can someone read a minidump *.dmp file?

[E]

http://members.localnet.com/~eddie180/Misc/Mini031508-01.dmp

I built a computer for a relative that has an occasional blue screen and
memory dump. I changed out the video card and RAM about a year ago. She
still had an occasional blue screen. I then changed out the power
supply. The PC worked fine for a few months, until yesterday morning it
blue screened again. It seems that it can blue screen at any time, no
matter what task is being performed. She tolerated it until the last two
recent episodes, when after it blue screened, the system would not boot.
Just a black screen and no POST. When I brought it home, and hooked it
up to my monitor, keyboard etc... it came on with no problem. I've never
had it long enough to duplicate the blue screen.

Here is a list of components:
ASUS P4P800SE 865PE/ICH5 motherboard.
Nvidia video card
1024MB of name brand memory listed as compatible with the board
Antec 500W Basiq PSU

Also it has in it PCI cards from her previous Dell computer such as...
A Lucent chip set soft modem
Sound Blaster 5.1
three port firewire card

I can lose these PCI cards from the old Dell, since she is on DSL, the
Asus board has onboard sound, and who needs firewire.

Here is a link to the minidump file created by the latest blue screen...
http://members.localnet.com/~eddie180/Misc/Mini031508-01.dmp

I may try on my own to read the minidump by following the directions
given here... http://support.microsoft.com/kb/315263

Thanks in advance
Eddie

 

[Paul]

http://members.localnet.com/~eddie180/Misc/Mini031508-01.dmp

I built a computer for a relative that has an occasional blue screen and
memory dump. I changed out the video card and RAM about a year ago. She
still had an occasional blue screen. I then changed out the power
supply. The PC worked fine for a few months, until yesterday morning it
blue screened again. It seems that it can blue screen at any time, no
matter what task is being performed. She tolerated it until the last two
recent episodes, when after it blue screened, the system would not boot.
Just a black screen and no POST. When I brought it home, and hooked it
up to my monitor, keyboard etc... it came on with no problem. I've never
had it long enough to duplicate the blue screen.

Here is a list of components:
ASUS P4P800SE 865PE/ICH5 motherboard.
Nvidia video card
1024MB of name brand memory listed as compatible with the board
Antec 500W Basiq PSU

Also it has in it PCI cards from her previous Dell computer such as...
A Lucent chip set soft modem
Sound Blaster 5.1
three port firewire card

I can lose these PCI cards from the old Dell, since she is on DSL, the
Asus board has onboard sound, and who needs firewire.

Here is a link to the minidump file created by the latest blue screen...
http://members.localnet.com/~eddie180/Misc/Mini031508-01.dmp

I may try on my own to read the minidump by following the directions
given here... http://support.microsoft.com/kb/315263

Thanks in advance
Eddie

I have a copy of Debugdiag from Microsoft here. One problem I have
with this tool, is it is too heavyweight for the job. It consists of
a client and a server task. My typical usage pattern, is install it,
read a dump with it, then uninstall it, which is not very practical.
I don't like to leave it installed. If the part that does dump analysis
was separate, at least I'd like that a little better.

http://www.microsoft.com/downloads/...41-c458-46f1-b24d-f60151d875a3&displaylang=en

I followed your KB article, and I did find a copy of "dumpchk" on my
Win2K CD. It was in support, and was inside a CAB file. I needed
to copy the dumpchk.exe and msdis110.dll into a folder, along with
your dump file. I used a DOS window, to run it, and redirected the
output to a text file.

Now, I don't know if it is really telling the truth or not. I suppose
if I install debugdiag again, I could find out.

*******
Filename . . . . . . .Mini031508-01.dmp
Signature. . . . . . .PAGE
ValidDump. . . . . . .DUMP
MajorVersion . . . . .free system
MinorVersion . . . . .2600
DirectoryTableBase . .0x00039000
PfnDataBase. . . . . .0x80566e48
PsLoadedModuleList . .0x805624a0
PsActiveProcessHead. .0x80568558
MachineImageType . . .i386
NumberProcessors . . .2
BugCheckCode . . . . .0x1000007f
BugCheckParameter1 . .0x00000008
BugCheckParameter2 . .0xf7abfd70
BugCheckParameter3 . .0x00000000
BugCheckParameter4 . .0x00000000

ExceptionCode. . . . .0x80000003
ExceptionFlags . . . .0x00000000
ExceptionAddress . . .0x00000000
*******

When I look here -

http://aumha.org/a/stop.htm

I get this -

0x1000007F: UNEXPECTED_KERNEL_MODE_TRAP_M

and that is why I don't trust the result.

OK, I tried Debugdiag, and this is what was returned.

"DebugDiag failed to locate the PEB (Process Environment Block)
in Mini031508-01.dmp, and as a result, debug analysis for this
dump may be incomplete or inaccurate."

So maybe it is an actual kernel problem.

Years and years ago, I used to do a lot of problem debugging
on proprietary computers we used to build from scratch. My
experience is, if it doesn't "crash once a day", it isn't
possible to make good progress on fixing it. So if the
problem is so infrequent as to be non-reproducible in
a reasonable interval, then changing the hardware config
may be the best thing for it. You may not get enough
crashes, to figure it out.

You can run a copy of Prime95, and this may help you determine
if the motherboard/CPU/RAM has a load dependent problem. When you
start this, and it offers to "Join GIMPS?", say No and choose
the Torture Test instead. When the custom dialog comes up, it
will offer to test some amount of memory (for me, it wants to
test 760MB or so). You can turn that number down a bit, if
you want to do a few other things on the machine at the same
time as the test is running.

http://www.mersenne.org/gimps/p95v255a.zip

Once the custom dialog is set up, start it running. On a P4
with Hyperthreading, the program should start two test threads.

For bad memory, or a processor with problems, the program can
detect an error in 10 seconds. (That is for a system overclocked
into unstable territory.) It will run for hours on a conservatively
set up system. The program won't tell you what is broken, but it
will be something in the CPU-Northbridge-Memory area of the
motherboard.

The longer it runs error free, the "better" your system is. I've
run it for 16 hours on my old P3 system. But never waited that
long on more modern systems. When you're done, there are "stop" and
"exit" options in the left-most menu.

You can also run something like memtest86+ from memtest.org, but
considering the infrequent errors, memtest86+ is too meek to
really kick the wheels off the computer. Prime95 does a better
job of that.

Sometimes, when memory has a low measurable error rate, a
little extra Vdimm in the BIOS can improve the error performance
of the memory. (I use 2.7V on my 2.5V DDR memory, and any memory
should be able to take that much. Winbond BH-5, if memory
serves, could take 3.3V applied to it, to give an extreme
example of voltage boost. But they don't make that memory
any more.)

Alternately, you can adjust the timings in the BIOS, and
loosen them a bit. Say you had 2.5-3-3-6 memory, you could
try 3-4-4-8 and see what happens. If you made such an adjustment
in the BIOS, your first test would be to use memtest86+, as
a quick check that you didn't mis-adjust anything. You don't
want to boot Windows, if memory is messed up badly.

Otherwise, your instinct, of removing the add-in cards and
simplifying the setup, may be a next step. But as long as
the crash rate of the box is low, it'll be a bugger to find.

You can also do a quick visual check for bad caps (bulging
tops or leaking electrolyte from the aluminum cylinders),
but that isn't likely to be the problem. But since a
visual check is fast and cheap, it is worth a look.

http://www.badcaps.net/images/caps/kt7/image004.png

Paul

 

[Lionel van den Berg]

When I brought it home, and hooked it
up to my monitor, keyboard etc... it came on with no problem. I've never
had it long enough to duplicate the blue screen.

It's funny you say that. I don't know too much about hardware, or
windows, but my brothers computer experienced similar problems a few
years ago. Turned out he had a keyboard (or was it mouse) driver
installed that was specific for his input device. There was a bug in the
custom driver that was causing doze to crash.

Check the drivers, make sure doze has all updates installed etc.


Hmmm, not good practice X-posting. Cut to single group.


Lionel.

 

[Kyle]

| http://members.localnet.com/~eddie180/Misc/Mini031508-01.dmp
|
| I built a computer for a relative that has an occasional blue screen
and
| memory dump. I changed out the video card and RAM about a year ago.
She
| still had an occasional blue screen. I then changed out the power
| supply. The PC worked fine for a few months, until yesterday morning
it
| blue screened again. It seems that it can blue screen at any time,
no
| matter what task is being performed. She tolerated it until the last
two
| recent episodes, when after it blue screened, the system would not
boot.
| Just a black screen and no POST. When I brought it home, and hooked
it
| up to my monitor, keyboard etc... it came on with no problem. I've
never
| had it long enough to duplicate the blue screen.
|
| Here is a list of components:
| ASUS P4P800SE 865PE/ICH5 motherboard.
| Nvidia video card
| 1024MB of name brand memory listed as compatible with the board
| Antec 500W Basiq PSU
|
| Also it has in it PCI cards from her previous Dell computer such
as...
| A Lucent chip set soft modem
| Sound Blaster 5.1
| three port firewire card
|
| I can lose these PCI cards from the old Dell, since she is on DSL,
the
| Asus board has onboard sound, and who needs firewire.
|
| Here is a link to the minidump file created by the latest blue
screen...
| http://members.localnet.com/~eddie180/Misc/Mini031508-01.dmp
|
| I may try on my own to read the minidump by following the directions
| given here... http://support.microsoft.com/kb/315263
|


Diagnosing a fairly rare blue screen crash problem is like looking for
the proverbial needle in the hay stack. Just a couple more
suggestions come to mind in addition to the informed comments posted
by Paul.

There could be a power/voltage rail problem, which might be caused by
the system or an external source. Setup a voltage monitoring program
and log results to a file, look for dips in the voltages beyond 5%
deviation from spec. There could be power line brownouts that occur
where the computer is in use that can affect stable operation of the
system, and testing the system at your home may not result in the same
operation of the computer. You probably don't know whether the blue
screen error message is the same stop error each time. If the stop
error is rarely the same error, I would suspect power regulation as
one possible source of the problem if no problems are detected after
prolonged testing with programs such as memtest86 and prime95. It
could be a capacitor in the Vcore or Vmem circuit, a bad capacitor in
the PS, dirt in the PS, AC line spikes/brownouts, a bad connection
from the PS to the motherboard (unplug/replug power connectors a few
times, this might help). Run a diagnostic on the HD, does it check
out OK for bad sectors. A dying HD can be the source of corrupted
system files. Keep in mind that it only takes one erroneous bit in a
critical system program to bring down the house. If you locate the
problem, post back with your findings.

 

[E]

Now, I don't know if it is really telling the truth or not. I suppose
if I install debugdiag again, I could find out.

*******
Filename . . . . . . .Mini031508-01.dmp
Signature. . . . . . .PAGE
ValidDump. . . . . . .DUMP
MajorVersion . . . . .free system
MinorVersion . . . . .2600
DirectoryTableBase . .0x00039000
PfnDataBase. . . . . .0x80566e48
PsLoadedModuleList . .0x805624a0
PsActiveProcessHead. .0x80568558
MachineImageType . . .i386
NumberProcessors . . .2
BugCheckCode . . . . .0x1000007f
BugCheckParameter1 . .0x00000008
BugCheckParameter2 . .0xf7abfd70
BugCheckParameter3 . .0x00000000
BugCheckParameter4 . .0x00000000

ExceptionCode. . . . .0x80000003
ExceptionFlags . . . .0x00000000
ExceptionAddress . . .0x00000000
*******

When I look here -

http://aumha.org/a/stop.htm

I get this -

0x1000007F: UNEXPECTED_KERNEL_MODE_TRAP_M

and that is why I don't trust the result.

OK, I tried Debugdiag, and this is what was returned.

"DebugDiag failed to locate the PEB (Process Environment Block)
in Mini031508-01.dmp, and as a result, debug analysis for this
dump may be incomplete or inaccurate."

So maybe it is an actual kernel problem.

Years and years ago, I used to do a lot of problem debugging
on proprietary computers we used to build from scratch. My
experience is, if it doesn't "crash once a day", it isn't
possible to make good progress on fixing it. So if the
problem is so infrequent as to be non-reproducible in
a reasonable interval, then changing the hardware config
may be the best thing for it. You may not get enough
crashes, to figure it out.

You can run a copy of Prime95, and this may help you determine
if the motherboard/CPU/RAM has a load dependent problem. When you
start this, and it offers to "Join GIMPS?", say No and choose
the Torture Test instead. When the custom dialog comes up, it
will offer to test some amount of memory (for me, it wants to
test 760MB or so). You can turn that number down a bit, if
you want to do a few other things on the machine at the same
time as the test is running.

http://www.mersenne.org/gimps/p95v255a.zip

Once the custom dialog is set up, start it running. On a P4
with Hyperthreading, the program should start two test threads.

For bad memory, or a processor with problems, the program can
detect an error in 10 seconds. (That is for a system overclocked
into unstable territory.) It will run for hours on a conservatively
set up system. The program won't tell you what is broken, but it
will be something in the CPU-Northbridge-Memory area of the
motherboard.

The longer it runs error free, the "better" your system is. I've
run it for 16 hours on my old P3 system. But never waited that
long on more modern systems. When you're done, there are "stop" and
"exit" options in the left-most menu.

You can also run something like memtest86+ from memtest.org, but
considering the infrequent errors, memtest86+ is too meek to
really kick the wheels off the computer. Prime95 does a better
job of that.

Sometimes, when memory has a low measurable error rate, a
little extra Vdimm in the BIOS can improve the error performance
of the memory. (I use 2.7V on my 2.5V DDR memory, and any memory
should be able to take that much. Winbond BH-5, if memory
serves, could take 3.3V applied to it, to give an extreme
example of voltage boost. But they don't make that memory
any more.)

Alternately, you can adjust the timings in the BIOS, and
loosen them a bit. Say you had 2.5-3-3-6 memory, you could
try 3-4-4-8 and see what happens. If you made such an adjustment
in the BIOS, your first test would be to use memtest86+, as
a quick check that you didn't mis-adjust anything. You don't
want to boot Windows, if memory is messed up badly.

Otherwise, your instinct, of removing the add-in cards and
simplifying the setup, may be a next step. But as long as
the crash rate of the box is low, it'll be a bugger to find.

You can also do a quick visual check for bad caps (bulging
tops or leaking electrolyte from the aluminum cylinders),
but that isn't likely to be the problem. But since a
visual check is fast and cheap, it is worth a look.

http://www.badcaps.net/images/caps/kt7/image004.png

Thanks for spending some time on this. I am now reading
http://aumha.org/a/stop.htm as well as copying and pasting some of the
hex numbers into google. Of all the systems I've built from scratch
(about 4) and worked on, I've never had one that had these sparse yet
persistent blue screen stop errors. So I've never had to try any of this
type of debugging.

I'm hoping to find that one of the addresses listed in the debug info
you posted for me will be just one in a range of addresses for a piece
of hardware. BugCheckParameter2 . .0xf7abfd70 might have some
significants. Also 0x1000007F: UNEXPECTED_KERNEL_MODE_TRAP_M is worth
looking into.

I have also downloaded this free GUI application from MS...
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx#E3

In addition to the three Dell supplied PCI cards, she is still using the
old Dell CRT monitor, and maybe even mouse and keyboard that came with
the Dell system. Maybe one of these is the culprit.

I also may check if there is a BIOS update for the board, remove the
three unneeded PCI cards, and update device drivers for remaining
hardware. Set BIOS to disable memory caching.

The current Windows XP Home install is the original install. I've never
reinstalled the OS. Its only been updated from Windows Update. The
system has never been over clocked, although the board was designed with
this in mind. The BIOS is set up conservatively. CPU came as boxed set
with Intel heat sink/fan, and runs ~33C idol. The hard drive is a
Seagate Barracuda SATA which should be pretty reliable. Visual
inspection was one of the first things I did when I opened it up this
time. The caps all look like they are intact to my eyes and I can't see
where anything is shorting to ground or to other hardware in the case. I
ran memtest before I changed out the system memory the first time, and
it checked out ok. Still I replaced it.

This may just be concept and correlation, but I have found a couple
others with similar problems in web based message boards that have this
same Asus motherboard. But Asus boards are highly regarded and it would
be the last thing that I would suspect.

Thanks again
Eddie

 

[E]

It's funny you say that. I don't know too much about hardware, or
windows, but my brothers computer experienced similar problems a few
years ago. Turned out he had a keyboard (or was it mouse) driver
installed that was specific for his input device. There was a bug in the
custom driver that was causing doze to crash.

And as I wrote the above I started to wonder the same thing. Maybe just
try a different keyboard and mouse. She is still using the same Dell CRT
Monitor, and if I recall, the same Dell keyboard and mouse. Maybe
coffee on the keyboard?

Check the drivers, make sure doze has all updates installed etc.

I may remove three PCI cards that aren't currently being used. The
system had this same problem before changing out the video card, but I
will update it anyway. I've thought of doing a clean install of XP as well.

Hmmm, not good practice X-posting. Cut to single group.

Yes, I knew better. Haven't posted anything in Usenet for awhile and
thought maybe it didn't matter anymore. But if it helps me getting a
reply, I will comply.

Eddie

 

[E]

"E" <[email protected]> wrote in message

| Here is a link to the minidump file created by the latest blue
screen...
| http://members.localnet.com/~eddie180/Misc/Mini031508-01.dmp
|
| I may try on my own to read the minidump by following the directions
| given here... http://support.microsoft.com/kb/315263
|


Diagnosing a fairly rare blue screen crash problem is like looking for
the proverbial needle in the hay stack. Just a couple more
suggestions come to mind in addition to the informed comments posted
by Paul.

There could be a power/voltage rail problem, which might be caused by
the system or an external source. Setup a voltage monitoring program
and log results to a file, look for dips in the voltages beyond 5%
deviation from spec. There could be power line brownouts that occur
where the computer is in use that can affect stable operation of the
system, and testing the system at your home may not result in the same
operation of the computer. You probably don't know whether the blue
screen error message is the same stop error each time. If the stop
error is rarely the same error, I would suspect power regulation as
one possible source of the problem if no problems are detected after
prolonged testing with programs such as memtest86 and prime95. It
could be a capacitor in the Vcore or Vmem circuit, a bad capacitor in
the PS, dirt in the PS, AC line spikes/brownouts, a bad connection
from the PS to the motherboard (unplug/replug power connectors a few
times, this might help). Run a diagnostic on the HD, does it check
out OK for bad sectors. A dying HD can be the source of corrupted
system files. Keep in mind that it only takes one erroneous bit in a
critical system program to bring down the house. If you locate the
problem, post back with your findings.

This is a new Antec 500W PSU, that was notably heavier than the first
off name '580 Watt' PSU that I had used when I first built the system.
But I guess that doesn't rule out problems with the power circuits on
the motherboard that you mention. The PC has been in four different
residences, so I don't think its a a problem with whatever 120VAC
circuit its plugged into.

There are 13 minidump files in the /Windows/Minidump folder. I have
downloaded this debugging application from MS...
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx#E3
Maybe it will clue me in.

If I remove the three unneeded PCI boards from the system, that will
take some off hay the stack.

The HD is a Seagate Barracuda SATA, but running diags on this disk isn't
a bad idea.

Eddie

 

[E]

http://members.localnet.com/~eddie180/Misc/Mini031508-01.dmp

I downloaded a debuging utility from MS called WinDbg found here...
http://www.microsoft.com/whdc/devtools/debugging/default.mspx

I loaded individualy all of the 13 minidump files from the
/windows/minidump folder into WinDbg. I'm no pro at reading this type of
information. I can only pick out what is obvious to me, but WinDbg seems to
fault the Sound Blaster card, its driver, or an IRQ problem related to the
Sound Blaster. Although there are no conflicts listed in system information.

I have saved the output of WinDbg as text files and put them here...
http://members.localnet.com/~eddie180/Debug/
Files dated from 12-21-06 and back mention "emu10k1m.sys ".

I started out with the latest dump file dated 03-15-08, the one I linked
to in my original post, and its analysis was incomplete. WinDbg complained
that...

"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000
...and...

Unable to load image nt, Win32 error 0n2
Unable to add module at 00000000
Debugger can not determine kernel base address

Eventually it came up with...

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
...and...

Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: f7abfd70
Arg3: 00000000
Arg4: 00000000

Basicaly the same results from Paul's analysis, with nothing that would,
to me, point to a specific driver or piece of hardware. Analysis of the
second youngest dump file dated 05-07-07 gave several...

Your debugger is not using the correct symbols

...messages. The most note worthy thing that came out of 05-07-07 was...

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a

bad >IRQL level or double freeing the same allocation, etc.

Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: 00000028, Memory contents of the pool block
Arg4: 82158008, Address of the block of pool being deallocated

As I worked backwards in time through the dump files, I got output
similiar to the most recent one dated 03-15-08. With the "nt was not found
in the image list" complaint. But with this exeption...

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address
at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 815cc3df, address which referenced memory

I then skipped to the very first, dated 09-21-04. The debug output of it
was the most telling...

Probably caused by : emu10k1m.sys (

emu10k1m!>CEFXParamSetNotifySink::Unadvise+e5 )

...and...

STACK_COMMAND: kb

FOLLOWUP_IP:
emu10k1m!CEFXParamSetNotifySink::Unadvise+e5
f7bee6fb 8d45e0 lea eax,[ebp-20h]

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: emu10k1m!CEFXParamSetNotifySink::Unadvise+e5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: emu10k1m

IMAGE_NAME: emu10k1m.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3b6b5fb2

FAILURE_BUCKET_ID: 0xD1_emu10k1m!>CEFXParamSetNotifySink::Unadvise+e5

BUCKET_ID: 0xD1_emu10k1m!CEFXParamSetNotifySink::Unadvise+e5

Followup: MachineOwner

All the dump files dated 12-21-06 and before, gave output similiar to this
saying...

Probably caused by : emu10k1m.sys ( emu10k1m+186fb )

Eddie

 

[Paul]

http://members.localnet.com/~eddie180/Misc/Mini031508-01.dmp

I downloaded a debuging utility from MS called WinDbg found here...
http://www.microsoft.com/whdc/devtools/debugging/default.mspx

I loaded individualy all of the 13 minidump files from the
/windows/minidump folder into WinDbg. I'm no pro at reading this type of
information. I can only pick out what is obvious to me, but WinDbg seems to
fault the Sound Blaster card, its driver, or an IRQ problem related to the
Sound Blaster. Although there are no conflicts listed in system information.

I have saved the output of WinDbg as text files and put them here...
http://members.localnet.com/~eddie180/Debug/
Files dated from 12-21-06 and back mention "emu10k1m.sys ".

I started out with the latest dump file dated 03-15-08, the one I linked
to in my original post, and its analysis was incomplete. WinDbg complained
that...

"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000
...and...

Unable to load image nt, Win32 error 0n2
Unable to add module at 00000000
Debugger can not determine kernel base address

Eventually it came up with...

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
...and...

Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: f7abfd70
Arg3: 00000000
Arg4: 00000000

Basicaly the same results from Paul's analysis, with nothing that would,
to me, point to a specific driver or piece of hardware. Analysis of the
second youngest dump file dated 05-07-07 gave several...

Your debugger is not using the correct symbols

...messages. The most note worthy thing that came out of 05-07-07 was...

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a

bad >IRQL level or double freeing the same allocation, etc.

Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: 00000028, Memory contents of the pool block
Arg4: 82158008, Address of the block of pool being deallocated

As I worked backwards in time through the dump files, I got output
similiar to the most recent one dated 03-15-08. With the "nt was not found
in the image list" complaint. But with this exeption...

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address
at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 815cc3df, address which referenced memory

I then skipped to the very first, dated 09-21-04. The debug output of it
was the most telling...

Probably caused by : emu10k1m.sys (

emu10k1m!>CEFXParamSetNotifySink::Unadvise+e5 )

...and...

STACK_COMMAND: kb

FOLLOWUP_IP:
emu10k1m!CEFXParamSetNotifySink::Unadvise+e5
f7bee6fb 8d45e0 lea eax,[ebp-20h]

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: emu10k1m!CEFXParamSetNotifySink::Unadvise+e5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: emu10k1m

IMAGE_NAME: emu10k1m.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3b6b5fb2

FAILURE_BUCKET_ID: 0xD1_emu10k1m!>CEFXParamSetNotifySink::Unadvise+e5

BUCKET_ID: 0xD1_emu10k1m!CEFXParamSetNotifySink::Unadvise+e5

Followup: MachineOwner

All the dump files dated 12-21-06 and before, gave output similiar to this
saying...

Probably caused by : emu10k1m.sys ( emu10k1m+186fb )

Eddie

It almost seems like two different problems, or like perhaps
a new driver was installed for the sound card, somewhere through
the period covered by the dumps.

You can try removing the sound card, and using the onboard sound
if available. You should be able to go to the support.asus.com
site, and find a driver for onboard sound for the P4P800 SE.

I'd try a test with Prime95, and see how long it will run error
free. I get bored after about four hours of that, so that is
probably enough error free testing, if you want to stop. If
you have a temperature measurement program like Speedfan, you can
watch the temperature while the test is running.

Sometimes, memory develops faulta, as time passes. I've had a
couple pieces of generic RAM bought on sale at local stores,
that lasted a little over a year. And then had a stuck fault
that memtest86+ could find. The replacement RAM from Crucial
has been fine to date.

You could also get a copy of CPUZ from www.cpuid.com/cpuz.php
and check that the clocks used and memory timing values, make
sense for the hardware. That would be a basic check that
something was not fouled up, along the way, in the BIOS.
And you don't want to "clear" the BIOS, without understanding
what the hardware is doing at this moment - studying the system
as it now stands, may help you understand the root cause of the
problems.

Paul

 

[mr deo]

Here is a list of components:
ASUS P4P800SE 865PE/ICH5 motherboard.
Nvidia video card
1024MB of name brand memory listed as compatible with the board
Antec 500W Basiq PSU

Also it has in it PCI cards from her previous Dell computer such as...
A Lucent chip set soft modem
Sound Blaster 5.1
three port firewire card

I can lose these PCI cards from the old Dell, since she is on DSL, the
Asus board has onboard sound, and who needs firewire.

the SoundBlaster card is your problem.. Dump it, and dump all of the drivers
and your pc will run flawless...

SB cards are good if your willing to invest the time and effort into making
them work AND making the software on the pc use them correctly.

Even a properly configured SB card can err when other programs make invalid
calls.

 

[E]

the SoundBlaster card is your problem.. Dump it, and dump all of the drivers
and your pc will run flawless...

SB cards are good if your willing to invest the time and effort into making
them work AND making the software on the pc use them correctly.

Even a properly configured SB card can err when other programs make invalid
calls.

Yes, I have read this much before about SoundBlaster cards and there
drivers. People seem to harp on the drivers more.

I have the same card in my system, and it hasn't ever given me trouble.
But I never play games. Just use it for music. A while ago I hooked my MIDI
keyboard up to the onboard sound in my box and there was to much latency. So
I got an SB Live 5.1. It worked good for that.

The current driver in the problem PC is the original 2001 dated driver
that comes with XP. I assumed it would be stable. Windows Update is offering
a more recent driver dated 2003. I haven't checked Creative's site yet.
Still not sure whether to update the driver, or just remove the card all
together. I'm leaning towards the later.

Thanks for your reply
Eddie

 

[E]

It almost seems like two different problems, or like perhaps
a new driver was installed for the sound card, somewhere through
the period covered by the dumps.

No, the SoundBlaster is still using the 2001 dated driver that that comes
with a Windows XP install. Windows Update has a newer one dated 2003. This
might fix the problem, but I'm afraid to chance it now. I've read about
Creative drivers being buggy.

You can try removing the sound card, and using the onboard sound
if available. You should be able to go to the support.asus.com
site, and find a driver for onboard sound for the P4P800 SE.

I am definately leaning towards this now, and removing the firewire card
as an extra precaution.

I'd try a test with Prime95, and see how long it will run error
free. I get bored after about four hours of that, so that is
probably enough error free testing, if you want to stop. If
you have a temperature measurement program like Speedfan, you can
watch the temperature while the test is running.

I have the Asus Probe software installed now. Its running pretty cool, but
the case is open and there is no load, exept for me typing on the keyboard.

Sometimes, memory develops faulta, as time passes. I've had a
couple pieces of generic RAM bought on sale at local stores,
that lasted a little over a year. And then had a stuck fault
that memtest86+ could find. The replacement RAM from Crucial
has been fine to date.

I may run memtest again. But this memory was changed once as a trial an
error attempt to fix the problem.

You could also get a copy of CPUZ from www.cpuid.com/cpuz.php
and check that the clocks used and memory timing values, make
sense for the hardware. That would be a basic check that
something was not fouled up, along the way, in the BIOS.
And you don't want to "clear" the BIOS, without understanding
what the hardware is doing at this moment - studying the system
as it now stands, may help you understand the root cause of the
problems.

Yes that would be a good idea, although I think everything is currently
running in spec. I think I have a cpuid setup file on my own box. I'm
putting that on my checklist. I've thought of reinstalling the OS. But its
so much work. Finding installed applications and what not. And I only can
get dial-up where I live, so I don't have updated software on tap. But
reinstalling the OS is good to do once in a while.

Thanks again
Eddie

 

[Clark]

Sorry I did not see the original message, but I used to get a Blue Screen
with a pool call message in Vista, which was related to my modem. If you
have one, try taking it out or disabling it if the system is running.

Clark

 

[kony]

No, the SoundBlaster is still using the 2001 dated driver that that comes
with a Windows XP install. Windows Update has a newer one dated 2003. This
might fix the problem, but I'm afraid to chance it now. I've read about
Creative drivers being buggy.

1) MS does not write your CL sound card driver. When
Windows was first installed, unfortunately MS thrust that
old driver upon you, it would have been better if MS never
bundled any driver and you (or whoever installed the OS) had
instead gotten the then-current driver from Creative.

2) Letting Windows Update take control of this would be
doubly bad since you lose more control of what the default
fallback driver is, versus having nothing associated after
uninstalling an official Creative driver.

You should make a backup of the OS, so in worst case you
just revert back to how it was before any changes are made,
then download and install the latest XP driver from
Creative's website, not Windows Update.

I have the Asus Probe software installed now. Its running pretty cool, but
the case is open and there is no load, exept for me typing on the keyboard.

Hopefully this is correct, but on occasion Asus Probe has
been known to not be accurate for any given board. You
might double-check what the bios health/hardware monitor
screen displays for temps, though for CPU it may be a little
higher reading in the bios because the bios doesn't have
Halt-Idle cooling mechanism like Windows does.

 

[Kyle]

|
message
| | >
| > | >
| >> Here is a list of components:
| >> ASUS P4P800SE 865PE/ICH5 motherboard.
| >> Nvidia video card
| >> 1024MB of name brand memory listed as compatible with the board
| >> Antec 500W Basiq PSU
| >>
| >> Also it has in it PCI cards from her previous Dell computer
such as...
| >> A Lucent chip set soft modem
| >> Sound Blaster 5.1
| >> three port firewire card
| >>
| >> I can lose these PCI cards from the old Dell, since she is on
DSL, the
| >> Asus board has onboard sound, and who needs firewire.
| >
| > the SoundBlaster card is your problem.. Dump it, and dump all of
the
| drivers
| > and your pc will run flawless...
| >
| > SB cards are good if your willing to invest the time and effort
into
| making
| > them work AND making the software on the pc use them correctly.
| >
| > Even a properly configured SB card can err when other programs
make
| invalid
| > calls.
| >
|
| Yes, I have read this much before about SoundBlaster cards and
there
| drivers. People seem to harp on the drivers more.
|
| I have the same card in my system, and it hasn't ever given me
trouble.
| But I never play games. Just use it for music. A while ago I hooked
my MIDI
| keyboard up to the onboard sound in my box and there was to much
latency. So
| I got an SB Live 5.1. It worked good for that.
|
| The current driver in the problem PC is the original 2001 dated
driver
| that comes with XP. I assumed it would be stable. Windows Update is
offering
| a more recent driver dated 2003. I haven't checked Creative's site
yet.
| Still not sure whether to update the driver, or just remove the card
all
| together. I'm leaning towards the later.
|


Good detective work, now here's some suggestions for the "fix". Use
only the latest drivers from the Creative web site. Depending upon
the SBLive card you have (the model) it MAY only work "well" in a
particular PCI slot. I have an old SB0100 (I think that's the model
number) and have had several "fights" with the card to make it work
correctly in 2 different mobos. On one motherboard, the card would
not be recognized properly by the Plug-n-Pray subsystem except when
installed in a particular PCI slot. In another system, the SBLive
caused system lockups (which I identified eventually by trying to run
the mixer at startup, and an instant lockup would occur each time I
ran the creative mixer), and ATM, I can't recall what I did to fix
that problem, tho I must have fixed it as it now works properly with
win2k and winxp in that box (a dual boot system). Heh, I found some
of the info on my SBLive horror story, you can read it here:

http://www.nforcershq.com/forum/image-vp437057.html

In the end, the "solution" that worked for me was this: I put a newer
AMD Barton core CPU in the system and pulled out the 1.4G AMD Tbird
CPU. And, I can guarantee that the Tbird CPU was not defective
(memtest86 and prime95 stable as a rock), as it is still running in
another system. Isn't that the sh*ts.

There is a "driver cleaner" program for the SBLive drivers, run the
driver cleaner (ctzap seems to ring a bell) before installing the
latest drivers. I recommend against using the MS windows update site
for obtaining SBLive 5.1 drivers.

In the end, when it works right, the SBLive 5.1 cards are darn good
sound quality cards, imho, and I fought the battle to get mine working
in it's current system because it's my "digital recording" machine
which I use for recording/digitizing old vinyl records and for
recording satellite TV receiver audio/video programming which I make
into DVDs for my kid.

Of course, there is one other possibility, such as some sort of
oddball driver conflict between the SBLive driver and some other
system driver. However, I'd give the "install the latest drivers"
approach a go before giving up.

 

[mr deo]

The current driver in the problem PC is the original 2001 dated driver
that comes with XP. I assumed it would be stable. Windows Update is offering
a more recent driver dated 2003. I haven't checked Creative's site yet.
Still not sure whether to update the driver, or just remove the card all
together. I'm leaning towards the later.

Thanks for your reply
Eddie

I use 3 creative cards at the moment, and I must say that I do like them!..
But....
The onboard sound is probably fine for what your user wants (they had a dell
FFS lol)..

Removing the card AND the drivers and allowing it to run long enough to see
if it bluescreens means that you can eliminate it..
If it crashes with the card out AND drivers removed, then that's your
problem..

with Creative products the newest driver isnt forever the best, but I would
try to get say the last 3-4 releases.. I dont know if any of their patches
contain firmware fixes but you might want to be aware of that just in case..
(as you cant roll them back as easily)

 

[mr deo]

No, the SoundBlaster is still using the 2001 dated driver that that comes
with a Windows XP install. Windows Update has a newer one dated 2003. This
might fix the problem, but I'm afraid to chance it now. I've read about
Creative drivers being buggy.

Windows Update cant distinguish betwen cards that well..
Think of it this way, if you installed the wrong 2001 driver, it may think
that the hardware you have is the same as the drivers your using..

Or, the worse stuff is where companys like Linksys (creative do it too)
release "Version" changes that means old and new drivers are not
interchangable..
So you should look on the Creative site and make sure that it only list 1
version of the card.. Unified drivers are not that uncommon so it shouldnt
be a problem, but I wouldnt let windows update do it.

 

[CBFalconer]

Sorry I did not see the original message, but I used to get a Blue
Screen with a pool call message in Vista, which was related to my
modem. If you have one, try taking it out or disabling it if the
system is running.

Notice that other answers are properly organized, by answering
either inline or at the bottom. You should also trim the quoted
material to only material relevant to your answer.

Please do not top-post. Your answer belongs after (or intermixed
with) the quoted material to which you reply, after snipping all
irrelevant material. See the following links:

<http://www.catb.org/~esr/faqs/smart-questions.html>
<http://www.caliburn.nl/topposting.html>
<http://www.netmeister.org/news/learn2quote.html>
<http://cfaj.freeshell.org/google/> (taming google)
<http://members.fortunecity.com/nnqweb/> (newusers)

 

[E]

1) MS does not write your CL sound card driver. When
Windows was first installed, unfortunately MS thrust that
old driver upon you, it would have been better if MS never
bundled any driver and you (or whoever installed the OS) had
instead gotten the then-current driver from Creative.

Yes, I didn't think MS wrote it. But I read somewhere in the past that
the CL sound card driver bundled with XP install disk was stable. If the
old CL was indeed the culprit I am glad to have finally identified it,
and have learned a lesson on that as well.

I have the same card in my old system, and it hasn't causes any obvious
problems running Windows XP. Works fine in Linux too it seems. But the
Linux Sound Blaster driver is part of ALSA (Advanced Linux Sound
Architecture) written by open source contributors.

I also had 'Plug and Play aware OS' set to NO in the BIOS. I changed it
to YES. I don't know if that makes any difference now, or would have, in
the past.

2) Letting Windows Update take control of this would be
doubly bad since you lose more control of what the default
fallback driver is, versus having nothing associated after
uninstalling an official Creative driver.

If MS didn't write the Creative Labs sound card driver bundled with the
XP install disk, then wouldn't this driver from Windows Update be a CL
written driver as well?

You should make a backup of the OS, so in worst case you
just revert back to how it was before any changes are made,
then download and install the latest XP driver from
Creative's website, not Windows Update.

After I read what you say here, I went to Creative's site, and they
apparently have a different driver for a Soundblaster 5.1 from Dell.
This SB 5.1 is indeed from her old Dell Dimension 4100. When I selected
my SB Live! 5.1 Digital (Dell) through Creative's menu system I was
eventually taken to a page that told me, "Please note that the product
you have selected has been classified as 'End of Service Life'". With no
apparent option to download a driver. I then went to Dell's site looking
for the driver and they have no option to select Windows XP as the
operating system for the Dell Dimension 4100. So it seems I was stuck
with Microsoft supplied drivers, or doing a web search to find
something. The common SB Live! 5.1's latest driver at Creative's site is
dated 2003, like the driver on at Windows Update.

I think I might have went through this when I first built the system,
and just settled for the bundled driver. A poor decision I suppose. I
wanted her to keep the SB Live! 5.1 because I thought it would provide
better gaming performance.

It doesn't much matter now though. I have removed the Sound Blaster 5.1,
a TI chipset Firewire card that I had transfered from the old Dell,
moved critical data to the designated data partition, reformatted the C
partition, installed XP from scratch, enabled onboard SoundMax hardware
and installed its latest driver from Asus.

I did the clean install because AVG Anti-virus has detected several
viruses over the last few months (although I don't think they where the
cause of the fatal stop errors and blue screens). Plus there was some
spyware, and three tool bars on the system. Could have stripped it all
away with Ad-Aware. But I was worried about viruses that AVG may not
have detected.

Hopefully this is correct, but on occasion Asus Probe has
been known to not be accurate for any given board. You
might double-check what the bios health/hardware monitor
screen displays for temps, though for CPU it may be a little
higher reading in the bios because the bios doesn't have
Halt-Idle cooling mechanism like Windows does.

Yes, Asus probe read 33C at idol, while the environmental monitor in the
BIOS measured 38C. I'll wait and see. Hopefully I won't get another call
saying "it blue screened again". When I hooked her system back up at
here place, I noticed the lights dim for a split second when I turned
the system on, or even when I flipped the switch on the power strip.
Hopefully not more cause for problems and will ruin my reputation as the
family system builder.

Thanks
Eddie

 

[E]

Windows Update cant distinguish betwen cards that well..
Think of it this way, if you installed the wrong 2001 driver, it may think
that the hardware you have is the same as the drivers your using..

Or, the worse stuff is where companys like Linksys (creative do it too)
release "Version" changes that means old and new drivers are not
interchangable..
So you should look on the Creative site and make sure that it only list 1
version of the card.. Unified drivers are not that uncommon so it shouldnt
be a problem, but I wouldnt let windows update do it.

See my reply to Kony. This SB Live! 5.1 is actually a SB Live! 5.1
Digital (Dell). I got it from her old Dell Dimension 4100. Unless I
missed something, which is possible, neither Creative or Dell seem to
offer a driver for this exact card, running Windows XP. I don't know if
it made a difference. But the SB Live! 5.1 Digital (Dell) is sitting on
my table now. I went with the onboard sound.