BSOD BCCode 4e after IE10 crash

SJesMe · 31 Oct 2014

Random, multiple BSODs associated with IE10, IE11 and FF v32 crashes. Doesn't seem associated with any particular web page or other specific activity. Most recent BSOD showed this report after normal reboot:

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: 4e
BCP1: 0000000000000099
BCP2: 000000000010DA97
BCP3: 0000000000000000
BCP4: 00000000001E3D97
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\103014-21138-01.dmp
C:\Users\***\AppData\Local\Temp\WER-52681-0.sysdata.xml

Attaching dump file per request:

Attachment 338874

Other than telling you I am 99.99% positive I have no malware or virus (Avast! MBAM, Panda and ADWCleaner have all been run without finding anything), I will apologize for running CCleaner and erasing any earlier BSOD info there was (probably 5-6 prior to this last one).

The BSODs, crashing all browsers mentioned above and NVidia display adapter "stopped working" errors have been continuous since I took this machine out of the box 3 weeks ago. In addition to changing out browsers for test purposes, I have updated the NVidia driver from 332.21 to 344.11 and rolled back to 332.21, all without any significant improvement.

Any help will be very much appreciated.

Arc · 31 Oct 2014

Hi SJesMe.

My friend Mike (ThrashZone) directed me to your thread.

It seems that you are having a memory corruption. Not necessarily a physical RAM failure, it may be some driver passing some bad information to the memory too. But the crash dumps are not pointing to anything precisely. Let us test both the possibilities.

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.

It it does not show any error, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

SJesMe · 31 Oct 2014

My thanks to Mike and to you. I will run Memtest86+ first and report back prior to running DV. Guess this will give me a good chance to catch up on real life work/chores instead of messing with this desktop all day!

SJesMe · 31 Oct 2014

Sheez ... going on 8 hours and only 4 passes complete (no errors so far). Is that normal??

Arc · 01 Nov 2014

Very normal. It will take hours to complete 8 passes on 8 GB RAM.

SJesMe · 01 Nov 2014

Update: 10 passes, no errors. Would it be ok if I uninstalled the NVidia driver and just used whatever generic video driver for a day to see if the problem persists? I'm a little leery of this Driver Verifier thing but if you believe it's best, I'll give it a shot.

Arc · 01 Nov 2014

SJesMe said:

Update: 10 passes, no errors. Would it be ok if I uninstalled the NVidia driver and just used whatever generic video driver for a day to see if the problem persists? I'm a little leery of this Driver Verifier thing but if you believe it's best, I'll give it a shot.

Driver verifier should be the next step there. :)

SJesMe · 01 Nov 2014

Will do. I'll update status as it goes. BTW (knock on wood), no crashes or BSODs today ... yet ...

SJesMe · 01 Nov 2014

Well that didn't take long. Here's the report I got after BSOD and reboot to Windows normally:

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: d1
BCP1: FFFFF980217F2FF8
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF880040059F9
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\110114-29998-01.dmp
C:\Users\Sharon\AppData\Local\Temp\WER-84568-0.sysdata.xml

and here's the dump report:

Attachment 339000

It also placed an SFdebugFiles folder on my desktop which I cannot access or find (other than seeing it on the desktop) to upload.

I was downloading/installing MS Updates when the crash occurred.

I have NOT disabled DV yet.

Many thanks for your continued assistance.

SJesMe · 01 Nov 2014

BSOD #2 (computer idle at the time)

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: 50
BCP1: FFFFF90000002AF0
BCP2: 0000000000000000
BCP3: FFFFF80002FB825F
BCP4: 0000000000000007
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\110114-24382-01.dmp
C:\Users\Sharon\AppData\Local\Temp\WER-89903-0.sysdata.xml

Dump report:

Attachment 339035