BSOD running Plex Media Server, now NIC not working and locking up

Page 4 of 6 FirstFirst ... 23456 LastLast

  1. Posts : 127
    Windows 7 Ultimate x64
    Thread Starter
       #31

    bobafetthotmail said:
    Just in case it wasn't clear, clearing CMOS =/ reflashing bios. The latter means doing a BIOS update to the latest version, as it erases the BIOS and creates it again hereby fixing a corrupted BIOS, while clearing CMOS just resets settings to factory default. It is risky, or not depending on what features has that board (double BIOS chips, additional stuff that allows you to reflash it agan from USB at boot, whatever)
    No worries, I know that. I can see my reply was a bit unclear when I referred to flashing the BIOS again. What I meant is that I upgraded it to the latest version fairly recently, perhaps 1-2 months ago.

    I had hoped we'd gotten the system stable now but unfortunately I just had another BSOD. It's a weird one as I'm 95% sure I decided to shut it down for the evening several hours ago but then I noticed that the lights were on and so switched on the monitor and there was a BSOD referring to teamviewervpn.sys. I can only think that it must have woken in response to a WOL signal from one of my other machines perhaps, although I guess it's possible it happened when I shutdown and I just didn't notice it hadn't completed successfully.

    I haven't done the disc scan yet. I'll do that tomorrow as I don't want to leave the machine on overnight unattended.

    Anyway, perhaps Arc can cast his expert eye over the dump for me. I've posted what Windows showed when I rebooted below:

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.1
    Locale ID: 2057

    Additional information about the problem:
    BCCode: d1
    BCP1: FFFFF9800573AD20
    BCP2: 0000000000000002
    BCP3: 0000000000000000
    BCP4: FFFFF88004292DB5
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\071613-15147-01.dmp
    d:\wintemp\user\WER-21340-0.sysdata.xml

    EDIT: I checked the SYSTEM log and I did indeed shutdown at 21:48 and the next restart was at 01:46, although I guess if it did restart and BSOD before loading Windows that might not show in the log.

    I'm also wondering if perhaps this latest BSOD might be connected to my disabling Offline Files, SuperFetch and VSCS earlier. I'll probably need VSCS anyway as I think EaseUS ToDo Backup might need it, for doing System backups if not Data backups.
      My Computer


  2. Posts : 127
    Windows 7 Ultimate x64
    Thread Starter
       #32

    I've done a disk check on both the SATA and IDE HDDs now and they were fine.

    The boot delay turned out to be due to a dodgy SATA cable on the ODD. I replaced it and it doesn't delay at that screen anymore.

    I had another problem when I reconnected my IDE HDD and plugged my PCI tuner card in. When I booted, the keyboard was not functional at POST and when it automatically went to boot Windows it BSOD the first time and the second time said somthing about not having an ACPI compatible BIOS. I disconnected the IDE cable from the board and then it worked normally again, so I shutdown and replaced the IDE cable and now it seems to be OK, so it seems I might have had two dodgy cables, although it seems strange that would have caused these BSOD at boot as I'm not booting from the IDE HDD (add I had done a disk check in Windows with the IDE HDD and the old cable and that worked fine).

    Regarding the latency issues, the author of LatencyMon has told me

    "Your system appears to be OK. Regarding excessive hard disk usage and spikes under load, I suggest you make sure that your harddisks have enough free space and are not fragmented. You can use the standard Windows defragmentation tool for that. If fragmentation on your system is low and not a problem then I suggest considering if excessive paging might be the problem (take a look at your memory load, kill of processes that consume a lot of memory, etc.)"

    My HDDs are defragged and have plenty of space, so that's not an issue. I also told him that I see tons of hard pagefaults from svchost.exe when analysing the disk with Windows defrag but no latency spikes and he replied

    "Whether they are connected depends on the priority of the process that incurs the page fault. Defrag runs at lower or idle priority. In principle, only a real-time priority process/thread can compete and thus influence the interrupt to process latency measurements."

    Which makes sense, although it doesn't get me any nearer to understanding why I'm getting latency spikes with MediaPortal, where it does matter as that's for playing media and having spikes during that could cause audio/video glitches. I guess I should ask on the MediaPortal forums if anyone knows anything about that.
      My Computer


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

    The latest BSOD as you posted is caused by teamviewervpn.sys, TeamViewer VPN Adapter driver.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {fffff9800573ad20, 2, 0, fffff88004292db5}
    
    *** WARNING: Unable to verify timestamp for teamviewervpn.sys
    *** ERROR: Module load completed but symbols could not be loaded for teamviewervpn.sys
    Probably caused by : teamviewervpn.sys ( teamviewervpn+2db5 )
    
    Followup: MachineOwner
    ---------
    And the driver date is historically old.
    Code:
    fffff880`04290000 fffff880`0429d000   teamviewervpn T (no symbols)           
        Loaded symbol image file: teamviewervpn.sys
        Image path: \SystemRoot\system32\DRIVERS\teamviewervpn.sys
        Image name: teamviewervpn.sys
        Timestamp:        Thu Dec 13 14:52:09 2007 (4760F9C1)
        CheckSum:         00017C81
        ImageSize:        0000D000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    How do I update TeamViewer?
      My Computer


  4. Posts : 127
    Windows 7 Ultimate x64
    Thread Starter
       #34

    Thanks Arc. Is there any clue in there as to what the PC was doing at the time (i.e. waking in response to a WOL signal)?

    I checked and there's an update from 8.0.19045 to 8.0.19617 so I've done that and now the driver File Version is v9.0.0.3 dated 06/06/2013, Product Version 2.1_rc4 9/3 (the digital signature timestamp is still 17/12/2007 though), which is quite a jump for a minor update and hopefully will prevent it happening again.
      My Computer


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

    I am not very sure about either of your questions, but what I can say that the remote control mechanism sometimes cause BSODs.
      My Computer


  6. Posts : 127
    Windows 7 Ultimate x64
    Thread Starter
       #36

    Arc said:
    I am not very sure about either of your questions, but what I can say that the remote control mechanism sometimes cause BSODs.
    OK, thanks.
      My Computer


  7. Posts : 1,711
    Win 7 Pro 64-bit 7601
       #37

    doveman007 said:
    Which makes sense, although it doesn't get me any nearer to understanding why I'm getting latency spikes with MediaPortal, where it does matter as that's for playing media and having spikes during that could cause audio/video glitches. I guess I should ask on the MediaPortal forums if anyone knows anything about that.
    Emphasis on "could". Do you experience such glitches or distorted audio? On some systems it's normal, or at least not severe enough to cause visible effects.

    I've disabled Offline Files, SuperFetch and VSCS. I don't have any of the others.
    If the issue is still there you can enable them again.

    What I meant is that I upgraded it to the latest version fairly recently, perhaps 1-2 months ago.
    I assume the latency problem was already present. If not, reverting to an older BIOS (just check the CPU compatibility first, if you revert to a too old BIOS it will stop recognizing the CPU) could solve it.

    The way I see this, with all the jumpiness of the BIOS and machine starting on its own, and NIC hating IDE, there is a hardware issue somewhere, a buggy BIOS, damaged mobo, a malfunctioning PSU (yes, bad PSUs can power up the system out of the blue like that, some were even kick-started, that is you give a kick and the PSU powers up).

    Btw, what are the voltages from the PSU? Check in BIOS after a while it has been on (restart) and from HWMonitor while running (note that the BIOS is likely the only one that is 100% right, the other can be off by some 20%).
    Try to disconnect power from secondary stuff (the CD player or a secondary HDD, addon cards you can do without) to see if the voltages change (increase) and latency decreases.
    Trying with another PSU would be cool, but I understand that it's a bit annoying.
      My Computer


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

    bobafetthotmail said:
    Emphasis on "could". Do you experience such glitches or distorted audio? On some systems it's normal, or at least not severe enough to cause visible effects.
    I'm probably more obsessed with this at the moment than I should be, because this is a system I'm building for my brother and once I've sent it to him, it's going to be next to impossible to check things like latency over the Net using TeamViewer. In some ways, it's perhaps easier to check for and eliminate latency issues (in theory anyway!) than to test every possible scenario to see if there's any audio/video glitches and if I've ensured there are no latency issues and my brother reports that he's experiencing glitches, at least I'll know it's not that and can look at settings/codecs, etc.

    I'm not sure at the moment whether LatencyMon is just showing phantom readings though. If not, it would seem to suggest that DPC Latency Checker is pretty useless as it's not showing any of the latency spikes that LatencyMon is, so anyone just using that would think there is no latency problem and any issues they're having must be due to something else. On the other hand, if LatencyMon is only meant to be used with nothing else running, as the author initially suggested, then it's not much use for establishing whether any programs/activity are triggering latency spikes and DPC Latency Checker is probably more useful if there's no such restrictions with it.

    If the issue is still there you can enable them again.
    OK, I've re-enabled SuperFetch and VSCS. I don't think I have any use for Offline Files, so I might as well leave that disabled.

    I assume the latency problem was already present. If not, reverting to an older BIOS (just check the CPU compatibility first, if you revert to a too old BIOS it will stop recognizing the CPU) could solve it.

    The way I see this, with all the jumpiness of the BIOS and machine starting on its own, and NIC hating IDE, there is a hardware issue somewhere, a buggy BIOS, damaged mobo, a malfunctioning PSU (yes, bad PSUs can power up the system out of the blue like that, some were even kick-started, that is you give a kick and the PSU powers up).

    Btw, what are the voltages from the PSU? Check in BIOS after a while it has been on (restart) and from HWMonitor while running (note that the BIOS is likely the only one that is 100% right, the other can be off by some 20%).
    Try to disconnect power from secondary stuff (the CD player or a secondary HDD, addon cards you can do without) to see if the voltages change (increase) and latency decreases.
    Trying with another PSU would be cool, but I understand that it's a bit annoying.
    I think I flashed the latest BIOS before installing Windows, so I never looked at the latency with a previous version. I'll certainly try re-flashing the latest version, just in case something's got messed up and if I still have the same problems, try an earlier version. I've only got an Athlon II X4 630 in there, so it's unlikely the previous BIOS won't be compatible (I'll check first of course though).

    Most of the time I've been running with only a single SATA HDD and had the latency issues still but I'll check the voltages as you suggest. Currently I've also got a SATA ODD and IDE HDD connected. I decided to remove the IDE ODD, mainly to tidy up the cabling and arrangement and because it's cheap enough for my brother to buy himself another SATA ODD if he wants. I've disabled the SATA3 for now as I'm not using it and it speeds up POST by eliminating the first screen and I figured I might as well disable anything I'm not using to see if it helps make the system more stable. If necessary, I'd be prepared to remove the IDE HDD and try and find a cheap SATA HDD (the IDE one is only 80GB, so I don't need anything special) but the BIOS doesn't actually allow me to disable the IDE controller (although I could of course disable it in Device Manager).

    The PSU is a Seasonic G-360, which is supposedly a very good one using high quality components, so it should be fine but of course, even the best models have faulty units slip through the net. Unfortunately I don't really have a spare I can use (if the system was totally non-functional, I'd probably take the Antec CP-850 from my main system and test with that but I couldn't do that for any length of time to check stability as I need to use my main system).

    I did wonder if the dodgy IDE cable could have been shorting some of the lines on the IDE connector and if this did share a PCI bus with the NIC, whether that could have been causing it to stop working temporarily but then I remembered that it happened with just the CF->IDE adapter plugged in, so it can't have been that.

    However weird and redundant the "SATA IDE Combined Mode" BIOS option (which is now disabled) is, it seems unlikely that would cause the NIC to stop working, as it's obviously intended to be used by users and it seems unlikely the manufacturers would put in an option that breaks the NIC. Perhaps the "Aggressive Link State Power Management" option (also now disabled), was triggering the problem when an IDE device was connected though. Perhaps it's possible that Networx was somehow the final straw but I'll just have to see if it reoccurs. If so, it may well be there's a microfracture in the board being triggered by plugging in stuff to the IDE connector but it seems unlikely that this would then be corrected by unplugging it again.

    If it does happen again, I'll double-check with the Dr Lan cable test in the BIOS, to see if it's just happening in Windows (should have done that before but I only discovered this test recently).
      My Computer

  9.    #39

    Why do you need TeamViewer VPN. I'd uninstall the program and all remnants of that VPN and then reinstall the latest version.

    Where did you get Ultimate and how is it activated? Please post back the output from http://go.microsoft.com/fwlink/?linkid=52012
      My Computer


  10. Posts : 127
    Windows 7 Ultimate x64
    Thread Starter
       #40

    gregrocker said:
    Why do you need TeamViewer VPN. I'd uninstall the program and all remnants of that VPN and then reinstall the latest version.

    Where did you get Ultimate and how is it activated? Please post back the output from http://go.microsoft.com/fwlink/?linkid=52012
    Sorry for the delay in replying. I needed to borrow the power lead from the PC to work on my brother's Raspberry Pi (which I'm also having problems with but that's another story) and frankly have been a bit reluctant to turn on the PC for fear of running into more problems but I guess I can't keep putting it off!

    I'm not sure I do need the VPN component on this particular PC but nonetheless, it shouldn't be causing BSOD and works fine on other PCs (as does the other software that was causing BSOD, which fingers crossed have been resolved by tweaking the BIOS settings, etc). Hopefully updating Teamviewer has sorted that particular problem out anyway.

    As for your questions. I bought Ultimate and activated it with Microsoft using my key. Output is below:

    Code:
    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    
    Validation Code: 0
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-FX8WW-PGVVM-W69YC
    Windows Product Key Hash: G0IoKNtQuZbGXRpYTtNcJHSLzAU=
    Windows Product ID: 00426-OEM-9402076-14585
    Windows Product ID Type: 8
    Windows License Type: COA SLP
    Windows OS version: 6.1.7601.2.00010100.1.0.001
    ID: {81C96419-83A1-465B-990C-7E216FE37F5C}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Ultimate
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_gdr.130318-1533
    TTS Error: 
    Validation Diagnostic: 
    Resolution Status: N/A
    
    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    
    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002
    
    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002
    
    OGA Data-->
    Office Status: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 77F760FE-153-80070002_7E90FEE8-175-80070002_025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3
    
    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\iexplore.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed
    
    File Scan Data-->
    
    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{81C96419-83A1-465B-990C-7E216FE37F5C}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-W69YC</PKey><PID>00426-OEM-9402076-14585</PID><PIDType>8</PIDType><SID>S-1-5-21-4142153632-2294863933-3660688552</SID><SYSTEM><Manufacturer>To Be Filled By O.E.M.</Manufacturer><Model>To Be Filled By O.E.M.</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>P1.80</Version><SMBIOSVersion major="2" minor="6"/><Date>20111227000000.000000+000</Date></BIOS><HWID>C4C40D00018400F2</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  
    
    Spsys.log Content: 0x80070002
    
    Licensing Data-->
    Software licensing service version: 6.1.7601.17514
    
    Name: Windows(R) 7, Ultimate edition
    Description: Windows Operating System - Windows(R) 7, OEM_COA_SLP channel
    Activation ID: 022a1afb-b893-4190-92c3-8f69a49839fb
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00426-00188-020-714585-02-2057-7601.0000-1522013
    Installation ID: 011233698945697890692972915495290251918235112246918961
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
    Partial Product Key: W69YC
    License Status: Licensed
    Remaining Windows rearm count: 3
    Trusted time: 30/07/2013 18:07:09
    
    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: N/A
    HealthStatus: 0x0000000000000000
    Event Time Stamp: N/A
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:
    
    
    HWID Data-->
    HWID Hash Current: MgAAAAEAAwABAAEAAAABAAAAAwABAAEAln0mUUAKJByUshAz5oIUzqoOqlFYpualQho=
    
    OEM Activation 1.0 Data-->
    N/A
    
    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information: 
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            ALASKA        A M I
      FACP            ALASKA        A M I
      HPET            ALASKA        A M I
      MCFG            ALASKA        A M I
      AAFT            ALASKA        OEMAAFT 
      MCFG            ALASKA        A M I
      SSDT            AMD           POWERNOW
      My Computer


 
Page 4 of 6 FirstFirst ... 23456 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 20:14.
Find Us