driver errors

MogwaiMogwai
edited July 2005 in Science & Tech
I am getting the ioccasional BSOD from what the microsoft crash site says are device driver errors. How can I pin down which driver/s are to blame.
I have installed the Dumpck.exe file into the system tools and am trying to run it but the prompt box opens for a second and I cant get any data
So what am I doing wrong.
I have read through the knowlrdge base articles so I guess what I am asking is how do I actually read the data from dumck etc so's I can continue hunting??!! :confused:
Any help would be greatly appreciated
Oh by the way I ran Memtest for 24= hrs only 2 days ago so I am fairly certain it isnt that

Comments

  • profdlpprofdlp The Holy City Of Westlake, Ohio
    edited June 2005
    The most common hardware items to cause the dreaded BSOD are video and network. I'd try either an updated video driver, or rolling back to an older one if you already have the latest. If that doesn't help you might do the same with your network card drivers.

    What do your temperatures look like? If this recently started it could be due to the arrival of hot summer weather.

    NOTE: Moving to the Windows Forum. :)
  • TheBaronTheBaron Austin, TX
    edited June 2005
    theres a possibility that a device driver crash will have something included in the event viewer (under administrative tools in the control panel). whenever my 9700 pro was overheating, it would throw an ati driver error in there, which is how I pinpointed the problem. just check in there and see if you see any errors corresponding with your crash times
  • MogwaiMogwai
    edited June 2005
    Well temps are fine and there is not a lot of info in the event manager other than this
    Error code 1000008e, parameter1 c000001d, parameter2 baf79076, parameter3 f7c52934, parameter4 00000000.

    now what I want to do is read the information in the memory dump but I dont know how, can anyone advise.
    I know about the dumpchk.exe memory.dmp command, thing is I am not getting a readout from it when I run it, so what next? I am guessing i will try and decode the above error codes..... bah... confused am I :confused:
  • MogwaiMogwai
    edited June 2005
    hmm ok well have found more info now can someone please tell me how to get at the info that flashes in the command prompt when i run pstat.exe
    I figure its pretty basic but not for me :confused:
    when I run it in the command prompt the diag box opens for a sec but i cannot rread it its too quick!!! so how do I send it to somewhere where I can glean the info


    please someone...!!!!!
  • profdlpprofdlp The Holy City Of Westlake, Ohio
    edited June 2005
    Mogwai wrote:
    ...can someone please tell me how to get at the info that flashes in the command prompt when i run pstat.exe...
    Instead of using the Start>>Run box, look around for a shortcut to "Command Prompt". That will open a DOS box which won't go away until you tell it to.
  • MogwaiMogwai
    edited June 2005
    yup gottit thanks a million Prof :thumbsup:

    Ok well am now getting lots of info will now try to decode, have managed to get psts.exe up unfortunatly the dumpchk.exe Memory.dmp only gives a ****Debug Client cannot open dump file error 80070002
    Gah!
    Will have to wait for another BSOD episode unless anyone else has another idea
  • MogwaiMogwai
    edited July 2005
    Ok well thanks for all the help folks but I seem to have licked it...fingers crossed anyways

    I ran Driver Cleaner Pro and removed all of the drivers I didn't want and then did the same from "safe mode" and low and behold the dry and desicated corpses of drivers past cluttering up the system, it is these I figure that were causing the conflicts.
    Removed them all and no problems so far ;)
  • profdlpprofdlp The Holy City Of Westlake, Ohio
    edited July 2005
    Glad you got it. :thumbsup:
  • MogwaiMogwai
    edited July 2005
    oh well spoke too soon, another reboot...gah and still the same error ie debug client cannot open error file etc, any ideas anyone?
  • profdlpprofdlp The Holy City Of Westlake, Ohio
    edited July 2005
    Try disabling System Restore, clean the old drivers out (again) in Safe Mode, then reboot and re-enable System Restore.
Sign In or Register to comment.