Help reading my dump file and know whats wrong with my laptop?

  • Thread starter Thread starter periko
  • Start date Start date
P

periko

Hi.
I have a HP laptop ze1210(ze1000 series), well this one have a AMD
processor, running at 1.2Ghz with 256RAM.

I install a fresh copy of windows xp twice, because i can work with, but
sometimes gives me the BSOD went a start my laptop.

I'm not a debugger, i have some dump files, could someone help me with my
dump files to see what is wrong with this laptop

I will appreciated a lot.

Windows xp sp2, i have try English and Spanish version.

NOTE: BSOD error is: IRQ_NOT_EQUAL_OR_LESS, i already change the memory twice.

This laptop doesn't have a battery.
 
The BSOD screen give some other details, usually consisting of a file name
and other sequences of numbers, what are they?
 
Periko

Interpreting dump files is not easy.

IRQ_NOT_EQUAL_OR_LESS ? Have you typed it correctly? I think it should
be IRQ_NOT_LESS_OR_EQUAL ?

Background information on Stop Error message:
http://msdn2.microsoft.com/en-us/library/ms793589.aspx

Typically due to a bad driver, or faulty or incompatible hardware or
software. Use the General Troubleshooting of STOP Messages checklist
above. Technically, this error condition means that a kernel-mode
process or driver tried to access a memory location to which it did not
have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was
too high. (A kernel-mode process can access only other processes that
have an IRQL lower than, or equal to, its own.)
http://aumha.org/a/stop.htm

Have you made any changes to hardware or software immediately prior to
the first time the problem occurred?

You can get replacement batteries if one is needed.

Does your Windows XP CD include the SP2 update or are you downloading
the SP2 update after installing Windows XP?

Are there any yellow question marks in Device Manager? Right click on
the My Computer icon on your Desktop and select Properties,
Hardware,Device Manager. If yes what is the Device Error code?

Try Start, Run, type "sigverif.exe" without quotes and hit OK. What
drivers are listed as unsigned? Disregard those which are not checked.

Does the Stop Error occur during the boot process or later?

This link may be useful to have:
http://h10025.www1.hp.com/ewfrf/wc/...&lc=en&cc=uk&dlc=en&os=228&rule=17793&lang=en


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
Hi.
I have a HP laptop ze1210(ze1000 series), well this one have a AMD
processor, running at 1.2Ghz with 256RAM.

I install a fresh copy of windows xp twice, because i can work with, but
sometimes gives me the BSOD went a start my laptop.

I'm not a debugger, i have some dump files, could someone help me with my
dump files to see what is wrong with this laptop

I will appreciated a lot.

Windows xp sp2, i have try English and Spanish version.

NOTE: BSOD error is: IRQ_NOT_EQUAL_OR_LESS, i already change the memory twice.

This laptop doesn't have a battery.
Click to expand...

Upload The Minidumps to any free web hosting and Give The link .... I
can Run a Debugger On Them
 
Hi DL.
Look the BSOD faster than my eyes, this info give dumpchk.exe, i have
more than 10 dumpfiles, this is the info i get aftert running dumpchk.exe -v
-x -e dumpfile.dmp > dumpfile.txt

Mini122107-07.dmp

----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 00039000
PfnDataBase 81800000
PsLoadedModuleList 8055a620
PsActiveProcessHead 805606d8
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 0000004e
BugCheckParameter1 00000002
BugCheckParameter2 000044f1
BugCheckParameter3 0000efef
BugCheckParameter4 00000001
PaeEnabled 00000000
KdDebuggerDataBlock 8054c260
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 000005b4
DriverListOffset 000031c8
DriverCount 0000006d
StringPoolOffset 00005228
StringPoolSize 00000ed0
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack f9cb3a4c
DebuggerDataOffset 00002f38
DebuggerDataSize 00000290
DataBlocksOffset 000060f8
DataBlocksCount 00000003


Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Fri Dec 21 23:20:50 2007
System Uptime: 0 days 0:10:48
start end module name
804d7000 806ebe80 nt Checksum: 00218862 Timestamp: Wed Feb 28
01:10:41 2007 (45E54711)

Unloaded modules:
f45af000 f45da000 kmixer.sys Timestamp: unavailable (00000000)
f9f15000 f9f16000 drmkaud.sys Timestamp: unavailable (00000000)
f45da000 f45fd000 aec.sys Timestamp: unavailable (00000000)
f4a2a000 f4a37000 DMusic.sys Timestamp: unavailable (00000000)
f9393000 f93a1000 swmidi.sys Timestamp: unavailable (00000000)
f9de8000 f9dea000 splitter.sys Timestamp: unavailable (00000000)
f43d9000 f43ea000 Serial.SYS Timestamp: unavailable (00000000)
f9bcc000 f9bd1000 Cdaudio.SYS Timestamp: unavailable (00000000)
f964c000 f964f000 Sfloppy.SYS Timestamp: unavailable (00000000)
f9bc4000 f9bc9000 Flpydisk.SYS Timestamp: unavailable (00000000)

Finished dump check
----------------------------------------------------------------------------
Mini122107-03.dmp

----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 0d67c000
PfnDataBase 81800000
PsLoadedModuleList 8055a620
PsActiveProcessHead 805606d8
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 1000000a
BugCheckParameter1 00000004
BugCheckParameter2 00000002
BugCheckParameter3 00000000
BugCheckParameter4 804e6617
PaeEnabled 00000000
KdDebuggerDataBlock 8054c260
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 000004ac
DriverListOffset 000030c0
DriverCount 00000072
StringPoolOffset 00005298
StringPoolSize 00000f80
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack f4705b54
DebuggerDataOffset 00002e30
DebuggerDataSize 00000290
DataBlocksOffset 00006218
DataBlocksCount 00000003


Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Fri Dec 21 21:04:36 2007
System Uptime: 0 days 0:00:28
start end module name
804d7000 806ebe80 nt Checksum: 00218862 Timestamp: Wed Feb 28
01:10:41 2007 (45E54711)

Unloaded modules:
f469c000 f46ad000 Serial.SYS Timestamp: unavailable (00000000)
f9b6c000 f9b71000 Cdaudio.SYS Timestamp: unavailable (00000000)
f9d38000 f9d3b000 Sfloppy.SYS Timestamp: unavailable (00000000)
f9b64000 f9b69000 Flpydisk.SYS Timestamp: unavailable (00000000)

Finished dump check
----------------------------------------------------------------------------

----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 00039000
PfnDataBase 81800000
PsLoadedModuleList 8055a620
PsActiveProcessHead 805606d8
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 0000004e
BugCheckParameter1 00000002
BugCheckParameter2 00002b01
BugCheckParameter3 0000efef
BugCheckParameter4 00000001
PaeEnabled 00000000
KdDebuggerDataBlock 8054c260
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 00000548
DriverListOffset 00003158
DriverCount 00000062
StringPoolOffset 00004e70
StringPoolSize 00000d50
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack f9c8bab8
DebuggerDataOffset 00002ec8
DebuggerDataSize 00000290
DataBlocksOffset 00005bc0
DataBlocksCount 00000003


Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Fri Dec 21 23:09:50 2007
System Uptime: 0 days 0:00:19
start end module name
804d7000 806ebe80 nt Checksum: 00218862 Timestamp: Wed Feb 28
01:10:41 2007 (45E54711)

Unloaded modules:
f9b74000 f9b79000 Cdaudio.SYS Timestamp: unavailable (00000000)
f9d38000 f9d3b000 Sfloppy.SYS Timestamp: unavailable (00000000)
f9b6c000 f9b71000 Flpydisk.SYS Timestamp: unavailable (00000000)

Finished dump check
------------------------------------------------------------------------------

This are the 3 different dump files i have.

Looking around, is my audio driver? or dumpchk.exe doesn't give any info
about the problem DL?
 
Hi Gerry.

I was thinking it was the modem, because the first time i try to a Test
Communication, i receive the BSOD, but the error was different than this one,
them i check the driver and it was from MS, them i download the driver from
HP and the problem was solve.

Now i'm locking for another memory and test.

I will check this check list u give to me and let u know.

I have not change any HW, just the memory, i update all windows from
windowsupdate.

I don't have any yellow mark in my device manager.

I will run the sigverif.exe and let u know.

The error is in the boot process, went appear the screen with wide blue
lines at the top and the Bottom and them goes to the windows desktop.

I already check HP site, but they say this error is because Symantec
Anti-virus, i have been checking others items there, and they say the same
for this error, they just Ctrl+c -> Ctrl+v, i don't have anything from
Symantec in this laptop.

I let u now my status, thanks!!!
 
One of your memory dumps referred to this Stop Error Report
http://msdn2.microsoft.com/en-us/library/ms793247.aspx

It's not overhelpful but points again to a driver.

Quote from link below: This indicates that the memory management Page
File Number list is corrupted. Can be caused by corrupt physical RAM, or
by drivers passing bad memory descriptor lists.
http://aumha.org/a/stop.htm

Why did you make changes to your memory? Who advised you on what memory
to install? How many memory sticks are currently installed?

What follows next was written for a desktop computer and not with a
laptop in mind. If your RAM memory is made up of more than one stick and
if so this offers a simple way to heck for faulty memory. Open the
computer casing and carefully remove one memory card (stick) from it's
slot and run the computer with it removed to see whether the problem
occurs. Repeat the process putting the first memory card back in and
removing the second memory card and test that card. Make sure you allow
sufficient time for an error to occur. When removing the card you will
need to lift a retaining clip each end of the memory card to allow it to
be removed. Take great care not to touch the motherboard. You can also
get an Anti-Static wrist band from a computer store to prevent a static
electricity discharge from you damaging the motherboard.
http://www.ehow.com/how_895_install-ram.html

http://www.elephantboycomputers.com/page2.html#Hardware_Tshoot

http://h10025.www1.hp.com/ewfrf/wc/...=uk&lc=en&dlc=en&product=86586&dlc=en&lang=en

A lot of documented causes of error can be ancient history. I read the
Symantec report on the HP site. The report related to a problem years
ago. You get the same with many Microsoft Knowledge Base Articles. They
often refer to a problem that Microsoft subsequently fixed.

Another source of information you have not, so far as I am aware, looked
at.

Please post copies of all Error and Warning Reports appearing in
the System and Application logs in Event Viewer for the last boot. No
Information Reports or Duplicates please. Indicate which also appear in
a previous boot.

You can access Event Viewer by selecting Start, Control Panel,
Administrative Tools, and Event Viewer. When researching the meaning
of the error, information regarding Event ID, Source and Description
are important.

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Click the button and close Event
Viewer.Now start your message (email) and do a paste into the body of
the message. Make sure this is the first paste after exiting from
Event Viewer.


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
devil_himself.

http://www.fileden.com/files/2007/1...om/files/2007/12/22/1657972/Mini122107-07.dmp

Here they are, hope you could read the files, if not let me know please,
thanks.
Click to expand...

BugCheck 1000000A, {4, 2, 0, 804e6617}
Probably caused by : memory_corruption ( nt!MiRemovePageByColor+6a )

STACK_TEXT:
f4705bd4 804eb20a 019ff000 019ff000 f4705ca0 nt!MiRemovePageByColor
+0x6a
f4705c0c 804e1718 00000000 019ff000 01000000 nt!MmAccessFault+0xa3b
<<<<------- Bad Ram ,
f4705c0c 80565779 00000000 019ff000 01000000 nt!KiTrap0E+0xcc
f4705ca0 80570164 019e0000 00060a38 00000001 nt!ProbeForWrite+0x39
f4705d38 804de7ec 000000cc 00000000 00000000 nt!NtReadFile+0x8a
f4705d38 7c91eb94 000000cc 00000000 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be
wrong.
00a5c26c 00000000 00000000 00000000 00000000 0x7c91eb94

=========================================================================
BugCheck 4E, {2, 2b01, efef, 1}
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromList+3f )

========================================================================

Suggestion :-

1.Run "memtest" to stress the ram. If memtest reports the ram is
faulty, ram is bad. Sometimes some faulty ram can pass memtest .Reset
the memory stick to another slot.If You have More then one Stick of
Ram Take out one memory stick And Run "Memtest" on each separately .
If windows does not crash, the removed memory stick is faulty.

2.Check the temperature of the CPU and make sure that it is not
overheat. Make sure that the CPU fan works properly . Try Changing It

3.Clean the dust inside the computer case

4.Make sure that your PSU have adequate power For all the hardware.

5.Update Video Card Drivers. Also Reset video card. Run 3DMark to test
your video card. Check to default setting if you video card is
"overclocked"

6. Run chkdsk /r at command prompt
==================================================================================
 
Back
Top