1.    30 May 2016 #1
    Join Date : May 2016
    Posts : 3
    Windows 10

    BSOD after frequent bad stub errors


    I have just gotten my first BSOD after I thought I solved my issues (bad ram). It has occurred after frequent bad stub errors, leading me to believe they are linked. I have tried to solve bad stub errors using sfc/scannow, returning corrupt files that couldn't be fixed. I have run AVG scan and Malware-bytes scan to see if some malicious program had altered files both returned nothing. I have only recently started having bad stub errors that occur on windows applications and 3rd party applications. I don't think my SSD or HDD is failing as my OS install is on the SSD and everything else is on the HDD, and the errors have happened with programs installed on SSD and with ones installed on HDD, therefore not linking it specifically to my hard drive or SSD (as far as to my understanding of the issue). It would be greatly appreciated if someone could look at my dump file to help determine the cause of my BSOD and to what I think will be the cause of bad stub errors. My windows 10 installation was upgraded to from windows 7, and I have installed all updates pushed to me by Microsoft. Lastly if it helps at all I had just stopped playing a game, so the computer had swung from high load to almost no load.

    Attachment 82460

    edit to comply with bsod post rules, sorry was a bit hasty
      My ComputerSystem Spec
  2.    30 May 2016 #2
    Join Date : Apr 2014
    Space coast of Florida
    Posts : 5,382
    Windows 10 Pro X64 16299.19

    Looks liek AVG is causing the problem
    Code:
    ffffd000`219064c8  fffff801`d1063b5dUnable to load image avgldx64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for avgldx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgldx64.sys
     avgldx64+0x3b5d
    
    ffffd000`21905418  fffff801`d10d7d37Unable to load image avgidsdrivera.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for avgidsdrivera.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgidsdrivera.sys
     avgidsdrivera+0x27d37
    Please uninstall and run with the built-in Windows Defender for a while to test. If that resolves the problem stay with Defender (that's what I use) or try a different AV program.
      My ComputersSystem Spec
  3.    01 Jun 2016 #3
    Join Date : May 2016
    Posts : 3
    Windows 10
    Thread Starter

    Quote Originally Posted by Ztruker View Post
    Looks liek AVG is causing the problem
    Code:
    ffffd000`219064c8  fffff801`d1063b5dUnable to load image avgldx64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for avgldx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgldx64.sys
     avgldx64+0x3b5d
    
    ffffd000`21905418  fffff801`d10d7d37Unable to load image avgidsdrivera.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for avgidsdrivera.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgidsdrivera.sys
     avgidsdrivera+0x27d37
    Please uninstall and run with the built-in Windows Defender for a while to test. If that resolves the problem stay with Defender (that's what I use) or try a different AV program.
    Ok so I deleted AVG, and that seemed to solve the errors, but they came back and now I just got another blue screen. Again it would be really appropriated if someone could look at the report thingy. Attachment 82763
      My ComputerSystem Spec
  4.    01 Jun 2016 #4
    Join Date : Apr 2014
    Space coast of Florida
    Posts : 5,382
    Windows 10 Pro X64 16299.19

    The last dump says:

    Code:
    BugCheck 1A, {41792, fffff6800022fa00, 100000, 0}
    Probably caused by : memory_corruption ( ONE_BIT )
    Time to test your RAM. Download Memtest86+ (you want the 2nd one Download - Pre-Compiled Bootable ISO (.zip)). Unzip it then create a CD from the iso file using your CD burning software. There is a good freeware burner called ImgBurn which will do this easily.

    DO NOT burn the .iso file directly to CD. It must be used as input to a program that knows what to do with it, like the one I mentioned above.

    You can do this on any computer that has a working CD Burner.

    You can also use a Flash drive instead of a CD.

    Download - Auto-installer for USB Key (Win 9x/2k/xp/7) *NEW!*.
    Unzip and run Memtest86+ USB Installer.exe.
    It will format the flash drive if you tell it to. I used a small, 16MB flash drive and it had 8.5GB left when done.

    Boot the CD or Flash drive and run Memtest86+ for at least 3 complete passes unless it shows errors sooner than that. 10 passes is better, overnight is best.

    If that doesn't show any errors, then we need to run Driver Verifier to flush out the driver causing the problem.

    Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Warning:
    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier.
      My ComputersSystem Spec

 


Similar Threads
Thread Forum
Event ID 20 errors becoming more frequent
Hello. I have been using hwinfo to monitor my PC, and it is reading WHEA errors. Checking in the event system viewer, they are all event ID 20, and event ID 5. The PC is barely a month old, and was originally using windows 8.1, and never had...
BSOD Crashes and Debugging
Frequent BSOD
Hello guys. In the past few months my PC has been constantly having a BSOD, usually 2 times a week or so (more frequently in the last few days). Most of the times it happens right after booting the OS, with WHEA_UNCORRECTABLE_ERROR. One time I...
BSOD Crashes and Debugging
Frequent BSOD, please help
Hello, so recently I've been getting a BSOD stating "CRITICAL_STRUCTURE_CORRUPTION win32kfull.sys". It happens randomly but its quite often. It might happen 1-2 times per hour or 1-2 per day. I don't know what to do anymore, I did all kinds of...
BSOD Crashes and Debugging
Frequent BSOD - X64_IP_MISALIGNED
I am getting frequent BSOD's. Hardware tests have all come out clear. I am using all the latest drivers but have not been able to resolve the problem. Could you please take a look at the attached files and advise what I should do next. Many...
BSOD Crashes and Debugging
The stub received bad data, WHAT
Every time I open any programs, half the time it don't work, because of an obnoxious error that appears saying "The stub received bad data." How do you fix this thing?
General Support
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 09:05.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums