BSOD and Stop Error 0x0000001E - Sporadic

Hello sluggo97.

Avast is causing some problems there.

Code:

fffff880`055487d8  fffff880`03f05905Unable to load image \??\C:\Windows\system32\drivers\aswMonFlt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
 aswMonFlt+0x21905

Description here: http://www.carrona.org/drivers/drive...=aswMonFlt.sys

Uninstall Avast using Avast Uninstall Utility. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

You have reasons to do some more extensive system scan.

Code:

fffff880`05548ef8  fffff880`010f9000 ataport!ChannelSyncAcpiEvalMethod <PERF> (ataport+0x0)
fffff880`05548f00  fffff880`01110930 ataport!__PchSym_ <PERF> (ataport+0x17930)
fffff880`05548f08  fffff880`010f9000 ataport!ChannelSyncAcpiEvalMethod <PERF> (ataport+0x0)
fffff880`05548f10  fffff880`01110924 ataport!__PchSym_ <PERF> (ataport+0x17924)
fffff880`05548f18  fffff880`010f9000 ataport!ChannelSyncAcpiEvalMethod <PERF> (ataport+0x0)
fffff880`05548f20  fffff880`01110840 ataport!__PchSym_ <PERF> (ataport+0x17840)
fffff880`05548f28  fffff880`010f9000 ataport!ChannelSyncAcpiEvalMethod <PERF> (ataport+0x0)
fffff880`05548f30  fffff880`01110834 ataport!__PchSym_ <PERF> (ataport+0x17834)
fffff880`05548f38  fffff880`010f9000 ataport!ChannelSyncAcpiEvalMethod <PERF> (ataport+0x0)
fffff880`05548f40  fffff880`01110918 ataport!__PchSym_ <PERF> (ataport+0x17918)
fffff880`05548f48  fffff880`010f9000 ataport!ChannelSyncAcpiEvalMethod <PERF> (ataport+0x0)
fffff880`05548f50  fffff880`01110618 ataport!__PchSym_ <PERF> (ataport+0x17618)

Scan the system for possible virus infection with the following programs, too.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

And the display driver is causing some issues there, too.

Code:

BugCheck D1, {0, 2, 1, fffff8800446d1c1}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiCompleteSignalCommmand+151 )

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

I would suggest you to do a clean install of the display driver, using the 314.22 WHQL driver.

• Uninstall All nvidia items in Control Panel > Programs and features
  
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

The Logitech Webcam.

Code:

BugCheck 50, {fffff87f859e0eac, 0, fffff88004480fdc, 5}

*** WARNING: Unable to verify timestamp for lvuvc64.sys
*** ERROR: Module load completed but symbols could not be loaded for lvuvc64.sys

Could not read faulting driver name
Probably caused by : ks.sys ( ks!KsStreamPointerAdvance+0 )

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

Search for driver updates in Logitech Support - Downloads, Manuals, FAQs & More . If not found, disable the webcam.

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.

Let us know the results.
________________________________________________________________________________
BSOD ANALYSIS:

Code:

BugCheck 1E, {ffffffffc0000005, fffff80002b784c7, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!PpmPerfSelectDomainStates+17 )

Followup: MachineOwner
------------------------------------------------------------------------------------
BugCheck 50, {fffff87f859e0eac, 0, fffff88004480fdc, 5}

*** WARNING: Unable to verify timestamp for lvuvc64.sys
*** ERROR: Module load completed but symbols could not be loaded for lvuvc64.sys

Could not read faulting driver name
Probably caused by : ks.sys ( ks!KsStreamPointerAdvance+0 )

Followup: MachineOwner
--------------------------------------------------------------------------------------
BugCheck D1, {0, 2, 1, fffff8800446d1c1}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiCompleteSignalCommmand+151 )

Followup: MachineOwner
---------------------------------------------------------------------------------------
BugCheck D1, {fffff87fff5f4df5, 2, 0, fffff8800532b4be}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSelectContext+42 )

Followup: MachineOwner
---------------------------------------------------------------------------------------
BugCheck 1E, {0, 0, 0, 0}


Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

Apparently the BSOD is caused by Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller (NDIS6.20) driver,

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa801fb7ccb9, 2, 0, fffff880015965d9}

*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

And the driver is very old.

Code:

fffff880`04200000 fffff880`04212000   L1E62x64 T (no symbols)           
    Loaded symbol image file: L1E62x64.sys
    Image path: L1E62x64.sys
    Image name: L1E62x64.sys
    Timestamp:        Sun Aug 23 10:38:09 2009 (4A90CEB9)
    CheckSum:         0001697B
    ImageSize:        00012000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Get the updates from ATHEROS Network drivers for Windows, it is a newer version than what is available OEM.

At the same time, as the "memory corruption" is stated there, 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.

At the same time, I would suggest you to unistall Citrix Deterministic Network Enhancer Miniport.

Code:

fffff880`0bcbd8b8  fffff880`053bf319Unable to load image dne64x.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dne64x.sys
*** ERROR: Module load completed but symbols could not be loaded for dne64x.sys
 dne64x+0x1b319

Let us know the results when done.

sluggo97 said:

I have replaced the network driver as requested. MEMTest has run overnight. In four passes, there are 32 errors so far. I will update again when I get home.

Enough of testing. A single error is enough.

Now follow the part three 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:
No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

Or, if you want, you may change the RAM with a new kit.

The combinations of tests should be .... as per your explanation ....

No code has to be inserted here.