[SOLVED] DPC issues PLEASE HELP, dump file - Windows 8.1 x64

Joined
Jan 31, 2015
Posts
10
I'm trying to eliminate the audio poping, cracking, and visual lagging that is happening on my computer while on the desktop and while in games. I've identified some of the drivers who have the highest latency however two of them are by Microsoft Corporation which are suppose to update with windows update and I've updated windows so I don't know what to do.

I started at https://www.sysnative.com/forums/wi...ues-with-wpa-windows-windows-vista-7-8-a.html I tried step II but the picture examples that they show don't look like what I'm seeing in Windows Performance Toolkit (it didn't launch itself, I had to), and when I finally get the .etl file, the DPC CPU Usage isn't in there, I CAN'T FIND IT.

So I used latencyMon and found out what driver is causing these issues; when I'm just on my desktop or watching a youtube video and not gaming (which is most of the time because it's unbearable when gaming) the driver is USBPORT.sys and when I'm gaming it's dxgkml.sys. I went to the Driver Reference which identified them as Usbport 1.1 & 2.0 Port Driver and DirectX Graphics Kernel respectfully, but I already knew that because LatencyMon told me what they were. However their sources are windows update and my OS IS up to date.

I understand that both of those are Microsoft drivers but I didn't run the verifier on any driver by "Microsoft Corporation" because the tutorial on how to use Verifer said TO NOT verify driver with that publisher name. Either way my Computer BSOD and I doubt that those two drivers are the only ones that are the problem.

Here is the dump file after running Driver Verifier.
 

Attachments

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)

This is the general bug check code for fatal errors found by Driver Verifier.

Code:
0: kd> .bugcheck
Bugcheck code 000000C4
Arguments 00000000`000000f6 00000000`000001bc ffffe000`70b80080 fffff801`87f44766

The reason for the bug check according to the 1st parameter was a driver that performed an incorrect reference.

Code:
// Current process address
0: kd> !process ffffe00070b80080

PROCESS ffffe00070b80080
    SessionId: none  Cid: 1aec    Peb: 7ffdf000  ParentCid: 15c4
    DirBase: 1643f3000  ObjectTable: ffffc00103c62140  HandleCount: <Data Not Accessible>
    Image: PEUpdater.exe
    VadRoot ffffe000736231d0 Vads 89 Clone 0 Private 357. Modified 4527. Locked 0.
    DeviceMap ffffc000fa611e80
    Token                             ffffc00103c62440

The process was PEUpdater.exe, in relation to Asus bloatware.

Code:
0: kd> k
Child-SP          RetAddr           Call Site
ffffd000`278f9368 fffff802`a1f126b0 nt!KeBugCheckEx
ffffd000`278f9370 fffff802`a1f17fa0 nt!VerifierBugCheckIfAppropriate+0x3c
ffffd000`278f93b0 fffff802`a1dd83cb nt!VfCheckUserHandle+0x1b8
ffffd000`278f9490 fffff802`a1c71575 nt! ?? ::NNGAKEGL::`string'+0x1d18b
ffffd000`278f9530 fffff802`a1f248e9 nt!ObReferenceObjectByHandle+0x25
ffffd000`278f9580 fffff801`87f44766 nt!VerifierObReferenceObjectByHandle+0x49
ffffd000`278f95c0 00000000`00000000 AsUpIO+0x1766

The driver that caused the incorrect reference was AsUpIo.sys, Asus related. We can see verifier checked the user handle, it referenced it instead as kernel-mode, therefore verifier threw the bug check.

Code:
0: kd> lmvm AsUpIO
start             end                 module name
fffff801`87f43000 fffff801`87f4a000   AsUpIO   T (no symbols)           
    Loaded symbol image file: AsUpIO.sys
    Image path: \SystemRoot\SysWow64\drivers\AsUpIO.sys
    Image name: AsUpIO.sys
    Timestamp:        Mon Aug 02 22:47:59 2010

2010, really old. No doubt it's referencing improperly. Update it if you'd like, although I just recommend getting rid of all Asus bloatware. It's completely unnecessary.
 
Last edited:
I uninstalled the Asus software, I'm also noticing audio anomalies and input lag as well as brief moments when I'm watching a video and it will stop unless I move my mouse. I uninstalled chrome and reinstalled it however I am still getting these issues, note that these were also occurring yesterday when I was verifying drivers. I have not tried gaming yet but I want to verify drivers again, I'm still not testing "Microsoft Corporation" drivers, but I'll cross that bridge when I get to it. I'll post the dump file shortly.
 
It was stuttering when it was off. Unfortunately my computer froze I'm not sure when it did not show a stop error (bsod) so I'm not sure if it crashed or not my cursor could not move but I did get the file I'll post it.
 

Attachments

DRIVER_POWER_STATE_FAILURE (9f)

This bug check indicates that the driver is in an inconsistent or invalid power state.

Code:
0: kd> .bugcheck
Bugcheck code 0000009F
Arguments 00000000`00000003 ffffe000`44d88060 fffff802`1643e8e0 ffffe000`450fbb40

Code:
0: kd> !irp ffffe000450fbb40
Irp is active with 7 stacks 5 is current (= 0xffffe000450fbd30)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [ 16, 0]   0  0 ffffe00044d88060 00000000 fffff8009d4271a4-ffffe000450af5a0    
           \Driver\amd_sata    CLASSPNP!ClasspPowerUpCompletion
            Args: 00000000 00000000 00000000 00000002

Code:
0: kd> lmvm amd_sata
start             end                 module name
fffff800`9cab6000 fffff800`9cad3000   amd_sata T (no symbols)           
    Loaded symbol image file: amd_sata.sys
    Image path: \SystemRoot\System32\drivers\amd_sata.sys
    Image name: amd_sata.sys
    Timestamp:        Mon Sep 17 04:40:39 2012

Did you not update your chipset drivers when you installed Windows? 2012 is pretty old for the SATA driver.

Motherboards - CROSSHAIR V FORMULA-Z - ASUS
 
Code:
[COLOR=#ff0000]BugCheck 9F[/COLOR], {[COLOR=#0000cd]3[/COLOR], [COLOR=#ff8c00]ffffe00044d88060[/COLOR], fffff8021643e8e0, [COLOR=#008000]ffffe000450fbb40[/COLOR]}

Probably caused by : [COLOR=#ff0000]amd_sata.sys[/COLOR]

It seems that a IRP has become stuck, and caused the system to timeout. This is usually implemented by Watchdog checking.

Code:
0: kd> [COLOR=#008000]!irp ffffe000450fbb40[/COLOR]
Irp is active with 7 stacks 5 is current (= 0xffffe000450fbd30)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [ 16, 0]   0  0 ffffe00044d88060 00000000 fffff8009d4271a4-ffffe000450af5a0    
           \Driver\amd_sata    CLASSPNP!ClasspPowerUpCompletion
            Args: 00000000 00000000 00000000 00000002
[COLOR=#ff0000]>[ 16, 2][/COLOR]   0 e1 ffffe000450af060 00000000 fffff8009c98e564-00000000 Success Error Cancel pending
           \Driver\disk    partmgr!PmPowerCompletion
            Args: 00051100 00000001 00000001 00000002
 [ 16, 2]   0 e1 ffffe000450afb20 00000000 fffff80214b36f4c-ffffe000450f9c18 Success Error Cancel pending
           \Driver\partmgr    nt!PopRequestCompletion
            Args: 00051100 00000001 00000001 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-ffffe000450f9c18    

            Args: 00000000 00000000 00000000 00000000

I'm usually quite hesistant about Stop 0x9F's now, since typically the driver being blamed isn't always the correct one, based upon how IRPs are completed in Windows. The lower bus related drivers are usually the only ones which can handle power related IRPs, like the IRP which has become stuck.

Code:
0: kd> [COLOR=#008000]lmvm amd_sata[/COLOR]
start             end                 module name
fffff800`9cab6000 fffff800`9cad3000   amd_sata T (no symbols)           
    Loaded symbol image file: amd_sata.sys
    Image path: \SystemRoot\System32\drivers\amd_sata.sys
    Image name: amd_sata.sys
    Timestamp:        [COLOR=#ff0000]Mon Sep 17 09:40:39 2012[/COLOR] (5056E207)
    CheckSum:         000198AD
    ImageSize:        0001D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I would suggest checking for any chipset updates for your motherboard.

Code:
0: kd> [COLOR=#008000]!sysinfo machineid[/COLOR]
Machine ID Information [From Smbios 2.7, DMIVersion 39, Size=2521]
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = 1901
BiosReleaseDate = 12/24/2013
SystemManufacturer = To be filled by O.E.M.
SystemProductName = To be filled by O.E.M.
SystemFamily = To be filled by O.E.M.
SystemVersion = To be filled by O.E.M.
SystemSKU = SKU
BaseBoardManufacturer = [COLOR=#ff0000]ASUSTeK COMPUTER INC[/COLOR].
BaseBoardProduct = [COLOR=#ff0000]CROSSHAIR V FORMULA-Z[/COLOR]
BaseBoardVersion = Rev 1.xx
 
I could have sworn that I had updated these drivers, I remember downloading 900 MB for the chipset but I checked the device manger and it is from 2012 (I don't even see it listed in the driver page for my motherboard). I'm downloading it now it'll take some time I'll install it then run verifier again.
 
My computer crashed but it didn't leave a dmp file I don't want to run verifier again, but if I have to I'll run it tomorrow. I'm still getting a input lag and the audio anomalies that accompany them, dpclat is still painting my latency with a bunch of red bars and latencyMon still says that USBPORT.sys is the problem driver even though I've updated my chipset driver (WHICH WAS A LOT HARDER THAN IT SHOULD HAVE BEEN, but it's updated now). What can I do?
 
Without a dump file there's not really much we can say. We can look at traces for the DPCs, etc, but you're crashing, so it's better to just look at the crash dumps.
 
The file is around 800 MB and it says the last time it was modified was 12:00 PM 2/1/2015 so it wouldn't have the information but I'll try to post it anyway. I'll run the verifier but the reason I don't like it is because I have to wait for the computer to crash, freeze or run a stop error (bsod) and I don't know how long that will be. But I'll try it again if that really is the only why to diagnose this problem but they told me that I shouldn't run the MS driver but shouldn't I because they are the ones causing the most latency? Also I can't upload the file even when it's compressed it's too big.
 
I'll run the verifier but the reason I don't like it is because I have to wait for the computer to crash, freeze or run a stop error (bsod) and I don't know how long that will be.
You'd be doing this regardless of having verifier enabled or not as far as crashes go.



1.
Compress the kernel-dump and upload it to OneDrive, paste the link here.

2. Your verifier flags should look like this:


1.
Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (only on Windows 7 & 8/8.1)
- DDI compliance checking (only on Windows 8/8.1)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

3. MSFT drivers are not actually causing high latency. It's either a hardware issue or a 3rd party driver interfering. Likely the latter, but who knows at this point till we see more dumps.
 
I left my computer on overnight but when I tried to wake it my inputs didn't do anything and there still wasn't a dmp file that was current so... I don't know what to do. I'll post a link for the memory file but that file is also not current. I'm thinking I should probably just reinstall the OS but the thing is I've already done that to try and fix this but it didn't and now it's just worse. https://onedrive.live.com/redir?resid=187BD76C6AB038A5!1118&authkey=!AOYo9EWTlBVIjCk&ithint=file,zip
 
That kernel-dump is of the 0x9F we've seen regarding amd_sata.sys, so it won't be of much extra use unfortunately. If no dump was generated, can you check the following and ensure yours is set to match?


1.
Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

4. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

If yes, and still no crash dumps, this is likely a hardware problem.
 
I've reinstalled my OS and took apart all the pieces of my computer and put them back together (CPU included), it would appear that window 8.1 it just has high latency I'm not getting the high amounts that I was before but I'll be sure to be careful before install drivers. I've taken a "if it's not broken don't fix it" mindset this time, I only update the graphics and chipset drivers, and avoiding hardware programs that I don't need that might cause instabilities. It's unfortunate that we weren't able to diagnose the root problem but at least it's working now.
 

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

Back
Top