1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Crash when encoding

Discussion in 'PC Hardware' started by CamaroZ28c, 2006/09/15.

  1. 2006/09/15
    CamaroZ28c

    CamaroZ28c Inactive Thread Starter

    Joined:
    2006/09/15
    Messages:
    5
    Likes Received:
    0
    Hello all, this is my first post here. Everytime I try to encode a video to create a dvd the computer will restart itself after a few minutes. I use Nerovision express to do this. I have gotten minidumps ranging from driver issues to memory corruption. This has been happening for quite a while now. I was told that my RAM was bad (and memtest also detected errors) so I bought 2 new sticks of Corsair XMS ddr400. I checked with them and they said my mobo would be compatible. Now memtest is seeing errors with this as well. I'd appreciate any help you guys can give. I have downloaded your dump checking software and if needed can post them here. Thanks again!
     
  2. 2006/09/15
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Did you load the BIOS defaults when you put in the new RAM?

    When you do, the BIOS will use the 'standard' timings for your RAM.

    If that doesn't help, it's likely we're looking at a faulty motherboard.
     
    Arie,
    #2

  3. to hide this advert.

  4. 2006/09/15
    mattman

    mattman Inactive Alumni

    Joined:
    2002/06/10
    Messages:
    8,198
    Likes Received:
    63
    If it is possible that greasy dust has been pushed into the RAM slots, get some Contact Cleaner and spray the slots and connectors on the RAM modules. Do not power up the system until it has completely dried and dissipated.

    Do the RAM tests on one stick at a time.

    Check the temperatures and the voltages. Here is a power calculator:
    http://www.journeysystems.com/power_supply_calculator.php

    If you cannot find any other cause than the motherboard, try doing a BIOS upgrade.

    Matt
     
  5. 2006/09/15
    CamaroZ28c

    CamaroZ28c Inactive Thread Starter

    Joined:
    2006/09/15
    Messages:
    5
    Likes Received:
    0
    Thanks guys, I will try that. By the way, it just crashed again and this time the dump says it was symevent.sys. I'll paste the results of that dump below.



    Opened log file 'c:\debuglog.txt'

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


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

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.050301-1519
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
    Debug session time: Fri Sep 15 20:26:04.312 2006 (GMT-5)
    System Uptime: 0 days 4:07:42.003
    Loading Kernel Symbols
    ..................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ............
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 4E, {2, 4a5bc, 7ffef, 1}

    *** ERROR: Symbol file could not be found. Defaulted to export symbols for SYMEVENT.SYS -
    Probably caused by : SYMEVENT.SYS ( SYMEVENT+2bae )

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

    1: kd> !analyze -v;r;kv;lmtn;.logclose;q
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    PFN_LIST_CORRUPT (4e)
    Typically caused by drivers passing bad memory descriptor lists (ie: calling
    MmUnlockPages twice with the same list, etc). If a kernel debugger is
    available get the stack trace.
    Arguments:
    Arg1: 00000002, A list entry was corrupt
    Arg2: 0004a5bc, entry in list being removed
    Arg3: 0007ffef, highest physical page number
    Arg4: 00000001, reference count of entry being removed

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


    CUSTOMER_CRASH_COUNT: 4

    DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

    BUGCHECK_STR: 0x4E

    LAST_CONTROL_TRANSFER: from 80529325 to 805371aa

    STACK_TEXT:
    ae98eb00 80529325 0000004e 00000002 0004a5bc nt!KeBugCheckEx+0x1b
    ae98eb28 804ec70c 00000000 c7860000 88c79568 nt!MiUnlinkPageFromList+0x3f
    ae98eb58 80583b6d c7860000 00000000 ae98ecd8 nt!MmCheckCachedPageState+0x227
    ae98ebe8 f7b72cc8 896215e8 1cc20000 00004000 nt!CcFastCopyRead+0x301
    ae98ec40 f743e9a2 896215e8 ae98ecd8 00004000 Ntfs!NtfsCopyReadA+0x1bf
    ae98ec68 ae7fbbae 896215e8 ae98ecd8 00004000 sr!SrFastIoRead+0x40
    WARNING: Stack unwind information not available. Following frames may be wrong.
    00000000 00000000 00000000 00000000 00000000 SYMEVENT+0x2bae


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    SYMEVENT+2bae
    ae7fbbae 5f pop edi

    SYMBOL_STACK_INDEX: 6

    FOLLOWUP_NAME: MachineOwner

    SYMBOL_NAME: SYMEVENT+2bae

    MODULE_NAME: SYMEVENT

    IMAGE_NAME: SYMEVENT.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP: 3ec1d807

    FAILURE_BUCKET_ID: 0x4E_SYMEVENT+2bae

    BUCKET_ID: 0x4E_SYMEVENT+2bae

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

    eax=f772713c ebx=0004a5bc ecx=00000000 edx=00000000 esi=8173b9a0 edi=c0396af4
    eip=805371aa esp=ae98eae8 ebp=ae98eb00 iopl=0 nv up ei ng nz na po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
    nt!KeBugCheckEx+0x1b:
    805371aa 5d pop ebp
    ChildEBP RetAddr Args to Child
    ae98eb00 80529325 0000004e 00000002 0004a5bc nt!KeBugCheckEx+0x1b (FPO: [Non-Fpo])
    ae98eb28 804ec70c 00000000 c7860000 88c79568 nt!MiUnlinkPageFromList+0x3f (FPO: [Non-Fpo])
    ae98eb58 80583b6d c7860000 00000000 ae98ecd8 nt!MmCheckCachedPageState+0x227 (FPO: [Non-Fpo])
    ae98ebe8 f7b72cc8 896215e8 1cc20000 00004000 nt!CcFastCopyRead+0x301 (FPO: [Non-Fpo])
    ae98ec40 f743e9a2 896215e8 ae98ecd8 00004000 Ntfs!NtfsCopyReadA+0x1bf (FPO: [Non-Fpo])
    ae98ec68 ae7fbbae 896215e8 ae98ecd8 00004000 sr!SrFastIoRead+0x40 (FPO: [Non-Fpo])
    WARNING: Stack unwind information not available. Following frames may be wrong.
    00000000 00000000 00000000 00000000 00000000 SYMEVENT+0x2bae
    start end module name
    804d7000 806fd000 nt ntkrnlmp.exe Tue Mar 01 18:57:27 2005 (42250F77)
    806fd000 8071dd00 hal halmacpi.dll Wed Aug 04 00:59:09 2004 (41107B2D)
    ae36d000 ae397180 kmixer kmixer.sys Wed Jun 14 03:47:45 2006 (448FCD31)
    ae480000 ae488080 ipfltdrv ipfltdrv.sys Fri Aug 17 15:55:07 2001 (3B7D84AB)
    ae528000 ae539ee0 NAVENG NAVENG.sys Fri Jul 28 19:07:55 2006 (44CAA6DB)
    ae53a000 ae602f20 NAVEX15 NAVEX15.sys Fri Jul 28 19:34:41 2006 (44CAAD21)
    ae603000 ae641000 NAVAP NAVAP.sys Fri May 02 23:08:14 2003 (3EB340AE)
    ae7f9000 ae809a60 SYMEVENT SYMEVENT.SYS Wed May 14 00:45:43 2003 (3EC1D807)
    ae832000 ae872280 HTTP HTTP.sys Thu Mar 16 18:33:09 2006 (441A03C5)
    aeb6b000 aeb92f00 secdrv secdrv.sys Tue Aug 31 08:42:55 2004 (4134805F)
    aebbb000 aec0c400 srv srv.sys Fri Apr 21 01:12:25 2006 (444877C9)
    aec0d000 aec1e000 NAVAPEL NAVAPEL.SYS Fri May 02 23:08:21 2003 (3EB340B5)
    aec96000 aecc2400 mrxdav mrxdav.sys Wed Aug 04 01:00:49 2004 (41107B91)
    aefe1000 aeff5400 wdmaud wdmaud.sys Wed Jun 14 04:00:44 2006 (448FD03C)
    af126000 af134d80 sysaudio sysaudio.sys Wed Aug 04 01:15:54 2004 (41107F1A)
    af502000 af505280 ndisuio ndisuio.sys Wed Aug 04 01:03:10 2004 (41107C1E)
    b161e000 b1624000 pgfilter pgfilter.sys Sun Sep 18 20:02:52 2005 (432E0E3C)
    b1686000 b169d480 dump_atapi dump_atapi.sys Wed Aug 04 00:59:41 2004 (41107B4D)
    b169e000 b16c1000 Fastfat Fastfat.SYS Wed Aug 04 01:14:15 2004 (41107EB7)
    b16cb000 b1739a00 mrxsmb mrxsmb.sys Fri May 05 04:41:42 2006 (445B1DD6)
    b1762000 b178ca00 rdbss rdbss.sys Fri May 05 04:47:55 2006 (445B1F4B)
    b182d000 b184ed00 afd afd.sys Wed Aug 04 01:14:13 2004 (41107EB5)
    b184f000 b186ff00 ipnat ipnat.sys Wed Sep 29 17:28:36 2004 (415B3714)
    b1870000 b1897c00 netbt netbt.sys Wed Aug 04 01:14:36 2004 (41107ECC)
    b1898000 b18efd80 tcpip tcpip.sys Thu Apr 20 06:51:47 2006 (444775D3)
    b18f0000 b1902400 ipsec ipsec.sys Wed Aug 04 01:14:27 2004 (41107EC3)
    b999b000 b999d900 Dxapi Dxapi.sys Fri Aug 17 15:53:19 2001 (3B7D843F)
    b9a29000 b9a5c200 update update.sys Wed Aug 04 00:58:32 2004 (41107B08)
    b9a5d000 b9a8d100 rdpdr rdpdr.sys Wed Aug 04 01:01:10 2004 (41107BA6)
    b9ade000 b9aeee00 psched psched.sys Wed Aug 04 01:04:16 2004 (41107C60)
    b9b8f000 b9ba5680 ndiswan ndiswan.sys Wed Aug 04 01:14:30 2004 (41107EC6)
    b9ba6000 b9bb9900 parport parport.sys Wed Aug 04 00:59:04 2004 (41107B28)
    b9bba000 b9c1bc00 ALCXSENS ALCXSENS.SYS Mon Feb 23 12:11:09 2004 (403A423D)
    b9c1c000 b9c3f980 portcls portcls.sys Wed Aug 04 01:15:47 2004 (41107F13)
    b9c40000 b9cd6700 ALCXWDM ALCXWDM.SYS Mon Jun 21 03:53:19 2004 (40D6A1FF)
    b9cd7000 b9cf9e80 USBPORT USBPORT.SYS Wed Aug 04 01:08:34 2004 (41107D62)
    b9cfa000 b9d1c680 ks ks.sys Wed Aug 04 01:15:20 2004 (41107EF8)
    b9d1d000 b9d30780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 01:07:04 2004 (41107D08)
    b9d31000 b9eb4000 ati2mtag ati2mtag.sys Tue Mar 21 21:56:21 2006 (4420CAE5)
    ba9c0000 ba9c0d00 dxgthk dxgthk.sys Fri Aug 17 15:53:12 2001 (3B7D8438)
    ba9e1000 ba9e3280 rasacd rasacd.sys Fri Aug 17 15:55:39 2001 (3B7D84CB)
    baf10000 baf1e100 usbhub usbhub.sys Wed Aug 04 01:08:40 2004 (41107D68)
    baf40000 baf49480 NDProxy NDProxy.SYS Fri Aug 17 15:55:30 2001 (3B7D84C2)
    baf50000 baf59f00 termdd termdd.sys Wed Aug 04 00:58:52 2004 (41107B1C)
    baf60000 baf68900 msgpc msgpc.sys Wed Aug 04 01:04:11 2004 (41107C5B)
    baf70000 baf7bd00 raspptp raspptp.sys Wed Aug 04 01:14:26 2004 (41107EC2)
    baf80000 baf8a200 raspppoe raspppoe.sys Wed Aug 04 01:05:06 2004 (41107C92)
    baf90000 baf9c880 rasl2tp rasl2tp.sys Wed Aug 04 01:14:21 2004 (41107EBD)
    bafa0000 baface00 i8042prt i8042prt.sys Wed Aug 04 01:14:36 2004 (41107ECC)
    bafdc000 bafdfc80 mssmbios mssmbios.sys Wed Aug 04 01:07:47 2004 (41107D33)
    baff8000 baffa580 ndistapi ndistapi.sys Fri Aug 17 15:55:29 2001 (3B7D84C1)
    baffc000 bafffc80 serenum serenum.sys Wed Aug 04 00:59:06 2004 (41107B2A)
    bf800000 bf9c1180 win32k win32k.sys Wed Oct 05 19:05:44 2005 (43446A58)
    bf9c2000 bf9d3580 dxg dxg.sys Wed Aug 04 01:00:51 2004 (41107B93)
    bf9d4000 bfa17000 ati2dvag ati2dvag.dll Tue Mar 21 21:56:42 2006 (4420CAFA)
    bfa17000 bfa56000 ati2cqag ati2cqag.dll Tue Mar 21 21:12:22 2006 (4420C096)
    bfa56000 bfa8c000 atikvmag atikvmag.dll Tue Mar 21 21:18:34 2006 (4420C20A)
    bfa8c000 bfd16120 ati3duag ati3duag.dll Tue Mar 21 21:40:09 2006 (4420C719)
    bfd17000 bfe2b100 ativvaxx ativvaxx.dll Tue Mar 21 21:33:39 2006 (4420C593)
    f7405000 f741f580 Mup Mup.sys Wed Aug 04 01:15:20 2004 (41107EF8)
    f7420000 f7436780 KSecDD KSecDD.sys Wed Aug 04 00:59:45 2004 (41107B51)
    f7437000 f7448f00 sr sr.sys Wed Aug 04 01:06:22 2004 (41107CDE)
    f7449000 f7468780 fltmgr fltmgr.sys Mon Aug 21 04:14:57 2006 (44E97991)
    f7469000 f7480800 SCSIPORT SCSIPORT.SYS Wed Aug 04 00:59:39 2004 (41107B4B)
    f7481000 f7499a80 viamraid viamraid.sys Fri Mar 31 00:18:28 2006 (442CC9B4)
    f749a000 f74b1480 atapi atapi.sys Wed Aug 04 00:59:41 2004 (41107B4D)
    f74b2000 f74d7700 dmio dmio.sys Wed Aug 04 01:07:13 2004 (41107D11)
    f74d8000 f74f6880 ftdisk ftdisk.sys Fri Aug 17 15:52:41 2001 (3B7D8419)
    f74f7000 f7506d80 serial serial.sys Wed Aug 04 01:15:51 2004 (41107F17)
    f7507000 f7511800 fetnd5bv fetnd5bv.sys Mon Jun 12 05:05:11 2006 (448D3C57)
    f7517000 f7525b80 drmk drmk.sys Wed Aug 04 01:07:54 2004 (41107D3A)
    f7527000 f7535080 redbook redbook.sys Wed Aug 04 00:59:34 2004 (41107B46)
    f7537000 f7543180 cdrom cdrom.sys Wed Aug 04 00:59:52 2004 (41107B58)
    f7547000 f7551380 imapi imapi.sys Wed Aug 04 01:00:12 2004 (41107B6C)
    f7557000 f755fd00 intelppm intelppm.sys Wed Aug 04 00:59:19 2004 (41107B37)
    f7597000 f75a7a80 pci pci.sys Wed Aug 04 01:07:45 2004 (41107D31)
    f75a8000 f75d5d80 ACPI ACPI.sys Wed Aug 04 01:07:35 2004 (41107D27)
    f75f7000 f75ffc00 isapnp isapnp.sys Fri Aug 17 15:58:01 2001 (3B7D8559)
    f7607000 f7611500 MountMgr MountMgr.sys Wed Aug 04 00:58:29 2004 (41107B05)
    f7617000 f7623c80 VolSnap VolSnap.sys Wed Aug 04 01:00:14 2004 (41107B6E)
    f7627000 f762fe00 disk disk.sys Wed Aug 04 00:59:53 2004 (41107B59)
    f7637000 f7643200 CLASSPNP CLASSPNP.SYS Wed Aug 04 01:14:26 2004 (41107EC2)
    f7647000 f7651e80 uagp35 uagp35.sys Wed Aug 04 01:07:43 2004 (41107D2F)
    f7687000 f768f700 netbios netbios.sys Wed Aug 04 01:03:19 2004 (41107C27)
    f7697000 f769f700 wanarp wanarp.sys Wed Aug 04 01:04:57 2004 (41107C89)
    f76b7000 f76bf880 Fips Fips.SYS Fri Aug 17 20:31:49 2001 (3B7DC585)
    f76c7000 f76cfd80 HIDCLASS HIDCLASS.SYS Wed Aug 04 01:08:18 2004 (41107D52)
    f76e7000 f76f6900 Cdfs Cdfs.SYS Wed Aug 04 01:14:09 2004 (41107EB1)
    f7707000 f770d200 PCIIDEX PCIIDEX.SYS Wed Aug 04 00:59:40 2004 (41107B4C)
    f770f000 f7713900 PartMgr PartMgr.sys Fri Aug 17 20:32:23 2001 (3B7DC5A7)
    f7717000 f771f000 videX32 videX32.sys Wed Feb 22 04:10:28 2006 (43FC3894)
    f771f000 f7725d00 viaagp1 viaagp1.sys Wed Jul 02 05:08:01 2003 (3F02AF01)
    f7757000 f775c200 vga vga.sys Wed Aug 04 01:07:06 2004 (41107D0A)
    f775f000 f7763a80 Msfs Msfs.SYS Wed Aug 04 01:00:37 2004 (41107B85)
    f7767000 f776e880 Npfs Npfs.SYS Wed Aug 04 01:00:38 2004 (41107B86)
    f776f000 f7775ee0 SCDEmu SCDEmu.SYS Mon Jun 05 09:08:33 2006 (44843AE1)
    f777f000 f7785180 HIDPARSE HIDPARSE.SYS Wed Aug 04 01:08:15 2004 (41107D4F)
    f7787000 f778d500 usbprint usbprint.sys Wed Aug 04 01:01:23 2004 (41107BB3)
    f778f000 f7793500 watchdog watchdog.sys Wed Aug 04 01:07:32 2004 (41107D24)
    f77d7000 f77de000 GEARAspiWDM GEARAspiWDM.sys Mon Apr 05 17:37:14 2004 (4071DF9A)
    f77df000 f77e4000 usbuhci usbuhci.sys Wed Aug 04 01:08:34 2004 (41107D62)
    f77e7000 f77e8000 fdc fdc.sys unavailable (00000000)
    f77ef000 f77f5000 kbdclass kbdclass.sys Wed Aug 04 00:58:32 2004 (41107B08)
    f77f7000 f77fb880 TDI TDI.SYS Wed Aug 04 01:07:47 2004 (41107D33)
    f77ff000 f7803580 ptilink ptilink.sys Fri Aug 17 15:49:53 2001 (3B7D8371)
    f7807000 f780b080 raspti raspti.sys Fri Aug 17 15:55:32 2001 (3B7D84C4)
    f780f000 f7814a00 mouclass mouclass.sys Wed Aug 04 00:58:32 2004 (41107B08)
    f7817000 f781c000 flpydisk flpydisk.sys Wed Aug 04 00:59:24 2004 (41107B3C)
    f786a000 f7896a80 NDIS NDIS.sys Wed Aug 04 01:14:27 2004 (41107EC3)
    f7897000 f789a000 BOOTVID BOOTVID.dll Fri Aug 17 15:49:09 2001 (3B7D8345)
    f7937000 f7939580 hidusb hidusb.sys Fri Aug 17 16:02:16 2001 (3B7D8658)
    f793b000 f793df80 mouhid mouhid.sys Fri Aug 17 15:47:57 2001 (3B7D82FD)
    f793f000 f7941760 IPFilter IPFilter.sys Wed May 09 20:59:32 2001 (3AF9F604)
    f7947000 f794ab00 usbscan usbscan.sys Wed Aug 04 00:58:44 2004 (41107B14)
    f7987000 f7988b80 kdcom kdcom.dll Fri Aug 17 15:49:10 2001 (3B7D8346)
    f7989000 f798a100 WMILIB WMILIB.SYS Fri Aug 17 16:07:23 2001 (3B7D878B)
    f798b000 f798c500 viaide viaide.sys Wed Aug 04 00:59:42 2004 (41107B4E)
    f798d000 f798e700 dmload dmload.sys Fri Aug 17 15:58:15 2001 (3B7D8567)
    f79a5000 f79a6100 swenum swenum.sys Wed Aug 04 00:58:41 2004 (41107B11)
    f79a7000 f79a8280 USBD USBD.SYS Fri Aug 17 16:02:58 2001 (3B7D8682)
    f79a9000 f79aaf00 Fs_Rec Fs_Rec.SYS Fri Aug 17 15:49:37 2001 (3B7D8361)
    f79ab000 f79ac080 Beep Beep.SYS Fri Aug 17 15:47:33 2001 (3B7D82E5)
    f79ad000 f79ae080 mnmdd mnmdd.SYS Fri Aug 17 15:57:28 2001 (3B7D8538)
    f79af000 f79b0080 RDPCDD RDPCDD.sys Fri Aug 17 15:46:56 2001 (3B7D82C0)
    f79b5000 f79b6100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 16:07:23 2001 (3B7D878B)
    f79c5000 f79c6a80 ParVdm ParVdm.SYS Fri Aug 17 15:49:49 2001 (3B7D836D)
    f7a4f000 f7a50000 speedfan speedfan.sys Wed Jun 15 09:55:53 2005 (42B04179)
    f7a50000 f7a50680 giveio giveio.sys Wed Apr 03 20:33:25 1996 (316334F5)
    f7ab2000 f7ab2b80 Null Null.SYS Fri Aug 17 15:47:39 2001 (3B7D82EB)
    f7abf000 f7abfc00 audstub audstub.sys Fri Aug 17 15:59:40 2001 (3B7D85BC)
    f7b52000 f7bde480 Ntfs Ntfs.sys Wed Aug 04 01:15:06 2004 (41107EEA)

    Unloaded modules:
    ae36d000 ae398000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ae36d000 ae398000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ae3bd000 ae3e8000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba9c1000 ba9c2000 drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    aeecb000 aeef6000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    af0e6000 af0f3000 DMusic.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    aefbe000 aefe1000 aec.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    af106000 af114000 swmidi.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7a07000 f7a09000 splitter.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f76a7000 f76b0000 processr.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f781f000 f7824000 Cdaudio.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba9e5000 ba9e8000 Sfloppy.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    Closing open log file c:\debuglog.txt
     
  6. 2006/09/15
    mattman

    mattman Inactive Alumni

    Joined:
    2002/06/10
    Messages:
    8,198
    Likes Received:
    63
    I am not familar with Memtest, try the memory diagnostics in my signature. They run from a floppy boot disk.

    Since this is to do with burning, I wonder if any of your programs have created "virtual" drives. I have had problems with those in the past. Look in Device Manager for any drives that you cannot identify as "real ". Virtual drives are created in the memory and may be a source of the problems.

    Look at the way you are carrying out the burning process. If you are trying to encode and burn at the same time, look at encoding to file and then burning. Try reducing the burn speed.

    Look at reinstalling the programs involved with the burning process (and probably best to uninstall first, then reinstall). Check for updates for your motherboard/chipset drivers (particularly the IDE drivers).

    Matt
     
  7. 2006/09/15
    mattman

    mattman Inactive Alumni

    Joined:
    2002/06/10
    Messages:
    8,198
    Likes Received:
    63
  8. 2006/09/22
    CamaroZ28c

    CamaroZ28c Inactive Thread Starter

    Joined:
    2006/09/15
    Messages:
    5
    Likes Received:
    0
    Just wanted to post a short note about the current situation with my problem. I went ahead and uninstalled the symantec antivirus and switched to the AVG one. Since then I have been able to encode video again. I'm hoping that it is a permanent solution and not just a temporary fluke. I just want to thank you all that responded very much for the help!!
     
  9. 2006/09/29
    CamaroZ28c

    CamaroZ28c Inactive Thread Starter

    Joined:
    2006/09/15
    Messages:
    5
    Likes Received:
    0
    Another quick update. After putting the side panel on (which has a window and another fan with leds) it started its crashing problem again. Leads me to believe that maybe the psu is not putting out what it is supposed to. Is it possible that the psu could be causing my RAM errors? Thanks again.
     
  10. 2006/09/29
    mattman

    mattman Inactive Alumni

    Joined:
    2002/06/10
    Messages:
    8,198
    Likes Received:
    63
    Here is a power calculator:
    http://www.journeysystems.com/power_supply_calculator.php
    also make a note of what he says about having enough amps on the 12 volt rail.

    I have a similar case/tower. I find you need to be careful connecting those fans, on mine the pins on the connector just push out the back when you connect them.

    Having the problem when you put the side-panel back on might make me wonder about a heat/temperature problem. Check the direction of which way the fans blow. Hold a sliver of paper next the fan vent. There should be a stream of air flowing in at the bottom/front and out at the top/back. Check there is a good flow coming out of the PSU. With so many "additional" fans, air may possibly be getting drawn in through the PSU, rather than blowing out (or the flow is weakened by the power of the other fans). PSU manufacturers are now using 120mm fans (some with 2).

    Check the vents for dust blockage. On that case I mentioned I need to remove all the fans occasionally to unblock the vents.

    Matt
     
  11. 2006/09/29
    CamaroZ28c

    CamaroZ28c Inactive Thread Starter

    Joined:
    2006/09/15
    Messages:
    5
    Likes Received:
    0
    thanks matt, i'll give it a try!
     
  12. 2006/09/29
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Nah, those only use a few watts.

    I'm with Matt here, and believe a cooling problem looks likely.
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.