BSOD & IRQL Error Message

Discussion in 'Software' started by ColKorn, Feb 10, 2010.

  1. ColKorn

    ColKorn Private First Class

    I'm running under Win XP Pro, SP 2.

    Every time I run a SystemSuite system (SYS1) diagnostic, I get a BSOD, with the error message:

    "DRIVER_IRQL_NOT_LESS_THAN_EQUAL ...Dump of Physical Memory...."

    ...and the Technical Info I got from the latest BSOD IRQL error message:

    0x000000D1 (0xC0300000, 0x000000FF, 0x00000000, 0x1EF4724)

    Then the system reboots OK.

    (Just recently upgraded the motherboard)

    Just what does this particular error message mean?

    BTW, SystemSuite, now in its 10th version, has gotten pretty good
    reviews over time.


    My specs:

    Gigabyte EP45-UD3P Mobo
    Intel Core 2 Quad processor
    GeForce GT 220 video card
    2 Gig RAM
     
  2. BriJack

    BriJack Guest

    This forum thread is yours too:
    http://www.pcmech.com/forum/showthread.php?p=1454475
    We can see from that what has been suggested already over the last 5-6 days.

    Presumably this is the software program that, using it, is the precursor to a BSOD:
    http://avanquest.com/USA/software/s...e-software&sub=complete-pc-utilities-software

    I tend to agree with the posters in that other forum.
    These 'magical' optimising programs are usually just money earners, as there is plenty of excellent freeware software that does all that is needed - safely.
    But for users with little technical knowledge or skills around windows, they are led to believe these programs can do things they simply can't, and sometimes also believe (totally wrongly) that a paid-for software program is always better than a freeware program.

    Anyway, see this MG Guide on how to set up your system to produce a readable text log of the minidump of the BSOD:
    http://forums.majorgeeks.com/showthread.php?t=35246
    The 'minidump' itself is illegible characters - that's why the Mod on that other forum said you posting them wouldn't help. But I'm surprised they didn't suggest debugging the minidump to get the full, text reasons for the BSOD.
    I do also agree with that other Forum Mod, that - when you changed the MoBo - it would have been better to do a thorough format and reinstall of Windows. XP Repair install is a very poor utility and will never, ever be as efficient as a reinstall and does frequently lead to a troublesome OS.
    Other than that, when you resolve it (or if you can't, and opt for saving personal data and doing a thorough format and reinstall) don't forget to update your XP to Service Pack 3 and all the critical security updates that have appeared long after SP3 too.
     
    Last edited by a moderator: Feb 10, 2010

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