Sign in with
Sign up | Sign in
Your question

Foxconn P9657AA-8KS2H Intel Core 2 Duo Crashes on Vid encode

Last response: in Overclocking
Share
December 28, 2006 6:37:02 PM

Hi, weird problem here.
I've just assembled a new system with the following specs:

Intel Core 2 Duo E6400 (Factory Clock at 2.13GHz) Factory Cooled

Foxconn P9657AA-8KS2H MB

1GB pqi TURBO 1GB 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400)

3x Seagate Barracuda 7200.9 ST3250824AS 250GB 7200 RPM 8MB Cache SATA 3.0Gb/s Hard Drives

Leadtek Winfast PX7950 GT TDH 256MB Geforce 7950GT 256-bit GDDR3 PCI Express x16 HDCP Video Card

Westinghouse LVM-42W2 42" 1080p Monitor (using HDCP DVI input)

Compaq DVD-ROM Drive

Lite-On DVD+/-RW DL

Anyway, the system runs perfectly in just about any application, be it HD Video Playback, Video Editing, Half-Life 2, Photoshop, Illustrator, what have you. However, every time I try to encode a video using ANY software, it crashes. Usually in the form of a spontaneous reboot in the middle of the encoding process. I've tried Divx Converter, Dr. Divx, Mediacoder, Videora iPod Converter, VirtualDub, etc. Everything behaves the same way. If I send the "System has recovered from a serious error" data to Microsoft after restarting, it usually tells me that "a driver" (it won't say which one) caused a System Stop, but once it told me that it was a service pack 2 problem. I'm thinking it may be a motherboard issue because in another (possibly unrelated) episode of bizarre behavior, the system won't let me use the keyboard (it's Ps2) under windows if I install nTune. Hence, my video card is also at the stock clock settings. The nTune thing is of little concern to me unless it's related to the video problem, but I do a LOT of video and I really can't have this problem right now. Google turns up nothing, so hopefully the Tom's crowd will have some ideas. This is really weirding me out. Anyone?
December 28, 2006 6:46:54 PM

What does the Event Viewer tell you?
December 29, 2006 3:49:19 AM

Hi, Thanks for your interest. Event viewer, most recently, said the following:

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 12/27/2006
Time: 7:35:42 PM
User: N/A
Computer: DESKTOP
Description:
Faulting application drdivx.exe, version 2.0.0.14, faulting module drdivx.exe, version 2.0.0.14, fault address 0x00051bec.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 64 72 64 ure drd
0018: 69 76 78 2e 65 78 65 20 ivx.exe
0020: 32 2e 30 2e 30 2e 31 34 2.0.0.14
0028: 20 69 6e 20 64 72 64 69 in drdi
0030: 76 78 2e 65 78 65 20 32 vx.exe 2
0038: 2e 30 2e 30 2e 31 34 20 .0.0.14
0040: 61 74 20 6f 66 66 73 65 at offse
0048: 74 20 30 30 30 35 31 62 t 00051b
0050: 65 63 0d 0a ec..
Related resources
December 30, 2006 2:26:26 PM

A second attempt yielded the same results, but with two errors this time:

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 12/29/2006
Time: 11:15:35 PM
User: N/A
Computer: DESKTOP
Description:
Faulting application drdivx.exe, version 2.0.0.14, faulting module drdivx.exe, version 2.0.0.14, fault address 0x00051bec.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 64 72 64 ure drd
0018: 69 76 78 2e 65 78 65 20 ivx.exe
0020: 32 2e 30 2e 30 2e 31 34 2.0.0.14
0028: 20 69 6e 20 64 72 64 69 in drdi
0030: 76 78 2e 65 78 65 20 32 vx.exe 2
0038: 2e 30 2e 30 2e 31 34 20 .0.0.14
0040: 61 74 20 6f 66 66 73 65 at offse
0048: 74 20 30 30 30 35 31 62 t 00051b
0050: 65 63 0d 0a ec..


As well as this one:


Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1001
Date: 12/29/2006
Time: 11:15:38 PM
User: N/A
Computer: DESKTOP
Description:
Fault bucket 332973384.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 42 75 63 6b 65 74 3a 20 Bucket:
0008: 33 33 32 39 37 33 33 38 33297338
0010: 34 0d 0a 4..


Seriously, anyone have ANY ideas whatsoever?
December 30, 2006 4:36:23 PM

:?: What PSU are you running ?

:?: What voltage is your RAM running at, and does it pass MemTest86+ and PRIME 95 (over all cores, and at least 85% of all RAM).
January 5, 2007 3:23:31 AM

Okay,

My PSU is an ALLIEO AL-A400ATX (400 W)

My RAM is running at stock voltage (2.0V) and it passes MemTest86+ and Prime 95 with no errors whatsoever. This may be a long shot, but I'm starting to wonder if it's the SATA Controller Drivers. My logic, convoluted as it may be, springs from the fact that the error reports that the system leads me to after reboots all seem to think I've received a BSOD (Blue Screen of Death) with warnings that sound vaguely familiar from the time about 5 years ago when I learned the importance of having 80-wire IDE ribbon cables. (If you plugged a newer HD in with an old 40-wire cable, your system would BSOD). I've tried updating the drivers there, but that doesn't seem to work either. Alas. As usual, any suggestions would be absolutely appreciated. Thanks in advance.
January 5, 2007 7:31:45 AM

Try setting PCI Express Frequency in the BIOS to 99 MHz or 101 MHz instead.

Confirm Intel INF Drivers installed (PCI, IDE, etc)

Check BIOS for anything related to IDE, SATA, or RAID, or Disk Controllers, might be worth listing what you've got.

I find the most annoying problems often have a fairly simple solution.
January 8, 2007 3:46:12 PM

Fixed the problem: Bought an Nvidia Chipset ASUS Motherboard. Works like a charm. I know, it's kinda the coward's way out, but I really need this system working and I just didn't have the time to keep trying different tests. I would definitely like to thank everyone that tried to help out though. It's good to know you're out there. Thanks.
January 8, 2007 7:32:22 PM

Quote:
My logic, convoluted as it may be, springs from the fact that the error reports that the system leads me to after reboots all seem to think I've received a BSOD (Blue Screen of Death) with warnings that sound vaguely familiar from the time about 5 years ago when I learned the importance of having 80-wire IDE ribbon cables. (If you plugged a newer HD in with an old 40-wire cable, your system would BSOD).


The reason (years ago) that they started using 80 wire cables was that back then you could get data corruption through line induction when the data wires sat right next to each other. Basically getting crosstalk interferance between lines. The extra 40 wires that were added are simply ground lines inbetween each data line. The grounded wire has the effect of minimizing the "field" the data lines create when current pssses through them.

I wont do it, but I am assuming that using a 40 wire IDE cable is no longer an issue and should work the same as an 80 wire. The reason I say this is because everyone is using rounded cables, thus negating the effect an 80 wire ribbon cable has on line induction (electro magnetic crosstalk).
!