Sproadic BSODs, error 0x0000001e

Welcome to the forum.

Please remove Avast! and use MSE for testing purpose.

Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-

• Microsoft Security Essentials - Free Antivirus for Windows
• Malwarebytes - Free
• Good and Free system security combination.

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Fix these drivers:

AsInsHelp64.sys Fri Jan 4 11:36:10 2008 (477DC5CA)
Asus Ai Booster software
Driver Reference Table - AsInsHelp64.sys

AtiPcie.sys Tue May 5 21:00:22 2009 (4A005486)
ATI PCIE Driver for ATI PCIE chipset or [br] ATI PCI Express (3GIO) Filter[br]Found in my ATI video drivers (I have an Intel chipset)
Driver Reference Table - AtiPcie.sys

AsUpIO.sys Mon Jul 6 08:21:38 2009 (4A515FB2)
ASUS hardware monitoring software related
Driver Reference Table - AsUpIO.sys

ASACPI.sys Thu Jul 16 09:31:29 2009 (4A5E9F11)
Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). Also a part of many Asus utilities (Win8 versions available from Windows Update as an Optional Update - but check Asus first!)
Driver Reference Table - ASACPI.sys

To perform a clean install of a driver, follow this tutorial:

• How to Clean Left Over Driver Files with Driver Sweeper

Reduce items at start-up. Nothing except anti-virus is required:

• Startup Programs - Change
• Troubleshoot Application Conflicts by Performing a Clean Startup

Disk Check on your hard disk for file system errors and bad sectors on it:

• Disk Check

Make scans with the following:

Kaspersky TDSSKiller

• Anti-rootkit utility TDSSKiller

ESET online scanner

• Free Online Virus Scanner | ESET

If this does not provide stability. Test RAM.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

Bugcheck Summary

Code:

Debug session time: Mon Nov 25 14:36:34.006 2013 (UTC + 6:00)
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532
System Uptime: 0 days 11:42:52.193
Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+8f )
BugCheck 3B, {c0000005, fffff8000318b11f, fffff88008ede580, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8000318b11f, Address of the instruction which caused the bugcheck
Arg3: fffff88008ede580, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!MiRelinkStandbyPage+8f
BiosVersion = 0403   
BiosReleaseDate = 06/21/2010
SystemManufacturer = ASUSTeK Computer INC.
SystemProductName = CG1330
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Nov 22 11:54:04.614 2013 (UTC + 6:00)
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532
System Uptime: 0 days 10:20:10.800
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+36e )
BugCheck 1000007E, {ffffffffc0000005, fffff800030d35ce, fffff880031d8918, fffff880031d8170}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Bugcheck code 1000007E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800030d35ce, The address that the exception occurred at
Arg3: fffff880031d8918, Exception Record Address
Arg4: fffff880031d8170, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x7E_nt!MiUnlinkPageFromLockedList+36e
BiosVersion = 0403   
BiosReleaseDate = 06/21/2010
SystemManufacturer = ASUSTeK Computer INC.
SystemProductName = CG1330
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``