Solved Fresh Build - Constant BSOD - Multiple Codes - 3b, 50, a

[Dave76]

Good choice on the RAM.

Running with two RAM cards installed at stock settings is a quick way to test the system for any instability. If it runs stable, then it is indicating that the settings need adjusting for the 4X2GB RAM cards to become stable.

The 1.56v for the RAM you have should be enough voltage at 1333MHz, for all four RAM cards installed and the QPI/Vtt Voltage 1.16v.

Set both channels to the same timings.
For the 'Command Rate' 2 and 2T are the same thing.
Did you set the first four RAM timings to 9-9-9-24?

With these settings saved in BIOS, install all four RAM cards and run Prime95 blend test.

 

[LP81]

Well...

Just got home tonight and it looks like the new RAM showed up in the mail on Saturday.

Popped it in and so far it is stable.

I am going thru and loading up the essentials then run the PRIME95 tests again (low, high and blend)

but so far it seems that swapping out to 1.5V memory has done the trick.

I will report back in a few days as to if this if officially "solved"

thanks

 

[Dave76]

That's good news, hope the new RAM runs stable for you.

Let us know in a couple of days if you have any issues, if none you can mark the thread Solved.

 

[LP81]

Good news and Bad News...

No new BSODs to speak of... but now I am having LAN connection issues...

I get about 30-45 seconds of full latency followed by nothing.

Problems exists across all mediums:
Downloads - pull down some data then freeze, have to constantly pause and resume downloads (Firefox, IE and Chrome)
YouTube - plays nicely for about 30 seconds then it catches up to the buffered spot and stop playing
Diablo 3 - 100ms ping for about 30 seconds then 800+ms ping for a few seconds. then back to normal.

I am on a hardwired connection, have reset the router, cable modem, etc. Downloaded the latest LAN drivers directly from manufactured site. Verified my speed on speedtest.net and pingtest.net - both strong connections, but obviously not a long enough of a test to show the dropping.

This seemed to happen with the original Mobo I had as well. I originally chalked it up to the BSOD and memory issues we have now solved, but since it is on the new board as well I think it is a symptom of the board itself.

I have also verified my connection (wired and wireless) with 2 other computer in my house and they are streaming/buffering cleanly.

That being said...

I did not install any of the goofy drivers on the original disc since they are mostly bloatware junk that do nothing.

Are there are extended tests or similar I can run to help diagnose the dropped signals?

 

[Dave76]

Have you updated all your drivers from the Gigabyte website?
GA-Z68AP-D3 Driver Download
Check them all, install the LAN driver from Gigabyte.

 

[LP81]

Have you updated all your drivers from the Gigabyte website?
GA-Z68AP-D3 Driver Download
Check them all, install the LAN driver from Gigabyte.

... Downloaded the latest LAN drivers directly from manufactured site. ...

​

Yep - Already downloaded both the LAN driver and the LAN Diagnostic tool directly from gigabyte's site. I see no need for any of the other drivers list there (except maybe the chipset ones)

 

[Vir Gnarus]

Latency spikes are commonly the result of packet loss, which results in the connection needing to resuscitate itself to get back on track. You said this occurred on the previous motherboard as well? If so, unless you happened to be grabbing mobo's from a bad batch, I can't suspect the onboard network controller to be responsible.

You may want to change ports on the router to see if that affects anything. Next, grab a new cable and see if that works (majority of network problems boil down to cabling issues). As for software issues that may cause this, I've found that a heavily bloated hosts file caused by antispyware programs like Spybot Search & Destroy can generate these spikes, because during certain network activity Windows will periodically buffer the hosts file, and if it's big enough then it'll cause these hangs. Misbehaving AV products can also cause this, so check for any engine updates on em as well as try and determine if there's any conflicts like running two AV engines at once (never a good idea).

 

[LP81]

According to pingtest.org there were zero packets lost during it's test

I'll try a different port & cable when I get home.

Only AV/ASW on the system right now is Microsoft Security Essentials.

Only other item that might be going out and getting constant feedback is the a Network Monitor Widget -- Desktop gadgets - Microsoft Windows -- Network Meter V6.4
- by Keat

 

[Vir Gnarus]

I still recommend you locate your hosts file (\Windows\system32\drivers\etc) and see how many entries are present.

As for figuring out if there's any software that's spiking this, we could use xperf with network tags, but we'll wait until you take care of the cable and port thing before we resort to it. If other troubleshooting venues do not offer a solution, then you can do preliminary setup for xperf by installing the Windows SDK. When asked what items to install, you'll want to select the Performance Toolkit in its entirety.

 

[LP81]

Swapped out network cables and ports.

No difference.

Verified original cord on a laptop and it's a smooth connection

Host file is basically empty:

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost



Downloaded the SDK, but it told me I don't have .NET Framework 4 installed.

Looked in my windows update list and there's 15 or so files that keep failing to install.

Told it to install them now rather than at restart and up pops:

Install Windows Service Pack

Installation was not sucessful

A system error prevented the service pack from installing. Please download and run the "Check for System Update Readiness" tool at Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2

If the "Check for System Update Readiness" tool doesn't fix the problem, visit the Microsoft Website for more information (Details)


Downloaded said file (took multiple tries obvious with said jittery connection), ran it and it said

Some updates were not installed: Hotfix for Windows (KB947821)

 

[LP81]

I continues on the path Microsoft kept leading me along and ran Microsoft FixIt

attached is the ResultReport.html it spit out for reference (zipped because it was an html file)

Tried to install updates again and no dice, same errors about not being able to install the service pack

 

[James7679]

Did you update the chipset driver? My GB MoBo didn't play nice until I did.

 

[Vir Gnarus]

I think this guy may be on to something. Follow the instructions present to prep things up for use fo the Readiness Tool. Notice that network issues may still cause it to fail in downloading properly. Try downloading the proper Readiness Tool from your laptop and then transfer it via LAN over to the victim PC and then install it from there.

As for the SDK thing, you can download .NET 4 here

 

[James7679]

Patrick, were you able to get this resolved?

 

[LP81]

Weird, no new emails came thru saying there were replies.

I have been in the office all week so I didn't have much time.

I did the chipset drivers, very minor improvement, still drops randomly.

Installing .NET right now

 

[LP81]

So I started to go thru that list...

Downloaded said file: Windows6.1-KB947821-v22-x64.msu


It installed "Hotfix for Windows (KB947821) (update 1 of 1)..."


Checked the CheckSUR.log and it had somethign different than the 3 options listed on the one page:

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_2_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1:
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_4_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_4_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.cat

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 145
Found 3 errors
CBS MUM Corrupt Total count: 2
CBS Catalog Corrupt Total count: 1

Unavailable repair files:
servicing\packages\Package_2_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_4_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_4_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_2_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_4_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_4_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.cat



Different files were listed than the guide, but intuition kicked in and I filled in the blanks...



Found the appropriate 979916 MSU File... Extracted it the files and replaced them.


Reran the Windows6.1-KB947821-v22-x64.msu

Rechecked the CheckSUR.log


Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 120
No errors detected



Ran SFC /SCANNOW

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.


Time to restart and see if I can install the outstanding windows updates that linger and if it fixes my network

 

[LP81]

OK, so I finally have all of my updates installed - had to do a few manually because Windows Update wasn't cooperating, but I think I am finally there...

Now to determine if my connection is stable (at work right now so I can't do this til tonight)

 

[LP81]

I thought it was going to be stable but no dice... As you can see in the attachment, it goes full speend then craps out for a bit, full speed, crap... back and forth...

This particular instance was downloading a 300MB+ file... 2-3 meg come down with no issue, anything larger it chokes.

 

[LP81]

Monday morning bump

 

[Vir Gnarus]

The drops look like they aren't systematic. Can you verify if there's a pattern to them or if it's just randomness in either timing or length?

As for logging all this, your options is to either produce a log from Performance Monitor (startup guide here), Xperf, or ProcMon.

For Xperf, you'll need to have the Windows SDK installed, specifically the "Performance Toolkit" for it. This is a good guide on how to setup and run Xperf properly to log network-based activity. You'll want strict instances where you are solely performing specific operations like just downloading a large file, or playing a game. I believe you do not need to do the heap logging, so you can disregard that portion of the guide. Xperf is probably the most thorough log for us to look at, aside from ProcMon. Unlike ProcMon, however, it's a bit easier to read.

For ProcMon, grab it here, then open it. Immediately stop capturing by clicking the magnifying glass button, then clear entries by clicking the eraser button next to it. Then, start a download of a large file or something. Start capturing by clicking the magnifying button again and let it capture a moment when the network speed plummets. Then save as (make sure to check "all events") a procmon log.

For both Xperf and Procmon logs, I really doubt either will fit here as an attachment, so you may need to use something like MirrorCreator.com or whatever to upload it to some 3rd-party filesharing sites.