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.

Windows Vista Can't Get Stable BSOD - Please help me with this MiniDump

Discussion in 'Legacy Windows' started by winjunkie, 2009/03/17.

  1. 2009/03/17
    winjunkie

    winjunkie Inactive Thread Starter

    Joined:
    2009/03/16
    Messages:
    7
    Likes Received:
    0
    Hi all,

    I've trying to get my sys stable and each time i think it is it does it fun little BSOD thats driving me crazy.

    I first seen this bsod when running prime blend tests. I then tweaked my bios settings and passed 24hr small test and 26 hours blend test. MemTest Passed 50x test #5 and 3x all tests.

    When i run 3dmark 06 or vantage it will come up with this bsod message.

    An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval.

    I was getting IRQL (most likely related to cpu?) message but i think i fixed that, just before it did another bsod with system_service or something like that but for some reason that dump didn't save.


    anyway any help would be greatly appreciated.

    Specs:

    Q6600
    680i Mobo
    Patriot Ram (ram is running well under specs)
    850w PSU

    Temps are all cool 25c-30c idle - 50c~56c load depending on core
    .


    Vista x64 SP1 (reinstalled twice)


    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    CLOCK_WATCHDOG_TIMEOUT (101)
    An expected clock interrupt was not received on a secondary processor in an
    MP system within the allocated interval. This indicates that the specified
    processor is hung and not processing interrupts.
    Arguments:
    Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: fffffa60019d2180, The PRCB address of the hung processor.
    Arg4: 0000000000000003, 0.

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


    BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: svchost.exe

    CURRENT_IRQL: d

    STACK_TEXT:
    fffffa60`034bc6d8 fffff800`01aa7321 : 00000000`00000101 00000000`00000031 00000000`00000000 fffffa60`019d2180 : nt!KeBugCheckEx
    fffffa60`034bc6e0 fffff800`01a51e7a : fffff800`01f483c0 fffffa60`034bc800 fffffa60`034bc850 fffff800`01f483c0 : nt! ?? ::FNODOBFM::`string'+0x34b4
    fffffa60`034bc720 fffff800`01f25d74 : 00000000`00000000 00000004`06fb0b8e 00000000`00000000 00000004`06fb6d3c : nt!KeUpdateSystemTime+0xea
    fffffa60`034bc750 fffff800`01a59aed : 00000000`3784a203 fffff800`01b77680 fffffa80`05e552e8 00000000`017d7840 : hal!HalpHpetClockInterrupt+0x8c
    fffffa60`034bc780 fffff800`01a26ea9 : fffffa80`00000000 fffffa60`034bc930 00000000`00000000 00000000`00000008 : nt!KiInterruptDispatchNoLock+0x14d
    fffffa60`034bc910 fffff800`01cce9bf : 00000000`00000000 fffffa60`034bcca0 00000000`00000000 00000000`00000001 : nt!KeFlushProcessWriteBuffers+0xc9
    fffffa60`034bc960 fffff800`01a57df3 : fffffa80`06461060 00000000`00013880 ffffffff`fffe7960 00000000`00000000 : nt!NtQuerySystemInformation+0x117f
    fffffa60`034bcc20 00000000`771e5dda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`007cf2c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771e5dda


    STACK_COMMAND: kb

    SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME: Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

    BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

    Followup: MachineOwner
    ---------
     
  2. 2009/03/18
    mattman

    mattman Inactive Alumni

    Joined:
    2002/06/10
    Messages:
    8,198
    Likes Received:
    63
    Hi and welcome to the BBS,

    There is not much information in the dump and there is not much information about that error.

    I suggest going through the basis. Start with the RAM, move it to different slots. Run with individual modules if you can. Check if there is any special information about RAM in the motherboard manual. Go to the Patriot website and check if your motherboard is listed as compatible. If not, try borrowing a different brand and testing with that.

    Check that the model of CPU is listed as compatible at the motherboard manufacturer's website.

    Did you get Vista 64bit drivers on a disk with the motherboard? If not, you will need to source them (from the hardware manufacturer's website). Get the chipset drivers first.

    Those programs you mention seem to be testing/benchmark programs. Does it blue screen with normal programs?

    Did you build the system yourself? Is say, the CPU heatsink and fan standard or have you modified them? The temperatures rises a little high. Consider that there may be an air pocket in the thermal compound between the processor and the heatsink or maybe too much compound was used.

    Matt
     

  3. to hide this advert.

  4. 2009/03/18
    Rockster2U

    Rockster2U Geek Member

    Joined:
    2002/04/01
    Messages:
    3,181
    Likes Received:
    9
    You would be well served to look at some 3dmark 06 forums with specific reference to your GPU settings and check out your video cards independently in both slots.

    ;)
     
  5. 2009/03/19
    winjunkie

    winjunkie Inactive Thread Starter

    Joined:
    2009/03/16
    Messages:
    7
    Likes Received:
    0
    Thanks for the reply, I seem to have fixed it, I had to reduce my overclock further, by 30fsb in total,

    I thought that it may have been related to some driver or whatever since it passed testing for 24-26 hours. Seems stable now, I'm just trying to reduce my voltages now and keep stable. After buying the most expensive mobo on the market at the time, I'm really not happy with its ocing ability/compatibility with this cpu seems a lot of people are getting similar errors and have to set it to a similar clock to get stable.

    Also thanks for the welcome mattman, nice to be a part of an expert community that has experience at decode these minidumps
     
    Last edited: 2009/03/19

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.