BSOD after installing MS Updates

Florida Rene · 19 Jan 2014

After installing Windows Updates, I now sometimes get the BSOD while scrolling an open web page in IE-11 or FF-26.0. Not always. Sometimes.

The error message is

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8006C33038
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\011714-54771-01.dmp
C:\temp\WER-88062-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Recent Windows Update files are listed in Update History jpg attached.

I tried to attach the zipx file for the SF BSOD tool report, created by WinZip 17.5, but SF gave me an error msg saying that file type isn't accepted. So I redid it as a Zip file via 7-Zip and I hope that's okay.

I'm mystified by all this. Please help.

Arc · 20 Jan 2014

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8006b028f8, 0, 0}

Probably caused by : hardware

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

Hi Florida Rene. How old the computer is? Let us know, as it may be the most vital information here.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

Let us know the results.

Florida Rene · 21 Jan 2014

Hello Arc, and THANK YOU for pitching in.

First answer: March 9, 2011 was HP's "build date".

Speccy report is attached...done after running the computer normally for about 7 hours.

I'll get to the other tests shortly.

Florida Rene · 21 Jan 2014

Got a chance to run FURMARK. Stopped when extra fan came on and temp went over 65.

Ran SPECCY immediately afterwards. Attached is the new SPECCY report.

Florida Rene · 21 Jan 2014

Arc said:

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Not comfortable with running this test because I don't have your skill level.

Also, I don't know how I'd watch for red lines overnight. Is there a way to configure the test so it stops if a red line occurs?

Golden · 21 Jan 2014

The red lines stay on the screen until you stop the program.

Florida Rene · 22 Jan 2014

Ran Prime95. Passed all tests.

Stopped it when the loop restarted.

Any reaction to the test results posted here and above?

Arc · 22 Jan 2014

Prime95 looks fine. What about the memtest?

Florida Rene · 22 Jan 2014

Arc said:

Prime95 looks fine. What about the memtest?

Haven't run it yet. Trepidation.

Florida Rene · 22 Jan 2014

Tried memtest and I guess it's not for my skill level. After getting the USB prepared, the jpg below shows what it contained.

Rebooted, but computer went straight to normal boot-up. Decided my trepidation was appropriate.

Looked around the Internet and suddenly discovered that I am among thousands having the same problem after installing the nVidia GeForce update. As you probably noted in my first post above, I had installed the nVidia update just before this BSOD nonsense started. This link shows one of many threads devoted to this issue.

https://forums.geforce.com/default/t...zing-my-pc/26/

I'm continuing to research this, and I thank you, Arc, for helping on this. Many posters say rolling back to nVidia 314.22 solved the issue for them. I'm now going to investigate this in the hope that it does it for me too. If only I knew how to "roll back".

Thanks again, Arc.