Random freezing and BSOD on new build

Hi kyturne.

The crash dumps are not very informative for some technical reasons. But let us take some steps which should be helpful here.

First, Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Next, Go to Control Panel > Hardware and Sound > Power options (or simply Control Panel > Power Options, depending on your control panel view). Take a screenshot of that window and let us see it following Screenshots and Files - Upload and Post in Seven Forums.

Post the screenshot now. Some actions might be required depending on it.

Also monitor how the computer runs. Let us see any further BSOD dump if they can provide some more.

Finally, a question for you. When, why and how you uninstalled AVG, and what you employed there as its replacement?

Please understand that those steps are not any solutions but an attempt to make a path for troubleshooting the issue.

Hi kyturne, welcome to 7F! :)

Follow the steps that Arc has laid out for you then,

Can you elaborate on the memory? According to ASRock it doesn't support the size you are currently using,

Code:

16GB (2 x 8 GB) - Crucial Ballistix Sport

See near the bottom: ASRock > Fatal1ty 970 Performance:

Code:

DDR3    1066    2GB    Crucial    CT25664BA1067.16SFD    Micron   D9JNLDS         v    4pcs
DDR3    1066    1GB    Crucial    CT12864BA1067.8SFB     Micron    Z9HWQ    SS    v    4pcs

The only ones it does are:

Code:

DDR3    1600    8GB    AMD          AE316G1601U2K          DS    v    2pcs    
DDR3    1600    8GB    Kingston    KHX16C9P1K2/16          DS    v    2pcs    v
DDR3    1600    8GB    Kingston    KHX16C10B1K2/16X        DS    v    2pcs    v

After we see if your machine has calmed down or not, you can try different memory, do you have any spares?

You still have some unnecessary startup programs.

Code:

SUPERAntiSpyware    c:\program files\superantispyware\superantispyware.exe    Lola\Kylie    HKU\S-1-5-21-4081503487-1175601121-3345614134-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
zASRockInstantBoot        Lola\Kylie    HKU\S-1-5-21-4081503487-1175601121-3345614134-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
Fatal1tySTU        Lola\Kylie    HKU\S-1-5-21-4081503487-1175601121-3345614134-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
Ralink Wireless Utility    c:\progra~2\ralink\common\raui.exe -s    Public    Common Startup
NvBackend    "c:\program files (x86)\nvidia corporation\update core\nvbackend.exe"    Public    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
ShadowPlay    c:\windows\system32\rundll32.exe c:\windows\system32\nvspcap64.dll,shadowplayonsystemstart    Public    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

Deduct them too.

The issue is a network related one, apparently.

Code:

BugCheck A, {12, 2, 1, fffff80002c206f4}

Probably caused by : tcpip.sys ( tcpip!TcpUpdateMicrosecondCount+79 )

Followup: MachineOwner
---------

And your network driver is old enough, which needs to be updated.

Code:

    Image name: netr28x.sys
    Timestamp:        Mon Mar 05 18:07:36 2012

This is a network chip is developed by Ralink, RT5592, but I am not sure about the vendor. But MediaTek (the present owner of Ralink) does not have this one listed.
PCI Database is silent about this one, too.

One ASUS card I have found using RT5592, but there is n feasible update from ASUS too.

If you can let us know the brand and model of your networking card, we may search for a possible update for it; which is the first preference at this moment.

Did you see this page? Rosewill.com - N600PCE - Downloads Updated as of last week. Follow the install instructions to the letter.

If a straight up install fails and 7 allows you to install in compatibility mode try Vista or even XP. If all that doesn't work try like you mentioned, hard-wire your net to test to see if the card is causing your bsod's. While I was looking around for the above link I saw a lot of problems with rosewill cards.

Ky, you have 12 dumps:

• 4 ntkrnlmp
• 1 tcpip
• 1 csrss
• 2 amdppm
• 3 hardware
• 1 cfosspeed6 - Here I would suggest removing zasrockinstant boot, and while you're at it uninstall fatal1tystu their both showing in your startup report, if you're using fatal1 tuning to overclock, again uninstall it and return everything to their defaults including your BIOS. Do this first and test for BSOD!

All point to various types of misaligned memory, i.e., poor driver design. I believe you're having a cascading effect where when one goes the others follow, we just don't know which driver starts the cascade.

• Can you find out if your CPU is based on Alpha, IA-64, MIPS, or SuperH architectures?

Second move; With tcpip involved did you try installing in compatibility mode? If you don't want to try that do like you mentioned in an earlier post about removing the rosewell device, the card and uninstall the driver program for it. Then restart your on-board connection and hard-wire to the internet. Test for BSOD!

Third; There is still the case for mismatched RAM see post #3, you can try running Memtest+86 or maybe a faster way would be to pull one stick and test for BSOD then try the other and test, you should be okay booting up on 8GB, if you get a BSOD on either I would start thinking about new RAM. Don't forget to move them to different slots, you could have a bad slot. Test after each move.

Could you please post the screen shot of Control Panel > Power Options, that Arc requested?

You can post back however you like; Whether or not either of the three steps have or have not caused a BSOD.

Ditto to Anak, as he posted .....

• 4 ntkrnlmp
• 1 tcpip
• 1 csrss
• 2 amdppm
• 3 hardware
• 1 cfosspeed6 -

It ensures a high possibility of memory issue. Otherwise such a versatility is not very possible. You have to minimize the possibilities of memory issue, and so memtest86+ would be a nice tool for you.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result.