Multiple BSOD's while booting into windows and also while working.


  1. Posts : 6
    Windows 7 Ultimate X64
       #1

    Multiple BSOD's while booting into windows and also while working.


    Hello,

    I am having issues with this newly build PC. I have a Biostar motherboard, AMD 455 processor, and GSkill 2X4=8GB Memory. The system BSOD's randomly at startup or while working. The error codes are different most of the times. I have compiled the debugging files as per directions and they are attached to this message. Please help...
    Thank you.

    Note: This PC is using the university's internet connection through LAN. I also have some network drives configured to it.
      My Computer


  2. Posts : 6
    Windows 7 Ultimate X64
    Thread Starter
       #2

    Some BSOD Codes I have encountered: STOP: 0X00000019, 0X0000001A, 0X0000001E
      My Computer


  3. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #3

    Problem Devices:
    Code:
    Cisco AnyConnect VPN Virtual Miniport Adapter for Windows x64	ROOT\NET\0000	This device is disabled.
    Is the above device disabled intentionally? If so, why?

    I would recommend enabling it, updating any drivers for it, and then disabling it. That will ensure it does not cause conflicts even disabled.


    Problematic Software:
    Code:
    Start Menu\Programs\Accessories\MSI Afterburner	ITORG\phhp.tomitalab:Start Menu\Programs\Accessories\MSI Afterburner	ITORG\phhp.tomitalab
    The above software has known problems with Windows 7. I would recommend removing it.


    Code:
    SYMEVENT64x86.SYS Thu Apr 15 19:32:19 2010 (4BC7BE23)
    SRTSP64.SYS Fri Mar 4 13:39:16 2011 (4D714DF4)
    SYMEVENT64x86.SYS
    SRTSP64.SYS

    Your Symantec software is out of date by a year or more. Please update to the 2012 version or remove it and replace it with Microsoft Security Essentials - Free Antivirus for Windows. Whether you remove it or update it, I would recommend contacting Symantec and getting help removing/updating the software so remnants of the old software do not remain to cause conflicts with the system.

    I suspect the out of date Symantec software is what is causing your crashes...
      My Computer


  4. Posts : 6
    Windows 7 Ultimate X64
    Thread Starter
       #4

    Hello Writhziden,

    I will make the suggested changes and will revert back with feedback after a few days. Thank you for the troubleshooting.

    Sumi
      My Computer


  5. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #5

    You're welcome. Look forward to hearing back when you have had a chance to do the steps and test whether the system is stable or not. When I say test, I mean doing your normal routine for long enough that you feel comfortable the system is working as it should.

    Best of luck!
      My Computer


  6. Posts : 6
    Windows 7 Ultimate X64
    Thread Starter
       #6

    Hello writhziden,

    Yesterday I tried to log in the problematic computer in my office, and somehow after several attempts I got into windows and tried to make a CBS.log file along with the other debugging files as usual. However, I could only get the CBS.log file before the computer BSOD'ed on me again. I was in the middle of a long explanatory post, but lost it all. I am attaching the CBS.log file from my mediafire account because of the file size limitation on this forum File Link. I also want to list the STOP codes and other messages I received while BSOD's. The following codes were encountered on different attempts to boot into windows, and several times while working in the windows:

    STOP: 0X00000019, 1A, 1E, 6B, 7E, 50.
    On several other occasions I received unusual STOP codes such as :
    1. "STOP: C0000139 {Entry Point Not Found} The procedure entry point NtOpenFile could not be located in the dynamic link Library ntdll.dll."
    2. "Stop: C000021a {Fatal System Error} The initial session precess or system process terminated unexpectedly with a status of 0X00000000 (0Xc0000428 0X00100560). The system has been shutdown."

    I also found that my disk failed chkdsk and sfc scannow commands. In the end of the command prompt I could see that there were correuption in file system. I think the attached log file may reflect on which files are corrupt. One time I could boot up but then I got all sorts of error such as: "C:\Windows\System32\RpcRtRemote.dll is not designed to run on windows or it contains an error" and eventually system BSOD'ed.

    Now, my office tech dept. wants to clone the existing drive so that they don"t have to install a new OS after we get a new drive replacement. But is it a good idea, thinking that the existing drive is BSOD'ing all the time. Would a clone of this drive make a new replacement drive susceptible to BSOD as well? Please advise.

    Thank you.

    Sumi
      My Computer


  7. Posts : 6
    Windows 7 Ultimate X64
    Thread Starter
       #7

    I just got home from office, and my department's tech support guy worked on the machine to find out any problems. He said that the Cisco VPN agent is always disabled intentionally unless used to connected, and he also said that all the other machines in the organization (426) are using the same thing. Also, he said that the Symantec is an enterprise edition thing, and is forced to my computer by a server, so it is what it is.
    After he troubleshot for almost 2 hours, and tried cloning the drive to test if a replacement worked, he concluded that the replacement drive is also BSOD'ing. Then we thought it must be something else. In the end he took out the network cable, and rebooted and then it worked without BSOD. I have come home for the weekend, but the machine is still running on one stick of RAM (I had 2 GSkill sticks installed 4 GB each) and without network cable. We hope that when we go back on Monday it is still running. Please advise.

    Sumi
      My Computer


  8. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #8

    Understand the VPN/Symantec comments.

    The crashes you listed indicate RAM as the likely suspect. It could also still be hard disk related (possibly a virus?) problem that cloned corruption onto the new drive, and I would advise a clean install on the new drive to test further. I strongly suspect a bad piece of hardware or a badly corrupted Windows install given the variety of BugCheck codes. Let us know how things are going when you check again on Monday.
      My Computer


  9. Posts : 6
    Windows 7 Ultimate X64
    Thread Starter
       #9

    Hello Writhziden,

    I went out of town for a few days, so could not follow up. Finally, the culprit was a faulty RAM. I had two sticks installed and one of them was faulty. Now after removing it everything is back to normal.
    Thank you for your suggestion... Rep up!!

    Sumi
      My Computer


  10. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #10

    You're welcome. Glad to see it solved!!
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 16:12.
Find Us