ACPI.sys, NDIS.sys, and TCPIP.sys causing massive DPC latency spikes

I am running Win 7 Ultimate. I recently reinstalled my OS. Using LatencyMon and DPCLatency checker, I've noticed that these three drivers are causing massive spikes. How do I replace these files with non-problematic files?
(Originally, my computer was on Home Prem, I did an anytime upgrade to Ultimate, this time I did a clean install)
Thanks.

Dear all,
I am also doing home recording with my computer, via firewire and I also see latency spikes.
Its for an advanced home user difficult to judge, what is causing issues.
Audio clicks and drops were mainly caused on my (high performance system) by non optimal combination of Firewire Card/Chipset, Windows 7 Firewire driver and driver of the audio Interface, but which I could finally solve.
My Solution for my system:
- 1st I had to buy a new firewire card with recommended chipset of audio interface vendor
- Additionally I had to use the Win7 Firewire "legacy" driver
-> Then my audio clicks and drops went away.
Month later the vendor releases a new version of his Mixer/driver for the audio interface (Saffire mix control).
And what shall I tell:
- the normal Win7 firewire driver could be chosen (which seems to be more optimized in terms of latency)
- under Cubase (with setting "optimize cubase for windows") the firewire latency went down from 200us to even 76-90us on average.
Of course Microsoft shall work on optimizing their OS, I want an optimized OS as good base for everything.
But all my problems went away in terms of recording, at least on my system, when I optimized things around Mircrosoft.
With a Laptop this might be a different issue ..
LatencyMon v3.0: CONCLUSION
Your system seems to have difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. One or more DPC routines belonging to a driver running in your system appear to be executing for too long. At
least one detected problem appears to be network related. You may have to disable wireless adapters to get better results.
OS version:                                          
Windows 7 Service Pack 1, 6.1, build: 7601
CPU:                                                 
GenuineIntel Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz
Logical processors:                                   8
RAM:                                                 
17170518016 total
VM:                                                  
2147352576, free: 1916923904
Reported CPU speed:                                   2807 MHz
Measured CPU speed:                                   2722 MHz
Highest measured kernel timer latency (µs):           1289.9413
Highest measured SMI routine or CPU stall (µs)        98.8614
Highest DPC routine execution time (µs):              1978.9440
Driver with highest DPC routine execution time:       ndis.sys - NDIS 6.20-Treiber, Microsoft Corporation
Highest reported total DPC routine time (%):          0.9446
Driver with highest DPC total execution time:         Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation
Total time spent in DPCs (%)                          1.7380
DPC count (execution time <250 µs):                   3443062
DPC count (execution time 250-500 µs):                0
DPC count (execution time 500-999 µs):                68
DPC count (execution time 1000-1999 µs):              6
DPC count (execution time 2000-3999 µs):              0
DPC count (execution time >=4000 µs):                 0

Similar Messages

  • Satellite L450-188 - How to disable ACPI.sys and update BIOS?

    Hi, hoping someone can help me with a slight problem i'm having
    I recently bought a Satellite L450-188 (part number PSLY0E-03K019EN) running Windows 7 64bit
    I use the laptop with a DJ program called Rane Serato Scratch Live, i've been having usb latency issues, getting usb dropouts when I try to use the program on its lowest audio buffer setting (which I expected to be able to do)
    When I contacted the support team at Serato with my problem, they suggested I run a program to check the DPC times on my laptop, when I submitted the report to them, they said ACPI.sys was causing the issue, and suggested I might want to disable it, but i wasn't too confident with doing this.
    The other suggestion was to try and find bios updates for my laptop, but I'm not too clued-up with this sort of thing, and I'm worried I might damage the laptop by maybe installing the wrong thing.
    Can anyone give me any advice on this, as I'm not sure what to do
    thanks
    jim

    Hi jimbob_1,
    Normally ACPI means Advanced Configuration and Power Interface and controls some power saving options.
    So if something is wrong with ACPI.sys file I would recommend reinstalling Windows using Toshiba recovery disk.
    By the way: Are you running preinstalled Windows version or another one?
    As Akuma wrote you can download BIOS update on Toshiba website. http://eu.computers.toshiba-europe.com/ > Support & Downloads > Download Drivers
    Your notebook belongs to PSLY0E series, therefore you can download newest BIOS.
    Before you start the BIOS update, close all running programs and extract all files from zip-archive. You start the update as Administrator and connect AC/DC adaptor. Make also sure that battery is fully charged.

  • T410 - high DPC latency in ACPI.sys on BIOS update (leads to audio pops and crackles)

    I recently updated my Thinkpad T410's BIOS because the fan wasn't working properly. The fan is working fine now, but ever since the BIOS update I've been experiencing severe audio pops and crackles. I used the tool LatencyMon to inspect, and the chief culprit seems to be ACPI.sys, with execution times as long as 10ms.
    I've tried disabling all the power management options in the BIOS and changing everything to max performance. I've also tried disabling other various devices such as the network adapters, but nothing seems to help. Any idea?

    Hi agrilledfish,
    Is your BIOS 3.03?
    I found a post on MixVibes regarding audio drops:
    Audio drops/USB problems
    You can try to disable ACPI.sys in device manager or uninstall and reinstall the software.
    Be AWESOME Everyday!
    Donate KUDOS and Click "Accepted Solution"
    Did someone help you today?
    Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"
    This will help the rest of the Community with similar issues identify the verified solution and benefit from it.

  • After Deploying an Image: Windows Boot Manager - Missing ACPI.sys

    Hi,
    I am currently working on deploying a Windows 7 Pro x64 image to a number of clients over our network using FOG. We used KVM in Ubuntu to build the base image. The image has a small virtual disk for the Windows installation and is deployed to clients with larger
    drives. Prior to capture the image, we ran sysprep /generalize /shutdown /oobe /unattend:unattend.xml, then boot the VM to the FOG client and let FOG save off the disk image. We then deploy the image to clients over FOG.
    FOG successfully copies the image over, then reboots the PC. The computer attempts to boot from the local hard drive, then fails at the Windows Boot Manager screen, saying:
    Windows boot manager
    Windows failed to start. A recent hardware or software change might be the cause....
    File: \Windows\system32\drivers\ACPI.sys
    Status: 0xc0000098
    Info: Windows failed to load because a critical system driver is missing or corrupt.
    I've updated the client's BIOS, tried a different hard drive, used ATA secure erase to wipe the drive before formatting, and still encounter this same issue with certain client computers. Are there any other steps I can take to resolve this issue?
    What files in Panther should I look at (or post) to troubleshoot? I don't see anything too obvious in diagerr, and sestuperr.log is just about empty.

    We're using two models of 120GB SSDs, and deploying to 5 different motherboards (4 Intel models + 1 MSI model). The issue is most common with the DH55TC Intel boards.
    We're using FOG due to budget limits--otherwise, WDT definitely would have been considered.

  • ACPI.sys problems

    I continue to get a blue screen each time on boot, but eventually it takes me into Windows and all is OK. Below is the dump file if anyone can help...
    Microsoft (R) Windows Debugger Version 6.3.9600.17200 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Bitmap Dump File: Only kernel address space is available
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    OK                                             C:\Windows
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\Windows
    Windows 8 Kernel Version 9600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17085.x86fre.winblue_gdr.140330-1035
    Machine Name:
    Kernel base = 0x81801000 PsLoadedModuleList = 0x81a00438
    Debug session time: Wed Aug 13 10:43:56.571 2014 (UTC + 1:00)
    System Uptime: 0 days 1:09:24.416
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    *                        Bugcheck Analysis                                    *
    Use !analyze -v to get detailed debugging information.
    BugCheck 9F, {3, 86f6c6c8, 82d55b44, 89ab2290}
    Probably caused by : ACPI.sys
    Followup: MachineOwner
    0: kd> !analyze -v
    *                        Bugcheck Analysis                                    *
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 00000003, A device object has been blocking an Irp for too long a time
    Arg2: 86f6c6c8, Physical Device Object of the stack
    Arg3: 82d55b44, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: 89ab2290, The blocked IRP
    Debugging Details:
    DRVPOWERSTATE_SUBCODE:  3
    IMAGE_NAME:  ACPI.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  53088850
    MODULE_NAME: ACPI
    FAULTING_MODULE: 82f2a000 ACPI
    IRP_ADDRESS: 89ab2290
    DEVICE_OBJECT: 80370c40
    DRIVER_OBJECT: 8036e378
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    BUGCHECK_STR:  0x9F
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre
    DPC_STACK_BASE:  FFFFFFFF82D5A000
    STACK_TEXT:  
    82d55b1c 8199f1ac 0000009f 00000003 86f6c6c8 nt!KeBugCheckEx
    82d55b54 8199f0f8 00000000 819f8790 00000002 nt!PopIrpWatchdogBugcheck+0xae
    82d55b68 8187e456 adc60938 adc608f0 19e736dd nt!PopIrpWatchdog+0x28
    82d55c20 8187e053 82d55c68 00000000 aaa84bc0 nt!KiExecuteAllDpcs+0x216
    82d55d44 8191dae0 00000000 f7ffffdf ff7effff nt!KiRetireDpcList+0xf3
    82d55d48 00000000 f7ffffdf ff7effff efffbfff nt!KiIdleLoop+0x38
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    FAILURE_BUCKET_ID:  0x9F_VRF_3_POWER_DOWN_IMAGE_ACPI.sys
    BUCKET_ID:  0x9F_VRF_3_POWER_DOWN_IMAGE_ACPI.sys
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0x9f_vrf_3_power_down_image_acpi.sys
    FAILURE_ID_HASH:  {79570452-9ffd-73a3-d1ad-2718dca08365}
    Followup: MachineOwner
    0: kd> !analyze -v
    *                        Bugcheck Analysis                                    *
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 00000003, A device object has been blocking an Irp for too long a time
    Arg2: 86f6c6c8, Physical Device Object of the stack
    Arg3: 82d55b44, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: 89ab2290, The blocked IRP
    Debugging Details:
    DRVPOWERSTATE_SUBCODE:  3
    IMAGE_NAME:  ACPI.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  53088850
    MODULE_NAME: ACPI
    FAULTING_MODULE: 82f2a000 ACPI
    IRP_ADDRESS: 89ab2290
    DEVICE_OBJECT: 80370c40
    DRIVER_OBJECT: 8036e378
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    BUGCHECK_STR:  0x9F
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre
    DPC_STACK_BASE:  FFFFFFFF82D5A000
    STACK_TEXT:  
    82d55b1c 8199f1ac 0000009f 00000003 86f6c6c8 nt!KeBugCheckEx
    82d55b54 8199f0f8 00000000 819f8790 00000002 nt!PopIrpWatchdogBugcheck+0xae
    82d55b68 8187e456 adc60938 adc608f0 19e736dd nt!PopIrpWatchdog+0x28
    82d55c20 8187e053 82d55c68 00000000 aaa84bc0 nt!KiExecuteAllDpcs+0x216
    82d55d44 8191dae0 00000000 f7ffffdf ff7effff nt!KiRetireDpcList+0xf3
    82d55d48 00000000 f7ffffdf ff7effff efffbfff nt!KiIdleLoop+0x38
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    FAILURE_BUCKET_ID:  0x9F_VRF_3_POWER_DOWN_IMAGE_ACPI.sys
    BUCKET_ID:  0x9F_VRF_3_POWER_DOWN_IMAGE_ACPI.sys
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0x9f_vrf_3_power_down_image_acpi.sys
    FAILURE_ID_HASH:  {79570452-9ffd-73a3-d1ad-2718dca08365}
    Followup: MachineOwner
    0: kd> !analyze -v
    *                        Bugcheck Analysis                                    *
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 00000003, A device object has been blocking an Irp for too long a time
    Arg2: 86f6c6c8, Physical Device Object of the stack
    Arg3: 82d55b44, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: 89ab2290, The blocked IRP
    Debugging Details:
    DRVPOWERSTATE_SUBCODE:  3
    IMAGE_NAME:  ACPI.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  53088850
    MODULE_NAME: ACPI
    FAULTING_MODULE: 82f2a000 ACPI
    IRP_ADDRESS: 89ab2290
    DEVICE_OBJECT: 80370c40
    DRIVER_OBJECT: 8036e378
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    BUGCHECK_STR:  0x9F
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre
    DPC_STACK_BASE:  FFFFFFFF82D5A000
    STACK_TEXT:  
    82d55b1c 8199f1ac 0000009f 00000003 86f6c6c8 nt!KeBugCheckEx
    82d55b54 8199f0f8 00000000 819f8790 00000002 nt!PopIrpWatchdogBugcheck+0xae
    82d55b68 8187e456 adc60938 adc608f0 19e736dd nt!PopIrpWatchdog+0x28
    82d55c20 8187e053 82d55c68 00000000 aaa84bc0 nt!KiExecuteAllDpcs+0x216
    82d55d44 8191dae0 00000000 f7ffffdf ff7effff nt!KiRetireDpcList+0xf3
    82d55d48 00000000 f7ffffdf ff7effff efffbfff nt!KiIdleLoop+0x38
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    FAILURE_BUCKET_ID:  0x9F_VRF_3_POWER_DOWN_IMAGE_ACPI.sys
    BUCKET_ID:  0x9F_VRF_3_POWER_DOWN_IMAGE_ACPI.sys
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0x9f_vrf_3_power_down_image_acpi.sys
    FAILURE_ID_HASH:  {79570452-9ffd-73a3-d1ad-2718dca08365}
    Followup: MachineOwner
    0: kd> lmvm ACPI
    start    end        module name
    82f2a000 82f99000   ACPI       (pdb symbols)          c:\symbols\acpi.pdb\25C14E6BE529448C9CF14E1C90AEA6FD2\acpi.pdb
        Loaded symbol image file: ACPI.sys
        Image path: ACPI.sys
        Image name: ACPI.sys
        Timestamp:        Sat Feb 22 11:21:52 2014 (53088850)
        CheckSum:         00070198
        ImageSize:        0006F000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    0: kd> !devobj ffffffff80370c40 f
    Device object (80370c40) is for:
      \Driver\ACPI DriverObject 8036e378
    Current Irp 00000000 RefCount 0 Type 00000032 Flags 00000000
    DevExt 80370a08 DevObjExt 80370cf8 
    ExtensionFlags (0x30000000)  DOE_RAW_FDO
                                 Unknown flags 0x10000000
    Characteristics (0000000000)  
    AttachedTo (Lower) 86f6c6c8 \Driver\ACPI_HAL
    Device queue is not busy.
    0: kd> !drvobj ffffffff8036e378 f
    Driver object (8036e378) is for:
     \Driver\ACPI
    Driver Extension List: (id , addr)
    Device Object list:
    913ed740  91334860  9c9b7928  8cbde020
    8cb90f10  8cbd01b0  8cb84680  88bfe2d0
    88bfd4c0  88bfc840  88bfa7b0  88bfa900
    88bf8030  88bf7330  88bf7490  88bf75f0
    88bf7750  88bf78b0  88bf7a10  88bf7b70
    88bf7cd0  88bf7df0  88bf7f10  88bde820
    88bde930  88bdd710  88bdd820  88bdd930
    88bdc750  88bdc8c8  88bdb618  88bdb790
    88bdb908  88bda640  88bda7b8  88bda930
    88bd9688  88bd9800  88bd5620  88bd57e0
    88bd6860  88bd6980  88bd6aa0  88bd3860
    88bd3980  88bd3aa0  88bb5948  88bb5a68
    88bb5cd0  88bb5df0  88bb4870  88bb7f10
    88bb4308  88b9d2f0  88ba02f0  80370c40
    DriverEntry:   82f426dd ACPI!GsDriverEntry
    DriverStartIo: 00000000
    DriverUnload:  82f5a7d8 ACPI!ACPIUnload
    AddDevice:     82f8b544 ACPI!ACPIDispatchAddDevice
    Dispatch routines:
    [00] IRP_MJ_CREATE                      82f2b005
    ACPI!ACPIDispatchIrp
    [01] IRP_MJ_CREATE_NAMED_PIPE           82f2b005
    ACPI!ACPIDispatchIrp
    [02] IRP_MJ_CLOSE                       82f2b005
    ACPI!ACPIDispatchIrp
    [03] IRP_MJ_READ                        82f2b005
    ACPI!ACPIDispatchIrp
    [04] IRP_MJ_WRITE                       82f2b005
    ACPI!ACPIDispatchIrp
    [05] IRP_MJ_QUERY_INFORMATION           82f2b005
    ACPI!ACPIDispatchIrp
    [06] IRP_MJ_SET_INFORMATION             82f2b005
    ACPI!ACPIDispatchIrp
    [07] IRP_MJ_QUERY_EA                    82f2b005
    ACPI!ACPIDispatchIrp
    [08] IRP_MJ_SET_EA                      82f2b005
    ACPI!ACPIDispatchIrp
    [09] IRP_MJ_FLUSH_BUFFERS               82f2b005
    ACPI!ACPIDispatchIrp
    [0a] IRP_MJ_QUERY_VOLUME_INFORMATION    82f2b005
    ACPI!ACPIDispatchIrp
    [0b] IRP_MJ_SET_VOLUME_INFORMATION      82f2b005
    ACPI!ACPIDispatchIrp
    [0c] IRP_MJ_DIRECTORY_CONTROL           82f2b005
    ACPI!ACPIDispatchIrp
    [0d] IRP_MJ_FILE_SYSTEM_CONTROL         82f2b005
    ACPI!ACPIDispatchIrp
    [0e] IRP_MJ_DEVICE_CONTROL              82f2b005
    ACPI!ACPIDispatchIrp
    [0f] IRP_MJ_INTERNAL_DEVICE_CONTROL     82f2b005
    ACPI!ACPIDispatchIrp
    [10] IRP_MJ_SHUTDOWN                    82f2b005
    ACPI!ACPIDispatchIrp
    [11] IRP_MJ_LOCK_CONTROL                82f2b005
    ACPI!ACPIDispatchIrp
    [12] IRP_MJ_CLEANUP                     82f2b005
    ACPI!ACPIDispatchIrp
    [13] IRP_MJ_CREATE_MAILSLOT             82f2b005
    ACPI!ACPIDispatchIrp
    [14] IRP_MJ_QUERY_SECURITY              82f2b005
    ACPI!ACPIDispatchIrp
    [15] IRP_MJ_SET_SECURITY                82f2b005
    ACPI!ACPIDispatchIrp
    [16] IRP_MJ_POWER                       82f2b005
    ACPI!ACPIDispatchIrp
    [17] IRP_MJ_SYSTEM_CONTROL              82f2b005
    ACPI!ACPIDispatchIrp
    [18] IRP_MJ_DEVICE_CHANGE               82f2b005
    ACPI!ACPIDispatchIrp
    [19] IRP_MJ_QUERY_QUOTA                 82f2b005
    ACPI!ACPIDispatchIrp
    [1a] IRP_MJ_SET_QUOTA                   82f2b005
    ACPI!ACPIDispatchIrp
    [1b] IRP_MJ_PNP                         82f2b005
    ACPI!ACPIDispatchIrp
    Fast I/O routines:
    FastIoDetachDevice                      82f5c25d
    ACPI!ACPIFilterFastIoDetachCallback
    0: kd> !drvobj \Driver\ACPI_HAL
    Driver object \Driver\ACPI_HAL not found

    Hi,
    The dump result you uploaded is here:
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck 9F, {3, 86f6c6c8, 82d55b44, 89ab2290}
    Probably caused by : ACPI.sys
    Followup: MachineOwner
    For BugCheck 9F, please see:
    Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE. This bug check indicates that the driver is in an inconsistent or invalid power state.
    * Bugcheck Analysis *
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 00000003, A device object has been blocking an Irp for too long a time
    Arg2: 86f6c6c8, Physical Device Object of the stack
    Arg3: 82d55b44, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: 89ab2290, The blocked IRP
    The Bug check told this BSOD is probably caused by ACPI.sys, which is an inbox component of Widnows operating system, detailed debug information, I am afraid that is not supported through the forums here.
    The information about ACPI.sys:
    The Windows ACPI driver, Acpi.sys, is an inbox component of the Windows operating system. The responsibilities of Acpi.sys include support for power management and Plug and Play (PnP) device enumeration. On hardware platforms that have an
    ACPI BIOS, the
    HAL causes Acpi.sys to be loaded during system startup at the base of the
    device tree. Acpi.sys acts as the interface between the operating system and the ACPI BIOS. Acpi.sys is transparent to the other drivers in the device tree. 
    Reference:
    Acpi.sys: The Windows ACPI Driver
    Thank you for your understanding
    Best regards
    Michael Shao
    TechNet Community Support

  • Tracing complete, solution required bsod due to ACPI.sys

    hi, hassaan here
    i got a bsod today and i debugged it, the result i got, is you can find at:
    https://skydrive.live.com/redir?resid=F80746862BC199FD!155&authkey=!AExsDmGkIac7haY&ithint=file%2c.txt
    the main cause is ACpi.sys and showing reason, VISTA_DRIVER_FAULT;
    i really required help, what is the cause and what solution is required.
    awaiting for reply.
    thanks.

    Hi,
    Please upload the source file to Skydrive, and then share to us.
    Meanwhile, update all your drivers and then run sfc /scannow command:
    Use the System File Checker tool to repair missing or corrupted system files
    http://support.microsoft.com/kb/929833
    Karen Hu
    TechNet Community Support

  • Possible audio latency issues due to acpi.sys

    Hello, I use Vista to run the digital DJ program, Traktor. While I've never had any latency issues before, they recently started cropping up and I ran LatencyMon to see where the problem could be. It appears that the problem may be the service, acpi.sys,
    as it had the highest execution of 1.2, which is fairly high. I've tried using Process Explorer and entering into the BIOS to turn off acpi.sys, but wasn't able to. Is there really any way of disable this service?
    Thank you.

    Hi,
    As this issue did not occur before, system restore can be under consideration.
    To disable the feature, you can also go to Device Manager, expand System Devices.
    This issue can occur due to hardware or software conflictions. Let us try the steps below to narrow down the cause of the issue. Please check if we can boot in Win7 normally:
    Device Clean Boot
    ==============
    In this situation, your system will only have the basic hardware devices and it should be more stable. If it is inconvenient to unplug the devices, we can disable them in Device Manager. Please refer to the following steps:
    1. Click "Start", type "DEVMGMT.MSC" in the Search textbox and press Enter.
    2. Expand "Sound, video and game controllers".
    3. Right click on your Sound Card, select "Properties"
    4. Click "Driver" tab, click Disable (Disable the selected device). Click OK
    5. Please use the same method to disable other hardware such as: Modem, network card, CD-R drive. Please note some devices such as video adapter are not available to be disabled.
    6. Please restart the computer. Can we boot in Windows Vista properly? If so, please continue prepare a clean boot to troubleshoot.
    Clean Boot prevents software conflicts by preventing the startup items and non Microsoft services from loading. This way you can safely follow the process of elimination to check which application is causing this behavior.
    Refer:
    How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7
    http://support.microsoft.com/kb/929135
    Note: Ensure that you put your computer back to normal startup mode after completing the troubleshooting steps. Steps are available in the article given above.
    Regards,
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

  • Pciimaq.sys causes nt40 to crash during booting?

    I'm trying to install a 1408 IMAQ card. Anyhow, the system running
    NT40+SP6 does not manage to boot anymore. It allways presents me with a
    blue-screen,
    telling me that PCIIMAQ.SYS causes some kind of adress error.
    What can I do to fix this?
    Regards,
    Thomas jennewein

    Is the IMAQ board in the computer when this crash occurs? Do the crash occur if the boasrd is out of the computer. If you can boot without the board in, you probably have a bad board. If it still does not boot, can you boot in safe mode and uninstall the driver or it won't even let you select which mode to boot in?

  • DPC latency - NDIS.SYS -

    Hello,
    I've spend days with this issue and done tons of research online and cannot find a resolution. 
    I can easily replicate this by streaming video online and here is an output from not even 3 minutes;
    CONCLUSION
    Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing
    for too long. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS
    setup. Check for BIOS updates. 
    LatencyMon has been analyzing your system for  0:00:28  (h:mm:ss) on all processors.
    SYSTEM INFORMATION
    Computer name:                                        BASEMENT-PC
    OS version:                                           Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
    Hardware:                                             Z68X-UD3H-B3, Gigabyte Technology Co., Ltd.
    CPU:                                                  GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
    Logical processors:                                   4
    Processor groups:                                     1
    RAM:                                                  8109 MB total
    CPU SPEED
    Reported CPU speed:                                   3410.0 MHz
    Measured CPU speed:                                   2292.0 MHz (approx.)
    Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.
    MEASURED INTERRUPT TO USER PROCESS LATENCIES
    The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the
    signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.
    Highest measured interrupt to process latency (µs):   1026890.71290
    Average measured interrupt to process latency (µs):   22.754394
    Highest measured interrupt to DPC latency (µs):       1026762.790580
    Average measured interrupt to DPC latency (µs):       20.927825
     REPORTED ISRs
    Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.
    Highest ISR routine execution time (µs):              217.898240
    Driver with highest ISR routine execution time:       ndis.sys - NDIS 6.20 driver, Microsoft Corporation
    Highest reported total ISR routine time (%):          1.516305
    Driver with highest ISR total time:                   ndis.sys - NDIS 6.20 driver, Microsoft Corporation
    Total time spent in ISRs (%)                          1.774242
    ISR count (execution time <250 µs):                   89542
    ISR count (execution time 250-500 µs):                0
    ISR count (execution time 500-999 µs):                0
    ISR count (execution time 1000-1999 µs):              0
    ISR count (execution time 2000-3999 µs):              0
    ISR count (execution time >=4000 µs):                 0
    REPORTED DPCs
    DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.
    Highest DPC routine execution time (µs):              5353.539003
    Driver with highest DPC routine execution time:       ndis.sys - NDIS 6.20 driver, Microsoft Corporation
    Highest reported total DPC routine time (%):          0.257649
    Driver with highest DPC total execution time:         ndis.sys - NDIS 6.20 driver, Microsoft Corporation
    Total time spent in DPCs (%)                          0.742536
    DPC count (execution time <250 µs):                   216143
    DPC count (execution time 250-500 µs):                0
    DPC count (execution time 500-999 µs):                69
    DPC count (execution time 1000-1999 µs):              0
    DPC count (execution time 2000-3999 µs):              0
    DPC count (execution time >=4000 µs):                 0
     REPORTED HARD PAGEFAULTS
    Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted
    and blocked from execution.
    NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.
    Process with highest pagefault count:                 chrome.exe
    Total number of hard pagefaults                       148
    Hard pagefault count of hardest hit process:          90
    Highest hard pagefault resolution time (µs):          2645.792669
    Total time spent in hard pagefaults (%):              0.026785
    Number of processes hit:                              4
     PER CPU DATA
    CPU 0 Interrupt cycle time (s):                       5.116707
    CPU 0 ISR highest execution time (µs):                217.898240
    CPU 0 ISR total execution time (s):                   2.019442
    CPU 0 ISR count:                                      89542
    CPU 0 DPC highest execution time (µs):                5353.539003
    CPU 0 DPC total execution time (s):                   0.821584
    CPU 0 DPC count:                                      211370
    CPU 1 Interrupt cycle time (s):                       0.373808
    CPU 1 ISR highest execution time (µs):                0.0
    CPU 1 ISR total execution time (s):                   0.0
    CPU 1 ISR count:                                      0
    CPU 1 DPC highest execution time (µs):                164.455718
    CPU 1 DPC total execution time (s):                   0.004153
    CPU 1 DPC count:                                      1067
    CPU 2 Interrupt cycle time (s):                       0.360522
    CPU 2 ISR highest execution time (µs):                0.0
    CPU 2 ISR total execution time (s):                   0.0
    CPU 2 ISR count:                                      0
    CPU 2 DPC highest execution time (µs):                200.432258
    CPU 2 DPC total execution time (s):                   0.008878
    CPU 2 DPC count:                                      1420
    CPU 3 Interrupt cycle time (s):                       0.167079
    CPU 3 ISR highest execution time (µs):                0.0
    CPU 3 ISR total execution time (s):                   0.0
    CPU 3 ISR count:                                      0
    CPU 3 DPC highest execution time (µs):                51.623460
    CPU 3 DPC total execution time (s):                   0.010540
    CPU 3 DPC count:                                      2356
    This computer is VERY clean and has no anti-virus/firewalls/software
    All drivers are updated (I'm not sure if the BIOS is updated yet)
    SO far from research I've change my SSD to AHCI from IDE after doing some registry changes. MADE IT SO MUCH FASTER not why the original builder of the computer didn't do this in the beginning
    I've disabled power setting on the WIFI adapter
    When I disable the WIFI it seems to fix the issue but I NEED WIFI - I can't find anywhere online that explains if buying a new WIFI NIC would fix this?
    I tried to run in command 'verifier' and an option to select all drivers on the computer - It made me restart but after that it crashed and needed to be set back to a restore point???

    So I disabled the WIFI card and hooked up directly to the switch and I'm not seeing NDIS.sys coming up as latency and after light testing it appears I'm not freezing up for the second or so randomly.
    I think I"ll buy another WIFI card and see what happens.
    LatencyMon does show now
    Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One problem may be related to power management, disable CPU throttling settings in Control
    Panel and BIOS setup. Check for BIOS updates. 
    LatencyMon has been analyzing your system for  0:03:51  (h:mm:ss) on all processors.
    SYSTEM INFORMATION
    Computer name:                                        BASEMENT-PC
    OS version:                                           Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
    Hardware:                                             Z68X-UD3H-B3, Gigabyte Technology Co., Ltd.
    CPU:                                                  GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
    Logical processors:                                   4
    Processor groups:                                     1
    RAM:                                                  8109 MB total
    CPU SPEED
    Reported CPU speed:                                   3410.0 MHz
    Measured CPU speed:                                   2280.0 MHz (approx.)
    Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.
    MEASURED INTERRUPT TO USER PROCESS LATENCIES
    The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the
    signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.
    Highest measured interrupt to process latency (µs):   10308.587998
    Average measured interrupt to process latency (µs):   1.961673
    Highest measured interrupt to DPC latency (µs):       533.311552
    Average measured interrupt to DPC latency (µs):       0.726360
     REPORTED ISRs
    Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.
    Highest ISR routine execution time (µs):              185.646628
    Driver with highest ISR routine execution time:       dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
    Highest reported total ISR routine time (%):          0.138654
    Driver with highest ISR total time:                   dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
    Total time spent in ISRs (%)                          0.191304
    ISR count (execution time <250 µs):                   333205
    ISR count (execution time 250-500 µs):                0
    ISR count (execution time 500-999 µs):                0
    ISR count (execution time 1000-1999 µs):              0
    ISR count (execution time 2000-3999 µs):              0
    ISR count (execution time >=4000 µs):                 0
    REPORTED DPCs
    DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.
    Highest DPC routine execution time (µs):              537.933138
    Driver with highest DPC routine execution time:       nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 340.52 , NVIDIA Corporation
    Highest reported total DPC routine time (%):          0.078815
    Driver with highest DPC total execution time:         USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation
    Total time spent in DPCs (%)                          0.362878
    DPC count (execution time <250 µs):                   1825222
    DPC count (execution time 250-500 µs):                0
    DPC count (execution time 500-999 µs):                10
    DPC count (execution time 1000-1999 µs):              0
    DPC count (execution time 2000-3999 µs):              0
    DPC count (execution time >=4000 µs):                 0
     REPORTED HARD PAGEFAULTS
    Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted
    and blocked from execution.
    NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.
    Process with highest pagefault count:                 chrome.exe
    Total number of hard pagefaults                       1559
    Hard pagefault count of hardest hit process:          939
    Highest hard pagefault resolution time (µs):          249817.816129
    Total time spent in hard pagefaults (%):              0.436725
    Number of processes hit:                              12
     PER CPU DATA
    CPU 0 Interrupt cycle time (s):                       12.339137
    CPU 0 ISR highest execution time (µs):                185.646628
    CPU 0 ISR total execution time (s):                   1.769483
    CPU 0 ISR count:                                      333205
    CPU 0 DPC highest execution time (µs):                537.933138
    CPU 0 DPC total execution time (s):                   2.342733
    CPU 0 DPC count:                                      1394787
    CPU 1 Interrupt cycle time (s):                       5.371672
    CPU 1 ISR highest execution time (µs):                0.0
    CPU 1 ISR total execution time (s):                   0.0
    CPU 1 ISR count:                                      0
    CPU 1 DPC highest execution time (µs):                210.444575
    CPU 1 DPC total execution time (s):                   0.574316
    CPU 1 DPC count:                                      296645
    CPU 2 Interrupt cycle time (s):                       2.886236
    CPU 2 ISR highest execution time (µs):                0.0
    CPU 2 ISR total execution time (s):                   0.0
    CPU 2 ISR count:                                      0
    CPU 2 DPC highest execution time (µs):                166.552786
    CPU 2 DPC total execution time (s):                   0.056599
    CPU 2 DPC count:                                      16722
    CPU 3 Interrupt cycle time (s):                       1.892698
    CPU 3 ISR highest execution time (µs):                0.0
    CPU 3 ISR total execution time (s):                   0.0
    CPU 3 ISR count:                                      0
    CPU 3 DPC highest execution time (µs):                178.875953
    CPU 3 DPC total execution time (s):                   0.382826
    CPU 3 DPC count:                                      117078

  • Windows xp, minidump, applemtm.sys caused crash

    hi, my mbp just crashed in windows xp.
    remained minidump said, applemtm.sys caused crash...
    ^^ i know this info is too little figure out the problem...
    but, is there anyone faced like this one?
    -------- minidump -----
    ATTEMPTEDSWITCH_FROMDPC (b8)
    A wait operation, attach process, or yield was attempted from a DPC routine.
    This is an illegal operation and the stack track will lead to the offending
    code and original DPC routine.
    Arguments:
    Arg1: 00000000, Original thread which is the cause of the failure
    Arg2: 00000000, New thread
    Arg3: 00000000, Stack address of the original thread
    Arg4: 00000000
    Debugging Details:
    *** Kernel symbols are WRONG. Please fix symbols to do analysis.
    * 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: nt!_KPRCB *
    * 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: nt!KPRCB *
    * 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: nt!_KPRCB *
    * 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: nt!KPRCB *
    * 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: nt!_KPRCB *
    * 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: nt!_KPRCB *
    * 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: nt!_KPRCB *
    * Symbols can not be loaded because symbol path is not initialized. *
    * The Symbol Path can be set by: *
    * using the NT_SYMBOLPATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    * Symbols can not be loaded because symbol path is not initialized. *
    * The Symbol Path can be set by: *
    * using the NT_SYMBOLPATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    FAULTING_MODULE: 804d9000 nt
    DEBUGFLR_IMAGETIMESTAMP: 47685ec5
    CUSTOMERCRASHCOUNT: 1
    DEFAULTBUCKETID: WRONG_SYMBOLS
    BUGCHECK_STR: 0xB8
    LASTCONTROLTRANSFER: from 80547c4b to 804fbf0e
    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    bacd3c8c 80547c4b 000000b8 ffffffff 00000202 nt+0x22f0e
    bacd3ce4 b7e06569 00000000 00000000 00000000 nt+0x6ec4b
    bacd3d10 b7e4be4a 8a1711d8 00000000 8a451e08 Wdf01000+0x15569
    bacd3d2c b7fcb53b 8a171290 75dc0430 8a23fbc8 Wdf01000+0x5ae4a
    bacd3d4c b7fcb651 75bae3b8 8a00de70 bacd3da8 applemtm+0x53b
    bacd3d5c b7e261b2 760ef150 75dfc680 bacd3d80 applemtm+0x651
    bacd3da8 b7e26253 b7e57a08 8a203978 89f10ea8 Wdf01000+0x351b2
    bacd3dc0 b7dfd5d3 8a00df97 8a203978 00000000 Wdf01000+0x35253
    bacd3ddc b7dfd68d 01f10ea8 8962e450 bacd3e08 Wdf01000+0xc5d3
    bacd3dec 804f280d 8a46c5a8 8a00de70 89f10ea8 Wdf01000+0xc68d
    bacd3e08 804f36b0 8a46c5a8 8a00de70 8962e450 nt+0x1980d
    bacd3e38 b99210d5 8a00de70 88da4980 8a2d3028 nt+0x1a6b0
    bacd3ea0 b9921d47 895bd170 00000000 8a2d37d8 USBPORT+0xa0d5
    bacd3ed0 b9922944 026e6f44 8a2d30e0 8a2d30e0 USBPORT+0xad47
    bacd3f08 b992413a 8a2d3028 80548abc 8a2d3230 USBPORT+0xb944
    bacd3f34 b993224b 8a2d3028 80548abc 8a2d3028 USBPORT+0xd13a
    bacd3f70 b99323c2 8a2d3028 00000001 8a34a834 USBPORT+0x1b24b
    bacd3f8c ba6b8d54 8a2d364c 6b755044 00000000 USBPORT+0x1b3c2
    bacd3fbc 8a34adb2 8a34a310 b993225c bacd3fd0 sptd+0x11d54
    bacd3fc0 8a34a310 b993225c bacd3fd0 80547e6f 0x8a34adb2
    bacd3fc4 b993225c bacd3fd0 80547e6f 8a2d364c 0x8a34a310
    bacd3fc8 bacd3fd0 80547e6f 8a2d364c 8a2d3028 USBPORT+0x1b25c
    bacd3fcc 80547e6f 8a2d364c 8a2d3028 00000000 0xbacd3fd0
    bacd3fd0 8a2d364c 8a2d3028 00000000 00000000 nt+0x6ee6f
    bacd3fd4 8a2d3028 00000000 00000000 b401ff4a 0x8a2d364c
    bacd3fd8 00000000 00000000 b401ff4a 6803fe95 0x8a2d3028
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    applemtm+53b
    b7fcb53b ?? ???
    SYMBOLSTACKINDEX: 4
    SYMBOL_NAME: applemtm+53b
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: applemtm
    IMAGE_NAME: applemtm.sys
    BUCKET_ID: WRONG_SYMBOLS
    Followup: MachineOwner
    ---------

    My MBP crashed with exactly the same dump. The crashes occurred during a StandBy operation (My MBP crashed regularly but not reproducably while trying to stand by/sleep).
    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Documents and Settings\vas\Desktop\Mini070508-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: srvc:symbolshttp://msdl.microsoft.com/download/symbols
    Executable search path is: c:\windows\i386
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpspsp2rtm.040803-2158
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Sat Jul 5 22:53:49.999 2008 (GMT-7)
    System Uptime: 0 days 22:33:47.814
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck B8, {0, 0, 0, 0}
    * WARNING: Unable to verify timestamp for applemtm.sys
    * ERROR: Module load completed but symbols could not be loaded for applemtm.sys
    Probably caused by : applemtm.sys ( applemtm+53b )
    Followup: MachineOwner
    1: kd> !analyze -v
    * Bugcheck Analysis *
    ATTEMPTEDSWITCH_FROMDPC (b8)
    A wait operation, attach process, or yield was attempted from a DPC routine.
    This is an illegal operation and the stack track will lead to the offending
    code and original DPC routine.
    Arguments:
    Arg1: 00000000, Original thread which is the cause of the failure
    Arg2: 00000000, New thread
    Arg3: 00000000, Stack address of the original thread
    Arg4: 00000000
    Debugging Details:
    CUSTOMERCRASHCOUNT: 1
    DEFAULTBUCKETID: DRIVER_FAULT
    BUGCHECK_STR: 0xB8
    PROCESS_NAME: System
    LASTCONTROLTRANSFER: from 80544c3b to 804f9c12
    STACK_TEXT:
    bace7ccc 80544c3b 000000b8 ffffffff 00000202 nt!KeBugCheck+0x14
    bace7cdc 8054498b bace7d24 88d3b418 bab40120 nt!ScPatchFxe+0x46
    bace7cf0 80502b17 88d3b488 88d3b418 804fad6c nt!KiSwapContext+0x2f
    bace7cfc 804fad6c 00000000 00000000 8a19a4b0 nt!KiSwapThread+0x6b
    bace7d24 b7022569 00000000 00000000 00000000 nt!KeWaitForSingleObject+0x1c2
    bace7d50 b7067e4a 8a0c2a30 00000000 8a37efb0 Wdf01000!FxWaitLockInternal::AcquireLock+0x3a
    bace7d6c b939853b 8a0c2ae8 75e65b78 8a19a480 Wdf01000!imp_WdfWaitLockAcquire+0xc9
    WARNING: Stack unwind information not available. Following frames may be wrong.
    bace7d8c b9398651 75c81210 89eee008 bace7de8 applemtm+0x53b
    bace7d9c b70421b2 764c7c80 7652beb8 bace7dc0 applemtm+0x651
    bace7de8 b7042253 b7073a08 89ad4140 89b38378 Wdf01000!FxRequestBase::CompleteSubmittedNoContext+0x63
    bace7e00 b70195d3 89eee12f 89ad4140 00000000 Wdf01000!FxRequestBase::CompleteSubmitted+0x97
    bace7e1c b701968d 01b38378 88a9ed80 bace7e48 Wdf01000!FxIoTarget::RequestCompletionRoutine+0x195
    bace7e2c 804f053f 8a053350 89eee008 89b38378 Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x35
    bace7e48 804f13e2 8a053350 89eee008 88a9ed80 nt!IopUnloadSafeCompletion+0x1d
    bace7e78 b9843ee5 89eee008 892f5ee0 8a25c028 nt!IopfCompleteRequest+0xa2
    bace7ee0 b9844b57 89bdc4a8 00000000 8a25c7d8 USBPORT!USBPORT_CompleteTransfer+0x373
    bace7f10 b9845754 026e6f44 8a25c0e0 8a25c0e0 USBPORT!USBPORT_DoneTransfer+0x137
    bace7f48 b9846f6a 8a25c028 80545aac 8a25c230 USBPORT!USBPORT_FlushDoneTransferList+0x16c
    bace7f74 b9854fb0 8a25c028 80545aac 8a25c028 USBPORT!USBPORT_DpcWorker+0x224
    bace7fb0 b9855128 8a25c028 00000001 89edc578 USBPORT!USBPORT_IsrDpcWorker+0x37e
    bace7fcc 80544e5f 8a25c64c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
    bace7ff4 805449cb b3f6362c 00000000 00000000 nt!KiRetireDpcList+0x61
    bace7ff8 b3f6362c 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
    805449cb 00000000 00000009 0081850f bb830000 0xb3f6362c
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    applemtm+53b
    b939853b ?? ???
    SYMBOLSTACKINDEX: 7
    SYMBOL_NAME: applemtm+53b
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: applemtm
    IMAGE_NAME: applemtm.sys
    DEBUGFLR_IMAGETIMESTAMP: 47685ec5
    FAILUREBUCKETID: 0xB8_applemtm+53b
    BUCKET_ID: 0xB8_applemtm+53b
    Followup: MachineOwner
    Message was edited by: tourist604

  • Videoprt.sys is giving me high dpc latency. Does anyone know a fix?

    Hiya. I am optimizing my windows-partition. Killing all unessecary drivers, services and processes goes a long way. Also due to sloppy coding in XP kernel, I need to set processes to idle priority, to avoid CPU2 stalling CPU1 when maxed. I have also set win32priorityseparation to 25, which is superficially similar to a low-latency linux-config I did.
    However still, I have a module "Videoprt.sys" which reports 1.5ms DPC latency. (Using RATTv3) Dpc latency checker also reports DPC latency of 1.5ms. I see computers out there with 10uS DPC latency
    Does anyone know a fix for this?
    Peace Be With You.

    Fixed it needed to have a return null;
    this is the code
    if
            (MonthjComboBox.getSelectedItem().equals("") ||
             DayjComboBox.getSelectedItem().equals("") ||
             YearjComboBox.getSelectedItem().equals("")){
            return null;

  • I want Firefox to open to my homepage every time after it crashes. I do not want it to return to the tabs and applications that caused the crash. I am willing to lose information. How do I do this?

    Firefox crashes or seizes up when there are too many tabs and applications open, and causes my computer to crash or seize up. I use task manager to close Firefox or I restart my computer. Then, when Firefox restarts again, it automatically re-opens all the tabs and applications that caused the computer to seize or crash in first place. This is a waste of my time. I want Firefox to reopen to my homepage even if it crashes. I am willing to lose information to have Firefox reopen to a low-memory homepage. How do I do this?

    Set the Integer pref browser.sessionstore.max_resumed_crashes to 0 on the about:config page to get the about:sessionrestore page immediately with the first restart after a crash has occurred or the Task Manager was used to close Firefox.
    * http://kb.mozillazine.org/browser.sessionstore.max_resumed_crashes
    That will allow you to deselect the tab(s) that you do not want to reopen, but will allow to reopen other tabs.
    See:
    * http://kb.mozillazine.org/Session_Restore#Restoring_a_session_after_a_crash
    * http://kb.mozillazine.org/Browser.sessionstore.max_resumed_crashes
    See also:
    * https://wiki.mozilla.org/Session_Restore#Preferences
    To open the <i>about:config</i> page, type <b>about:config</b> in the location (address) bar and press the "<i>Enter</i>" key, just like you type the url of a website to open a website.<br />
    If you see a warning then you can confirm that you want to access that page.<br />
    *Use the Filter bar at to top of the about:config page to locate a preference more easily.
    *Preferences that have been modified show as bold (user set).
    *Preferences can be reset to the default via the right-click context menu if they are user set
    *Preferences can be changed via the right-click context menu: Modify (String or Integer) or Toggle (Boolean)

  • My ipod touch 4g just updates today on itunes and the update caused more trouble than good. My ipod will no longer show me the battery percentage in the top right hand corner and also I am not allowed to drag other applications to the bottom panel.

    My ipod touch 4g just updates today on itunes and the update caused more trouble than good for me. My ipod will no longer show me the battery percentage in the top right hand corner and I am not allowed to drag other applications to the bottom panel. Also my itunes doesn't allow "enable disk use" anymore. Can anyone help? My ipod now says that it's the 4.3.4 version

    - Unjailbroken iPod never showed % battery.  Just the icon.
    - Unjailbroken iPod Touches never had a disk mode.
    - What happens when you try to drag a wiggling app to a empty space in the bottom? Does it move and snap back?

  • TS3579 I found this useful because I did not know about the effect of typing in data and that you could only drag to rearrange the data.  I had typed in data before and this had caused problems but restoring defaults did not cause correct dates to show up

    I found this  (TS3579: If the wrong date or time is displayed in some apps on your Mac Learn about If the wrong date or time is displayed in some apps on your Mac) useful because I did not know about the effect of typing in data and that you could only drag to rearrange the data.  I had typed in data before and this had caused problems but restoring defaults did not cause correct dates to show up in Finder. 

    It sounds like there are a couple things going on here.  First check if you have a successful install of SQL Server, then we'll figure out the connection issues.
    Can you launch SQL Server Configuration Manager and check for SQL Server (MSSQLSERVER) if default instance or SQL Server (other name) if you've configured your instance as a named instance.  Once you find this, make sure the service is started. 
    If not started, try to start it and see if it throws an error.  If you get an error, post the error message your hitting.  If the service starts, you can then launch SSMS and try to connect.  If you have a default instance, you can use the machine
    name in the connection dialog.  Ex:  "COWBOYS" where Cowboys is the machine name.  However, if you named the SQL Server instance during install, you'll need to connect using the machine\instance format.  Ex:  COWBOYS\Romo (where Romo
    is the instance name you set during install).
    You can also look at the summary.txt file in the SQL Server setup error logs to see what happened on the most recent install.  Past install history is archived in the log folder if you need to dig those up to help troubleshoot, but the most
    recent one may help get to the bottom of it if there is an issue with setup detecting a prior instance that needs to be repaired.
    Thanks,
    Sam Lester (MSFT)
    http://blogs.msdn.com/b/samlester
    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click
    "Mark as Answer" and
    "Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

  • The upgrade to Firefox 4 is causing massive problems with my computer. How do I uninstall it and go back to using the previous version?

    Firefox 4 is absolutely awful - it is causing massive problems with my computer. How do I uninstall Firefox 4 and go back to the previous version of Firefox?

    According to the instructions given on the Norton Community forum under "Other Norton Products/Comcast-Customers - Norton Toolbar Problem in Firefox 10", I have done everything necessary. And I do have a Norton toolbar (Safe Web and Identity Safe) when I open Firefox 10. As was mentioned in the previous posts here, you need to run manual LiveUpdate then reboot until you have version 5.2.0.13. Then reboot and run manual LiveUpdate again and reboot once more. One thing that I noticed is that Norton never told me that it had updated the patch for Firefox 10, so I didn't know. I guess if you have the toolbar when you run Firefox 10, then you have done it all.

Maybe you are looking for

  • How to payment a little for a customer invoice.

    Hi all ! I have a request, help me please ! I enter a customer invoice with value 1000 (USD) from SAP T-Code FB70. When customer payment a little ( 400 USD ) for this invoice, I will post incoming invoice with value 400 USD from T-Code F-28. If value

  • Close an entry document

    Hi experts. When you want to close an entry document from the WAE02 transaction, is there any option to check the status of the disposal document assigned to the entry document and not allow to close it if the disposal document is not canceled? Thank

  • Shifting from the second page printed

    hi, I create a report with reports10g . the size of the output paper is 15.2 * 21 cm. the papers used are continuous paper with matrix printer . I have a problem shifting from the second page printed. how to solve this problem? thank you in advance

  • Migrating Oracle BI Presentation Catalog between environments ?

    Background: OBIEE 11.1.1.6.2 BP1 installed Platform: Windows 2008 R2 server Task: I am confronted with the task of migrating the RPD and Web catalog from System Test to Integration and then Integration to Production Request: Can anyone point me to a

  • Netsh store=persistent resets on reboot

    I am running Windows 7 with a WiFi connection to my router, and I'm connecting a Raspberry Pi via an Ethernet cable. Network sharing is turned on, and to some extent this setup works. I can ping any location (e.g. bing.com) from the Pi. I can open a