Annoying BSOD

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 7 RTM
       #1

    Annoying BSOD


    I'm getting this BSOD a few times a week ever since I installed the RTM version of windows 7 x86 about a month ago:

    A clock interrupt was not received on a
    secondary processor
    STOP 0x00000101

    When windows boots back up, it states:

    Windows has recovered from an unexpected error
    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.48
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 101
    BCP1: 00000060
    BCP2: 00000000
    BCP3: 807C0120
    BCP4: 00000001
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\093009-24640-01.dmp
    C:\Users\Big\AppData\Local\Temp\WER-33984-0.sysdata.xml

    So I have no idea what the issue is. I had Windows 7 beta installed for the last few months and never once had this issue. I replaced my PSU thinking that might have been the issue but that didnt work. I think this error only seems to happen when the internet is in use, so I thought it might be a network driver issue, but I even tried updating them but it didnt seem to change anything. Any ideas on what the issue might be?

    Things I've Tried:
    - Installing Dual Core Optimizer again
    - Update Network Drivers (I have a built-in ethernet and a pci-card logitech)
    - Ran Memory Tests
    - Ran Scannow Tests in cmd line (nothing found)
    - Updated GFX Driver
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    Sean

    You running wired. correct? what anti virus are you running?
      My Computer


  3. Posts : 11,408
    ME/XP/Vista/Win7
       #3

    Hi seaned

    May be over heated CPU, clean out heat sink of dust.
      My Computer


  4. Posts : 7
    Windows 7 RTM
    Thread Starter
       #4

    Thanks for the replys guys,

    You running wired. correct? what anti virus are you running?
    Yeah, I'm running Avast! on it, and if I remember correctly when I had the Beta installed a few months ago I was using AVG instead. I have W7 installed on my laptop also with Avast! but no BSOD ... obviously it's not in use it as often, so that might be key.

    May be over heated CPU, clean out heat sink of dust.
    When I installed my PSU lastweek I did a bit of a clean-up in my tower to blow out dust, but I didnt take off the heatsink. My question to this solution would be why does the BSOD happen now and not when I was using the beta version of 7 or on XP?
      My Computer


  5. Posts : 845
    Windows 7 - Vista
       #5

    Hi -

    The bugcheck = 0x101 = Clock Watchdog Timeout = a CPU did not respond & timed out, probable cause = "unknown module"

    > 90% of 0x101 are CPU or other hardware like mobo.

    Apologies for bluntness -- Did you actually install a 9 year old Linksys LNE100TX Ethernet driver into Windows 7 ?

    From the dumps -- a Windows 2000-era Ethernet driver -
    Code:
    lne100v4.sys Wed May 03 23:07:50 2000 (391113B6)

    I suggest you start by updating that driver, if it is at all possible.

    Regards. . .

    jcgriff2

    .
      My Computer


  6. Posts : 7
    Windows 7 RTM
    Thread Starter
       #6

    I suggest you start by updating that driver, if it is at all possible.

    Regards. . .

    jcgriff2

    .
    Strangley enough yeah I have kept it in my system, but Windows 7 found the correct driver and installed it during the OS installation. I found the driver again on the Linksys website but obviously there is no Windows 7 support for that old of a driver. I figured it had something to do with a network driver but I'm still suiprised why the Windows 7 Beta OS never had issues with it? So does it seem that is what the culprit is?
      My Computer


  7. Posts : 845
    Windows 7 - Vista
       #7

    Hi -

    I looked at the other dumps that I had not seen yesterday and found 2 dumps that named the Windows 2000-era driver as the probable cause. The bugchecks of the two -

    0xa = invalid memory referenced

    0xd1 = improper access of paged memory


    For these 2 dumps, the stack text shows the driver lne100v4.sys -
    Code:
    ChildEBP RetAddr  
    807dcb64 88a6b38e nt!KiTrap0E+0x2cf
    807dcbe4 8ec0194d ndis!NdisMCompleteBufferPhysicalMapping+0x27
    WARNING: Stack unwind information not available. Following frames may be wrong.
    807dcc2c 88a6d18d lne100v4+0x194d
    807dcc58 88a3d54c ndis!ndisMDpc+0x173
    807dcc78 828783b5 ndis!ndis5InterruptDpc+0x99
    807dccd4 82878218 nt!KiExecuteAllDpcs+0xf9
    807dcd20 82878038 nt!KiRetireDpcList+0xd5
    807dcd24 00000000 nt!KiIdleLoop+0x38
    I do believe the driver is involved in the BSODs, but is not necessarily completely to blame. Several other dumps indicate the presence of OS corruption - that may be hardware failure or software. If it was just the driver alone, I would expect the same bugcheck each time (or similar ones).

    It is the Asian characters in the screenshot below that I am concerned
    The following is a screenshot from a 0x101 dump file and contains what appear to be Asian characters. Cut/paste caused the charachters to change to ???????, hence the reason for the screenshot -


    Attachment 30047



    The above are supposed to be the names of drivers.

    I would advise ditching that driver and see how things go, although I believe that you will probably run into trouble. You really should re-install Windows 7. Since you are running RTM, go to TechNet or MSDN and refresh the install copy. It may have been corrupted during the download process.

    Finally, to try and answer some of your questions and to leave you with additional ones -

    Windows 7, like Vista, employs a legacy driver to connect to the Internet during installation. What surprises me is that Windows 7 permitted the installation of the 9 year old Ethernet driver. Was there no indication in the Device manager?

    Regardless of how the driver got into the Windows 7 system, the fact is the driver was loaded into RAM at the time of the BSODs. I honestly don't understand how you ran Windows 7 Beta for months with that driver and no crashes. 4 & 6 month old NIC drivers are causing BSODs -- this past week. I am surprised that you were not here earlier seeking BSOD help.

    Please... seriously consider re-installing Windows 7 RTM.

    Regards. . .

    jcgriff2

    .
    Last edited by jcgriff2; 01 Oct 2009 at 05:30. Reason: add attachment
      My Computer


  8. Posts : 7
    Windows 7 RTM
    Thread Starter
       #8

    Thanks for the reply jcgriff2,

    I'll try removing all-together the Linksys card to see if that helps. The download from MSDN and the installation went fine for me, but I suppose a re-installation wouldn't be out of the question in the BSOD pops up again. I'm just going to try to disable the device, uninstall the driver, then remove the device from the computer. Do you think that's adequate enough, or is there more to it to make sure there isn't any old driver files left or that Windows doesn't reinstall it right away?
      My Computer


  9. Posts : 845
    Windows 7 - Vista
       #9

    I think your thoughts on this are just fine. You know your hardware, so removing the offending device (or replacing it) would be prudent. All the other drivers that I saw in the dumps had recent timestamps on them, so I don't believe other devices will cause BSODs for you.

    It is the varying bugchecks that concern me the most. But I have seen where a rogue driver such as the Win 2000-era one can cause memory corruption similar to that found in your system., the Asian characters notwithstanding. The other driver(s) with no name just letters & numbers is usually what I see.

    You should also test RAM at some point as well as running a chkdsk /r on the hard drive as it sounds like the system has a few miles on it. But you did move in the right direction with Windows 7 vs. Vista on that particular system, I think.

    I find that running a DirectX Kernel diagnostics report provides the quickest and overall comprehensive method to look for outdated drivers. Run dxdiag then save it as a text file and just look through the report for .sys files. Then look at the dates on it. If you care to post it (attach to post), I'll be glad to take a look at it for you.

    START | dxdiag | bottom-center of screen ".. save all information.." save as text file

    Regards. . .

    jcgriff2

    .
      My Computer


  10. Posts : 7
    Windows 7 RTM
    Thread Starter
       #10

    Thanks jcgriff2, here's the dxdiag file:
      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 05:44.
Find Us