[SOLVED] BSODs and DPC Latency issue.. - Windows 7 x64

E

eox08

Member
Joined
Jun 6, 2014
Posts
21
Hello everyone, I am having some pretty bizarre issues dealing with Latency and audio cracks. I am running the Latency Mon DPC checker and I see a few different drivers with a high execution amount. Now, I am not familiar with this side of the computer talk so I am hoping I can reach out to you in the hopes that someone can help me out here. The following attachments are my computer specs and a screenshot of the results from the Latency Mon Analysis.

Latency Mon Analysis 1.jpgLatency Mon Analysis 2.jpgLatency Mon Analysis 3.jpg
 
Re: DPC Latency issue..

Welcome to Sysnative!

My immediate suspicion lies with the asmtxhci.sys, Super Speed USB Controller, update the drivers and test, if that fails, connect your USB devices to a standard USB(2/3) port and test again.
 
Re: DPC Latency issue..

Dear,

To properly troubleshoot issues with high/frequent DPCs/IRPs, we require a XPERF trace. Please follow these steps to generate one:

  1. Download Windows Software Development Kit (SDK) for Windows and run the setup.
  2. Select Windows Performance Toolkit feature (all the others can be unchecked) and proceed with the download/installation.
  3. Once the installation finishes, open an elevated Command Prompt by right-clicking on CMD.EXE shortcut in your start menu and selecting Run As Administrator from the context menu.
  4. Type the following command, which will start tracing, in the Command Prompt window you just opened:
    Code: 
    xperf -on PROC_THREAD+LOADER+PROFILE+INTERRUPT+DPC+DRIVERS+POWER+IDLE_STATES -stackwalk Profile -BufferSize 1024 -MinBuffers 256 -MaxBuffers 256 -MaxFile 256 -FileMode Circular
    If you see a yellow warning "xperf: warning: This system is not fully configured for x64 stack tracing" after running the above command, please complete these extra steps (otherwise, proceed to the step #5):
    Read More:
    If you see a red error "xperf: error: NT Kernel Logger: A device attached to the system is not functioning. (0x1f)" after running the above command, please complete these extra steps (otherwise, proceed to the step #5):
    Read More:

    If you see a red error "xperf: error: NT Kernel Logger: Cannot create a file when that file already exists. (0xb7)", please do the following (otherwise, proceed to the step #5):
    Read More:
  5. Perform some activities with your computer for few minutes, making sure the issues you reported are reproduced.
  6. Run the following command, which will stop the tracing, in the command prompt window you already have opened:
    Code: 
    xperf -stop -d C:\CPU.etl
  7. Compress file C:\CPU.etl
  8. Upload the compressed file to a file sharing service (e.g. OneDrive or DropBox).
  9. Share the download link here.
Thank you.
 
Re: DPC Latency issue..

No sir, I don't believe I have anything hooked up for video via USB. I have an External HDD, Mouse, Keyboard, and a Midi Controller (Native Instruments Maschine) hooked up in the USB slots. Forgive me if I am not answering your question entirely right. This side of computers is new to me. But when I was running that test I had Cocko's Reaper and Propellerhead Reason running at the time.
 
Re: DPC Latency issue..

Also, how can I really test out asmtxhci.sys? Also, lately I have been getting the BSOD quite commonly. Would the XPERF trace I provided in the dropbox link show what is causing that crash?
 
Re: DPC Latency issue..

Okay, I am getting right on reading that thread. Will post the information needed in just a few minutes. Thank you so much Satrow!
 
Re: DPC Latency issue..

Ok, we don't have any memory dumps there, my guess is that you have some kind of cleanup software running at boot, or you have run it manually. Please turn that off/don't use it :)

The only BSODs logged since mid-January that I can see are all X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC = STOP 0x00000101: CLOCK_WATCHDOG_TIMEOUT
Usual causes: Device driver, BIOS bug, hardware defect (see Significant Posts section below)
<SNIP>

Significant Posts: Win 7 A Clock Interrupt... BSOD (101 Error) - Windows 7 Help Forums
These types of error messages are relatively simple, from a certain viewpoint: as frequently happens during normal processing, one core (processor) attempted to get the attention of another core, in order to synchronise their activites with respect to an operation that requires processor coordination. Described using "official" terminology:

"CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts."

The trigger for the crash is the "sender/requestor" processor going "wtf? why is there still no response after almost half a second?!?" Those inter-processor interrupts (IPIs) are some of the most critical activity imaginable, and an unrequited IPI is absolutely lethal - hence the crash.

AMD procs had known issues which manifested themselves in this manner under Vista and Windows 7. There were/are many possible problem permutations, some solved through BIOS updates, and some necessitating fiddling with the "Translation Lookaside Buffer" (TLB), as per torrentg's suggestion to look up 0x101 and AMD and TLB.

Your real aim is to give yourself the best possible chance of discovering a software cause for the target processor to go unresponsive, and thereby avoid the most obvious conclusion - that the processor is periodically unresponsive because of hardware-level defects

I can confidently tell you that the browsers, apps, and games cannot be the root cause of this problem, even though I don't doubt your observation that the operation of certain software seems to more easily trigger the crash. What you're looking for will be in one of the following categories:

a) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...)
- H2SO4
Click to expand...
This BSOD type cannot be successfully analysed without a full memory dump, set your machine to create full memory dumps -> Winkey+Pause/Break > Advanced system settings > Startup and Recovery Settings button > System failure > Write debugging information - change this to full memory dump.

Hopefully, there's a driver behind all this, we'll wait for the ETL analysis from TomasD.
 
Re: DPC Latency issue..

Okay, I went in to change the following settings for the memory dump. I don't see an option for a complete, or full memory dump. The drop down menu only gives me the following options: None, Small memory dump (256kb) and Kernel Memory dump. The last option is what was already selected. I do run the Ccleaner, so i am wondering if that has cleared out the memory dump information
 
Re: DPC Latency issue..

<From here>

Checks needed to ensure the computer is set correctly.

Conditions for creating memory dumps include:
For dumps to be produced. . .
â–ª Page file must be on OS drive
â–ª Page file base allocation size must be > than installed physical RAM
â–ª Windows Error Reporting (WER) system service should be set to MANUAL
â–ª Set page file to system managed, OS drive
Click to expand...
(Your WER settings appear to be fine, plenty of WER logs are being created.)

To view page file settings, bring up an Admin cmd/DOS screen & paste this applet -

Or, click on START; paste the applet into the StartSearch box -


Code: 
SystemPropertiesPerformance.exe /pagefile
Click to expand...

ASSURE THAT CCLEANER IS NOT DELETING DUMPS
CCLEANER | Cleaner icon | Windows tab | System category |
Uncheck Memory Dumps
Click to expand...

See also A hotfix is available that enables a Windows 7-based or Windows Server 2008 R2-based computer to create a memory dump file without a page file
 
Re: DPC Latency issue..

Ah ha! Ccleaner was infact clearing out the memory dump files. I unchecked the box. Now, I suppose I have to wait on another BSOD to happen in order to get the information needed
 
Re: DPC Latency issue..

Hopefully, Tomas will chip in soon with the results of the ETL analysis, that'll likely indicate if it's a driver issue, if not - then it's probably hardware and we'll need a full memory dump to get more details. Even then, it's likely to be impossible to pin down the hardware item with 100% accuracy.
 
Re: DPC Latency issue..

Having had a look at your cpu.etl file, I would like you to completely uninstall - at least for a short test period - Reaper Digital Audio Workstation. Although your DPC/ISR results actually look fine, reaper.exe (+reaper_host32.exe and reaper_host64.exe) are all hammering the CPU pretty hard.

Also, although it's not really flagging as a problem CPU usage wise or in any other way, do you know what reason.exe is?

Richard
 
I moved this to the correct section, it was in the tutorials section for some reason?

Stephen
 
Re: DPC Latency issue..

satrow said:
Hopefully, Tomas will chip in soon with the results of the ETL analysis, that'll likely indicate if it's a driver issue, if not - then it's probably hardware and we'll need a full memory dump to get more details. Even then, it's likely to be impossible to pin down the hardware item with 100% accuracy.
Click to expand...

The thing is that the PC uses external MIDI controller/sound card. I've seen many cases like this and the issues are usually pointing to USB/Firewire drivers in these cases, making them extremely difficult to troubleshoot. In cases when the computer has very specific hardware configuration (i.e. it is used for audio editing/mastering), I would strongly recommend the OP to start from the forums dedicated for people using similar configuration, as there are usually quite a lot of tips on improving the latency (usually involving custom audio drivers or tweaking buffering settings). Few examples:

 
Also, try connecting to the Intel USB ports, not the ASMedia Xhci USB ports, it might make a difference.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top