New
#1
Black & BSOD during Facebook, Wunderground and more
Really don't want to pay someone to fix if you can guide me through it.
Really don't want to pay someone to fix if you can guide me through it.
- Norton is known to cause blue screens. Please uninstall it and use MSE. Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:
NoteDo not start the trial version of MalwareBytes
- Also take a look at: Good & Free System Security Combination
- Revo Uninstaller "Free"
- Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling. This allows you to remove leftover registry entries of the software.
- Virus Check:
- Make scans with these tools below:
- Application conflict:
- Reduce the start-up items. This will help avoid software conflicts:
- System File Checker
- The SFC /SCANNOW Command - System File Checker scans the integrity of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible. If you have modified your system files as in theming explorer/system files, running sfc /scannow will revert the system files to it's default state.
- Link to full tutorial: SFC /SCANNOW Command - System File Checker
- Run Disk Check in Windows 7
- Run this on your Hard Drive(s). This will show you how to run Check Disk or chkdsk in Windows 7 to check a selected hard disk for file system errors and bad sectors on it. With both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
- Link to full tutorial: Disk Check
- Use Crystal Disk Info to upload a screenshot of your Hard Drives (s).
- Then test your Hard Drives (s) running a Hard Drive Diag.
- Check for heating issues using Speccy or HWmonitor
- HWMonitor CPUID - System & hardware benchmark, monitoring, reporting
- Speccy - System Information - Free Download
- Please upload a summary tab using Speccy. Screenshots and Files - Upload and Post in Seven Forums
- Test and Diagnose RAM issues with MEMTEST86+
- Pay close attention to Part 3 of the tutorial "If you have errors". Take the test for at least 7-10 passes. It may take up to 22 passes to find problems.
- Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold. RAM - Test with Memtest86+
Update these drivers:
000.fcl Fri Sep 26 19:11:22 2008 (48DCDF7A)
CyberLink FCL Driver
Driver Reference Table - 000.fcl
VSTCNXT6.SYS Thu Oct 16 06:52:22 2008 (48F69046)
Conexant SoftK56 Modem Driver
Driver Reference Table - VSTCNXT6.SYS
VSTBS26.SYS Thu Oct 16 06:54:06 2008 (48F690AE)
Conexant HSF_HWB2 WDM driver
Driver Reference Table - VSTBS26.SYS
VSTDPV6.SYS Thu Oct 16 06:57:45 2008 (48F69189)
Conexant SoftK56 Modem Driver
Driver Reference Table - VSTDPV6.SYS
viahduaa.sys Tue Apr 28 08:26:53 2009 (49F6696D)
VIA High Definition Audio Function Driver
Driver Reference Table - viahduaa.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
Rt64win7.sys Fri May 22 20:52:30 2009 (4A16BC2E)
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
Driver Reference Table - Rt64win7.sys
PxHlpa64.sys Wed Jun 24 05:16:35 2009 (4A416253)
Sonic CD/DVD driver (used by many different CD/DVD programs)
Driver Reference Table - PxHlpa64.sys
If no updates are available remove the software with Revo free.
- To perform a clean install of a driver, follow this tutorial:
AODDriver2.sys Tue Mar 6 15:55:00 2012 (4F55DEF4)
- Revo Uninstaller "Free"
- Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling. This allows you to remove leftover registry entries of the software.
AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7
Driver Reference Table - AODDriver2.sys
Bugcheck: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.
Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.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 http://ati.amd.com (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums
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.
If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.
Code:Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Debug session time: Sun Nov 10 23:19:53.936 2013 (UTC + 6:00) System Uptime: 0 days 0:18:42.434 BugCheck 3B, {c0000005, fffff8800a35aa8e, fffff880091fdb20, 0} *** WARNING: Unable to verify timestamp for SRTSP64.SYS *** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS Probably caused by : SRTSP64.SYS ( SRTSP64+63a8e ) BUGCHECK_STR: 0x3B PROCESS_NAME: RoxioBurnLaunc ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Debug session time: Sun Nov 10 16:14:33.539 2013 (UTC + 6:00) System Uptime: 0 days 2:11:13.287 BugCheck 1E, {ffffffffc0000005, fffff880012847f0, 1, 0} Probably caused by : hardware ( volsnap+267f0 ) BUGCHECK_STR: 0x1E_c0000005_R PROCESS_NAME: System ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Debug session time: Sun Nov 10 14:02:26.586 2013 (UTC + 6:00) System Uptime: 0 days 3:21:32.644 BugCheck 3B, {c0000005, fffff800032d3d67, fffff88008be9c30, 0} Probably caused by : memory_corruption ( nt!MiPfnShareCountIsZero+77 ) BUGCHECK_STR: 0x3B PROCESS_NAME: svchost.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Debug session time: Sun Nov 10 10:40:07.008 2013 (UTC + 6:00) System Uptime: 1 days 2:10:27.756 BugCheck A, {5a800327b6ba, 2, 0, fffff800032ae06b} *** WARNING: Unable to verify timestamp for SRTSP64.SYS *** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS Probably caused by : SRTSP64.SYS ( SRTSP64+7f374 ) BUGCHECK_STR: 0xA PROCESS_NAME: N360.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Debug session time: Sat Nov 9 08:28:45.393 2013 (UTC + 6:00) System Uptime: 0 days 0:18:30.141 BugCheck 24, {1904fb, fffff88008cb0d58, fffff88008cb05b0, fffff880014daccc} *** WARNING: Unable to verify timestamp for SRTSP64.SYS *** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS Probably caused by : SRTSP64.SYS ( SRTSP64+b1982 ) BUGCHECK_STR: 0x24 PROCESS_NAME: SearchProtocol ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Debug session time: Sat Nov 9 08:09:22.188 2013 (UTC + 6:00) System Uptime: 0 days 0:10:13.686 BugCheck D1, {fffff800072b6110, 2, 8, fffff800072b6110} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) BUGCHECK_STR: 0xD1 PROCESS_NAME: SearchProtocol ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Debug session time: Sat Nov 9 07:58:15.028 2013 (UTC + 6:00) System Uptime: 0 days 0:24:07.527 BugCheck 1A, {41287, 4a2d99e, 0, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+454f5 ) BUGCHECK_STR: 0x1a_41287 PROCESS_NAME: sidebar.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Debug session time: Sat Nov 9 07:33:14.348 2013 (UTC + 6:00) System Uptime: 0 days 21:59:54.111 BugCheck 50, {fffff120257fb990, 1, fffff880010607c4, 7} *** WARNING: Unable to verify timestamp for SYMEFA64.SYS *** ERROR: Module load completed but symbols could not be loaded for SYMEFA64.SYS Probably caused by : SYMEFA64.SYS ( SYMEFA64+e46bc ) BUGCHECK_STR: 0x50 PROCESS_NAME: N360.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Debug session time: Thu Nov 7 02:30:01.873 2013 (UTC + 6:00) System Uptime: 0 days 16:29:57.621 BugCheck 3B, {c0000005, fffff800032a1fcf, fffff8800ad99fa0, 0} Probably caused by : hardware ( nt!MiCheckControlArea+2ef ) BUGCHECK_STR: 0x3B PROCESS_NAME: N360.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Debug session time: Wed Nov 6 09:58:52.704 2013 (UTC + 6:00) System Uptime: 0 days 11:09:22.452 BugCheck 50, {fffff900c20351a8, 1, fffff800032b3af6, 7} Probably caused by : win32k.sys ( win32k!InternalRebuildHwndListForIMEClass+38 ) BUGCHECK_STR: 0x50 PROCESS_NAME: iexplore.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Debug session time: Tue Nov 5 22:07:43.338 2013 (UTC + 6:00) System Uptime: 0 days 18:40:06.086 BugCheck 19, {22, 220000000000, 0, 0} *** WARNING: Unable to verify timestamp for SYMEFA64.SYS *** ERROR: Module load completed but symbols could not be loaded for SYMEFA64.SYS Probably caused by : SYMEFA64.SYS ( SYMEFA64+e3e7e ) BUGCHECK_STR: 0x19_22 PROCESS_NAME: System ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Debug session time: Tue Nov 5 02:09:01.543 2013 (UTC + 6:00) System Uptime: 0 days 13:19:06.291 BugCheck 24, {1904fb, fffff88009337e68, fffff880093376c0, fffff800032b2317} Probably caused by : memory_corruption ( nt!MiReleaseSystemCacheView+20f ) BUGCHECK_STR: 0x24 PROCESS_NAME: N360.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Debug session time: Mon Nov 4 12:48:50.084 2013 (UTC + 6:00) System Uptime: 0 days 2:19:48.583 BugCheck 50, {fffffa0003277e53, 8, fffffa0003277e53, 7} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+43781 ) BUGCHECK_STR: 0x50 PROCESS_NAME: StartManSvc.ex ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Debug session time: Mon Nov 4 10:28:23.245 2013 (UTC + 6:00) System Uptime: 0 days 3:33:24.993 BugCheck 3B, {c0000005, fffff800032f5064, fffff880076e7f20, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3a985 ) BUGCHECK_STR: 0x3B PROCESS_NAME: gnotify.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Debug session time: Mon Nov 4 06:53:49.255 2013 (UTC + 6:00) System Uptime: 0 days 6:41:38.003 BugCheck 34, {50853, fffff88003154498, fffff88003153cf0, fffff800032d1d67} Probably caused by : memory_corruption ( nt!MiPfnShareCountIsZero+77 ) BUGCHECK_STR: 0x34 PROCESS_NAME: System ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``