1 2 Previous Next 18 Replies Latest reply on Feb 11, 2012 4:02 AM by jpiszcz

    Intel DP55KG: First blue screen after 1-2+ years

    jpiszcz

      Hello,

       

      This the first blue screen I have received on this motherboard, can anyone comment on it?

      I see this at least one other post like this for a DP55WG motherboard on this forum but there was no 'fix' or solution.

      I have not made any HW changes to my system, any thoughts to what could be causing this?

      I am running the latest BIOS.

       

      Version=1
      EventType=BlueScreen
      EventTime=129601175296652900
      ReportType=4
      Consent=1
      UploadTime=129601175386968899
      ReportIdentifier=4b53c242-db88-11e0-8ed2-00270e027bf3
      IntegratorReportIdentifier=091011-19500-01
      Response.type=4
      Response.AnalysisBucket=X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c
      DynamicSig[1].Name=OS Version
      DynamicSig[1].Value=6.1.7601.2.1.0.256.1
      DynamicSig[2].Name=Locale ID
      DynamicSig[2].Value=1033
      UI[2]=C:\Windows\system32\wer.dll
      UI[3]=Windows has recovered from an unexpected shutdown
      UI[4]=Windows can check online for a solution to the problem.
      UI[5]=&Check for solution
      UI[6]=&Check later
      UI[7]=Cancel
      UI[8]=Windows has recovered from an unexpected shutdown
      UI[9]=A problem caused Windows to stop working correctly.  Windows will notify you if a solution is available.
      UI[10]=Close
      Sec[0].Key=BCCode
      Sec[0].Value=fe
      Sec[1].Key=BCP1
      Sec[1].Value=0000000000000005
      Sec[2].Key=BCP2
      Sec[2].Value=FFFFFA800DE3A1A0
      Sec[3].Key=BCP3
      Sec[3].Value=0000000080863B34
      Sec[4].Key=BCP4
      Sec[4].Value=FFFFFA800D21DC48
      Sec[5].Key=OS Version
      Sec[5].Value=6_1_7601
      Sec[6].Key=Service Pack
      Sec[6].Value=1_0
      Sec[7].Key=Product
      Sec[7].Value=256_1
      State[0].Key=Transport.DoneStage1
      State[0].Value=1
      State[1].Key=CA
      State[1].Value=1
      State[2].Key=BLOB
      State[2].Value=CHKSUM=9421E79E3AA799FC54DBE99B0BEAD4F7;BID=OCATAG;ID=5837c289-6ac0-48f1-8c45-b1956ba7860a;SUB=9//10//2011 1:39:15 AM
      File[0].CabName=091011-19500-01.dmp
      File[0].Path=091011-19500-01.dmp
      File[0].Flags=851970
      File[0].Type=2
      File[0].Original.Path=C:\Windows\Minidump\091011-19500-01.dmp
      File[1].CabName=sysdata.xml
      File[1].Path=WER-21590-0.sysdata.xml
      File[1].Flags=851970
      File[1].Type=5
      File[1].Original.Path=C:\Users\user\AppData\Local\Temp\WER-21590-0.sysdata.xml
      File[2].CabName=WERInternalMetadata.xml
      File[2].Path=WER8719.tmp.WERInternalMetadata.xml
      File[2].Flags=589827
      File[2].Type=5
      File[2].Original.Path=C:\Users\user\AppData\Local\Temp\WER8719.tmp.WERInternalMetadata.xml
      File[3].CabName=Report.cab
      File[3].Path=Report.cab
      File[3].Flags=196608
      File[3].Type=7
      File[3].Original.Path=Report.cab
      FriendlyEventName=Shut down unexpectedly
      ConsentKey=BlueScreen
      AppName=Windows
      AppPath=C:\Windows\System32\WerFault.exe
        • 1. Re: Intel DP55KG: First blue screen after 1-2+ years
          Flying_Kiwi

          Justin Piszcz wrote:

           

           

          Response.AnalysisBucket=X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c
          DynamicSig[1].Name=OS Version
          DynamicSig[1].Value=6.1.7601.2.1.0.256.1

          I see a 'usb' in there so perhaps you unplugged a USB device and the OS didn't like it. What USB devices are connected/used and have you installed the newest chipset drivers from Intels website for your board? There were some problems with USB ports reported around the time that Win 7 SP1 came along so Intel released new drivers which addressed the issue. I don't know if the Windows Update provided drivers incorporate those fixes so get the drivers direct from Intel to be sure.

          • 2. Re: Intel DP55KG: First blue screen after 1-2+ years
            jpiszcz

            Hi,

             

            Thanks for the reply, it was (around) the time my iPhone 4 may have been doing a sync.. I've not changed anything in regards to the USB ports though, the devices on them have remained the same, perhaps it may have been some update, always a possibility.

             

            Thanks for the insight.

             

            Justin.

            • 3. Re: Intel DP55KG: First blue screen after 1-2+ years
              Flying_Kiwi

              If it does it again, make a careful note of what's going on at the time. As mentioned, updating your chipset drivers (from the Intel Website) may help to prevent a recurrence.

              • 4. Re: Intel DP55KG: First blue screen after 1-2+ years
                jpiszcz

                Hi,

                 

                Yes I did check via Intel's website they say they are up to date; however, the Audio driver and NIC were outdated though, updated those.

                 

                Justin.

                • 5. Re: Intel DP55KG: First blue screen after 1-2+ years
                  jpiszcz

                  Hi,

                   

                  This time I had a crash (?) wasn't watching but my machine rebooted, the only thing that has changed in the past 3-4 months was I upgraded the Cyber Power driver from 130 to 132 (to monitor the UPS via USB), I've went back to version 130, we'll see if it recurs..

                   

                  I'm also contact Cyber Power as well to see if if they have ever seen this before.

                   

                  (checked C:\Windows -- no memory DMP this time, a spontaenous reboot)

                   

                  Justin.

                  • 6. Re: Intel DP55KG: First blue screen after 1-2+ years
                    jpiszcz

                    Windows Debugging is NICE, checkout the analysis of the memory dump:

                    >> VISTA_DRIVER_FAULT
                    BTW I am running Windows 7.

                     

                    Loading Dump File [C:\Windows\MEMORY.DMP]
                    Kernel Summary Dump File: Only kernel address space is available
                    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
                    Executable search path is:
                    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
                    Product: WinNt, suite: TerminalServer SingleUserTS
                    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
                    Machine Name:
                    Kernel base = 0xfffff800`03260000 PsLoadedModuleList = 0xfffff800`034a5670
                    Debug session time: Sat Sep 10 04:37:02.969 2011 (UTC - 4:00)
                    System Uptime: 0 days 0:49:52.674
                    Loading Kernel Symbols
                    ...............................................................
                    ................................................................
                    .......................................................
                    Loading User Symbols
                    Loading unloaded module list
                    .....
                    *******************************************************************************
                    *                                                                             *
                    *                        Bugcheck Analysis                                    *
                    *                                                                             *
                    *******************************************************************************
                    Use !analyze -v to get detailed debugging information.
                    BugCheck FE, {5, fffffa800de3a1a0, 80863b34, fffffa800d21dc48}
                    *************************************************************************
                    ***                                                                   ***
                    ***                                                                   ***
                    ***    Your debugger is not using the correct symbols                 ***
                    ***                                                                   ***
                    ***    In order for this command to work properly, your symbol path   ***
                    ***    must point to .pdb files that have full type information.      ***
                    ***                                                                   ***
                    ***    Certain .pdb files (such as the public OS symbols) do not      ***
                    ***    contain the required information.  Contact the group that      ***
                    ***    provided you with these symbols if you need this command to    ***
                    ***    work.                                                          ***
                    ***                                                                   ***
                    ***    Type referenced: usbport!_DEVICE_EXTENSION                     ***
                    ***                                                                   ***
                    *************************************************************************
                    Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c )
                    Followup: MachineOwner
                    ---------
                    2: kd> !analyze -v
                    *******************************************************************************
                    *                                                                             *
                    *                        Bugcheck Analysis                                    *
                    *                                                                             *
                    *******************************************************************************
                    BUGCODE_USB_DRIVER (fe)
                    USB Driver bugcheck, first parameter is USB bugcheck code.
                    Arguments:
                    Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
                    using a physical memory address that was not allocated by
                    the USBport driver.
                    Arg2: fffffa800de3a1a0, Device extension pointer of the host controller
                    Arg3: 0000000080863b34, PCI Vendor,Product id for the controller
                    Arg4: fffffa800d21dc48, Pointer to Endpoint data structure
                    Debugging Details:
                    ------------------
                    *************************************************************************
                    ***                                                                   ***
                    ***                                                                   ***
                    ***    Your debugger is not using the correct symbols                 ***
                    ***                                                                   ***
                    ***    In order for this command to work properly, your symbol path   ***
                    ***    must point to .pdb files that have full type information.      ***
                    ***                                                                   ***
                    ***    Certain .pdb files (such as the public OS symbols) do not      ***
                    ***    contain the required information.  Contact the group that      ***
                    ***    provided you with these symbols if you need this command to    ***
                    ***    work.                                                          ***
                    ***                                                                   ***
                    ***    Type referenced: usbport!_DEVICE_EXTENSION                     ***
                    ***                                                                   ***
                    *************************************************************************
                    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
                    BUGCHECK_STR:  0xFE
                    PROCESS_NAME:  System
                    CURRENT_IRQL:  2
                    LAST_CONTROL_TRANSFER:  from fffff880043d0f7e to fffff800032dcc40
                    STACK_TEXT: 
                    fffff880`0318ca58 fffff880`043d0f7e : 00000000`000000fe 00000000`00000005 fffffa80`0de3a1a0 00000000`80863b34 : nt!KeBugCheckEx
                    fffff880`0318ca60 fffff880`044c5fac : 00000000`dfd89180 fffffa80`0de3b6a0 00000000`00000000 fffffa80`0d21dee0 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a
                    fffff880`0318caa0 fffff880`044c5b73 : fffffa80`0d21dc48 00000000`00000000 fffffa80`0d21dee0 00000000`00000600 : usbehci!EHCI_sMode_PollEndpointSlot+0x6c
                    fffff880`0318cb30 fffff880`044cad91 : fffffa80`0d21dc48 fffff880`03169040 fffffa80`0c77f040 00000000`00000000 : usbehci!EHCI_PollPerAsyEndpoint+0x53
                    fffff880`0318cb70 fffff880`043a4e8b : 00000000`00000002 fffffa80`0de3a1a0 00000000`00000000 00000000`00000050 : usbehci!EHCI_PollEndpoint+0x41
                    fffff880`0318cbb0 fffff880`043a99d1 : 00000000`00000050 00000000`00000004 fffffa80`0d21da00 fffffa80`0de3a050 : USBPORT!MPf_PollEndpoint+0x9b
                    fffff880`0318cbe0 fffff880`043b5077 : fffffa80`0de3a1a0 00000000`00000050 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
                    fffff880`0318cc40 fffff880`043a5f89 : fffffa80`0de3a050 00000000`00000000 fffffa80`0de3aa02 fffffa80`0de3aa18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3
                    fffff880`0318cca0 fffff800`032e80ac : fffff880`03164180 fffffa80`0de3aa18 fffffa80`0de3aa30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
                    fffff880`0318ccd0 fffff800`032d496a : fffff880`03164180 fffff880`0316f0c0 00000000`00000000 fffff880`043a5db0 : nt!KiRetireDpcList+0x1bc
                    fffff880`0318cd80 00000000`00000000 : fffff880`0318d000 fffff880`03187000 fffff880`0318cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
                    STACK_COMMAND:  kb
                    FOLLOWUP_IP:
                    usbehci!EHCI_sMode_PollEndpointSlot+6c
                    fffff880`044c5fac 4533c9          xor     r9d,r9d
                    SYMBOL_STACK_INDEX:  2
                    SYMBOL_NAME:  usbehci!EHCI_sMode_PollEndpointSlot+6c
                    FOLLOWUP_NAME:  MachineOwner
                    MODULE_NAME: usbehci
                    IMAGE_NAME:  usbehci.sys
                    DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c00
                    FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c
                    BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c
                    Followup: MachineOwner
                    ---------
                    • 7. Re: Intel DP55KG: First blue screen after 1-2+ years
                      jpiszcz

                      More:

                       

                       

                      2: kd> !thread
                      THREAD fffff8800316f0c0  Cid 0000.0000  Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 2
                      Not impersonating
                      DeviceMap                 fffff8a0000088f0
                      Owning Process            fffff800034611c0       Image:         Idle
                      Attached Process          fffffa800c77f040       Image:         System
                      Wait Start TickCount      0              Ticks: 191836 (0:00:49:52.660)
                      Context Switch Count      3076851            
                      UserTime                  00:00:00.000
                      KernelTime                00:47:15.598
                      Win32 Start Address nt!KiIdleLoop (0xfffff800032d4910)
                      Stack Init fffff8800318cdb0 Current fffff8800318cd40
                      Base fffff8800318d000 Limit fffff88003187000 Call 0
                      Priority 16 BasePriority 0 UnusualBoost 0 ForegroundBoost 0 IoPriority 0 PagePriority 0
                      Child-SP          RetAddr           : Args to Child                                                           : Call Site
                      fffff880`0318ca58 fffff880`043d0f7e : 00000000`000000fe 00000000`00000005 fffffa80`0de3a1a0 00000000`80863b34 : nt!KeBugCheckEx
                      fffff880`0318ca60 fffff880`044c5fac : 00000000`dfd89180 fffffa80`0de3b6a0 00000000`00000000 fffffa80`0d21dee0 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a
                      fffff880`0318caa0 fffff880`044c5b73 : fffffa80`0d21dc48 00000000`00000000 fffffa80`0d21dee0 00000000`00000600 : usbehci!EHCI_sMode_PollEndpointSlot+0x6c
                      fffff880`0318cb30 fffff880`044cad91 : fffffa80`0d21dc48 fffff880`03169040 fffffa80`0c77f040 00000000`00000000 : usbehci!EHCI_PollPerAsyEndpoint+0x53
                      fffff880`0318cb70 fffff880`043a4e8b : 00000000`00000002 fffffa80`0de3a1a0 00000000`00000000 00000000`00000050 : usbehci!EHCI_PollEndpoint+0x41
                      fffff880`0318cbb0 fffff880`043a99d1 : 00000000`00000050 00000000`00000004 fffffa80`0d21da00 fffffa80`0de3a050 : USBPORT!MPf_PollEndpoint+0x9b
                      fffff880`0318cbe0 fffff880`043b5077 : fffffa80`0de3a1a0 00000000`00000050 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
                      fffff880`0318cc40 fffff880`043a5f89 : fffffa80`0de3a050 00000000`00000000 fffffa80`0de3aa02 fffffa80`0de3aa18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3
                      fffff880`0318cca0 fffff800`032e80ac : fffff880`03164180 fffffa80`0de3aa18 fffffa80`0de3aa30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
                      fffff880`0318ccd0 fffff800`032d496a : fffff880`03164180 fffff880`0316f0c0 00000000`00000000 fffff880`043a5db0 : nt!KiRetireDpcList+0x1bc
                      fffff880`0318cd80 00000000`00000000 : fffff880`0318d000 fffff880`03187000 fffff880`0318cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
                      • 9. Re: Intel DP55KG: First blue screen after 1-2+ years
                        Flying_Kiwi

                        If your BIOS revision for the board is already rev 5936 (is it?) and you already have the latest Windows 7 chipset drivers installed rev 9.2.0.1030, the only other thing I can think of would be contacting Intel Tech support and the makers of your Apple software and phone drivers to see if they can help.

                        • 10. Re: Intel DP55KG: First blue screen after 1-2+ years
                          jpiszcz

                          Hello,

                           

                          Yes, I usually update the BIOS the day it comes out (I am subscribed to Intel's RSS feed for the BIOS releases)..

                          I guess I will need to open a case with Intel on this one, it is strange though, in Linux (on another DP55KG) USB appeared to have flaked out as well (I RMA'd that board) and thus far it has been OK.

                           

                          Other guy with exact same error:

                          http://communities.intel.com/message/134816

                           

                          And again:

                          http://northatlanticregiment.com/forum/index.php?/topic/4856-dp55wg-bsod-problems/

                           

                          In addition, I have run OZONE FURMARK and 4 CPUBURNS && MEMTEST86 -- all ran fine for hours, no issues.

                          So this specifically is something to do with the USB chipset on the motherboard.

                           

                          You know how with the first REV of SATA 6gbps Intel had to recall the motherboards?

                          I've also seen a host (i975 chipset) which use 4 raptors in raid-0 for 3-5+ years and now it no longer works properly if you put the hard drive on those ports, if you use an add-on card, it works fine. -- In addition, all raptors were replaced and the problem persisted, it was only fixed when different ports were used instead of the 4 main ones on the motherboard/Intel chipset.

                           

                          Is it possible that, if there is too much syncing with iPhone/iPad/other USB devices it could cause this issue(?)-- similar to what happened with 6gbps SATA and the example I mentioned above?

                           

                          Justin.

                          • 11. Re: Intel DP55KG: First blue screen after 1-2+ years
                            Flying_Kiwi

                            Justin Piszcz wrote:

                             

                            Is it possible that, if there is too much syncing with iPhone/iPad/other USB devices it could cause this issue(?)-- similar to what happened with 6gbps SATA and the example I mentioned above?

                            Do your other USB devices work OK with this board, if so I suspect it's simply some sort of conflict between the Apple related software or the phone and your PC. Perhaps its associated with the current being drawn when the battery in the phone is being charged ie it may not happen the same amount as when a fully charged phone is plugged in/unplugged as when it's heavily discharged....

                             

                            Your well spotted other examples of the same bug (and above question) are excellent points to put to Intel Tech support when you report the issue. The more cases of this issue are documented the more likely it is to be resolved more quickly. Good luck and let us know what they have to say about it.

                            • 12. Re: Intel DP55KG: First blue screen after 1-2+ years
                              jpiszcz

                              Hello,

                               

                              Yes, other devices do work OK.

                               

                              I also came across:

                              http://communities.intel.com/message/81630

                               

                              I am seeing something in similar in my logs too:

                              Warning : Hardware monitoring subsystem failed to initialize a virtual device.: QPI_FREQUENCY_MONITOR

                              Error : Unhandled exception detected while executing virtual device command response.: IdOfEvent: 384 | IdOfItem: QPI_FREQUENCY_MONITOR | Status: NoError | Return Value: Intel.PerfTune.DeviceData.DerivedMonitorItemData`1[System.Single]

                               

                              Justin.

                              • 13. Re: Intel DP55KG: First blue screen after 1-2+ years
                                jpiszcz

                                Hi,

                                 

                                Problem was found, as I noted before I had two DP55KGs with two i870 CPUs, I replaced my CPU and the problem has gone away, I will RMA the old CPU.

                                 

                                Justin.

                                • 14. Re: Intel DP55KG: First blue screen after 1-2+ years
                                  jpiszcz

                                  Spoke too soon earlier, I went on a trip when I came back, the day after or so the system crashed. After replacing everything a few times but the PSU, I replaced the PSU last week, no crashes yet. Will update if any further crashes, but I am pretty sure it was the PSU.  The PSU was an older one I used from an older system (Corsair 620 watt) from 2007, they don't even make them anymore, never had an Antec do that though..  Replaced with an Antec 650, hopefully this fixes the problem for now, or at least until the X79 boards come out next year.

                                  1 2 Previous Next