Brand new computer, occasional BSOD, can't find any pattern

Page 1 of 4 123 ... LastLast

  1. Posts : 18
    Windows 7 Professional x64
       #1

    Brand new computer, occasional BSOD, can't find any pattern


    Hi!

    So i have been having regular problems with my new computer running W7 Professional Sp1 64bit.

    I have checked the hard drive for errors, none found
    run memtest, 8 passes, no errors.
    tried sfc /scannow, no errors.
    Switched mouse, keyboard, monitor connection (from HDMI to VGA since i thought that might have caused all my previous blue screens)

    For internet i use an ethernetcable straight to the router
    All firmware and drivers are up to date and no errors are showing up in device manageer.

    It would be much appreciated if you could take a look at my dmp-files

    Theese are my specs:
    Gigabyte GA-Z77M-D3H - Intel i7 3770K - Intel HD Graphics 4000 - Samsung 830 256GB - Corsair Vengeance LP 16GB CL9 1600Mhz - Silverstone ST40NF (400W)

    If you need any additional info dont hesitate to ask

    Many Thanks in advance
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hello zap514, sorry to say, vut it is the failure of your antivirus program.
    Code:
    fffff880`03337928  fffff880`02c914d0Unable to load image \SystemRoot\system32\DRIVERS\eamonm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for eamonm.sys
    *** ERROR: Module load completed but symbols could not be loaded for eamonm.sys
     eamonm+0x44d0
    Description here: Driver Reference Table - eamonm.sys.

    I'd suggest to uninstall ESET.
    Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

    Download and install those, and then run full system scans with both of them, one by one.

    Also, Scan the system for possible virus infection.


    update the network driver.
    First, download the network card driver from manufactuer's website.
    Then reinstall the driver:

    1. Click the Start Button, type "devmgmt.msc" (without quotation marks) in the Start Menu Search box and press Enter.
    2. Double click to expand "Network adaptors".
    3. Right click your network card and click Uninstall.
    4. Check "Delete driver software for this device" check box, click OK.
    5. Restart the computer
    6. If windows does not auto configure the appropriate drivers at startup, install the downloaded one manually.

    And then, try to recover the error that is saying to be ntfs.sys.
    1. Update your SSD's Firmware (skip, if it is not a SSD)
    2. Re-seat the sata and power.
    3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
    4. Seatool for dos: SeaTools | Seagate download
      Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
      My Computer


  3. Posts : 18
    Windows 7 Professional x64
    Thread Starter
       #3

    I have followed your instructions and have not encountered any more blue screens. Thank you! :)
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    Nice to know :)
      My Computer


  5. Posts : 18
    Windows 7 Professional x64
    Thread Starter
       #5

    So it seems that the problem still persist. It was really weird actually, today when i turned on the computer, just after logging in a notification appears that Microsoft security essentials needs to be turned on, allthough I never turned it off (?).Then shortly after I received a new BSOD, similar to my previous blue screens, caused by ntoskrnl.exe, after that I got a couple of more blue screens. I have attached some new DPM files.
    I was hoping you could take a look at it.
    Thanks again in advance.
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 19, {3, fffffa8012820570, c000000000040, fffffa8012820f18}
    
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+cbb )
    
    Followup: Pool_corruption
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    BAD_POOL_HEADER (19)
    The pool is already corrupt at the time of the current request.
    This may or may not be due to the caller.
    The internal pool links must be walked to figure out a possible cause of
    the problem, and then special pool applied to the suspect tags or the driver
    verifier to a suspect driver.
    Arguments:
    Arg1: 0000000000000003, the pool freelist is corrupt.
    Arg2: fffffa8012820570, the pool entry being checked.
    Arg3: 000c000000000040, the read back flink freelist value (should be the same as 2).
    Arg4: fffffa8012820f18, the read back blink freelist value (should be the same as 2).
    
    Debugging Details:
    ------------------
    In such a situation, it is better to enable Driver Verifier to monitor the drivers.
    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

    Let us know the results, with the subsequent crash dumps, if any.
      My Computer


  7. Posts : 18
    Windows 7 Professional x64
    Thread Starter
       #7

    Okay so I have run verifier with all services except those signed by microsoft. then i get BSOD instantly at startup and have to use system restore to get the OS working again. The bluescreens said to be caused by ntoskrnl.exe and also a driver for my midi-keyboard. So i deleted it and ran verifier again and i still get regular blue screens, even after disabling verifier. The last two bluescreens were caused by:
    tunnel.sys (tunnel+0x2CD3)
    tunnel.sys (0xFFFFF880044C1CD3)

    I have attached the latest dumpfiles
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #8

    You need to uninstall Daemon tools. It is a very frequently BSOD causer.
    Code:
    *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
    *** WARNING: Unable to verify timestamp for dtsoftbus01.sys
    Try to search for any available updates for your Atheros NIC driver, in ATHEROS drivers for Microsoft Windows (Atheros?????).
      My Computer


  9. Posts : 212
    Windows 8 64-bit (6.2, Build 9200) (9200.win8_rtm.120725-1247)
       #9

    Arc said:
    You need to uninstall Daemon tools. It is a very frequently BSOD causer.
    Code:
    *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
    *** WARNING: Unable to verify timestamp for dtsoftbus01.sys
    Try to search for any available updates for your Atheros NIC driver, in ATHEROS drivers for Microsoft Windows (Atheros?????).
    To remove Daemon Tools, don't just uninstall it, run the STDP uninstaller as well, the Daemon Tools uninstaller won't remove the driver that causes bluescreens on it's own, so you have to use another uninstaller to remove it, here is a link for you.

    DuplexSecure - Downloads
      My Computer


  10. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #10

    tlarseth said:

    To remove Daemon Tools, don't just uninstall it, run the STDP uninstaller as well, the Daemon Tools uninstaller won't remove the driver that causes bluescreens on it's own, so you have to use another uninstaller to remove it, here is a link for you.

    DuplexSecure - Downloads
    You know mate, why I dont suggest it? I have noticed it many a times that after uninstalling Daemon tools when the persons not with ample experience of this standalone SPTD installer, they got SPTD reinstalled using it, and our aim of troubleshooting that is to make the system free from SPTD, is not attained.

    If you suggest it, always suggest to run the program, and then click the "uninstall" button only. If that is grayed out, exit the program, and dont touch any other buttons.
      My Computer


 
Page 1 of 4 123 ... LastLast

  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 05:53.
Find Us