Ransom BSOD's for no apparent reason/each one is different

Page 3 of 4 FirstFirst 1234 LastLast

  1. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #21

    Hi April, apologies this one slipped me by. Let's try some other stuff.

    Open an elevated command prompt, type in sfc /scannow and hit enter. Report back with the outcome.
      My Computer


  2. Posts : 34
    Windows 7 Home Premium 64bit OEM
    Thread Starter
       #22

    OMG TYVM <3!!! That was the 'First thing and most recent thing I did yet again'!! Have done it several times 'Hoping' I'd get lucky!! Hehe No such luck. After Spybot did 'Not' find anything I did the Malwarebytes install (After removing spybot of course) and it found 'several instances of 'Spigot'' *Sigh* (TYVM Kids taking advantage of Mom's puter while she was gone LMAO) At any rate, I have had numerous dumps since removal, all related now to the AR8121 etc etc Ethernet Controller along with the 'eg' (Bug? Virus?) that even shows in elevated command prompts. In fact it shows in ANY numerical figure anywhere on the computer period. Not sure, but I 'think' that it appeared after an install/uninstall of Logitech software/drivers which actually made my KB/Mouse lag more etc even after messing w/settings so went back to the default MS HID Compliant Mouse/KB. I truly appreciate your help and would not have 'Asked' for assistance if this had not been an issue for quite some time now (Feb) and being bedridden most of the time esp after chemo my PC is my 'Link' to the outside world and gaming w/our grandson we raise If there is 'Any' chance of saving or repairing it, I would be 'Forever' grateful!!!! TYVM Again! I have exhausted all knowledge I have and I am at a total loss now!
      My Computer


  3. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #23

    Yeah the first that show is the Atheros Ethernet controller driver which is pretty old. In fact every dump I've managed to look at is down to this driver with a 0xD1 error.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {fffff98017014e80, 2, 0, fffff88010d83a0c}
    
    *** WARNING: Unable to verify timestamp for L1E62x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
    Probably caused by : L1E62x64.sys ( L1E62x64+7a0c )
    
    Followup: MachineOwner
    ---------
    
    1: kd> lmvm L1E62x64
    start             end                 module name
    fffff880`10d7c000 fffff880`10d8e000   L1E62x64 T (no symbols)           
        Loaded symbol image file: L1E62x64.sys
        Image path: \SystemRoot\system32\DRIVERS\L1E62x64.sys
        Image name: L1E62x64.sys
        Timestamp:        Mon Mar 29 03:08:44 2010 (4BB00BAC)
        CheckSum:         00018E58
        ImageSize:        00012000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    I have to go out to work shortly but I'll look for a more suitable driver for you tonight when I get home. The one on the ASUS support page is actually dated earlier than that one, but I'm wondering if it may be more stable than the one you have installed. If you want to try it the link's below.


    Download

      My Computer


  4. Posts : 34
    Windows 7 Home Premium 64bit OEM
    Thread Starter
       #24

    TYVM!!! Ugh yeah I don't get it either. Had yet 'More' BSOD's last night and the last one was a tcpip.sys. When I ran disk cleanup awhile back, it wiped the 'Old' BSOD's that began in Feb, which at that point all were related to the O/S and not a single Ethernet one. That is new to the last couple months.

    Odd thing is this was the driver I had before *Shrug* and worked fine forever, so just not sure what's up. I have noticed that in the summer here every year I seem to have intermittent issues w/my PC connectivity 'and' my cable TV also tiling/etc and always have intermittent crashes in the summer. Cable guy comes out, messes around w/a few tweaks and it may/may not work better for a bit.
    Wondering if perhaps the 116 degree heat and the zillion electrical devices connected in my 'Room' (As I said, during chemo I'm bedridden for a few days, so my PC, Xbox, PS3, HDTV, Modem, Router etc etc are all in my room) combined with the cable wiring running on top of the house may be causing issues with everything and the problem is 'Not' the driver but brief intermittent connectivity loss causing my system to crash? Always has w/this Mobo, when I lose connectivity however brief the loss, there is a 50/50 chance it'll crash with a BSOD. Not sure, but it's a 'Thought'? Curious on your take on it!

    Esp since the Ethernet Controller issues have only occurred since we hit over 100 and noticed that the TV issues started at the same time. As for the driver, I had rolled back the driver originally, and then went back to the site for Atheros and d/l what I could find as the latest driver on there after my initial post, which is still pretty old. but the newest one I could find.

    I guess if worst comes to worst I could always try putting in a wireless card and seeing if the issue still occurs? Or perhaps even having the cable guys out again *Sigh* 50/50 chance there of things getting worse LMAO! Esp since they have been running new lines here the last month or so for our area. Speeds are already 199Mbps for 'My Connection', but they are upgrading lines for the DSL provider here Century Link. I guess my Last choice is wiping one of my 2TB drives of a previous stored image and backing everything up, since there are some VERY important court documents etc on here that I cannot lose which have been updated or added since the last image backup since I'm afraid one of these BSOD's and my HDD will finally *Poof* for good! TYVM again and sry about the book. Just trying to brainstorm what it could possibly be now, Ugh.
      My Computer


  5. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #25

    I can understand this is very annoying April and I sympathise, it's certainly a tricky one to work around. I don't know about the connectivity issues causing the BSOD, I've had intermittent connection issues with my ISP over the past few days and I just simply lose my net connection for a brief period before it kicks back in again. But I won't rule it out as I suppose it's possible.
    If it's hot there then try downloading and running Speccy which will show your temperatures, post a screenshot and we'll see if anything's looking abnormally high.

    So even with the driver I linked you still got BSODs?

    At least you've got a spare HDD to back up to, a clean install had crossed my mind as the problem may be rooted deeper than what the logs are showing (or what I'm getting from the logs). I'll ask a couple of bods to drop in and see if they can shed some light on what's going on and see if I've missed anything, and if you can post those temperatures in the meantime that would be great.
      My Computer


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

    Hi Apryldaun.

    Yes, I agree with boozad. The BSODs are caused by l1e62x64.sys which is Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller.
    Code:
    BugCheck D1, {fffff98017014e80, 2, 0, fffff88010d83a0c}
    
    *** WARNING: Unable to verify timestamp for L1E62x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
    Probably caused by : L1E62x64.sys ( L1E62x64+7a0c )
    
    Followup: MachineOwner
    ---------
    It is also the fact that the driver is old.
    Code:
        Image name: L1E62x64.sys
        Timestamp:        Mon Mar 29 07:38:44 2010 (4BB00BAC)
    There is another fact, which is not good. The driver available in https://www.qca.qualcomm.com/resources/driverdownloads/ is the same one that you have installed.
    Code:
    Signature   = "$Windows NT$"
    Class       = Net
    ClassGUID   = {4d36e972-e325-11ce-bfc1-08002be10318}
    Provider    = %ATHR%
    CatalogFile = L1E62x86.cat
    DriverVer   = 03/29/2010,1.0.0.22
    29th March, 2010.

    You may have a try, to uninstall and reinstall the network driver.

    Download the network driver from manufactuer's website: https://www.qca.qualcomm.com/resources/driverdownloads/.

    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. Windows will attempt to auto-configure an appropriate driver.

    If windows does not auto configure the appropriate drivers at startup, install the downloaded one manually. Run the setup.exe included in the zip.
      My Computer


  7. Posts : 34
    Windows 7 Home Premium 64bit OEM
    Thread Starter
       #27

    TYVM Guys! <3 I truly appreciate all the help!! Well, I rolled back and installed the 'Old' driver you linked Boozad, and not a BSOD yet, though I got TONS after I d/l the most current one. Ironic, that the oldest one the one on the ASUS site is actually appearing more stable so far! *Crossed Fingers* considering I was having several a day, the fact I haven't had any since earlier after I posted and immediately removed then d/l and installed the antique one (LOL) is a Good Sign!

    Let's hope this does it and we can 'Limp' it along until at least the A. Court Case is over or B. Even longer to keep some of my old programs that I'm relatively sure they will 'Not' allow me to get yet another license, after having gotten new ones when the Crappy tech messed up that simple PSU install and blew the 3 HDD's! If it occurs again I will definitely let you know ASAP LOL! As for the 'eg' bug Pffft I don't even care atm TBCH. It's not malware, not a virus (No scans detect it) just annoying (OCD OCD!) and more than likely a corruption of some type in the O/S that after several runs of SFC has nothing to do w/the integrity of the system files. Thanks again and keep your fingers crossed!! <3

    Oh and BTW first thing I did was ck core temps, GPU temps etc. All were at or well under since I have 5 fans on the sys along w/a gigantic wind tunnel CPU fan (LMAO can't remember atm but it's Zoltan or something like that been awhile now). No I was concerned that the wiring on the house is overheating and must be a bug on this particular MOBO or perhaps a setting in the BIOS but it will BSOD if I lose connection sometimes Gah. I really need to build a new one but $$ are a little low atm so have to limp it along as long as I can!
    Last edited by Apryldaun; 03 Jul 2014 at 00:59. Reason: Additional Info
      My Computer


  8. Posts : 34
    Windows 7 Home Premium 64bit OEM
    Thread Starter
       #28

    Update: Still no BSOD's since going back to the even older driver than my original one from the Atheros Ethernet Controller Driver from the above d/l! (Believe it's the same one from the ASUS P5QC d/l page) Still have fingers crossed! And eyes, and toes and... LMAO! Will ck in again later unless it crashes again! Once more, TYVM <3!! Never would have thought to go back to a 'Really Old' driver! LOL! But w/e works right? Although I do have to do an Ipconfig /release renew ever so often since it will lag badly at times, at least no BSOD's! Think I'll have hubby pick me up a new PCI-E NIC card and just disable the onboard one for now, since it's SO old until I can afford to build a new PC if it continues to show somewhat stable and no more BSOD's! Then FINALLY we can play our PC games again Hehe <3
    Last edited by Apryldaun; 03 Jul 2014 at 18:01. Reason: Additional Info
      My Computer


  9. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #29

    Glad to hear everything's ticking over nicely April, keep us updated.
      My Computer


  10. Posts : 34
    Windows 7 Home Premium 64bit OEM
    Thread Starter
       #30

    Well 'Boo' No pun intended Boozad LOL! Well now here we go w/the problem I started with 'Back' in Feb. When I try to play any games I got either the ntoskrnl.exe+75169 BSOD or other ntoskrnl.exe or most commonly ntoskrnl.exe 75bc0 over and over with random dxgkrnl.sys thrown in for 'Fun'! Now here is where it get's interesting! I was playing Borderlands 2 (Haven't played since Feb any of my PC games w/o a crash from 15min to an hour into them) and BAM again! Crashed w/the dxgkrnl.sys. Now the fun part! As I'm viewing the dump file in Blue Screen Viewer, the screen went black, said the NVIDIA driver failed and *Poof* again. Sigh. Just Ugh. LMAO! Just can't win I swear. Almost tempted to spend $$ I really don't have atm to try an 'Upgrade' in order to possibly repair the corrupt O/S without losing any files or programs. (The eg bug proves something is obviously 'Wrong' along w/problems w/creating new profiles and not a single person anywhere has any idea WTH the eg bit is or has ever even seen it!). What do you think? Do you think perhaps upgrading to Windows 7 64bit Ultimate will repair the O/S corruptions yet leave the programs, games and personal files for court in tact? I'm just at a loss here and grandson is getting 'antsy' that we can't play PC games any longer! Some of our 'Best' games are on PC!!! eg bug seems to be spreading too, if you notice the first attachment, the size on it is showing the 'eg' there now. *Sigh* So basically, do you think an upgrade would save my important files and programs and possibly fix the corrupted files?? I'm so 'Done' now and no one has any idea anywhere WTH that eg bit even is. And we are going back to square 1, where the problem first began with the initial BSOD's... Just at a loss now. TYVM again for all your help!! <3
      My Computer


 
Page 3 of 4 FirstFirst 1234 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 21:14.
Find Us