Co-author and topic starter: Admin writhziden
Please use the Windows Performance Analyzer (WPA) to provide us with your trace file.
You can check the original tutorial for Windows 7: How to Diagnose and Fix High DPC Latency Issues with WPA (Windows Vista/7/8) (click).
By the way, very similar steps can be used with the Windows 10 (and they are explained, with pictures, in following steps, at points 1 and 2).
Please use the Windows Performance Analyzer (WPA) to provide us with your trace file.
You can check the original tutorial for Windows 7: How to Diagnose and Fix High DPC Latency Issues with WPA (Windows Vista/7/8) (click).
By the way, very similar steps can be used with the Windows 10 (and they are explained, with pictures, in following steps, at points 1 and 2).
- Download and install the Windows 10 SDK - Software Development Kit (click).
Currently it's named winsdksetup.exe, size 1.13MB; but this can change when newer versions are released.
Check the instructions I made for you:
Read More:Click Download, save/run it and you'll see for first Specify location: leave it default or choose your preferred location, then click Next.Then you'll see Windows kits privacy: Niemiro said "you may opt in to CEIP if you so wish - it is not necessary, but you may wish to do so". Then click Next.Then you'll see License agreement: click Accept.Then you'll see Select the features you want to install: select only Windows Performance Toolkit and click Install.It will download and install the WinPerf. toolkit.Set the path environment variable adding the windows performance toolkit path: go to Control Panel\System and Security\System - advanced system settings, (click yes in the UAC window that should appear if you didn't disable it), click environment variables, double-click path under the system variables pane (or click it once and then click edit), and add C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\
If you have chosen another path in specify location, you should provide THAT ONE.
You can generate a new trace with this command, from an elevated command prompt window:Code:xperf -on DiagEasy
Read More:- Right-click windows start, click command prompt (admin), click yes on the user account control window that should appear (if you didn't disable UAC)
- click start, click windows system, right-click the command prompt in the list, click run as administrator, click yes on the user account control window that should appear (if you didn't disable UAC)
- click start, type directly cmd (or prompt), right-click the command prompt in the list of results, click run as administrator, click yes on the user account control window that should appear (if you didn't disable UAC)
- The same of above is valid if you do it in the searchbox (Cortana)
- click start, type directly cmd (or prompt), (the command prompt should already be the first hit in the list of results), press and keep pressed (hold) ctrl + shift Keys on your keyboard, then press enter, click yes on the user account control window that should appear (if you didn't disable UAC)
- The same of above is valid if you do it in the searchbox (Cortana)
Code:xperf -d "%userprofile%\Desktop\trace.etl"
Code:xperf -d "$env:userprofile\Desktop\trace.etl"
Zip (not RAR, please) the trace.etl up.
Check MicroSoft Support How-To: Zip and unzip files (click) if you don't know how to zip files.
- Download and run the BSOD Collection Application.
- Sysnative BSOD Collection (Dump files + System Files) Application Download LINK
For more information, read here:Read More:Explanation of the contents of the Sysnative output file: Sysnative BSOD Dump + File Collection App [Detailed] Output Explained
The Sysnative BSOD Dump + System File Collection App does not get installed (it is a stand-alone EXE) nor does it make any changes to the registry.
It only creates the SysnativeFileCollectionApp output folder + a zipped version, both located in Documents folder.
You can delete them at any time, but we suggest that you wait until our work together is completed before doing so.
If you have any questions or run into any problems with the app, please post IN YOUR THREAD about such issues/with the questions.
We, of course, are happy to answer any questions that you have or to address any concerns.
This app (including former versions of it) has been downloaded and executed in excess of one million times since the original version was conceived and released in early 2008 and is completely safe.
The app is now digitally signed by Sysnative Forums Software, Ltd.
This app has many other troubleshooting capabilities than just to solve BSODs, so you may see a staff member requesting an OP to run it even though the OP is not experiencing any BSODs.
- Save it to DOCUMENTS folder.
It's usually in C:\Users\Your-Windows-Profile-Name\Documents.
Or "%userprofile%\documents".
- Run the app
Double-click on the downloaded EXE file.
Output:
- New folder created in Documents: SysnativeFileCollectionApp
- A zipped version: SysnativeFileCollectionApp.zip.
Please be patient until it finishes.
For more information, read here:Read More:Please note that the app averages just a few minutes to run on most systems.
In other systems, it may take as long as 10-15 minutes to run.
You'll notice on your Taskbar that there are numerous CMD screens.
This is normal as the app runs Windows EXE files, custom batch script files as well as custom VBS script files and each one requires its own CMD prompt (screen).
Windows Explorer should open and highlight the zipped folder upon completion of the app.
Furthermore, on occasion, the CMD screen will read "waiting for system info" for over 15 minutes.
This is due to excess msinfo32/ WERCON entries.
If this occurs, simply bring up Task Manager or SysInternals Process Explorer and "kill" the Sysnative app.
- Sysnative BSOD Collection (Dump files + System Files) Application Download LINK
- Retrieve System Information, using speccy.Read More:
- Download Speccy x64 portable 1.32.740 (click)
If you need the 32bit version: Speccy x86 (NON-portable) - Unzip/decompress it and put it on your desktop.
- When the program opens, it will retrieve some information regarding your system.
- Once it's done, select the File menu and choose Publish snapshot. Answer Yes to the confirmation message.
- On the next screen that comes up, choose the Copy to Clipboard button and paste this link in your next reply.
- Download Speccy x64 portable 1.32.740 (click)
- Create a new thread HERE (if you do not have one yet) and attach the log files.
In your new thread you will post the following requested information:
- Provide the speccy link you got in the clipboard at previous point.
- Provide answers for (answer the best that you can)Read More:
- Write a brief description of your problem.
You can also include the steps you tried. - OS ? (Windows 10, 8.1, 8, 7, Vista)
- x86 (32bit) or x64 (64bit)?
- (Only for xp, vista, 7) Service pack?
- What was original installed OS on system?
- Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
- Age of system? (hardware)
- Age of OS installation?
- Have you re-installed the OS?
- System Manufacturer?
- Laptop or Desktop?
- Exact model number (if laptop, check label on bottom)
- MotherBoard - (if NOT a laptop)
- CPU
- RAM (brand, EXACT model, what slots are you using?)
- Video Card
- Power Supply - brand & wattage (if laptop, skip this one)
- Is driver verifier enabled or disabled?
- What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth)
- Are you using proxy, vpn, ipfilters or similar software?
- Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software)
- Are you currently under/overclocking? Are there overclocking software installed on your system?
- Write a brief description of your problem.
- You need to use a file sharing service to upload the zipped trace.etl and the SysnativeFileCollectionApp.zip.
Then provide the links that are generated by the hosting service in your post.
Several file sharing options are listed below (they are clickable links), however you are not limited to these:
- Provide the speccy link you got in the clipboard at previous point.
- While waiting for a reply.
- Run HDD Diagnostics: Hard Drive (HDD) Diagnostics (Sea Tools for DOS) & SSD Test
Check also next posts in that thread.
- Test RAM: Test RAM with PassMark MemTest86
- Run HDD Diagnostics: Hard Drive (HDD) Diagnostics (Sea Tools for DOS) & SSD Test
Last edited: