Solved BSOD playing FFXIV and browsing on chrome.

[NoelDP]

...and the CheckSUR data????

 

[kwall]

I am getting the same hot fix pop up every time I use it even after a restart.

 

[NoelDP]

The Hotfix IS the CheckSUR tool (AKA SURT) - so it's not surprising.

The CheckSUR logs are (surprisingly) clean.


I've uploaded a file - kwlaa.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.
Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.
Pick the option to use a Command Prompt
At the prompt type
DIR C:\kwlaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\kwlaa
or
DIR E:\kwlaa

The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

XCOPY <drive>:\kwlaa <drive>:\windows\winsxs /y /i /s /v /h

(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command (it should take almost no time)and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.
Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply
Also run a new MGADiag report, and post the result.

 

[kwall]

So I cracked and bought a new HDD for this new build. I would like to thank Arc and NoelDP for walking me through the problems I was having. If the bsod problems stemmed from my eight year old HDD, changing it out might help.

I will be checking this thread as solved. If any other problems surface I will return for the excellent service and knowledge of the sevenforum members.

Update: I ran Memtest86+ and one of my sticks was popping error codes. Going to run memtest for about 7 run to make sure the other one is at least healthy.

 

[Arc]

I ran Memtest86+ and one of my sticks was popping error codes. Going to run memtest for about 7 run to make sure the other one is at least healthy.

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

 

[kwall]

When I tested the bad memory alone in every dimm slot, I was getting error codes instantly. Then I took the good ram and tested it in each dimm slot. The results were better with no error codes. The good stick was running memtest for a couple of hours in each slot with no problems.

 

[Arc]

So it is determined that it is not a motherboard error, and the bad stick is pointed out, too
Good job

Now, you may do any of the following:

• Use the good stick only.
• Replace the entire memory with a new compatible RAM KIT.
• Replace the bad one only with one having the exact same specs of the existing one.

Be aware that if you take the last option, and the specs of the replacement RAM does not match with the existing, there will be issues.

 

[kwall]

Going to ship them back for a refund. Going to buy 8gb of Mushkin enhanced stealth (low profile version of the blackline).

I would again like to thank Arc and NoelDP for helping me with computer problems .