locked
Event 1001 bug check after a BSOD RRS feed

  • Question

  • Here are my details from the log. Can anyone explain and help me with this please?

    Log Name:      System
    Source:        Microsoft-Windows-WER-SystemErrorReporting
    Date:          1/31/2012 3:35:07 AM
    Event ID:      1001
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      JOHNSRIG-PC
    Description:
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001e (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 013112-19890-01.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
        <EventID Qualifiers="16384">1001</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-01-31T09:35:07.000000000Z" />
        <EventRecordID>56303</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>System</Channel>
        <Computer>JOHNSRIG-PC</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">0x0000001e (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)</Data>
        <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
        <Data Name="param3">013112-19890-01</Data>
      </EventData>
    </Event>


    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
    <Provider Name="Microsoft-Windows-Diagnostics-Performance" Guid="{CFC18EC0-96B1-4EBA-961B-622CAEE05B0A}" />
    <EventID>100</EventID>
    <Version>2</Version>
    <Level>1</Level>
    <Task>4002</Task>
    <Opcode>34</Opcode>
    <Keywords>0x8000000000010000</Keywords>
    <TimeCreated SystemTime="2012-01-31T09:37:06.191300000Z" />
    <EventRecordID>710</EventRecordID>
    <Correlation ActivityID="{038B2C50-F800-0002-236C-A68CFBDFCC01}" />
    <Execution ProcessID="1756" ThreadID="2700" />
    <Channel>Microsoft-Windows-Diagnostics-Performance/Operational</Channel>
    <Computer>JohnsRig-PC</Computer>
    <Security UserID="S-1-5-19" />
    </System>
    - <EventData>
    <Data Name="BootTsVersion">2</Data>
    <Data Name="BootStartTime">2012-01-31T09:34:37.640400200Z</Data>
    <Data Name="BootEndTime">2012-01-31T09:37:04.651297900Z</Data>
    <Data Name="SystemBootInstance">214</Data>
    <Data Name="UserBootInstance">146</Data>
    <Data Name="BootTime">140909</Data>
    <Data Name="MainPathBootTime">68773</Data>
    <Data Name="BootKernelInitTime">15</Data>
    <Data Name="BootDriverInitTime">2445</Data>
    <Data Name="BootDevicesInitTime">8893</Data>
    <Data Name="BootPrefetchInitTime">0</Data>
    <Data Name="BootPrefetchBytes">0</Data>
    <Data Name="BootAutoChkTime">0</Data>
    <Data Name="BootSmssInitTime">4130</Data>
    <Data Name="BootCriticalServicesInitTime">3474</Data>
    <Data Name="BootUserProfileProcessingTime">1765</Data>
    <Data Name="BootMachineProfileProcessingTime">0</Data>
    <Data Name="BootExplorerInitTime">35902</Data>
    <Data Name="BootNumStartupApps">20</Data>
    <Data Name="BootPostBootTime">72136</Data>
    <Data Name="BootIsRebootAfterInstall">false</Data>
    <Data Name="BootRootCauseStepImprovementBits">0</Data>
    <Data Name="BootRootCauseGradualImprovementBits">0</Data>
    <Data Name="BootRootCauseStepDegradationBits">4194304</Data>
    <Data Name="BootRootCauseGradualDegradationBits">4194304</Data>
    <Data Name="BootIsDegradation">false</Data>
    <Data Name="BootIsStepDegradation">false</Data>
    <Data Name="BootIsGradualDegradation">false</Data>
    <Data Name="BootImprovementDelta">0</Data>
    <Data Name="BootDegradationDelta">0</Data>
    <Data Name="BootIsRootCauseIdentified">true</Data>
    <Data Name="OSLoaderDuration">2152</Data>
    <Data Name="BootPNPInitStartTimeMS">15</Data>
    <Data Name="BootPNPInitDuration">8908</Data>
    <Data Name="OtherKernelInitDuration">1308</Data>
    <Data Name="SystemPNPInitStartTimeMS">9062</Data>
    <Data Name="SystemPNPInitDuration">2430</Data>
    <Data Name="SessionInitStartTimeMS">12647</Data>
    <Data Name="Session0InitDuration">1375</Data>
    <Data Name="Session1InitDuration">209</Data>
    <Data Name="SessionInitOtherDuration">2545</Data>
    <Data Name="WinLogonStartTimeMS">16778</Data>
    <Data Name="OtherLogonInitActivityDuration">14327</Data>
    <Data Name="UserLogonWaitDuration">6101</Data>
    </EventData>
    </Event>
    • Edited by edat362007 Tuesday, January 31, 2012 11:45 AM
    Tuesday, January 31, 2012 11:40 AM

All replies

  • Hello,

    Bug Check Code 0x1E: http://msdn.microsoft.com/en-us/library/windows/hardware/ff557408(v=vs.85).aspx

    Please use Microsoft Skydrive to upload dump files (c:\windows\minidump). Once done, post a link here.

    If you want to debug dump files by yourself, refer to that: http://support.microsoft.com/kb/315263

    You can also contact Microsoft CSS for assistance.



    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. 

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    Tuesday, January 31, 2012 8:28 PM
  • Here's the link for the only minidump I have left.

    https://skydrive.live.com/redir.aspx?cid=2230976b60724f09&resid=2230976B60724F09!120&parid=2230976B60724F09!119&authkey=!AOtMFELdGRzb7KI

     

    Got home today and wife had run a scan and deleted the other 4 or 5 I had. Thank you for your help with this.

    Wednesday, February 1, 2012 4:05 AM
  • Went to your link says the folder is empty.
    Free Support Tools
    Wednesday, February 1, 2012 12:10 PM
  • Sorry about that, I had put it in the wrong folder. Try the link now, it's there.
    Wednesday, February 1, 2012 5:04 PM
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: 0000000000000000, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    Debugging Details:
    ------------------
    Unable to load image \SystemRoot\system32\drivers\Lycosa.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Lycosa.sys
    *** ERROR: Module load completed but symbols could not be loaded for Lycosa.sys
    EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
    FAULTING_IP: 
    +3838303532303231
    00000000`00000000 ??              ???
    EXCEPTION_PARAMETER1:  0000000000000000
    EXCEPTION_PARAMETER2:  0000000000000000
    ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
    BUGCHECK_STR:  0x1E_0
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    LAST_CONTROL_TRANSFER:  from fffff800040c15fe to fffff800040c9c10
    STACK_TEXT:  
    fffff880`02f8ab98 fffff800`040c15fe : fffffa80`048bd830 00000000`00000000 fffff880`02f8b3a0 fffff800`040f5830 : nt!KeBugCheck
    fffff880`02f8aba0 fffff800`040f54fd : fffff800`042d371c fffff800`04210c30 fffff800`0404d000 fffff880`02f8b300 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff880`02f8abd0 fffff800`040f42d5 : fffff800`042140fc fffff880`02f8ac48 fffff880`02f8b300 fffff800`0404d000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`02f8ac00 fffff800`040f75c6 : fffff880`02f8b300 fffff880`02f8b3a0 fffffa80`00000001 fffffa80`05b5fd40 : nt!RtlDispatchException+0x415
    fffff880`02f8b2e0 fffff800`0408470a : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`06625400 : nt!RtlRaiseStatus+0x4e
    fffff880`02f8b880 fffff880`067cfc23 : fffffa80`06669040 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0xf5a9
    fffff880`02f8b900 fffffa80`06669040 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`00000007 : Lycosa+0x1c23
    fffff880`02f8b908 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`00000007 fffff880`0000001a : 0xfffffa80`06669040
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    Lycosa+1c23
    fffff880`067cfc23 ??              ???
    SYMBOL_STACK_INDEX:  6
    SYMBOL_NAME:  Lycosa+1c23
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: Lycosa
    IMAGE_NAME:  Lycosa.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c86fc86
    FAILURE_BUCKET_ID:  X64_0x1E_0_Lycosa+1c23
    BUCKET_ID:  X64_0x1E_0_Lycosa+1c23
    Followup: MachineOwner
    ---------
    2: kd> lmvm Lycosa
    start             end                 module name
    fffff880`067ce000 fffff880`067d5100   Lycosa   T (no symbols)           
        Loaded symbol image file: Lycosa.sys
        Image path: \SystemRoot\system32\drivers\Lycosa.sys
        Image name: Lycosa.sys
        Timestamp:        Wed Sep 08 04:01:26 2010 (4C86FC86)
        CheckSum:         0001462D
        ImageSize:        00007100
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    ---------------------------------------------------------
    Your BSOD was caused by Lycosa.sys driver. It belongs to Tarantula Keyboard Driver from Razer USA Ltd.
    Try updating it and check results. If this does not help, try contacting your Keyboard manufacturer Technical Support.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.   

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    Sunday, February 5, 2012 11:51 AM
  • I will give that a shot. Thank you very much for your help with this Mr X.
    Thursday, February 9, 2012 11:46 AM
  • Monday, February 20, 2012 4:36 AM