Pending 1 year old homebuilt PC = incredibly unstable

Discussion in 'General PC and Tech Security Questions' started by guysholliday, May 13, 2009.


Thread Status:
Not open for further replies.
  1. guysholliday Bronze Member

    Bronze
    Message Count:
    29
    Likes Received:
    0
    My System
    Loading...
    Re: 1 year old homebuilt PC = incredibly unst



    Right on cue, as I finished installing BurnInTest I got BSOD'ed with a hardware failure and a crsh dump. Any thoughts?
  2. jay2 Games developer

    Tech Member
    Message Count:
    1,540
    Likes Received:
    99
    My System
    Loading...
    Re: 1 year old homebuilt PC = incredibly unst

    Yes, post your crash dump and I'll move this to the BSOD forum.

    Right, you're moved now :).
    after you post the dump, try running BurnInTest.
  3. guysholliday Bronze Member

    Bronze
    Message Count:
    29
    Likes Received:
    0
    My System
    Loading...
    Re: 1 year old homebuilt PC = incredibly unst

    How do I post the crash dump? I ran BIT after the BSOD and FAILED. It couldn't allocate RAM from Windows, Test File could not be created for C:, and No Permission to open RAW network socket. I've tried to type this message 3 times, it keeps crashing.
  4. Google Advertisement

  5. jay2 Games developer

    Tech Member
    Message Count:
    1,540
    Likes Received:
    99
    My System
    Loading...
    Re: 1 year old homebuilt PC = incredibly unst

    This guide is from MadMonkey.


    BSOD Log/Dump File


    A BSOD (Blue Screen of Death) produces a log file otherwise known as a memory dump. This file contains the error codes you received on the blue screen itself, as well as what was actually happening at the time of the crash and what was loaded in memory. A debug analysis can often reveal the direct cause of the problem, or at the very least, give a good idea of the probable cause.


    How to Attach a Dump File in PCHF

    When it comes to your reply, below the "Quick Reply" message box, click on: "Go Advanced"

    The advanced screen will give a "Reply to Thread" screen with more options. Click on the attachment icon: and a Manage Attachments window will appear.

    Under the section "Upload File from your computer", click on the first Browse or Choose File button, and a Choose/Open file window will appear.

    Click on the "My Computer" or "Computer" icon on the left hand Window, double click on your local hard drive containing the "Windows" folder. Double click on your Windows folder, followed by the folder called “minidump”.

    Inside here, you’ll see the dump/log files starting with the filename “mini..”. The files themselves are actually marked with a date in Amercian format (mmddyy) followed by the number of crashes that day. For example: mini080109-01.dmp would be the first crash on the 1st of August2009.

    [IMG]

    To ensure the accuracy of the results, attach the latest file possible, and attach a few of them (you can attach up to three per post). Double click on the file you wish to upload, and then click on the Upload button, followed by Close this window.


    Troubleshooting

    minidump’s are normally enabled by default. However there may be several reasons why they do not appear in this folder.

    Make sure minidumps are enabled:
    - Go to My Computer, Control Panel, System followed by Advanced tab.
    - Under “Startup and Recovery”, click Settings.
    - Under “System failure”, make sure Write and event to the system log is ticked.
    - Under “Write debugging information”, make sure Small Memory Dump is selected.

    [IMG]

    Also, if you have performed a disk cleanup since the you received a BSOD, it would have been deleted.

    You must now wait or reproduce your blue screen again before uploading the log file.


    (NOTE: If you got any Blue Screens in those last crashes, please post them as well).

    It's nearly 2AM here, so I'm going to bed, but we'll get this fixed.
  6. guysholliday Bronze Member

    Bronze
    Message Count:
    29
    Likes Received:
    0
    My System
    Loading...
    Re: 1 year old homebuilt PC = incredibly unst

    Wow, unfortunately there's nothing in my minidump folder.

    How irritating.
  7. guysholliday Bronze Member

    Bronze
    Message Count:
    29
    Likes Received:
    0
    My System
    Loading...
    Re: 1 year old homebuilt PC = incredibly unst

    Hey, it did it again. Still no minidump file. Any ideas?
  8. madmonkey Site Manager

    Manager
    PCHF Staff
    Message Count:
    18,864
    Likes Received:
    759
    My System
    Loading...
    Re: 1 year old homebuilt PC = incredibly unst

    @jay, I'm with you! :)

    Can you be sure that you have followed the troubleshooting section GH? If so, there are severe cases where the system is unable to produce the log file, hard drive failure, connections, motherboard failure, power issues for example. The problems started immediately after your new hardware, or did they get progressively worse?
  9. guysholliday Bronze Member

    Bronze
    Message Count:
    29
    Likes Received:
    0
    My System
    Loading...
    Re: 1 year old homebuilt PC = incredibly unst

    I followed his instructions to the letter... I was able to run BurnInTest (suprisingly) and I passed with 0 errors. As for the hardware question, I haven't changed hardware since April '08 except for two more sticks of Corsair RAM last Christmas. The problems started about a 10 days ago.
  10. guysholliday Bronze Member

    Bronze
    Message Count:
    29
    Likes Received:
    0
    My System
    Loading...
    Re: 1 year old homebuilt PC = incredibly unst

    Here are the BurnInTest results.

    Attached Files:

  11. madmonkey Site Manager

    Manager
    PCHF Staff
    Message Count:
    18,864
    Likes Received:
    759
    My System
    Loading...
    Re: 1 year old homebuilt PC = incredibly unst

    OK, in that case, GH, we will have to work through each possibility.

    On your next couple of blue screens, could you try to note down the error code and driver name (if any)? This may help to narrow your problem down more quickly, even though it only appears for a split second.

    [IMG]

    At the moment, we don't have a lot of information to work on really, except that the PC has had a lot of hardware changes. The PC freezes and sometimes you'll receive a blue screen of death. The two are not always related. I'm sure your problems are hardware related from everything you have described so far.

    First of all! One question. Thanks for the hardware information you posted so far, but what is the make and wattage of the PSU you bought with this case?

    Next, some tasks!
    Can you take a look at the following thread, which describes how to perform a MemTest: http://www.pchelpforum.com/memory/58877-memtest86-how-download-run.html

    Also, can you download: CPU-Z
    - Click on the About tab, followed by Registers Dump.
    - Save the file to somewhere you'll remember, and then upload that file here.
  12. guysholliday Bronze Member

    Bronze
    Message Count:
    29
    Likes Received:
    0
    My System
    Loading...
  13. guysholliday Bronze Member

    Bronze
    Message Count:
    29
    Likes Received:
    0
    My System
    Loading...
    Re: 1 year old homebuilt PC = incredibly unst

    I just ran the Windows Memory Diagnostic tool and came up with no errors. Standby for CPU-Z results...

    Attached Files:

  14. madmonkey Site Manager

    Manager
    PCHF Staff
    Message Count:
    18,864
    Likes Received:
    759
    My System
    Loading...
    Re: 1 year old homebuilt PC = incredibly unst

    nice! I take it you went for the Newegg combo deal with that one! :)
  15. madmonkey Site Manager

    Manager
    PCHF Staff
    Message Count:
    18,864
    Likes Received:
    759
    My System
    Loading...
    Re: 1 year old homebuilt PC = incredibly unst

    wow that was quick GH, how many passes did you do?
  16. guysholliday Bronze Member

    Bronze
    Message Count:
    29
    Likes Received:
    0
    My System
    Loading...
    Re: 1 year old homebuilt PC = incredibly unst

    2 Passes is standard for Windows Diagnostic... I didn't see an option for more. I ran some sort of memory test as per the instructions on page 1 or 2. It ran for about 30 minutes with no errors.

    That was yesterday, of course.

1 year old homebuilt PC = incredibly unstable

Thread Status:
Not open for further replies.