BSOD randomly at startup with new PC (various error)

Page 1 of 2 12 LastLast

  1. Posts : 46
    Windows 7 Ultimate x64
       #1

    BSOD randomly at startup with new PC (various error)


    Hi everybody,
    my friend's brand new computer has got this problem since the first day: randomly, after the bios has loaded, a BSOD appears.

    Firstly I thought it was some software problem, so i reinstalled everything, but nothing changed.
    Here's the system configuration:

    CASE: Midi MS-tech LC-05B +Power supply 550W
    HARD DISK: Seagate 500GB 3.5" 7200rpm 16MB SATA3
    CPU: AMD FX-4100 Quad Core Buldozer
    RAM: RAM DDR3 G.SKILL RIPJAWS-X F3-10666CL9D-8GBXL 1333MHZ 8GB ( 2X4GB) CL9 1.5V
    MOBO: Asrock N68-VS3 FX
    Video card: integrated
    S.O. Windows 7 Ultimate x64

    So, I already tried to:
    - reinstall the system
    - changed antivirus from avast to avira
    - clean the vga driver with driver sweeper and re-install them with the latest version.
    - Ran memtest86 for 9hours with 0 errors
    - Updated the BIOS to the latest version

    After doing all this, he got again a blue screen, so at this point i'm out of option.

    That being said, I also mounted the hard driver of his old pc as a secondary hdd (but anyway I erased it), and he uses USB audio speaker (idk if this can help, but i write it down anyway).

    in the attach the dump files and the system health report!

    thanks,
    Alessandro
      My Computer


  2. Posts : 1,314
    Windows 7 64-bit
       #2

    Well it's evident we're dealing with hardware malfunctioning, but what is malfunctioning is what we need to determine.

    Couple things of note before we progress: a cheap PSU (including ones that come with cases) is going to cause problems. Extremely high rate of failure with them. In addition, any overclocking that may exist needs to be removed. Reset everything to factory defaults. Uninstall any software you may use for overclocking since software OCing is not recommended (only use BIOS).

    Now, since you ran Memtest86+ for several hours with no fault, there's a few other hardware tests to figure:

    CPU: Prime95 - Torture Test; Large FFTs; overnight (9+ hours)
    GPU: MemtestCL - Run twice (if any of the tests work on your GPU; ATI cards will need to install the ATI APP SDK as it requires OpenCL)
    Drives: Seatools - All basic tests aside from the Fix all or the advanced ones.

    All of these (excluding MemtestCL) are included in the UBCD if you prefer a Live CD environment (which is the best environment to test hardware on). Note that Prime95 currently does not work on the UBCD. Also, please provide us temps/voltages using HWInfo with Sensors only option checked. Log two 30-minute instances: one for idle, and one for high load.

    As for the 3 crashdumps you provided, none of them are entirely conclusive. However, I did notice from them what looks very much like corruption of the CPU registers. One especially looks evident that the CPU lost its register contents during code execution (if I'm looking at it right). These are commonly caused by PSU or CPU failure, as either the voltage provided by the PSU caused the CPU to drop its register contents, or the CPU itself simply failed to retain them. If I were to start swapping hardware (which is most likely what's gonna need to happen here) I'd start with those two first. Make sure the CPU also isn't overheating (as well as overclocked).

    Edit: I apologize, I thought the contents of that one CPU register were lost, but I misinterpreted the code. Correcting my error led me to data that I cannot access because it wasn't preserved in the minidump, so I cannot be 100% on what caused it, but it still looks a lot like the CPU lost its contents. The other minidumps still report corruption in the register contents.
      My Computer


  3. Posts : 46
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Thanks for your answer!

    Now I don't have the pc here, but I'll try to guide my friend via telephone.

    by the way, He just told me that a blue screen appeared also DURING the use of the pc...so I guess the thing is getting worse even more.
    Do you need the minidump file from this new crash?
      My Computer


  4. Posts : 1,314
    Windows 7 64-bit
       #4

    I doubt it'll prove anything different. If he wishes to do so, just to make sure this isn't a driver-based crash, he can turn on Driver Verifier as instructed here. Note that in addition to turning off the checks mentioned in the article, also don't check Force Pending I/O Requests. Then he can send in any crashdumps from crashes that may (hopefully) occur after DV is turned on (remember to have him restart the PC after finished setting it up).
      My Computer


  5. Posts : 46
    Windows 7 Ultimate x64
    Thread Starter
       #5

    I wrote to the shop, and they told me to try to run memtest (you don't say? lol), and to reinstall the system.

    Since i've already done that, they suggested to install the system with the AHCI mode...but i don't know what that is. I guess i've to change the hard disk BIOS settings and reinstall the system for the 3rd time?
      My Computer


  6. Posts : 1,314
    Windows 7 64-bit
       #6

    In the BIOS there most likely is a setting regarding the drives to set the interface to AHCI mode as opposed to, say, RAID or IDE mode. That's what they're referring too. Understand that changing this interface mode will require you to reinstall Windows should you choose to keep the changes, otherwise there will be issues (Windows may not even load).

    I doubt that's what we're dealing with here. There's nothing in these crashdumps that appear to hint to drive failure of any kinda. Of course, there's always the chance it could be, but it is extremely doubtful. I believe they're just biding their time or haven't been properly informed of the situation.
      My Computer


  7. Posts : 46
    Windows 7 Ultimate x64
    Thread Starter
       #7

    Vir Gnarus said:
    In the BIOS there most likely is a setting regarding the drives to set the interface to AHCI mode as opposed to, say, RAID or IDE mode. That's what they're referring too. Understand that changing this interface mode will require you to reinstall Windows should you choose to keep the changes, otherwise there will be issues (Windows may not even load).

    I doubt that's what we're dealing with here. There's nothing in these crashdumps that appear to hint to drive failure of any kinda. Of course, there's always the chance it could be, but it is extremely doubtful. I believe they're just biding their time or haven't been properly informed of the situation.
    I think the same.
    I've explained everything to them now, so we'll see.
    In the meantime, I made him run with just 1 RAM at the time: with one he had blue screen immediately, and now he's using just the second one.
    I'll be back with the feedback for this.

    thanks,
    Alessandro
      My Computer


  8. Posts : 46
    Windows 7 Ultimate x64
    Thread Starter
       #8

    BSOD during use also using once ram at the time
      My Computer


  9. Posts : 46
    Windows 7 Ultimate x64
    Thread Starter
       #9

    Today he called the shop and after some tests via tel, they'll do RMA...so I guess there's nothing we can do anymore :)
      My Computer


  10. Posts : 1,314
    Windows 7 64-bit
       #10

    It happens to the best of us. Sometimes failed hardware can slip by initial QC inspection and fail shortly after. Hope your new part(s) do the job well.

    If you feel this has been taken care of, you can mark it solved. Thanks.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 06:43.
Find Us