Switching to Cable Select

[kep55]

I've a couple other posts on a 'machine_check_exception' error, but this post is to help me hopefully solve theproblem. I have a Maxtor 6Y080P0 80 GB HDD and a Western Digital WD 300BB-00AUA1 30 GB HDD. There's something funky with the WD that causes the error above. I want to switch the drives from Master / Slave to Cable Select. Is this doable with a 'live' system?

mobo = Gigabyte GA K8NS Pro
CPU = AMD Athlon64 3000+
Mem = Kingston Hyperx 512 MB DDR PC3200
BIOS = Award F1 3/1/04
OS = WinXPro
Need any other info?

I know enuff to be dangerous. :tongue:

 

[Crashman]

Yes, just power down and switch to cable select.

<font color=blue>Only a place as big as the internet could be home to a hero as big as Crashman!</font color=blue>
<font color=red>Only a place as big as the internet could be home to an ego as large as Crashman's!</font color=red>

 

[kep55]

Cheez, Crashman, is there anything you don't know about PCs? Once more, you've helped me out. And beaucoup others I'm sure.
Hey, Tom! How about a pat on the back to Crashman.

I know enuff to be dangerous. :tongue:

 

[Crashman]

There aren't many things I don't know about PC's in comparison to what I do know. But even I'm not perfect.

<font color=blue>Only a place as big as the internet could be home to a hero as big as Crashman!</font color=blue>
<font color=red>Only a place as big as the internet could be home to an ego as large as Crashman's!</font color=red>

 

[kep55]

Crapadoodle! I switched my Maxtor from master and my WD from slave to both as Cable Select. Doggone if I'm not still getting that frigging machine_check_exception error.
I did notice that if I move / copy more than one or two files at a time from the WD to the Max the mce crops up.

I know enuff to be dangerous. :tongue:

 

[kep55]

Okay, it's not the HD, although after two or three file transfers at once the MCE pops up. I got these errors from the Event Viewer. Could they be the cause?

Here are some error messages I found in the Event Viewer. They all point to the COM+ events. Could these be causing the MCE?

Event Type: Warning
Event Source: EventSystem
Event Category: (52)
Event ID: 4354
Date: 8/21/2004
Time: 8:38:20 PM
User: N/A
Computer: CAESAR
Description:
The COM+ Event System failed to fire the StartShell method on subscription {A5978620-5B3F-F1D1-8ED2-00FA0035B753}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}. The subscriber returned HRESULT 80004001.

Event Type: Warning
Event Source: EventSystem
Event Category: (52)
Event ID: 4356
Date: 8/21/2004
Time: 11:20:56 PM
User: N/A
Computer: CAESAR
Description:
The COM+ Event System failed to create an instance of the subscriber partition:{41E90F3E-56C1-4633-81C3-6E8BAC8BDD70}!new:{D3938AB0-5B9D-11D1-8DD2-00AA004ABD5E}. CoGetObject returned HRESULT 80070422.


Event Type: Warning
Event Source: EventSystem
Event Category: (54)
Event ID: 4353
Date: 8/21/2004
Time: 11:20:56 PM
User: N/A
Computer: CAESAR
Description:
The COM+ Event System attempted to fire the EventObjectChange::ChangedSubscription event but received a bad return code. HRESULT was 80040201.

I know enuff to be dangerous. :tongue:

 

[Scotty35]

Have a look <A HREF="http://www.microsoft.com/technet/support/ee/result.aspx?prodname=windows operating system&lcid=1033&evtid=4354&evtsrc=eventsystem&prodver=5.2" target="_new">here</A> and <A HREF="http://support.microsoft.com/default.aspx?scid=kb;en-us;319590&sd=ee" target="_new">here</A>

Also check the ram modules for errors with Memtest86 which you can <A HREF="http://www.google.com.au/search?hl=en&ie=UTF-8&q=memtest&btnG=Google+Search&meta=" target="_new">Google Search</A> for your self this time and check your PSU is big enough to handle your devices.

You posted the same thing in the XP forum so I will post the same reply here.

 

[kep55]

I ran memtest (all 11 tests) four times and the RAM passed everything. The PSU has 430 watts. I'm going to disconnect the case connectors (USB, front sound, etc. ) and see if that's the problem. Coolermaster admits the 1394 connector does NOT follw the IEEE standard.

I know enuff to be dangerous. :tongue: