BSOD errors

Discussion in 'Software' started by TheOldThug, Aug 29, 2007.

  1. TheOldThug

    TheOldThug First Sergeant

    I have been getting some BSOD messages IRQ_NOT_LESS_OR_EQUAL, PDN_LIST_CORRUPT, and now something about a floating point error. I was thinking about trying the sticky above on "how to debug memory dumps". First of all it is over 2 years old, is it still up to date? Second I don't quite understand how and where to use the "Use !analyze -v to get detailed debugging information." Any info someone could give me would be helpful.
     
  2. dyamond

    dyamond Imelda Marcos of Majorgeeks

    The thread you are referring to (How to debug memory dumps) still contains accurate information pertaining to how you can figure out whats causing your BSOD's. It's a good place to start :)
     
  3. Adrynalyne

    Adrynalyne Guest

    Just follow it the best you can.

    The !analyze command is extra--you generally don't need that command, unless you want to get the nitty gritty details. So if you feel so inclined to skip that, you should be ok. Make CERTAIN you get the full symbols file source path...that entire line.

    As dyamond said, its still accurate, even for Windows Vista :)
     
  4. TheOldThug

    TheOldThug First Sergeant

    I recently had the processor fan replaced, could the processor possible been damaged to cause this floating point error?
     

MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds