PC resets intermittently (1 Viewer)

MattyZee

Portal Member
November 23, 2007
23
0
Adelaide
Home Country
My PC keeps resetting/crashing when TV server is recording. It can run fine for hours on end when idle but everytime i have tried to record, the PC has reset at least once for every time. I have attached the log files of the most recent (2nd reset ~30min into a 50min recording).

Oh, and Merry Christmas to all! :)

TV-Server Version: SVN 19-12-2007 Rev16673
MediaPortal Version: 0.2.3.0 +SVN 19-12-2007 Rev16673
MediaPortal Skin: Blue Two Wide
Windows Version: XP SP2
CPU Type: Intel Core2 Duo E6750
HDD: Seagate 250Gb
Memory: 2Gb Generic
Motherboard: Asus P5K Premium
Motherboard Chipset:
Motherboard Bios:
Video Card: Gigabyte GeForce 8500 GT
Video Card Driver:
Sound Card: Onboard
Sound Card AC3: Coaxial out
Sound Card Driver:
1. TV Card: Digital Now
1. TV Card Type: Dual Hybrid S2 PCIe
1. TV Card Driver: 1.0.4.2 (22/11/2007) NXP
2. TV Card:
2. TV Card Type:
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec: NVIDIA PureVideo
MPEG2 Audio Codec:
Satelite/CableTV Provider:
HTPC Case: Zalman HD135
Cooling:
Power Supply: Antec Trio
Remote:
TV: Panasonic 42" Plasma TH42PZ700A
TV - HTPC Connection: DVI->HMDI
 

level20peon

MP Donator
  • Premium Supporter
  • January 4, 2007
    1,082
    101
    42
    Aachen
    Home Country
    Germany Germany
    Hello MattyZee,

    I cannot find anything unusual in your logs. However there are hints you are using PowerScheduler. Maybe you should disable it and see whether the problem still occurs or not.

    Maybe you also should have a look into your Windows event log. There might be more usefull information to find.


    -level20peon
     

    MattyZee

    Portal Member
    November 23, 2007
    23
    0
    Adelaide
    Home Country
    Thanks Level20peon,

    Thats odd, i don't have power scheduler enabled. Why would this even be mentioned if i'm not using it?

    I've had a look in the Windows Event View and this is all i could see of interest:

    Information
    Code:
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x100000d1 (0xf76ce372, 0x00000005, 0x00000008, 0xf76ce372). A dump was saved in: C:\WINDOWS\Minidump\Mini122507-02.dmp.
    and
    Error
    Code:
    Error code 100000d1, parameter1 f76ce372, parameter2 00000005, parameter3 00000008, parameter4 f76ce372.
     

    ronilse

    Retired Team Member
  • Premium Supporter
  • July 19, 2005
    4,422
    283
    Moss
    Home Country
    Norway Norway
    Hi,
    MattyZee, have you enabled Grab EPG while timeshifting(if you have try to disable it)?

    Regards
    Roy
     

    MattyZee

    Portal Member
    November 23, 2007
    23
    0
    Adelaide
    Home Country
    Hi ronilse,

    No, i don't have EPG grab enabled during timeshifting. I actually use Big_Kev's EPG Download Manager and have it setup to grab the xmltv EPG at 4:00AM each day.

    I have downloaded WinDbg and am going to try and get some info from my MiniDump files. I will let you know what i find but i'm still open to suggestions in the meantime :)

    Thanks
     

    level20peon

    MP Donator
  • Premium Supporter
  • January 4, 2007
    1,082
    101
    42
    Aachen
    Home Country
    Germany Germany
    Thats odd, i don't have power scheduler enabled. Why would this even be mentioned if i'm not using it?

    I don't know. It is never mentioned in my logs, I also haven't enabled it.


    Information
    Code:
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x100000d1 (0xf76ce372, 0x00000005, 0x00000008, 0xf76ce372). A dump was saved in: C:\WINDOWS\Minidump\Mini122507-02.dmp.

    So what does this dump bmp say :rolleyes: ?


    -level20peon
     

    MattyZee

    Portal Member
    November 23, 2007
    23
    0
    Adelaide
    Home Country
    Well, it seems something in the DVICO software was causing the resets. So its not the TV servers fault. Here is the output of the WinDbg.
    Thanks for your help level20peon and ronilse.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: f76ce372, memory referenced
    Arg2: 00000005, IRQL
    Arg3: 00000008, value 0 = read operation, 1 = write operation
    Arg4: f76ce372, address which referenced memory
    
    Debugging Details:
    ------------------
    
    READ_ADDRESS:  f76ce372 
    
    CURRENT_IRQL:  5
    
    FAULTING_IP: 
    ZuluVcap+2372
    f76ce372 ??              ???
    
    CUSTOMER_CRASH_COUNT:  2
    
    DEFAULT_BUCKET_ID:  DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  Idle
    
    LAST_CONTROL_TRANSFER:  from 00000000 to f76ce372
    
    FAILED_INSTRUCTION_ADDRESS: 
    ZuluVcap+2372
    f76ce372 ??              ???
    
    STACK_TEXT:  
    f7a07c3c 00000000 8656e8d4 f76ce3b4 03000206 ZuluVcap+0x2372
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    ZuluVcap+2372
    f76ce372 ??              ???
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  ZuluVcap+2372
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: ZuluVcap
    
    IMAGE_NAME:  ZuluVcap.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  448f8e0b
    
    FAILURE_BUCKET_ID:  0xD1_CODE_AV_BAD_IP_ZuluVcap+2372
    
    BUCKET_ID:  0xD1_CODE_AV_BAD_IP_ZuluVcap+2372
    
    Followup: MachineOwner

    For anyone else having problems with the PC resetting (for any reason) here is a really good intro to debugging windows kernel of driver faults.

    http://www.networkworld.com/news/2005/041105-windows-crash.html

    Cheers
     

    Users who are viewing this thread

    Top Bottom