AMD Processors
Decrease font size
Increase font size
Topic Title: Another random BSODs thread
Topic Summary:
Created On: 02/10/2006 07:47 PM
Status: Read Only
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
View similar topics View similar topics
View topic in raw text format. Print this topic.
 02/10/2006 07:47 PM
User is offline View Users Profile Print this message

Author Icon
Miniboss204
Junior Member

Posts: 2
Joined: 02/06/2006

Ever since I've upgraded to an AMD 64 X2 4400+ (or maybe the WD Raptor two weeks earlier), I've gotten random BSODs. (I HOPE it's just a coincidence).

My computer has crashed four times on me so far. One time, I had just clicked on add/remove programs. And, another time it had crashed while I was browsing the internet and had Prime95 running for about 16 hours or so (Prime95 had no errors leading up to that point, so I doubt it was Prime95 related.).

My system specs:

Windows XP Professional, service pack 2
ASROCK 939 Dual Sata with latest bios (1.5)
2 gigs (4x512) of dual-channel pc3200 ram (by Transcend)
ATI x1800 XT with 6.2 drivers
Creative X-Fi ExtremeMusic
Thermaltake Silent Purepower 480w power supply (+12V@18A)
WD Raptor 74 gigs
Lite-On DVDRW SOHW-1633S

Nothing is overclocked.


Can someone translate these minidumps for me?

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: c05d3a98, lock type that was held (value 1,2,3, or PTE address)
Arg2: c000009d, error status (normally i/o status code)
Arg3: ba753642, current process (virtual address for lock type 3, or PTE)
Arg4: 1e342860, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------

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


MODULE_NAME: ftdisk

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 3b7d8419

ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000009d

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 80514ce0 to 804f9c37

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
bacf7930 80514ce0 0000007a c05d3a98 c000009d nt+0x22c37
bacf7960 8051584d 813d3b38 c05d3a98 ba753642 nt+0x3dce0
bacf79e0 8051f347 c05d3a98 ba753642 c05d3a98 nt+0x3e84d
bacf7a4c 80543568 00000008 ba753642 00000000 nt+0x48347
bacf7a64 ba753642 badb0d00 00000000 84eaba50 nt+0x6c568
bacf7b2c bab3297e 89e068e0 89dfd7e8 89e03a38 ftdisk+0xa642
bacf7b74 bab32e8a 89dc2ec0 87a55024 87a550e4 PartMgr+0x297e
bacf7ba0 bab3300d 89dc2ec0 c00000bb 87a55108 PartMgr+0x2e8a
bacf7bdc 804eeeb1 89dc2e08 87a55008 bacf7c5c PartMgr+0x300d
bacf7c18 804f6b05 89dc2e08 bacf7c38 bacf7c84 nt+0x17eb1
bacf7c60 805927ec 00000003 89e03a38 00000001 nt+0x1fb05
bacf7c88 805933a1 00000000 00000003 00000001 nt+0xbb7ec
bacf7cb0 80598c12 89e03a38 00000003 bacf7d20 nt+0xbc3a1
bacf7d3c 805993de bacf7d78 806e4974 e110a238 nt+0xc1c12
bacf7d58 80599537 bacf7d78 84f30c80 8056375c nt+0xc23de
bacf7d7c 80537757 84f30c80 00000000 89e3eb30 nt+0xc2537
bacf7dac 805ce794 84f30c80 00000000 00000000 nt+0x60757
bacf7ddc 805450ce 80537668 00000001 00000000 nt+0xf7794
00000000 00000000 00000000 00000000 00000000 nt+0x6e0ce


STACK_COMMAND: kb

FOLLOWUP_IP:
ftdisk+a642
ba753642 ?? ???

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 5

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: ftdisk+a642

IMAGE_NAME: ftdisk.sys

BUCKET_ID: WRONG_SYMBOLS

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


::::ERROR #2::::



KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: c05d3808, lock type that was held (value 1,2,3, or PTE address)
Arg2: c000009d, error status (normally i/o status code)
Arg3: ba701e40, current process (virtual address for lock type 3, or PTE)
Arg4: 6343d860, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------

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


FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 41107b4b

ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000009d

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 80514ce0 to 804f9c37

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
bad07874 80514ce0 0000007a c05d3808 c000009d nt+0x22c37
bad078a4 8051584d 81b616ac c05d3808 ba701e40 nt+0x3dce0
bad07924 8051f347 c05d3808 ba701e40 c05d3808 nt+0x3e84d
bad07990 80543568 00000008 ba701e40 00000000 nt+0x48347
bad079a8 ba701e40 badb0d00 89dd4a38 bad07c01 nt+0x6c568
bad07a2c 804eeeb1 89dd4a38 870a3008 bad07aac SCSIPORT+0xee40
bad07a68 804f6b05 89dd4a38 bad07a88 89d902d8 nt+0x17eb1
bad07ab0 8058db31 00000000 89e5d4a8 00000001 nt+0x1fb05
bad07ac8 80590f93 89d901f8 00000001 87873858 nt+0xb6b31
bad07d20 805913d2 89d901f8 00000001 00000000 nt+0xb9f93
bad07d54 804f669f 00000003 8055a5c0 8056375c nt+0xba3d2
bad07d7c 80537757 00000000 00000000 89e3e3c8 nt+0x1f69f
bad07dac 805ce794 00000000 00000000 00000000 nt+0x60757
bad07ddc 805450ce 80537668 00000001 00000000 nt+0xf7794
00000000 00000000 00000000 00000000 00000000 nt+0x6e0ce


STACK_COMMAND: kb

FOLLOWUP_IP:
SCSIPORT+ee40
ba701e40 ?? ???

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 5

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: SCSIPORT+ee40

MODULE_NAME: SCSIPORT

IMAGE_NAME: SCSIPORT.SYS

BUCKET_ID: WRONG_SYMBOLS

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

I have also gotten a kernel_stack_inpage_error and a machine_check_exception_error.

One thing that I've noticed is that the error code "9D" has popped up in at least two or three of the errors.

0xC000009D, or STATUS_DEVICE_NOT_CONNECTED: bad cabling, non-termination, or the controller is not able to obtain access to the hard disk.

I've replaced the SATA cable that came with the motherboard with a WD SecureConnect SATA cable. That wasn't the "fix", unfortunately.

Cool 'n' Quiet is disabled.

Ran MemTest overnight with no errors.

CPU temps are usually around 37C to 41C.
 02/10/2006 08:21 PM
User is offline View Users Profile Print this message

Author Icon
majmac01
Senior Member

Posts: 621
Joined: 09/20/2005

It is a memory problem.
Try running your rig with just two (2) sticks of your RAM and see if that improves things. If it does I'll say a bit more about setting up four sticks of RAM (You would be better off with two sticks of 1Gig RAM though!
 02/10/2006 08:30 PM
User is offline View Users Profile Print this message

Author Icon
Miniboss204
Junior Member

Posts: 2
Joined: 02/06/2006

quote:

Originally posted by: majmac01
It is a memory problem.
Try running your rig with just two (2) sticks of your RAM and see if that improves things. If it does I'll say a bit more about setting up four sticks of RAM (You would be better off with two sticks of 1Gig RAM though!



Thanks for the quick reply!

I was planning to buy new RAM anyway (leftover from a previous setup). But until then, I'll leave two sticks in there, and see how things go.
 05/02/2006 03:24 PM
User is offline View Users Profile Print this message

Author Icon
Froschkoenig84
Junior Member

Posts: 1
Joined: 05/02/2006

Hey.

I don't think that. - I've the same problem and just one Single-Memory.

...BUT I've a SATA-Controler-Card (SATA-IC) for any days and since this day, I've that problem.
btw. - "SCSIPORT.SYS" seems to say "HDD-Connection-Error", doesn't it?

I think the PC is faild to connect one of the Disks. - Maybe loosing at run time. - So it gives a bluescreen.

I installed a WindowsXP-Software-RAID - and I recognized one of my both HDDs going disconnected at runningmode. Windows don't like this and gives the blusescreen to sav the Hardware/Data/whatever.

I don't know a solution at the moment, but I will check it out. - Later I will tell you.
 05/03/2006 07:01 AM
User is offline View Users Profile Print this message

Author Icon
varianiv
Senior Member

Posts: 1254
Joined: 11/22/2004

When you installed Windows on your Raptor, did you remember to install the SATA controller driver using the "F6" option at the beginning of setup? Usually if you forget to install it your hard drive ends up being a weird letter like "D:" or "H:" instead of "C:", and Windows will complain that you don't have a paging file set. BSODs are also a common occurrence, since Windows does not know how to properly interface with your SATA drive.

It does appear to be a memory error at first glance, but the fact that you ran memtest86 successfully leads me to believe otherwise...

Hope all this helps.

-------------------------
AMD Opteron 165 CCBBE (2.7GHz @ 1.35v)
DFI CFX3200-DR (07/28)
Kingston HyperX DDR500 (3-3-3-8-1T)
Asus Dark Knight Radeon 4870 1GB
Audigy 2
2x 74GB Western Digital Raptors in RAID0
500GB SATA-300 WD Drive
CoolerMaster RealPowerPro 850W
NZXT Zero full-tower case
Windows XP Pro SP2
Statistics
112018 users are registered to the AMD Processors forum.
There are currently 0 users logged in.

FuseTalk Hosting Executive Plan v3.2 - © 1999-2014 FuseTalk Inc. All rights reserved.



Contact AMD Terms and Conditions ©2007 Advanced Micro Devices, Inc. Privacy Trademark information