TechSpot

Need help finding crash source using WinDbg

By BoundinAshes6
Sep 26, 2006
  1. i recently built a new computer and it has been crashing alot and i didnt know what to do and i just used WinDbg on all 8 of the minidumps that the crashes made can anyone help me find what is causing the crashes ? thanks in advance :)

    1
    BugCheck 1000000A, {0, 2, 1, 805217e0}

    Probably caused by : memory_corruption ( nt!MiRemovePageByColor+66 )

    2
    BugCheck 1000000A, {80ee4398, 1c, 0, 806e4416}

    *** WARNING: Unable to verify timestamp for nv4_disp.dll
    *** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
    Probably caused by : nv4_disp.dll ( nv4_disp+a10eb )

    3
    BugCheck 100000CF, {bfefe48f, 8, bfefe48f, 0}

    Could not read faulting driver name
    *** WARNING: Unable to verify timestamp for nv4_disp.dll
    *** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
    Probably caused by : nv4_disp.dll ( nv4_disp+f6fbc )

    4
    BugCheck 4E, {7, 392bc, 16e6b, 0}

    Unable to load image npf.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for npf.sys
    *** ERROR: Module load completed but symbols could not be loaded for npf.sys
    Probably caused by : npf.sys ( npf+282d )

    5
    BugCheck 19, {20, e1232720, e12329d8, c570405}

    Probably caused by : ntkrpamp.exe ( nt!ExFreePoolWithTag+2a3 )

    6
    BugCheck 1000007E, {c0000005, bfab050e, ae291c80, ae29197c}

    Probably caused by : nv4_disp.dll ( nv4_disp+dc50e )

    7
    BugCheck 1000008E, {c0000005, bfac6b2c, ae39fab0, 0}

    Probably caused by : nv4_disp.dll ( nv4_disp+f2b2c )

    8
    BugCheck 10000050, {80d53300, 0, 80530fff, 2}


    Could not read faulting driver name
    Unable to load image Vax347b.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for Vax347b.sys
    *** ERROR: Module load completed but symbols could not be loaded for Vax347b.sys
    Probably caused by : Vax347b.sys ( Vax347b+dbec )
     
  2. Rik

    Rik Banned Posts: 3,814

    Looks like it could be a ram problem, we could do with your system specs tho!!!!!!
     
  3. BoundinAshes6

    BoundinAshes6 TS Rookie Topic Starter

    AMD 4200 dual core x2 socket AM2
    1 gig corsair value select ram ( 2 x 512 )
    asus M2N - E mainboard
    XFI Fatal1ty soundcard
    XFX Gforce 7900 gt videocard
    74 gb WD raptor
    500 Gb sata II maxtor
     
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...