VideoHelp Forum




+ Reply to Thread
Results 1 to 9 of 9
  1. Member Xylob the Destroyer's Avatar
    Join Date
    Sep 2004
    Location
    Earth, for now
    Search Comp PM

    My HTPC randomly crashes/reboots... It's the one listed in my profile.

    Sometimes it happens under 'heavy load'.
    Sometimes it happens when the system is basically idle.

    I have error reporting turned on, so every time it reboots it asks me if I want to send a report. I say yes and when it's done it opens an internet page that says "This problem was caused by a device driver. Does this information help you?".

    NO!! It doesn't freakin' help me...
    Which driver? There's only a couple hundred... Plus, all of my drivers are signed by Micro$oft, so they should all be just find and dandy.

    Is there some sort of a log or file buried deep down inside of XP that I can look at to see which freakin' driver is causing this problem?

    TIA!!
    "To steal ideas from one person is plagiarism; to steal from many is research." - Steven Wright
    "Megalomaniacal, and harder than the rest!"
    Quote Quote  
  2. Member Soopafresh's Avatar
    Join Date
    Jan 2004
    Location
    United States
    Search Comp PM
    I know what you're going through. And you're right, the Microsoft error messages are less than useless.

    You're positive it isn't heat? Run it with the cover off and see if it crashes.

    If you're going to upgrade drivers, start with the video, then the drive controllers.
    Quote Quote  
  3. Member Xylob the Destroyer's Avatar
    Join Date
    Sep 2004
    Location
    Earth, for now
    Search Comp PM
    I'm not updating shit until I know what's causing the problem...
    I hate wild goose chases and I'll be damned if I'm gonna start randomly downloading and installing drivers in a blind attempt to hopefully fix a mystery.

    Stupid Microsoft...
    "To steal ideas from one person is plagiarism; to steal from many is research." - Steven Wright
    "Megalomaniacal, and harder than the rest!"
    Quote Quote  
  4. aBigMeanie aedipuss's Avatar
    Join Date
    Oct 2005
    Location
    666th portal
    Search Comp PM
    I'd start with some hardware diagnostics. Test the RAM with Memtest86+ and the windows memory diagnostic tool. Let the tests run for a significant period of time, such as overnight.

    Memtest86+
    http://www.memtest.org/


    Windows Memory Diagnostic
    http://oca.microsoft.com/en/windiag.asp


    also check the error log c:\windows\minidump miniXXX.dmp

    if you have skills and can use debugging tools run it through kd.exe

    tools here-http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
    --
    "a lot of people are better dead" - prisoner KSC2-303
    Quote Quote  
  5. Look in Event Viewer under Administrative tools and see if anything stands out.

    Try an extended period running in Safe Mode and/or BIOS setup. If it reboots in BIOS, the problem is basic hardware, no drivers involved. In Safe mode, very minimal drivers in use.

    Try to isolate when this began ocurring, and identify drivers added around that time. If no new hardware, focus on those which may have been automatically updated.

    Using MSConfig, you can screen out individual drivers.

    How often or regularly does the problem occur? What is the Longest time you have run without the error? Double that time for testing purposes.

    Example - PC has not run without rebooting within 4 hours for quite some time. Boot into BIOS and let sit overnite or 8 hours at a minimum. No reboot, hardware mostly eliminated. Sit in Safe Mode for 8 hours, no reboot, basic Windows functionality checked OK.

    Do you have an HP printer? Have had two or three with driver updates causing issues in the last few months.
    Quote Quote  
  6. Member Krispy Kritter's Avatar
    Join Date
    Jul 2003
    Location
    St Louis, MO USA
    Search Comp PM
    If it is sending error reports, then it is logging the errors in event viewer as noted above.
    Google is your Friend
    Quote Quote  
  7. Try disabling the automatic reboot.

    Your pc should crash and stop on a nice classic BSOD with an error message like "PAGE FAULT IN NON PAGED AREA", "IRQ_NOT_LESS_OR_EQUAL", "DRIVE_MOUNT_FAILURE" or a lot of any other messages.
    Then it should be easier to identify the problem.
    Quote Quote  
  8. Member Xylob the Destroyer's Avatar
    Join Date
    Sep 2004
    Location
    Earth, for now
    Search Comp PM
    The BSOD flashes by too quickly WAY to fast to read.
    "To steal ideas from one person is plagiarism; to steal from many is research." - Steven Wright
    "Megalomaniacal, and harder than the rest!"
    Quote Quote  
  9. Member blinky88's Avatar
    Join Date
    Mar 2004
    Location
    Australia
    Search Comp PM
    Go to this link you may well have the same problem I had, also check the FOUND files I referred to.

    https://forum.videohelp.com/topic346499.html
    Quote Quote  



Similar Threads

Visit our sponsor! Try DVDFab and backup Blu-rays!