Could someone please analyse my crash dumps

Status
Not open for further replies.
Hi,

I have regular bluescreens on my IBM ThinkPad R50e running winxp home SP2. Celeron M 248MB (256MB) RAM.

Could someone please check my minidumps and tell me whats going on?

I installed a new hdd recently and installed windows XP Home and sp2. Worked fine for a week then the blue screens started.

Dumps as follows:

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Andreas\Desktop\Mini111008-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: G:\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a6a0
Debug session time: Mon Nov 10 15:31:53.959 2008 (GMT+13)
System Uptime: 0 days 0:03:35.509
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
....................................................................................................................
Loading User Symbols
Loading unloaded module list
............
Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf817c17, f7b20568, 0}

Probably caused by : win32k.sys ( win32k!HMDestroyUnlockedObject+ab )

Followup: MachineOwner
---------


Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Andreas\Desktop\Mini111008-05.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: G:\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a6a0
Debug session time: Mon Nov 10 15:46:34.142 2008 (GMT+13)
System Uptime: 0 days 0:12:39.702
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
..................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 77, {1, 0, 0, f7d18c34}

Probably caused by : memory_corruption ( nt!MiIssuePageExtendRequestNoWait+2f8 )

Followup: MachineOwner
---------

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Andreas\Desktop\Mini111008-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: G:\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a6a0
Debug session time: Mon Nov 10 15:28:04.412 2008 (GMT+13)
System Uptime: 0 days 0:52:24.972
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.....................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
Unable to load image disk.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for disk.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {d, 0, 0, 0}

*** WARNING: Unable to verify timestamp for CLASSPNP.SYS
*** WARNING: Unable to verify timestamp for PartMgr.sys
Probably caused by : disk.sys ( disk!GUID_DEVINTERFACE_PARTITION+c )

Followup: MachineOwner
---------

Thanks in advance!
 

geekygirl63

Posts: 51   +0
Hey - Wondering about the age of your system....
Hard drive - IDE or SATA?
A couple of things right off the bat....

Get into setup (f2, or whatever key gets You into your bios)
When in setup check your clock time (date and time) to see if it is current. If it is not current, set it and reboot and see if it saves the time.

Second. Reseat the hard drive just to be sure its secure.

The time stamp issues I have not seen before but if the time of files on the hard drive don't match the time in the BIOS, it is a possibility that this is the problem.

when this happened the first time, do you recall any particular event or a particular thing you were doing when it happened?

tracy
 
  • Thread Starter Thread Starter
  • #3
Hey - Wondering about the age of your system....
Hard drive - IDE or SATA?
A couple of things right off the bat....

Get into setup (f2, or whatever key gets You into your bios)
When in setup check your clock time (date and time) to see if it is current. If it is not current, set it and reboot and see if it saves the time.

Second. Reseat the hard drive just to be sure its secure.

The time stamp issues I have not seen before but if the time of files on the hard drive don't match the time in the BIOS, it is a possibility that this is the problem.

when this happened the first time, do you recall any particular event or a particular thing you were doing when it happened?

tracy
At a guess 3 yo original owner is deceased. The notebook is using IDE hdd brand new WD hdd. I checked the system Date and time they are correct. Nothing special happend the first time the BSoD occured. I have reseated the HDD restarted and BSoD reoccured.

Any other ideas?
 

kimsland

Posts: 13,810   +3
Can be signs of a faulty internal HardDrive (make sure that you always complete all backups)

Please try this:

Manual steps to run Chkdsk from My Computer or Windows Explorer
  • Open My Computer, and then right-click the hard disk that you want to check.
  • Click Properties, and then click Tools.
  • Under Error-checking, click Check Now. A dialog box that shows the Check disk options is displayed
Use one of the following procedures:
  • • To run Chkdsk in read-only mode, click Start.
  • • (tick) To repair errors without scanning the volume for bad sectors, select the Automatically fix file system errors check box.
  • • To repair errors, locate bad sectors, and recover readable information, select the Scan for and attempt recovery of bad sectors check box.

Note If one or more of the files on the hard disk are open, you will receive the following message:
The disk check could not be performed because the disk check utility needs exclusive access to some Windows files on the disk. These files can be accessed by restarting Windows. Do you want to schedule the disk check to occur the next time you restart the computer?
Click Yes to schedule the disk check, and then restart your computer to start the disk check.

Wait until Chkdsk finishes Checking / Repairing any faults
Windows will then either restart your computer or continue loading Normally.

--------------------------

After that, you could do a Drive Diagnostics too
 
  • Thread Starter Thread Starter
  • #5
Now my computer wont detect the HDD at all

I agree but two hdd in a week. Could it be something to do with the motherboard damaging the hard drive?
 
Status
Not open for further replies.