BSOD - 0x0000001E - Help please :<

Hi yoskex and welcome to seven forums.

Security App

Code:

ngs64.sys                   Tue Jul 12 16:37:06 2011 (4E1C23D2)
nregsec64.sys               Fri Nov 11 20:55:41 2011 (4EBD376D)

Crashes indicate Norman Security Suite being a possible cause. Remove Norman Security Suite and replace with Microsoft Security Essentials to see if it provides more stability. Uninstallers (removal tools) for common antivirus software. Microsoft Security Essentials and Malwarebytes are recommended from a strict BSOD perspective. They do not cause blue screens on the system as other AV products do.

Microsoft Security Essentials, Free antivirus for windows and Malwarebytes Anti-Malware Free

   Information

• Do not start the free trial of MalwareBytes, unselect that option when prompted.
  
  
  
• Update and make full scans with both separately.

Scan your system with the following:

Kaspersky TDSSKiller - How to remove malware belonging to the family Rootkit.Win32.TDSS (aka Tidserv, TDSServ, Alureon)

ESET online scanner - One-time virus scanner free with ESET online scanner

Remove LogMeIn Hamachi software with Revo Uninstaller.

Code:

LogMeIn Hamachi Virtual network interface driver
hamachi.sys                 Thu Feb 19 16:36:41 2009

Revo Uninstaller
Download and install Revo Uninstaller free from here: Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Opt for "Advanced Mode" and uninstall the software (also delete the leftover registry entries).

Daemon Tools/Alcohol %

Code:

dtsoftbus01.sys             Fri Jan 13 19:45:46 2012

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although we have seen dtsoftbus01.sys blamed on several occasions). Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

As an alternative, many people recommend the use of Total Mounter or Magic ISO

Update your Logitech Camera Drivers to latest available:

Code:

LV302V64.SYS                Sat Jul 26 21:09:08 2008 (488B3E14)
LVUSBS64.sys                Sat Jul 26 21:06:36 2008 (488B3D7C)
lv302a64.sys                Sat Jul 26 21:06:31 2008 (488B3D77)
lvrs64.sys                  Sat Jul 26 21:09:02 2008 (488B3E0E)

Driver Reference Table - lv302a64.sys
Driver Reference Table - LVUSBS64.sys
Driver Reference Table - lvrs64.sys
Driver Reference Table - LV302V64.SYS

Also update your Razer Lycosa/Razer Tarantula Keyboard Drivers. But I would recommend using a different keyboard as their drivers are known cause of BSOD's.

Code:

Lycosa.sys                  Wed Sep  8 09:01:26 2010 (4C86FC86)

Driver Reference Table - Lycosa.sys

Please run these tests and report back the results

1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
2. Disk check for errors on the hard drive - How to Run Disk Check in Windows 7
3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

Check for a BIOS update for your motherboard:

Code:

BiosVersion = P01-B1
BiosReleaseDate = 03/23/2010
SystemManufacturer = Acer
SystemProductName = Aspire M5811

BSOD BUGCHECK SUMMARY

Code:

Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Wed Jun 12 20:11:33.876 2013 (UTC + 6:00)
System Uptime: 0 days 0:34:26.327
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Wed Jun 12 18:46:58.251 2013 (UTC + 6:00)
System Uptime: 0 days 0:03:11.702
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for Lycosa.sys
*** ERROR: Module load completed but symbols could not be loaded for Lycosa.sys
Probably caused by : Lycosa.sys ( Lycosa+1c23 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Wed Jun 12 16:36:01.630 2013 (UTC + 6:00)
System Uptime: 0 days 0:05:42.692
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for Lycosa.sys
*** ERROR: Module load completed but symbols could not be loaded for Lycosa.sys
Probably caused by : Lycosa.sys ( Lycosa+1c23 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  javaw.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Wed Jun 12 16:29:34.928 2013 (UTC + 6:00)
System Uptime: 0 days 1:03:08.380
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiIdleLoop+32 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Mon Jun 10 20:23:25.855 2013 (UTC + 6:00)
System Uptime: 0 days 0:31:08.916
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for Lycosa.sys
*** ERROR: Module load completed but symbols could not be loaded for Lycosa.sys
Probably caused by : Lycosa.sys ( Lycosa+1c23 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Mon Jun 10 18:52:22.010 2013 (UTC + 6:00)
System Uptime: 0 days 0:11:52.462
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for Lycosa.sys
*** ERROR: Module load completed but symbols could not be loaded for Lycosa.sys
Probably caused by : Lycosa.sys ( Lycosa+1c23 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Mon Jun 10 16:48:45.441 2013 (UTC + 6:00)
System Uptime: 0 days 0:28:02.503
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for Lycosa.sys
*** ERROR: Module load completed but symbols could not be loaded for Lycosa.sys
Probably caused by : Lycosa.sys ( Lycosa+1c23 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Mon Jun 10 15:19:14.460 2013 (UTC + 6:00)
System Uptime: 0 days 0:11:26.522
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for Lycosa.sys
*** ERROR: Module load completed but symbols could not be loaded for Lycosa.sys
Probably caused by : Lycosa.sys ( Lycosa+1c23 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

No need to hurry :) Take your time.
I'll be here for an update.

Hi, its been a while.
Any updates? Were your BSOD issues resolved?