Sign in with
Sign up | Sign in
Your question
Solved

BSOD and Maxtor hard drive, what could it be?

Tags:
  • Hard Drives
  • Blue Screen
  • Maxtor
  • Storage
Last response: in Storage
Share
November 21, 2009 3:16:27 PM

Hello:

I have the following equipment:

MB P4VM800
CPU Pentium 4 3.0 GHz
512 MB RAM
1 80GB Maxtor 6L080L0 HDD
1 DVD drive

OS:Windows XP SP3

BIOS temps:

CPU 60oC
M/B 37oC
CPU Fan Speed 2463 RPM
Chassis Fan speed N/A
Vcore 1.354V
+3.30V 3.370V
+5.00V 5.148V
+12.00V 12-129V

I'm getting the BSOD often and the event viewer reports a lot of:

Event_ID:11
Source: Disk
Description:The driver detected a controller error on \Device\Harddisk0\D.

Event_ID:5
Source:atapi
Description:A parity error was detected on \Device\Ide\IdePort0.

I bought a new IDE cable and didn't make a difference.

I ran SeaTools for Windows and the results were the following:

11/20/2009 5:16:37 PM
Model: Maxtor 6L080L0
Serial Number: L22WZ8EG
Firmware Revision: BAJ41G20
SMART - Pass 11/20/2009 5:16:37 PM
Short DST - Started 11/20/2009 5:16:46 PM
Short DST - Pass 11/20/2009 5:18:02 PM
Long DST - Started 11/20/2009 8:03:18 PM
Long DST - Pass 11/20/2009 8:44:46 PM

So basically all the test passed so I think the hard disk is not the problem.

Anyone knows what else could be causing then BSOD and the Event_ID 11 errors?

By the way this PC has a fresh copy of Windows XP SP3 installed. I reinstalled it thinking it may be a OS issue but apparently it isn't.

These are the contents of a dump file displayed by WinDbg:

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


Loading Dump File [C:\WINDOWS\Minidump\Mini111809-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 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Mon Nov 16 09:39:33.890 2009 (GMT-7)
System Uptime: 0 days 0:50:44.609
*********************************************************************
* 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 10000050, {ffffffe8, 1, 804e1928, 0}

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

*************************************************************************
*** ***
*** ***
*** 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+a928 )

Followup: MachineOwner

Thanks and any help is appreciated

More about : bsod maxtor hard drive

November 21, 2009 4:31:02 PM

i am new here, but will try 2 help u.

can u download this software

http://aeo3.com/hdsmart/index.html

and copy & paste the log file here.

the app is free and can access the hdd controller and hard disk smart info. some1 showed this to me few weeks ago.
m
0
l
November 21, 2009 4:45:05 PM

Here's the info:

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

Aeo3 HD Smart Lite (www.aeo3.com)

HD Smart Log Date-Time: 2009-Nov-21 11:42:44

CTRL-C to copy log to clipboard.

Hard drive SMART data may not be accessable via SCSI, FireWire and USB.
Some older hard drive do not have SMART data logging capability.
BIOS's Hard Drive SMART must be Enabled to access drive status.

* = Health Related Attribute. Refer to RawDec for value.


----------------------------------------------------------------------------------------------------------------------------------------------------------
AVAILABLE DISKS (USB, 1394, IDE, SATA, SCSI or in RAID Configuration)
----------------------------------------------------------------------------------------------------------------------------------------------------------
Disk Index: 0
Model: Maxtor 6L080L0
Size: 76.33 GB (81956689920 Byte)
Partitions: 2
Type: Fixed hard disk media
Interface: IDE
Status: OK

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



----------------------------------------------------------------------------------------------------------------------------------------------------------
HARD DISK S.M.A.R.T. DATA
----------------------------------------------------------------------------------------------------------------------------------------------------------
Disk Index 0
Model Maxtor 6L080L0
Serial L22WZ8EG
Heads 16
Size 76.33 GB
Partitions 2
Status OK
----------------------------------------------------------------------------------------------------------------------------------------------------------
No. AttrID AttrName RawDec Trshld Worst Value RawHex
----------------------------------------------------------------------------------------------------------------------------------------------------------
1 003 SPIN-UP TIME....................... 703 63 252 252 0000000002BF
2 004 START STOP COUNT................... 7 0 253 253 000000000007
3 005 * REALLOCATED SECTOR COUNT........... 0 63 253 253 000000000000
4 006 READ CHANNEL MARGIN................ 0 100 253 253 000000000000
5 007 SEEK ERROR RATE.................... 0 0 248 253 000000000000
6 008 SEEK TIME PERFORMANCE.............. 42651 187 239 248 00000000A69B
7 009 POWER-ON HOURS..................... 51643 0 242 242 00000000C9BB
8 010 * SPIN RETRY COUNT................... 0 157 252 252 000000000000
9 011 CALIBRATION RETRY COUNT............ 0 223 252 252 000000000000
10 012 POWER CYCLE COUNT.................. 1251 0 250 250 0000000004E3
11 192 POWER OFF RETRACT CYCLE............ 0 0 253 253 000000000000
12 193 LOAD UNLOAD CYCLE COUNT............ 0 0 253 253 000000000000
13 194 TEMPERATURE........................ 21 0 253 35 000000000015
14 195 HARDWARE ECC RECOVERED............. 527 0 252 253 00000000020F
15 196 * REALLOCATION EVENT COUNT........... 0 0 253 253 000000000000
16 197 * CURRENT PENDING SECTOR COUNT....... 0 0 253 253 000000000000
17 198 * UNCORRECTABLE SECTOR COUNT......... 0 0 253 253 000000000000
18 199 ULTRADMA CRC ERROR RATE............ 17754 0 1 1 00000000455A
19 200 WRITE ERROR RATE................... 0 0 252 253 000000000000
20 201 * SOFT READ ERROR RATE............... 0 0 252 253 000000000000
21 202 DATA ADDRESS MARK ERRORS........... 0 0 252 253 000000000000
22 203 RUN OUT CANCEL..................... 0 180 252 253 000000000000
23 204 SOFT ECC CORRECTION................ 0 0 252 253 000000000000
24 205 THERMAL ASPERITY RATE (TAR)........ 0 0 252 253 000000000000
25 207 SPIN HIGH CURRENT.................. 0 0 252 252 000000000000
26 208 SPIN BUZZ.......................... 0 0 252 252 000000000000
27 209 OFFLINE SEEK PERFORMANCE........... 157 0 240 240 00000000009D
28 210 ...UNKOWN...VENDOR SPECIFIC........ 0 0 252 253 000000000000
29 211 VIBRATION DURING WRITE............. 0 0 252 253 000000000000
30 212 SHOCK DURING WRITE................. 0 0 252 253 000000000000
----------------------------------------------------------------------------------------------------------------------------------------------------------





----------------------------------------------------------------------------------------------------------------------------------------------------------
IDE CONTROLLER
----------------------------------------------------------------------------------------------------------------------------------------------------------
Status Name/Description
----------------------------------------------------------------------------------------------------------------------------------------------------------
OK VIA Bus Master IDE Controller
OK Primary IDE Channel
OK Secondary IDE Channel
----------------------------------------------------------------------------------------------------------------------------------------------------------



----------------------------------------------------------------------------------------------------------------------------------------------------------
SCSI, SATA, DEDICATED CONTROLLER or RAID CONTROLLER
----------------------------------------------------------------------------------------------------------------------------------------------------------
Status Name/Description
----------------------------------------------------------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------------------------------------------------------



m
0
l
Related resources
November 22, 2009 2:34:59 PM

From the Aeo3 HDD SMART and Controller info, i think the hard disk is ok. No surface defects.

Windows does not seem to think the HDD controller is a problem as status is OK.

But between the controller and HDD, the

ULTRADMA CRC ERROR RATE............ 17754 <------ Here's yr problem.

THAT is definately too high - the number of errors in data transfer via the interface cable.

I think the possible source:

(A) I know u got a new cable, but it is the most likely cause. Recommend, using standard flat cable. Avoid those flat cables being rounded into a rubber tube for better airflow. Get one from a working system and see how that goes.

Use IDE cable with all 80 pins connected. Not those specifically came with CD/DVD-ROM drives.

http://www.pcguide.com/ref/hdd/if/ide/confCable80-c.htm...


(B) Interference near the HDD cable? Any potential source that can create an interference? Flat IDE


(C) If the cable is not the problem, than the connectors on the board or hdd may be of issue. Check for broken connectors or bent pin. This is usually very unlikely.


Your problem is definitely between the HDD and motherboard. All other hardware is ok.

Good luck.
m
0
l
November 22, 2009 2:47:52 PM

Hello:

I just ran memtest and it found a lot of errors.

Can this be the main problem?

Thanks
m
0
l

Best solution

November 23, 2009 5:40:52 AM

Since your hdd has lots of "ULTRADMA CRC ERROR RATE............ 17754", it is or was a problem. use aeo3 hd smart to check every day and see if that number increases. if it rises overtime, there is still a cable problem.

I definitely think the RAM errors are bigger problem than the hdd.

let's fix the RAM problem 1st.

ram test software:
1. memtest86+
2. prime95 (http://www.mersenne.org/freesoft/)

I like prime95 better b'cos it puts the whole memory system under stress during test. it can detect errors more realistically that is missed by memtest. if interested to know why, ask me later.

oh, don't update firmware when u got ram issues.

to do:

1. check if all ram sticks are the same speed, model or brand. let me know here.

2. remove all RAM and install only 1 stick on slot-1. run prime95 > torture test > lots of ram tested option. test each stick of ram in slot-1 individually for 30-60min.

mark ram with errors. those with errors doesn't mean it's broken.

3. combine good ones in slot-1 & 2. run prime95 again.

if error occurs now with 2 good stick of rams (when tested individually), it's a COMPATIBILITY problem between them.

If the ram speed is the same, go into BIOS and manually increase the DRAM voltage by 1 level/notch above the default DRAM Volt value. be careful not to raise dram voltage too much, it can damage and degrade.

run prime95 tests again.


if you want to know more, let me know the memory specs on each stick, including your motherboard.

hope this helps.
Share
November 23, 2009 9:10:17 PM

ok I already replaced the bad memory module which it is damaged. PC never even booted when I placed the bad module on the first slot.

Ran memory tests and there are no longer any errors.

Second thing the PC has is the IDE connector from the motherboard, it's bad.

I swapped it to the other one and the event viewer never reported the "disk error" error. As soon as I changed the cable to the original IDE connector, bum !! 10 errors appeared immediately on the event viewer.

So as long as I don't add any new IDE devices I won't have to replace the MB.

Thansk a lot for your help sefo.
m
0
l
!