Frequent BSODs and black screens, also IRQL-NOT-LESS-OR-EQUAL

Texasbacon · 01 Apr 2013

For the past month or so, my computer has been getting frequent Blue Screens, the most common error is IRQL-NOT-LESS-OR-EQUAL. I also have random black screens that shut down my computer while playing games (mainly Minecraft, to be specific) and while watching YouTube videos. There have also been some problems with my internet browser. When I click the icon on the taskbar, it will load and then automatically crash my computer. I have tried Chrome, Internet Explorer, and Firefox. I have also had startup repairs but they dont really seem to be doing anything to fix the problem. My computer is about a year and a half old (a HP laptop), and I have made sure all my drivers are up to date. I have tried several different methods, but the problem persists. I have noticed that the bottom of my computer generates much more heat then my old computer that I still have. Is this an overheating problem? Do I need to replace any parts or hardware? Any help would be very much appreciated.

koolkat77 · 02 Apr 2013

Probably.

Heat:
- only use the laptop on a hard surface - with nothing blocking any of the vents.
- use a laptop cooling pad if possible
- blow out all vents with canned air (DO NOT use a vacuum cleaner or an air compressor, they can damage the components).
- ensure that the fan comes on and is blowing air out of the vent (may not happen at startup, but should happen after using it for a while).

For monitoring heat of the system, use Speccy or HWMonitor:

Norton has been contributing to your crashes. Recommend uninstalling it with the Norton Removal Tool and replace with Microsoft Security Essentials. See if this stops the BSOD-s.

Download and run the Norton Removal Tool to remove the Norton Product

Microsoft Security Essentials is recommended from a strict BSOD perspective.

Microsoft Security Essentials, Free antivirus for windows
Malwarebytes Anti-Malware Free
Good and Free system security combination

Warning

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

Run a full scan with both (separately) once downloaded, installed and updated.

Code:

AODDriver2.sys  Tue Mar  6 15:55:00 2012
AMD Overdrive; also in EasyTune6 for Gigabyte motherboard. Known BSOD issues in Win7

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems.

Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect.

Sometimes the driver remains and continues to cause BSOD's.

Use the System File Checker tool (SFC.exe) to determine which file is causing the issue, and then replace the file.

To do this, follow these steps:

1. Open an elevated command prompt. To do this, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.

2. At the command prompt, type the following command, and then press ENTER: sfc /scannow
The sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions.

SFC /SCANNOW Command - System File Checker
Use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

Number down items at start-up. Keep only your anti-virus, this also improves the time for logging into windows.

1. Startup Programs - Change
2. Troubleshoot Application Conflicts by Performing a Clean Startup

Check a drive for errors:
1. Check a drive for errors
2. Check your hard disk for errors in Windows 7
3. Disk Check

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
RAM - Test with Memtest86+

Note

Pay close attention to part 3 of the tutorial in order to rule out the faulty stick.

Information

Errors are sometimes found after 8 passes.

Tip

Do this test overnight, before going to bed.

BSOD BUGCHECK SUMMARY

Code:

Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Mar 31 20:51:53.660 2013 (UTC + 6:00)
System Uptime: 0 days 0:04:53.267
BugCheck 1E, {ffffffffc0000005, fffffa8004d7cbb0, 0, 7efa8000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48d3d )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Mar 31 20:42:41.933 2013 (UTC + 6:00)
System Uptime: 0 days 0:05:39.540
BugCheck 1E, {ffffffffc0000005, fffffa8004bffbb0, 0, 7efa8000}
Probably caused by : NETIO.SYS ( NETIO!WfpTimerWheelTimeoutHandler+1e0 )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  MMLoadDrv.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Apr  1 06:34:23.176 2013 (UTC + 6:00)
System Uptime: 0 days 0:03:38.783
BugCheck 1E, {ffffffffc0000005, fffffa8004f1abb0, 0, 7efa8000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48d3d )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  MMLoadDrv.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Apr  1 03:47:32.056 2013 (UTC + 6:00)
System Uptime: 0 days 0:03:49.633
BugCheck 1E, {ffffffffc0000005, fffffa8004e71bb0, 0, 7efa8000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48d3d )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  MMLoadDrv.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Apr  1 03:43:07.506 2013 (UTC + 6:00)
System Uptime: 0 days 0:02:51.114
BugCheck 1E, {ffffffffc0000005, fffff80002f0b405, 0, ffffffffffffffff}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+115 )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Apr  1 03:36:40.958 2013 (UTC + 6:00)
System Uptime: 0 days 0:02:05.566
BugCheck 1E, {ffffffffc0000005, fffffa8004cabbb0, 0, 7efa8000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48d3d )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  MMLoadDrv.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Apr  1 00:20:25.272 2013 (UTC + 6:00)
System Uptime: 0 days 0:04:40.880
BugCheck A, {e1b00aed6, 2, 1, fffff80002f16405}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+115 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Mar 31 07:03:01.802 2013 (UTC + 6:00)
System Uptime: 0 days 0:03:36.410
BugCheck 1E, {ffffffffc0000005, fffffa8004c47bb0, 0, 7efa8000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48d3d )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Mar 31 05:38:54.334 2013 (UTC + 6:00)
System Uptime: 0 days 0:05:19.942
BugCheck A, {0, 2, 1, fffff80002e80638}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KiRequestProcessInSwap+60 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Mar 30 21:35:30.848 2013 (UTC + 6:00)
System Uptime: 0 days 0:04:08.455
BugCheck 1E, {ffffffffc0000005, fffffa8004e23bb0, 0, 7efa8000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48d3d )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Mar 30 21:30:31.473 2013 (UTC + 6:00)
System Uptime: 0 days 0:03:05.080
BugCheck 1E, {ffffffffc0000005, fffff80002e8c915, 0, ffffffffffffffff}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+1e3 )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Mar 27 16:20:30.489 2013 (UTC + 6:00)
System Uptime: 0 days 0:03:28.097
BugCheck A, {41fb, 2, 1, fffff80002f0d405}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+115 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Mar 23 22:51:10.494 2013 (UTC + 6:00)
System Uptime: 0 days 1:04:57.977
BugCheck FE, {8, 6, 6, fffffa8005b7b000}
*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
Probably caused by : usbfilter.sys ( usbfilter+518c )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Mar 23 21:18:25.060 2013 (UTC + 6:00)
System Uptime: 0 days 0:28:42.542
BugCheck FE, {8, 6, 6, fffffa8005b3c000}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : usbfilter.sys ( usbfilter+518c )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Mar 23 20:48:51.340 2013 (UTC + 6:00)
System Uptime: 0 days 0:04:03.948
BugCheck 1E, {ffffffffc0000005, fffffa8004c4bbb0, 0, fffa8000}
*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48d3d )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  mscorsvw.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Mar 23 20:40:25.585 2013 (UTC + 6:00)
System Uptime: 0 days 1:28:56.192
BugCheck FE, {8, 6, 6, fffffa8005d60000}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : usbfilter.sys ( usbfilter+518c )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Mar 23 09:01:15.858 2013 (UTC + 6:00)
System Uptime: 0 days 3:23:21.466
BugCheck 1E, {ffffffffc0000005, fffff80002ec27ef, 0, 7fffffa0000}
*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
Probably caused by : ntkrnlmp.exe ( nt!RtlImageNtHeaderEx+3f )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  SearchFilterHo
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Mar 23 05:37:16.222 2013 (UTC + 6:00)
System Uptime: 0 days 3:04:20.829
BugCheck 1E, {ffffffffc0000005, fffff80002eb27ef, 0, 7fffffa0000}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!RtlImageNtHeaderEx+3f )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  WmiPrvSE.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Mar 23 02:32:16.475 2013 (UTC + 6:00)
System Uptime: 0 days 1:18:29.957
BugCheck 1E, {ffffffffc0000005, fffff80002eb67ef, 0, 7fffffa0000}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!RtlImageNtHeaderEx+3f )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  WmiPrvSE.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Mar 20 05:02:30.462 2013 (UTC + 6:00)
System Uptime: 0 days 0:14:57.069
BugCheck FE, {8, 6, 6, fffffa8005b2a000}
*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
Probably caused by : usbfilter.sys ( usbfilter+518c )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Mar 20 01:42:07.283 2013 (UTC + 6:00)
System Uptime: 0 days 1:10:58.766
BugCheck FE, {8, 6, 6, fffffa8005d46640}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : usbfilter.sys ( usbfilter+518c )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Tue Mar 19 00:55:28.588 2013 (UTC + 6:00)
System Uptime: 0 days 1:45:14.196
BugCheck 1E, {ffffffffc0000005, fffff8000317d6ea, 1, 18}
*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
Probably caused by : ntkrnlmp.exe ( nt!ObpCreateHandle+29a )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  WmiPrvSE.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Mar 18 22:05:01.803 2013 (UTC + 6:00)
System Uptime: 0 days 3:58:49.410
BugCheck FE, {8, 6, 6, fffffa8005655000}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : usbfilter.sys ( usbfilter+518c )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Mar 17 07:40:03.011 2013 (UTC + 6:00)
System Uptime: 0 days 1:20:22.618
BugCheck 1E, {ffffffffc0000005, fffff800031d46ea, 1, 18}
*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
Probably caused by : ntkrnlmp.exe ( nt!ObpCreateHandle+29a )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  WmiPrvSE.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Mar 10 21:14:37.416 2013 (UTC + 6:00)
System Uptime: 0 days 21:05:54.023
BugCheck A, {fffffa80400c001c, 2, 0, fffff80002e86915}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+1e3 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Mar 10 00:08:09.546 2013 (UTC + 6:00)
System Uptime: 1 days 16:46:15.153
BugCheck 1E, {ffffffffc0000005, fffff800031d16ea, 1, 18}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!ObpCreateHandle+29a )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  FlashPlayerUpd
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Mar  7 08:28:05.813 2013 (UTC + 6:00)
System Uptime: 0 days 0:04:44.420
BugCheck A, {dc, 2, 1, fffff80002ec5405}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+115 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Texasbacon · 02 Apr 2013

Thanks, I'll try out these options.

koolkat77 · 02 Apr 2013

Good luck.

Be sure to post an update on how things are.

Texasbacon · 04 Apr 2013

After doing the majority of things on the list, it seems that the problem is resolved. Not only does my computer no longer Blue Screen, but it seems to run smoother as well. Thanks for all your support.

koolkat77 · 04 Apr 2013

You're welcome.

Be sure to post if you have further BSODs.