locked
Windows 7 x64 Blue Screen Local ID: 4105 RRS feed

  • Question

  • Hello, 

    I have noticed my laptop has blue screened a couple of times right after start up. 

    I already ran the memory diagnostics test.

    Does anyone know about this problem and how I can fix it?

    I get the following error code:

    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7601.2.1.0.768.3
      Locale ID: 4105

    Additional information about the problem:
      BCCode: a
      BCP1: 0000000000000000
      BCP2: 0000000000000002
      BCP3: 0000000000000001
      BCP4: FFFFF800030D6C3F
      OS Version: 6_1_7601
      Service Pack: 1_0
      Product: 768_1

    Files that help describe the problem:
      C:\Windows\Minidump\021314-35927-01.dmp
      C:\Users\user\AppData\Local\Temp\WER-131165-0.sysdata.xml

    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt

    Monday, February 17, 2014 6:52 PM

Answers

  • DP

    Only 2 of the four are recent and they are related to netio.sys.   More often than not the underlying cuase of netio.sys failing is the installed malware application in your case Symantec.   I would remove it and replace with MSE

    Symantec  is a frequent cause of BSOD's.  
    
    I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST
    http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN
    
    http://www.microsoft.com/security_essentials/
    
    
    For Norton 360 use this http://symantec.pcperformancetools.com/norton-360-how-to-uninstall.html
    
    

    If you continue to crash I would run driver verifier to find the underlying cause.

    These crashes were related to memory corruption (probably caused by a driver). 

    Please run this test to find which driver is causing the problem.  

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.


    Driver verifier (for complete directions see our wiki here)
    Co-Authored by  JMH3143


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Monday, February 24, 2014 12:40 PM
    Tuesday, February 18, 2014 7:53 PM

All replies

  • We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  
    We prefer at least 2 DMP files to spot trends and confirm the cause.

    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask

    Wanikiya and Dyami--Team Zigzag

    Monday, February 17, 2014 7:42 PM
  • Here is the link to the files:

    https://skydrive.live.com/redir?resid=31A515A4D887B0B9!209&authkey=!AMAY5NwlE64c9Gs&ithint=file%2c.rar

    Please keep me updated.

    Thanks

    Tuesday, February 18, 2014 6:59 PM
  • DP

    Only 2 of the four are recent and they are related to netio.sys.   More often than not the underlying cuase of netio.sys failing is the installed malware application in your case Symantec.   I would remove it and replace with MSE

    Symantec  is a frequent cause of BSOD's.  
    
    I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST
    http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN
    
    http://www.microsoft.com/security_essentials/
    
    
    For Norton 360 use this http://symantec.pcperformancetools.com/norton-360-how-to-uninstall.html
    
    

    If you continue to crash I would run driver verifier to find the underlying cause.

    These crashes were related to memory corruption (probably caused by a driver). 

    Please run this test to find which driver is causing the problem.  

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.


    Driver verifier (for complete directions see our wiki here)
    Co-Authored by  JMH3143


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Monday, February 24, 2014 12:40 PM
    Tuesday, February 18, 2014 7:53 PM
  • Ok thanks, will give it a try and let you know
    Wednesday, February 19, 2014 3:21 PM