BSOD usualy when idling, error 0x0000001e


  1. Posts : 5
    Windows 7 64bit
       #1

    BSOD usualy when idling, error 0x0000001e


    Hi there, from some time my PC is acting strange. I get BSOD 0x0000001e when idling or just browsing and I'm not sure what causes the problem. I'd appreciate some help :)

    P.S.: I attach the dump file :)
      My Computer


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

    Hello crazybg.

    The BSOD is caused by AVG TDI Driver. It is blocking the network access, and that's the reason behind the BSOD.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000005, fffff8800dafa120, 0, 0}
    
    *** WARNING: Unable to verify timestamp for avgtdia.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgtdia.sys
    Probably caused by : avgtdia.sys ( avgtdia+755c )
    
    Followup: MachineOwner
    ---------
    Description here: Driver Reference Table - avgtdia.sys

    Uninstall AVG using AVG Remover. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
    Download, install and update those, and then run full system scans with both of them, one by one.

    The AVG is blocking the Realtek network driver, it's failing.
    Code:
    fffff880`0dafa3b8  fffff880`07419cf8Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Rt64win7.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
     Rt64win7+0x19cf8
    And the driver is very old.
    Code:
    fffff880`07400000 fffff880`07467000   Rt64win7 T (no symbols)           
        Loaded symbol image file: Rt64win7.sys
        Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
        Image name: Rt64win7.sys
        Timestamp:        Thu Jan 13 17:27:19 2011 (4D2EE89F)
        CheckSum:         0006BB92
        ImageSize:        00067000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Update it from Realtek

    Let us know the results.

    If you continue to get crash, next time post it following the Blue Screen of Death (BSOD) Posting Instructions.
      My Computer


  3. Posts : 5
    Windows 7 64bit
    Thread Starter
       #3

    Thank you for the fast reaction! Sorry that I didn't post following the instruction but the next time I will do it. I will update the realtek drivers now and see what will happen :)
      My Computer


  4. Posts : 5
    Windows 7 64bit
    Thread Starter
       #4

    And again I have a problem with BSOD. Again it was nothing more than browsing I was doing.

    P.S.: I opened the minidump and noticed something. Yesterday I got BSOD again and the cause was the same file ntkrnlmp.exe but the process was firefox.exe. Now the process is winamp.exe. What I noticed is that I got the BSOD when closing Firefox (yesterday) and closing Winamp (today)
      My Computer


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

    Seatools 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.

    You may want to enable Driver Verifier . Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
      My Computer


  6. Posts : 5
    Windows 7 64bit
    Thread Starter
       #6

    I ran the test + I ran CHKDSK and I found nothing wrong. When I enabled Driver Verifier and restarted I couldn't start Windows. In the booting screen of Windows it blinked with a blue screen but it was so fast I couldn't read it. After 2-3restarts it was all the same so I did startup repair. I opened the verifier from the command prompt and deleted the settings but it said no setting were deleted I restarted again and yet I wasn't able to boot Windows. In the end I just made a System Recovery...
      My Computer


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

    This states that there is/are some drivers causing issues.

    Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

    • Double click to open it.
    • Click this button only:
    • If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

    Free up the startup. Dont worry or dont hesitate while doing it. Windows 7 does not need anything other program to auto start. It will not loss any functionality, too. All your programs are installed, you may call them anytime from Start > all programs.

    1. Click on the Start button
    2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
    3. Select the “Startup” tab.
    4. Deselect all items other than the antivirus. If you want, you may keep opjectdock, too.
    5. Apply > OK
    6. Accept then restart.

    Then, if it still crashing, enable Driver Verifier again. Make it sure that you are not selecting any driver provided by "microsoft" or "unknown".

    Now with DV on, use the computer normally. Let it crash a couple of times. Upload the crash dumps for analysis.
      My Computer


  8. Posts : 5
    Windows 7 64bit
    Thread Starter
       #8

    I selected drivers which provider was unknown so I ran the Driver Verifier again without selecting them. So, I got BSOD before booting Windows again but at least this time I have a crash dump.

    P.S.: This is the last dump 032913-34850-01.dmp

    P.S. 2: Could it be a memory related problem? After some comparing between the dumps I noticed that there is something similar between them and it is that line:
    Code:
    The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    Last edited by crazybg; 30 Mar 2013 at 05:53.
      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 19:58.
Find Us