Random BSOD at increasing intervals, seems network related.

Page 1 of 2 12 LastLast

  1. Posts : 8
    Windows 7 Ultimate x64
       #1

    Random BSOD at increasing intervals, seems network related.


    I've been getting these BSODs for the past 3 months or so, and they're becoming more frequent. Used to be once every few weeks, now it's every few days.

    I've tried to troubleshoot it as much as possible on my own, without much luck.

    Almost all the BSODs seem to point at l1c60x64.sys, which is my network adapter driver. I've tried updating, uninstalling, reinstalling, and reverting back to the original drivers that came with the mobo. Problem persists.
    Current drivers are the original ones, since those are the last ones I tried.

    Seems it usually happens after I have uTorrent running for a while, could be half a day, could be 2-3 days. I'm pretty sure there were a few cases where it wasn't running, so it might just be related to heavy traffic, which uTorrent generates.

    I'm pretty sure my warranty is over, but I'm checking that with the shop right now. Trying my luck here to see if there's anything else that might point to it being a software issue after all.

    Those last few dumps (that mention an nVidia driver) are from today, I tried turning on Driver Verifier and kept crashing on boot. So I'm not sure if those have anything to do with this, or if that's just the Verifier overloading everything. Turned it off and decided it would be better to use it under proper guidance :)

    Thanks in advance,

    Guy
      My Computer


  2. Posts : 3,056
    Windows 10
       #2

    Hello and welcome to SF Guy :).

    As you pointed out the issue appears to be originating l1c60x64.sys, the issue I have with it
    is that it is a Vista driver and not a Windows 7 driver, you should be using L1C62x64.sys.
    Attachment 302358


    Once the file has downloaded right click and extract it using Winrar.


    Install the driver using the device manager.




    I can also see you're using a VPN solution, is that absolutely necessary?
    As for DV faulting on the nVidia drivers, the latest batch of drivers from nVidia are not recommended
    unless necessary, luckily for you, your card is not a part of the 7xx series of cards so you can
    roll back to a known stable release.


    Please follow this detailed quote and roll-back the driver to a known stable release.

    Arc said:
    Install the 314.22 WHQL only.


    • Uninstall All nvidia items in Control Panel > Programs and features
      • 3D Vision Control Driver
      • 3D Vision Driver
      • Graphics Driver
      • HD Audio Driver
      • PhysX
      • nvidia Update

      (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
    • Now follow Drivers - Clean Left over Files after Uninstalling
    • Boot normally now. Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

    Let us know the results.
      My Computer


  3. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Er, my bad, looks like the original drivers I installed yesterday from the CD were Vista ones. But all the BSODs before it were with Win7 drivers from the Gigabyte website, and pointed to L1C62x64.sys as you can see in the other dumps.

    I'll update back to the latest drivers, but other than showing that this is happening with vista drivers as well as win7 drivers, I don't think this had any impact.

    As for the VPN, I've used both TunnelBear and Hotspot Shield, but removed them. What leftovers are you seeing?

    And regarding the nVidia drivers - the ones you've linked to are almost a year old, are those really the latest stable ones?
      My Computer


  4. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #4

    Well, for the sake of further testings, I've reverted to the specified nVidia drivers.

    I'll upload an updated dump once the next BSOD comes up, but there should already be several of them in the batch I've uploaded, using various Win7 driver versions. Like any of the ones from December to early January.
    Last edited by totoguy; 20 Jan 2014 at 02:54.
      My Computer


  5. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #5

    And I just got another one.
      My Computer


  6. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #6

    And another one.

    I've also tried running a memtest86+ check, let it run for 9 passes, no errors. So we can probably rule out any RAM issues.
      My Computer


  7. Posts : 3,056
    Windows 10
       #7

    Hi Guy, sorry for my short absence.

    The last dumps do seem to be caused by the same L1C62x64.sys.
    Thank you for following the advice as to changing the nVidia driver :),
    now it shouldn't bugcheck on boot due to it and will possibly help us uncovering a software issue
    rather than a hardware one as it seems to be at the moment.
    Can you think about a software that might be causing this? anything just put it out there
    you don't know what might spark. Are you doing any kind of streaming of some sort?

    Arc said:
       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.

       Tip



    Please enable driver verifier following this TUTORIAL | But using the settings listed below:


    1. Go to Start and type in "verifier" (without the quotes) and press Enter
    2. Select "Create custom settings (for code developers)" and click "Next"
    3. Select "Select individual settings from a full list" and click "Next"
    4. Select everything EXCEPT FOR "Low Resource Simulation", "Force Pending I/O Requests", "IRP Logging" and click "Next"
    5. Select "Select driver names from a list" and click "Next"
    6. Then select all drivers NOT provided by Microsoft, Unknown, or Macrovision and click "Next"
    7. Select "Finish" on the next page.
      My Computer


  8. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #8

    While doing some testing on my own, I switched to the proper drivers that came with the mobo - 2.0.4.4.
    I did that right after the last BSOD. It's been 2 days now, and no BSOD, even when I tried to generate a lot of uTorrent traffic.

    I'll keep monitoring this, but so far this has been the longest I've went through without any BSODs while uTorrent was working. I will keep you updated in a few more days, or in case a BSOD does show up eventually.

    If these drivers end up "fixing" the issue, is this really a fix? Should I still be worried that other versions of the driver are causing issues?
      My Computer


  9. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #9

    As for software that might have been causing this, nothing comes to mind. I've removed the VPN stuff, and other than uTorrent, Firefox, and the Steam client, there was nothing else running that's network related. That I know of, at least.
      My Computer


  10. Posts : 3,056
    Windows 10
       #10

    totoguy said:
    While doing some testing on my own, I switched to the proper drivers that came with the mobo - 2.0.4.4.
    I did that right after the last BSOD. It's been 2 days now, and no BSOD, even when I tried to generate a lot of uTorrent traffic.

    I'll keep monitoring this, but so far this has been the longest I've went through without any BSODs while uTorrent was working. I will keep you updated in a few more days, or in case a BSOD does show up eventually.

    If these drivers end up "fixing" the issue, is this really a fix? Should I still be worried that other versions of the driver are causing issues?
    Good work :).
    I don't intend to be a party pooper, just thorough, please check the minidump folder for any new
    dumps that you might have missed.

    Code:
    C:\Windows\minidump
    If new dump files are present in that folder copy them to the Desktop,
    zip and upload in your next post.

    Well this is kind of a tricky question if the older driver do eventually prove to be the solution
    then I would consider it a fix, although if this is a hardware issue it may popup for no
    apparent reason after a long while that it was seemingly OK,it may even be a specific temperature
    the chip isn't happy operating under, or it has be heat-stroked in the past and now is running off spec'
    in an unpredictable fashion.
      My Computer


 
Page 1 of 2 12 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 08:44.
Find Us