TechSpot

Computer freezing up randomly after rebuild

By manonfire1550
Mar 26, 2012
Post New Reply
  1. Hey guys, so I posted on here about 14 months back concerning a new rig I had just purchased from Cyberpower and the issues I was having with it and you guys were incredibly helpful then, so I figured I'd get some advice on this situation.

    So about two weeks ago I noticed my computer having some serious heat regulation issues, with the CPU shooting up from 33C to 64C just from sitting on the Desktop; I also noticed that my CPU fan wasn't changing speeds as it got hotter, even after I manually told it to in the BIOS; it also was giving a reading that made no sense for a CPU fan (4500 RPM), so I thought the CPU water cooling system may have finally gone. So i ended up getting a brand new aftermarket heat sink and cooling system (it's huge) and a new gaming case since i needed the extra room; did a swap of all of the materials,rebuilding the rig and installing the new fan and system.

    Right after, things went pretty good, was running games with no issues and the CPU wasn't even able to be pushed beyond 43 C (which was awesome). Then, all of a sudden it locks up mid game; no BSOD, no motherboard beeps, nothing. Turned it off and restarted, and then it ran fine for a while.

    Next day, the issue happened again, and again, and again, these times it happened when running different utilities; it seemed if I kept on the main screen and didn't run anything, nothing happened.

    So, i've been looking at the RAM (and am running memtest as we speak) and checked other issues with the cords, power supply, etc. It seems the PSU is fine and it may be that i have hte ram mispaired (in order to have the cooler fit I had to remove a ram chip, leaving me with 3 2GB chips (1600 DDR3), so i thougth the one chip was maybe having pressure on it, so i removed it to leave me with 2 and the issue presented, so i'm wondering if I have them mispaired or something.

    Now I plan on installing new RAM anyways (I want to get back up to 8GB so i ordered two 4GB chips of the same type) but my friend is going to be buying the chips, hence the memtest.

    Beyond the memtest, what other tests/diagnostics can I run to make sure it isn't something else causing the issue? Tests for the PSU, mobo, etc. would be useful. My next step after the memtest will be to check if one of the PCI items is causing the issue.

    The reason i'm a bit confused: everything worked fine before the swap, now it's having issues. Now I realize something could have happened between that, but I was careful and have worked on computers before, so i know the routines of what not to touch, how to ground, etc.

    That all being said, there is one thing worrying me: in swapping out the coolant systems, the old liquid cooling system had the back bracket GLUED to the back of the mobo (don't even get me started...). In order to attach the new heat sink/fan, I had to pry it off; i was as careful as possible, but I realize some damage may have been done to the mobo, but from what i've read and know, I would think mobo damage woudl cause issues with booting. It boots without issue, so i'm not thinking it's that.

    Any suggestions/direction pointing would be much appreciated. Thanks guys!
     
  2. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    "the old liquid cooling system had the back bracket GLUED"...
    Are you sure it was glue and not some sort of adhesive tape? This could have damaged the motherboard for sure... Bios settings, mounting issues? After the new memory is installed, tell us if the system stabilizes
     
  3. manonfire1550

    manonfire1550 TS Rookie Topic Starter Posts: 28

    My apologies, it was an adhesive tape.
     
  4. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    Well that sounds better :) So after the memory replacement let us know...
     
  5. manonfire1550

    manonfire1550 TS Rookie Topic Starter Posts: 28

    Will do. It's arriving this afternoon and we'll see. Memtest last night showed no issues on any of the RAM chips currently installed; ran it for 10 hours, 14 passes, so I'm a bit afraid it's NOT the ram causing the issue. What's the potential for it being a PSU issue? It's got a 700 Watt system in it with one SATA hard drive, DVD drive, HD 6800 series GPU, and the new fan setup. I don't think i'm pulling too much, but I'm also not 100% sure.

    I'll let you know after the memory, but any suggestions for next tests if it still fails after the new memory?
     
  6. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    "What's the potential for it being a PSU issue?"
    It is hard to say, but with the new RAM you will again have 8GB using 2- 4GB sticks, we will have to see how this works
     
  7. manonfire1550

    manonfire1550 TS Rookie Topic Starter Posts: 28

    So the memory didn't fix anything. Just finished installing the new RAM and it locked up within a few minutes of getting into WIndows. I'm not sure what else could be causing the issue, any suggestions or tests that I can run on boot (since it crashes soon after loading the OS).

    At this point, I realize it could be possibly anything, but the system boots just fine, so i'm not thinking it's necessarily an issue with the mobo.

    It's sitting two updates behind on the BIOS, but the two newest BIOS updates weren't showing as being "crucial" and I know from reading to always be careful with BIOS updates.

    Suggestions of tests I can run or additional information I can present you guys would be most helpful.

    Thank you
     
  8. manonfire1550

    manonfire1550 TS Rookie Topic Starter Posts: 28

    Nevermind guys, I got it working. Not sure what the issue was, but replacing the RAM helped; after it didn't work as stated above, I opened it up and reseated everything again, just to be safe and it's working great now.
     
  9. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    Okay manonfire1550,
    thanks for the update :)
     
  10. manonfire1550

    manonfire1550 TS Rookie Topic Starter Posts: 28

    It's happening again...

    I hope somebody reads this again.

    So as shown above I have been having system stability issues with my custom-built computer recently after a rebuild. It was assumed to potentially be memory (RAM) issues, the RAM was replaced and tested, and the computer worked perfectly fine for about 12 days. And when I say worked fine, I mean it was handling like 8 hours of high-end use a day (HD video, streaming, or gaming).

    Now, about 6 days ago, it crashed randomly on me again, in the same manner is usually has (computer just locks up, no blue screen, nothing). However, after retesting and rerunning things again and again, I've gotten two blue screens now that dictate a hardware error; their memory dumps are attached (I believe they are the same error as I checked them with a debugging tool).

    So, here's my situation/plea to you guys: this computer is responsible for live streaming a gaming match for a live event I'm helpign to run in less than 3 weeks (April 28th). So this computer needs to be working by then. I really don't have the cash to burn, so i'm hoping it's something I can work with (or isn't that expensive) but if push comes to shove, i'll purchase what I need if I'm relatively sure that's the issue.

    One of the odd concerns I have is the instability, the fact that it worked fine for 12 days and then all of a sudden crapped out. As to what is causing the lockup, the only consistent way i've been able to crash the system is running a video game (specifically it's been Mass Effect 3 and Deus Ex: Human Revolution), in which it'll crash somewhere within 1 to 3 hours of gameplay.

    Now i've run numerous stress tests on the system (CPU loading, CPU max temp, Graphics Card, memtest, etc.) and it won't crash on those. It passes memory test and even passes memory stability tests and whatever the hell the Windows disk memory test does.

    I'm looking for any and all advice people can post; if you can't see a direct issue, please suggest testing programs I can use to torque the system or hopefully identify it.

    The only thing I haven't done yet is reseat all the components; I'm going to do that shortly, but considering the issue resolved itself and then came back i'm not thinking it's a seating issue. There have been no booting issues and I can confirm no heat issues (CPU has never gotten higher than 44 and GPU never higher than 60), both values dropping very quickly once I stop running the game.

    Please help, I seriously appreciate it!

    NOTE: I would attach the dump files, but they are showing to be 700+ MB each...any suggestions on getting those to you?

    I can print out the debug issue:
    DUMP 1:

    ADDITIONAL_DEBUG_TEXT:
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    FAULTING_MODULE: fffff80003415000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    BUGCHECK_STR: 0x124_AuthenticAMD

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    CURRENT_IRQL: 0

    STACK_TEXT:
    fffff880`03490b08 fffff800`03a0fa3b : 00000000`00000124 00000000`00000000 fffffa80`07dbb028 00000000`b62ec000 : nt!KeBugCheckEx
    fffff880`03490b10 fffff800`035a1c43 : 00000000`00000001 fffffa80`08a9a780 00000000`00000000 fffffa80`08a9a7d0 : hal!HalBugCheckSystem+0x1e3
    fffff880`03490b50 fffff800`03a0f700 : 00000000`00000728 fffffa80`08a9a780 fffff880`03490eb0 00000000`14e65c00 : nt!WheaReportHwError+0x263
    fffff880`03490bb0 fffff800`03a0f052 : fffffa80`08a9a780 fffff880`03490eb0 fffffa80`08a9a780 00000000`00000000 : hal!HalInitializeBios+0x13e8
    fffff880`03490d00 fffff800`03a02e8f : 00000000`14e65bd0 00000000`00000001 fffff880`03490f30 00000000`00000000 : hal!HalInitializeBios+0xd3a
    fffff880`03490d40 fffff800`0349062c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
    fffff880`03490d70 fffff800`03490493 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x309c
    fffff880`03490eb0 00000000`00d2f78b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x2f03
    00000000`0843f390 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xd2f78b


    STACK_COMMAND: kb

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: AuthenticAMD

    IMAGE_NAME: AuthenticAMD

    BUCKET_ID: WRONG_SYMBOLS

    Followup: MachineOwner

    Dump 2:
    ADDITIONAL_DEBUG_TEXT:
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    FAULTING_MODULE: fffff80003410000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    BUGCHECK_STR: 0x124_AuthenticAMD

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    CURRENT_IRQL: 0

    STACK_TEXT:
    fffff880`03490b08 fffff800`03a0aa3b : 00000000`00000124 00000000`00000000 fffffa80`08359028 00000000`b4602000 : nt!KeBugCheckEx
    fffff880`03490b10 fffff800`0359cc43 : 00000000`00000001 fffffa80`08a9c770 00000000`00000000 fffffa80`08a9c7c0 : hal!HalBugCheckSystem+0x1e3
    fffff880`03490b50 fffff800`03a0a700 : 00000000`00000728 fffffa80`08a9c770 fffff880`03490eb0 00000000`223f0b00 : nt!WheaReportHwError+0x263
    fffff880`03490bb0 fffff800`03a0a052 : fffffa80`08a9c770 fffff880`03490eb0 fffffa80`08a9c770 00000000`00000000 : hal!HalInitializeBios+0x13e8
    fffff880`03490d00 fffff800`039fde8f : 00000000`223f0aa0 00000000`00000001 fffff880`03490f30 00000000`00000000 : hal!HalInitializeBios+0xd3a
    fffff880`03490d40 fffff800`0348b62c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
    fffff880`03490d70 fffff800`0348b493 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x309c
    fffff880`03490eb0 00000000`00fb8fb0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x2f03
    00000000`0893f6c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfb8fb0


    STACK_COMMAND: kb

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: AuthenticAMD

    IMAGE_NAME: AuthenticAMD

    BUCKET_ID: WRONG_SYMBOLS

    Followup: MachineOwner
     
  11. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    You have to ZIP the minidump files. Select all the minidump files and right-click, send them to a ZIPPED or COMPRESSED folder then attach this folder. And by the way, the debugging tools are not setup properly
     
  12. manonfire1550

    manonfire1550 TS Rookie Topic Starter Posts: 28

    I know the debugging tools are not setup properly, they require stupid symbols packages and whatnot that my Windows installation refuses to understand, for whatever reason. i just wanted to get what the bugchecker showed up.

    As to the dump files, still way too big. Compressing them only gets me down to 200 MB a pop.
     
  13. manonfire1550

    manonfire1550 TS Rookie Topic Starter Posts: 28

    Wow, i'm slow...ever have one of those days?

    I grabbed the full dump not the mini-dump files. The last 4 are attached.
     

    Attached Files:

  14. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    Do you have any yellow exclamation points in the device manger?
    Minidumps contain:
    IRQL_NOT_LESS_OR_EQUAL
    Ntoskrnl.exe
    HAL.dll
     
  15. manonfire1550

    manonfire1550 TS Rookie Topic Starter Posts: 28

    The IRQL_NOT_LESS_OR_EQUAL i think occurred when I was playing around with overclocking, so that one can probably be neglected.

    I know what Ntoskrnl.exe usually references; what is HAL.dll our of curiousity?

    Anyways, to answer your question, turns out there is: under Storage Volumes, it's a "Generic Volume"; i have no idea what it is either...under the properties, it says "This device cannot start (Code 10)".
     
  16. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    Hardware Abstraction Layer=HAL.dll This has to do with hard drives. How many and what type do you have installed?

    "under Storage Volumes, it's a "Generic Volume"...
    These can be internal, external, USB hard/flash drives
     
  17. manonfire1550

    manonfire1550 TS Rookie Topic Starter Posts: 28

    Hard Drives: 1, 7200 RPM 1.0 TB SATA drive.
    As for the device manager piece, that may just be a flash drive I have that tends to not want to work properly lately...let me remove it and see.

    Yep, just removed it and it went away; there are now no yellow exclamation marks in the device manager...
     
  18. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    Go to the hard drive's manufacturers support website and get their diagnostic software and run it, to see if the hard drive is sound. I have seen these big drives fail in just a few months with bad sectors. This can cause BSOD's like yours
     
  19. manonfire1550

    manonfire1550 TS Rookie Topic Starter Posts: 28

    Ran the extended test from the manufacturer's diagnostic tools and it ran with no issues. Ran it twice and got no issues for both runs; not sure if this is like the memtest thing where I should have it run 8-10 times, but two tests did run with positives.
     
  20. manonfire1550

    manonfire1550 TS Rookie Topic Starter Posts: 28

    On a side note, the computer hasn't crashed yet today...and I kind of tried to make it crash by running the game that's crashed it before; about 4 hours of that didn't crash it. On that same note, the computer doesn't seem to EVER crash if it's just sitting there or doing something small/easy like word processing or even running Spotify.

    Not sure if any of that helps or not...
     
  21. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    Could be a power supply issue, if the BSOD's continue
     
  22. manonfire1550

    manonfire1550 TS Rookie Topic Starter Posts: 28

    If a PSU issue, how would I go about testing that? I would think if it was a PSU issue the issues would be more consistent, not so unstable, but i'm also not sure.

    Also, chances of it being a mobo issue vs. PSU? Any way to potentially rule one or the other out?
     
  23. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    We have gone through a lot of checks and tests on this computer, and it seems to have improved so there's not much left except the power supply at this point if the BSOD's continue... The motherboard is the last thing to suspect
     
  24. manonfire1550

    manonfire1550 TS Rookie Topic Starter Posts: 28

    Well that's good to know :)

    Again for the PSU, any way to test it to be sure? I would prefer not to dump cash into the system to find out it isn't the issue (if possible).

    Thanks again for all the advice/assistance on this issue. I greatly appreciate it.
     
  25. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    Not really, with this type of problem no test would be able to find anything wrong. What is the make and model of the power supply?
     

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...