TechSpot

Continuing struggle with Blue Screens

By jrm5400
Oct 24, 2005
  1. I posted in this forum several months ago. My Minidumps at the time showed a cpu problem. I have since replaced the cpu, power supply, and motherboard and still can't get away from these intermittent blue screens.

    I have attached some more recent dumps from some testing I've been doing with a fresh install of XP.

    They all seem to indicate a machine check problem w/ cpu, ram, motherboard or powersupply. when those have all been replaced, I'm at a loss. ideas?
     

    Attached Files:

  2. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Hi jrm5400,

    Your PC have multiple culprits. The problem faulty m/b is fixed. All of bugcheck 9c are related to moviemk. I believe that your video card is faulty.


    GetPointerFromAddress: unable to read from 8055ee34
    THREAD 88196780 Cid 0920.09b8 Teb: 7ffab000 Win32Thread: 00000000 RUNNING on processor 0
    Not impersonating
    GetUlongFromAddress: unable to read from 8055ee44
    Owning Process 881e5c88 Image: moviemk.exe
    ffdf0000: Unable to get shared data
    Wait Start TickCount 26965
    Context Switch Count 36587
    ReadMemory error: Cannot get nt!KeMaximumIncrement value.
    UserTime 00:00:00.0000
    KernelTime 00:00:00.0000
    Start Address 0x7c810856
    Win32 Start Address 0x087de686
    Stack Init a9e91000 Current a9e90d34 Base a9e91000 Limit a9e8e000 Call 0

    New Message
    The video card may be the TV card. What is the manufacturer of your TV card? Your windows also have two minidumps crashed at module HSFHWBS2.sys and I have no idea what it is.
     
  3. jrm5400

    jrm5400 TS Rookie Topic Starter

    Suspected video card

    I was hoping it wouldn't turn out to be the video card. :-( When I first tried assembling the pc last year the machine wouldn't boot due to a faulty video card. I RMA'd the video card to ATI and this is the one I now have. Seems they either didn't fix it completely or sent me another bad one.
    The other dumps I supplied today were from a clean install where I used Movie Maker to force the bluescreen. Would you mind checking these to see if it confirms the same problem is happening? These are from my "normal" Windows install that we use when I'm not debugging. At times, the machine has rebooted several times on its own with no user interaction.

    cpc2004, thanks for all your help.
     
  4. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Hi Jrm,

    Most of crashes are at ATI display card driver. Probably it is the hardware error of your ATI video card. One crash maybe related to overheat and what is the temperature of your CPU?


    Debug report
    Mini102005-13.dmp BugCheck 10000050, {9d6ebbab, 1, 80567682, 0}
    Mini102005-13.dmp Probably caused by : ntoskrnl.exe ( nt!CmpParseKey+10d )

    Mini102005-09.dmp BugCheck 1000008E, {c0000005, bf9e366a, 9c159104, 0}
    Mini102005-09.dmp Probably caused by : ati2dvag.dll ( ati2dvag+1066a )

    Mini102005-10.dmp BugCheck 9C, {0, 8054d370, c4204000, 136}
    Mini102005-10.dmp Probably caused by : ntoskrnl.exe ( nt!KdPitchDebugger+ef4 )

    Mini102005-11.dmp BugCheck 1000008E, {c0000005, bf9e366a, 9d641044, 0}
    Mini102005-11.dmp Probably caused by : ati2dvag.dll ( ati2dvag+1066a )

    Mini102005-12.dmp BugCheck 1000008E, {c0000005, bf9e366a, b8b7e044, 0}
    Mini102005-12.dmp Probably caused by : ati2dvag.dll ( ati2dvag+1066a )

    Mini102005-14.dmp BugCheck 1000008E, {c0000005, 34788d1, 9d2c4068, 0}
    Mini102005-14.dmp Probably caused by : ati2dvag.dll ( ati2dvag+e06a )

    Mini102005-15.dmp BugCheck 9C, {0, 8054d370, c43ac000, 136}
    Mini102005-15.dmp Probably caused by : ntoskrnl.exe ( nt!KdPitchDebugger+ef4 )

    Mini102005-16.dmp BugCheck 1000008E, {c0000005, a13aec24, 8897bba0, 0}
    Mini102005-16.dmp Probably caused by : savrt.sys ( savrt+24c24 )

    Mini102005-17.dmp BugCheck 1000008E, {c0000005, a23ba490, 88a114e8, 0}
    Mini102005-17.dmp Probably caused by : navex15.sys ( navex15+5f490 )

    Mini102005-18.dmp BugCheck 9C, {0, 8054d370, c4014000, 136}
    Mini102005-18.dmp Probably caused by : ntoskrnl.exe ( nt!KdPitchDebugger+ef4 )

    Mini102105-02.dmp BugCheck 9C, {0, 8054d370, c4014000, 136}
    Mini102105-02.dmp Probably caused by : ntoskrnl.exe ( nt!KdPitchDebugger+ef4 )

    Mini102005-19.dmp BugCheck 1000008E, {c0000005, a1053490, 891093b4, 0}
    Mini102005-19.dmp Probably caused by : navex15.sys ( navex15+5f490 )

    Mini102005-20.dmp BugCheck 1000008E, {c0000005, 9dbce490, 889db4e8, 0}
    Mini102005-20.dmp Probably caused by : navex15.sys ( navex15+5f490 )

    Mini102105-01.dmp BugCheck 9C, {0, 8054d370, c4014000, 136}
    Mini102105-01.dmp Probably caused by : ntoskrnl.exe ( nt!KdPitchDebugger+ef4 )

    Mini102205-02.dmp BugCheck 10000050, {9dc0fbab, 1, 80567682, 3}
    Mini102205-02.dmp Probably caused by : ntoskrnl.exe ( nt!CmpParseKey+10d )

    Mini102105-03.dmp BugCheck 1000008E, {c0000005, bf9e366a, 9d0d8544, 0}
    Mini102105-03.dmp Probably caused by : ati2dvag.dll ( ati2dvag+1066a )

    Mini102105-04.dmp BugCheck 1000008E, {c0000005, bf9e366a, 9dc9c044, 0}
    Mini102105-04.dmp Probably caused by : ati2dvag.dll ( ati2dvag+1066a )

    Mini102205-01.dmp BugCheck 9C, {0, 8054d370, c4014000, 136}
    Mini102205-01.dmp Probably caused by : ntoskrnl.exe ( nt!KdPitchDebugger+ef4 )
     
  5. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Hi Jmr,

    Some of system crashes are related to faulty memory. I am not sure whether it is the ram or video memory. Run memtest to stress test the ram.
     
  6. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Hi jrm5400,

    Do you have any update of the problem?
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...