hi there,

Wondering if any of you good would like to help me with my unique problem. As the title says i have lost 4 HD's in a month and its driving me crazy not to mention lightening my wallet. I am new to this forum so i'm not sure how to proceed.

I installed a new MB last month after which i have started losing my HD's. I took my PC back to the technican and we tried to figure out if the problem was my motherboard. He found nothing wrong so we changed the HD again. Went back home and the same problem occoured 3 days later. system kept shutting down and on restart it would display the "your system has recovered from a serious error" message. it would do that about 3-4 times and then i would lose the HD. so we changed the HD again and installed a fresh piece... a week later the same problem and bye bye HD. I am concerned at whats happening and am wondering if i should consign this comp to the hardware graveyard!! JK.

Now the last time is the real doozy! comp shutdown while i was watching a video using VLC player and on restart the serious error message came up again. After that when it shut down for the second time the comp would not register the HD. I checked the bios and the HD did not show. then when i pushed the restart button about 5-6 times it came back on and started loading windows! but it did not get any further than that. it froze and when i tried restarting it did not recognise the disc. so i shut the somputer down for a couple of hours and tried again the problem still persisted. so i gave up and went out to order a new HD. i come back about 5 hours later and the wife is on the comp. The machine restarted without a hitch! i'm scared here... do i have a ghost in my system? lol. But seriously i would love it if one of you could help me. I'll post my comp specs to the best o my knowledge so if i miss anything please ask me and i will try to get the information to you.

Specs
OS: WinXP Pro
Ram : 2GB Kingston 633
HD : 1x80GB Seagate, 1x250GB Seagate
Motherboard: biostar GeForce 7050/610i M7-SE 256MB shared memory
SMTP: 450w
Chip : Intel DualCore 2.66GHZ

Thats all i can think of. lemme know if you need any more information.

Thanks for reading.

ReB.


And here's the debugger report:

Loading Dump File [C:\WINDOWS\Minidump\Mini080508-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
************************************************** **************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
************************************************** **************************
Executable search path is:
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Tue Aug 5 22:49:56.734 2008 (GMT+5)
System Uptime: 0 days 0:46:13.442
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded 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, {c000000e, c000000e, 0, 372000}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Probably caused by : ntoskrnl.exe ( nt+22c37 )

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

First off the hard drives, if truly faulty, would be under a full warranty.

Did you run the manufacturers diagnostic on them or how do you know or think they are faulty in themselves?

Seatools for DOS is the Seagate diag:

Seagate Technology - SeaTools


Your dump although limited by wrong symbols is a dump caused by MEMORY_CORRUPTION.

Are you sure your RAM is compatible with the motherboard?

Try running MemTest.

Just to add if it were not MEMORY_CORRUPTION it might be on further review:


0x00000077 or "KERNEL_STACK_INPAGE_ERROR"


0xC000000E, or STATUS_NO_SUCH_DEVICE: the drive went unavailable, possibly a bad hard drive, disk array, and/or controller card.


I would still test the hard drives with SeaTools first.

Then it might be time to suspect a bad motherboard.

We could also get more details if you try to get more dump logs.

BSOD
--------------------------------------------------
Read the post HERE for a few diagnostic ideas and post back any relevant data.

could you tell me how to run the SEA tools test. Not sure and i don't wanna jack anything up by doing the wrong thing. (i'm stupid you see)

Thanks

ReB.

Do you have a floppy drive?

Anyway if you have a floppy drive that is the easiest.

If not you need to use a CD ISO.

Details:

Answer

If you only have CD and have no software that can create an ISO here is a free ISO burner:

ISO Recorder v 2

i have burned the CD with Nero Express. is there something else i need to do?

No Floppy drive!

If you used NERO you need to have chosen: Burn Disk Image.

This is not a data CD.

If you did create a Disk Image then just boot the CD.


Verify that your BIOS has the CD set to boot prior to the hard drive.

yeah i did'nt change the priority in the Bios. Will do that now and get back with the results.

Thanks,

ReB