Which settings should I use for OCCT?
Vanessa
(18 items) |
|
Vanessa
(18 items) |
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Can anyone help me read these minidump files?
Featured Sponsors
Recent Reviews
-
Price reviewed: £16 After reviewing the Anker 8000DPI Gaming mouse - I was intrigued how the 2000DPI one compared. Here is my review for the 8K DPI one:...
-
£10, 2000 DPI, excellent design, elegant and a tiny USB for connectivity. What else could you ask for? This mouse is brilliant in all aspects! Really love using it as a on-the-go mouse! The USB...
-
This is my "quick review", I'll go more in-depth soon... Been running this kit for some time, having originally purchased it in late March/early April of 2012. When I bought it, I expected a kit...
-
This is a very nice and fast CPU... I see various reports on temperature, but mine runs cool at 4.5 GHz and rock solid doing BOINC tasks 24/7. Nothing but good things to say about this processor. I... -
Story : You play as the legendary beast hunter Van Helsing trying to hunt monsters, help the innocent civilians and hunt down the menace upon Borgovia. Graphics : As a game similar...
Can anyone help me read these minidump files? - Page 3
post #22 of 98
5/6/12 at 3:37pm
- Joined: Apr 2008
- Location: Guadalajara, Mexico
- Posts: 3,402
- Rep: 93 (Unique: 81)
- Select All Posts By This User
Honestly, IDK. OCCT kills the video signal and causes a BSOD, but Furmark passes the GPU test just fine 
|
Vanessa
(18 items) |
| CPU | Motherboard | Graphics | RAM |
|---|---|---|---|
| Intel Core i5 2500k | Gigabyte GA-Z77-D3H | EVGA GTX 660ti SuperClocked | PNY Optima MD4096SD3-1333 |
| Hard Drive | Hard Drive | Hard Drive | Optical Drive |
| Western Digital WD500AAKX 500GB SATA | Seagate ST2000DL003 | ADATA AS510S3-120GM-C 120GB SSD | Lite-On iHAS224-06 |
| Cooling | OS | Monitor | Monitor |
| Cooler Master Hyper 212+ | Windows 7 Ultimate x64 | Samsung B1930 | Benq G92HDA |
| Power | Case | Audio | |
| Corsair TX750 750W PSU | Gray Acteck Octanux | Logitech Z623 2.1CH | |
| View all | |||
|
Vanessa
(18 items) |
| CPU | Motherboard | Graphics | RAM |
|---|---|---|---|
| Intel Core i5 2500k | Gigabyte GA-Z77-D3H | EVGA GTX 660ti SuperClocked | PNY Optima MD4096SD3-1333 |
| Hard Drive | Hard Drive | Hard Drive | Optical Drive |
| Western Digital WD500AAKX 500GB SATA | Seagate ST2000DL003 | ADATA AS510S3-120GM-C 120GB SSD | Lite-On iHAS224-06 |
| Cooling | OS | Monitor | Monitor |
| Cooler Master Hyper 212+ | Windows 7 Ultimate x64 | Samsung B1930 | Benq G92HDA |
| Power | Case | Audio | |
| Corsair TX750 750W PSU | Gray Acteck Octanux | Logitech Z623 2.1CH | |
| View all | |||
post #24 of 98
5/6/12 at 3:43pm
- Joined: Apr 2008
- Location: Guadalajara, Mexico
- Posts: 3,402
- Rep: 93 (Unique: 81)
- Select All Posts By This User
It just did it. The monitors lost video completely and the fan started spinning at 100%. I pushed the reset button, then booted. windows told me there was a BSOD.
http://dl.dropbox.com/u/21018119/Minidumps%202.zip
Edited by Icekilla - 5/6/12 at 3:46pm
http://dl.dropbox.com/u/21018119/Minidumps%202.zip
Edited by Icekilla - 5/6/12 at 3:46pm
|
Vanessa
(18 items) |
| CPU | Motherboard | Graphics | RAM |
|---|---|---|---|
| Intel Core i5 2500k | Gigabyte GA-Z77-D3H | EVGA GTX 660ti SuperClocked | PNY Optima MD4096SD3-1333 |
| Hard Drive | Hard Drive | Hard Drive | Optical Drive |
| Western Digital WD500AAKX 500GB SATA | Seagate ST2000DL003 | ADATA AS510S3-120GM-C 120GB SSD | Lite-On iHAS224-06 |
| Cooling | OS | Monitor | Monitor |
| Cooler Master Hyper 212+ | Windows 7 Ultimate x64 | Samsung B1930 | Benq G92HDA |
| Power | Case | Audio | |
| Corsair TX750 750W PSU | Gray Acteck Octanux | Logitech Z623 2.1CH | |
| View all | |||
|
Vanessa
(18 items) |
| CPU | Motherboard | Graphics | RAM |
|---|---|---|---|
| Intel Core i5 2500k | Gigabyte GA-Z77-D3H | EVGA GTX 660ti SuperClocked | PNY Optima MD4096SD3-1333 |
| Hard Drive | Hard Drive | Hard Drive | Optical Drive |
| Western Digital WD500AAKX 500GB SATA | Seagate ST2000DL003 | ADATA AS510S3-120GM-C 120GB SSD | Lite-On iHAS224-06 |
| Cooling | OS | Monitor | Monitor |
| Cooler Master Hyper 212+ | Windows 7 Ultimate x64 | Samsung B1930 | Benq G92HDA |
| Power | Case | Audio | |
| Corsair TX750 750W PSU | Gray Acteck Octanux | Logitech Z623 2.1CH | |
| View all | |||
post #26 of 98
5/6/12 at 4:01pm
Ah, yep... here we go. 116 TDR video failure bugcheck. It's likely at this point hardware related. There are a multitude of things that can cause this specific bugcheck. Before going into that, I should mention this:
NOTE: If overclocking, please reset the system to default values while troubleshooting it. This includes CPU, RAM, GPU overclocking. You're more than welcome to put your stocks back to clock after we've diagnosed your issues!!!!!
The first thing I recommend doing if overclocks aren't the issue is fully uninstalling and reinstalling your AMD video card drivers, as a bad driver installation can cause 116 bugchecks, especially since the culprit is being pointed to atikmpag.sys (ati video card drivers). If these issues started happening after a driver update, rollback the video card drivers you installed to an earlier version that worked previously without issue.
If drivers do not help, your issue may be heat related, inadequate cooling, dust buildup in the fans or pci-e slot, so make sure your rig is being cooled adequately.
Run Furmark to test your video card to ensure that the card(s) itself is running as intended:
The following hardware issues can cause a TDR event:
Memtest download to test your RAM: http://www.memtest86.com/
To "reset" the pagefile, follow these instructions:
Run System File Checker:
- Over heating of GPU or CPU again resulting in corrupt data being communicated. (Point a house fan at the video card, take temperature readings from the card with an IR detector (or your finger - but be very, very careful!!!)
- GPU failure due to any sort of issue from insufficient power(VERY common) to heat. (check the power leads, use a multimeter to check the power output, try another, more powerful PSU)
The following software issues can cause a TDR event:
Dump for reference:
NOTE: If overclocking, please reset the system to default values while troubleshooting it. This includes CPU, RAM, GPU overclocking. You're more than welcome to put your stocks back to clock after we've diagnosed your issues!!!!!
The first thing I recommend doing if overclocks aren't the issue is fully uninstalling and reinstalling your AMD video card drivers, as a bad driver installation can cause 116 bugchecks, especially since the culprit is being pointed to atikmpag.sys (ati video card drivers). If these issues started happening after a driver update, rollback the video card drivers you installed to an earlier version that worked previously without issue.
If drivers do not help, your issue may be heat related, inadequate cooling, dust buildup in the fans or pci-e slot, so make sure your rig is being cooled adequately.
Run Furmark to test your video card to ensure that the card(s) itself is running as intended:
Quote:
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit
The following hardware issues can cause a TDR event:
Quote:
- Failing overclock on CPU or GPU (stop overclocking)
- Bad sector in memory resulting in corrupt data being communicated between GPU and the system (either video or system memory) ( MemTest and a video memory stress test: |MG| Video Memory Stress Test 1.7.116 Download )
- Corrupt hard drive/windows install resulting in corruption to the system registry or the page file (Hard drive diagnostics ( HD Diagnostic ), reset your pagefile
- Bad sector in memory resulting in corrupt data being communicated between GPU and the system (either video or system memory) ( MemTest and a video memory stress test: |MG| Video Memory Stress Test 1.7.116 Download )
- Corrupt hard drive/windows install resulting in corruption to the system registry or the page file (Hard drive diagnostics ( HD Diagnostic ), reset your pagefile
Memtest download to test your RAM: http://www.memtest86.com/
To "reset" the pagefile, follow these instructions:
Quote:
Use this technique to "reset" your pagefile:
a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
-Then click on the Advanced tab,
-then on the Performance Settings Button,
-then on the next Advanced tab,
-then on the Virtual Memory Change button.
b ) In this window, note down the current settings for your pagefile (so you can restore them later on).
-Then click on the "No paging file" radio button, and
- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.
-Click OK to exit the dialogs.
c ) Reboot (this will remove the pagefile from your system)
d ) Then go back in following the directions in step a ) and re-enter the settings that you wrote down in step b ). Follow the steps all the way through (and including) the reboot.
e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.
a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
-Then click on the Advanced tab,
-then on the Performance Settings Button,
-then on the next Advanced tab,
-then on the Virtual Memory Change button.
b ) In this window, note down the current settings for your pagefile (so you can restore them later on).
-Then click on the "No paging file" radio button, and
- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.
-Click OK to exit the dialogs.
c ) Reboot (this will remove the pagefile from your system)
d ) Then go back in following the directions in step a ) and re-enter the settings that you wrote down in step b ). Follow the steps all the way through (and including) the reboot.
e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.
Run System File Checker:
Quote:
SFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.
- Over heating of GPU or CPU again resulting in corrupt data being communicated. (Point a house fan at the video card, take temperature readings from the card with an IR detector (or your finger - but be very, very careful!!!)
- GPU failure due to any sort of issue from insufficient power(VERY common) to heat. (check the power leads, use a multimeter to check the power output, try another, more powerful PSU)
The following software issues can cause a TDR event:
Quote:
-Incompatible drivers of any sort (either GPU, sound, etc) ( http://www.microsoft.com/windows/com...s/default.aspx )
-Messy registry (I doubt this and don't approve of registry cleaners)
-Known vista issues resounding around multiple displays, aero, dreamscape, and various display drivers. (none known for this OS)
-Known vista issues that sometimes cause corrupt information to be sent to the video card from system memory (will be addressed completely in SP2, has had various fixes applied since vista's release) (none known for this OS)
-Bad direct x files (uninstall, then reinstall DirectX)
-bad system files (System File Checker - was run above)
-Bad driver (some drivers will cause an event due to internal bugs, however these are not nearly as common as many think due to all of the previous things causing the same symptom) - (remove all 3rd party programs and check to be sure drivers aren't loading. Then install only the necessary 3rd party stuff, and ensure it's the latest version and that it's compatible with Windows 7)
-Messy registry (I doubt this and don't approve of registry cleaners)
-Known vista issues resounding around multiple displays, aero, dreamscape, and various display drivers. (none known for this OS)
-Known vista issues that sometimes cause corrupt information to be sent to the video card from system memory (will be addressed completely in SP2, has had various fixes applied since vista's release) (none known for this OS)
-Bad direct x files (uninstall, then reinstall DirectX)
-bad system files (System File Checker - was run above)
-Bad driver (some drivers will cause an event due to internal bugs, however these are not nearly as common as many think due to all of the previous things causing the same symptom) - (remove all 3rd party programs and check to be sure drivers aren't loading. Then install only the necessary 3rd party stuff, and ensure it's the latest version and that it's compatible with Windows 7)
Dump for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Cardbox\Downloads\050612-27752-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e00000 PsLoadedModuleList = 0xfffff800`03044650
Debug session time: Sun May 6 14:04:22.137 2012 (UTC - 4:00)
System Uptime: 0 days 0:30:23.729
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8006ff24e0, fffff8800705c6d8, ffffffffc0000001, 3}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+86d8 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8006ff24e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800705c6d8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000003, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
atikmpag+86d8
fffff880`0705c6d8 4055 push rbp
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`02370a18 fffff880`0710b000 : 00000000`00000116 fffffa80`06ff24e0 fffff880`0705c6d8 ffffffff`c0000001 : nt!KeBugCheckEx
fffff880`02370a20 fffff880`070de569 : fffff880`0705c6d8 fffffa80`0940e000 00000000`00000000 fffffa80`093bf410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02370a60 fffff880`0710adad : fffffa80`06ff24e0 fffffa80`06ff24e0 fffffa80`06ff24e0 fffffa80`093bf410 : dxgkrnl!DXGADAPTER::PrepareToReset+0x109
fffff880`02370aa0 fffff880`07fb1f07 : fffffa80`06ff24e0 00000000`00000000 fffffa80`068ea7f0 fffffa80`093bf410 : dxgkrnl!TdrIsRecoveryRequired+0x245
fffff880`02370ad0 fffff880`07fdfd5a : fffffa80`ffffffff 00000000`0001c51a fffff880`02370c30 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02370bb0 fffff880`07fad29e : fffffa80`093bf410 ffffffff`feced300 fffffa80`068ea7f0 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`02370bf0 fffff880`07fd9e7a : 00000000`00000000 fffffa80`068ea7f0 00000000`00000080 fffffa80`093bf410 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`02370d00 fffff800`03116fda : 00000000`0354460c fffffa80`08e8fb60 fffffa80`06722ae0 fffffa80`08e8fb60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02370d40 fffff800`02e6d9c6 : fffff800`02ff1e80 fffffa80`08e8fb60 fffff800`02fffcc0 00000000`9f4fc000 : nt!PspSystemThreadStartup+0x5a
fffff880`02370d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
atikmpag+86d8
fffff880`0705c6d8 4055 push rbp
SYMBOL_NAME: atikmpag+86d8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4f7e4294
FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
Followup: MachineOwner
---------
- Joined: Apr 2008
- Location: Guadalajara, Mexico
- Posts: 3,402
- Rep: 93 (Unique: 81)
- Select All Posts By This User
Damn... That seems like a LOT of work :/ And I'm in finals + tons of homework 
How do I completely uninstall drivers to do a proper reinstallation?
It can't be dust. The PC was cleaned already.
Had another BSOD. I added the latest minidump to the file Minidumps 2 from Dropbox.
Edited by Icekilla - 5/6/12 at 4:23pm
How do I completely uninstall drivers to do a proper reinstallation?
It can't be dust. The PC was cleaned already.
Had another BSOD. I added the latest minidump to the file Minidumps 2 from Dropbox.
Edited by Icekilla - 5/6/12 at 4:23pm
|
Vanessa
(18 items) |
| CPU | Motherboard | Graphics | RAM |
|---|---|---|---|
| Intel Core i5 2500k | Gigabyte GA-Z77-D3H | EVGA GTX 660ti SuperClocked | PNY Optima MD4096SD3-1333 |
| Hard Drive | Hard Drive | Hard Drive | Optical Drive |
| Western Digital WD500AAKX 500GB SATA | Seagate ST2000DL003 | ADATA AS510S3-120GM-C 120GB SSD | Lite-On iHAS224-06 |
| Cooling | OS | Monitor | Monitor |
| Cooler Master Hyper 212+ | Windows 7 Ultimate x64 | Samsung B1930 | Benq G92HDA |
| Power | Case | Audio | |
| Corsair TX750 750W PSU | Gray Acteck Octanux | Logitech Z623 2.1CH | |
| View all | |||
|
Vanessa
(18 items) |
| CPU | Motherboard | Graphics | RAM |
|---|---|---|---|
| Intel Core i5 2500k | Gigabyte GA-Z77-D3H | EVGA GTX 660ti SuperClocked | PNY Optima MD4096SD3-1333 |
| Hard Drive | Hard Drive | Hard Drive | Optical Drive |
| Western Digital WD500AAKX 500GB SATA | Seagate ST2000DL003 | ADATA AS510S3-120GM-C 120GB SSD | Lite-On iHAS224-06 |
| Cooling | OS | Monitor | Monitor |
| Cooler Master Hyper 212+ | Windows 7 Ultimate x64 | Samsung B1930 | Benq G92HDA |
| Power | Case | Audio | |
| Corsair TX750 750W PSU | Gray Acteck Octanux | Logitech Z623 2.1CH | |
| View all | |||
post #28 of 98
5/6/12 at 4:49pm
Take it one step at a time / do it when you have time. Run memtest, if that passes run chkdsk, etc etc. It's really not a lot of work, it's just bunched up into one post so it seems like a lot. If you want to do a proper reinstall, I'd suggest a clean install of Windows and the latest important drivers only just to get everything out of the way of it being software. Here's a tutorial on how to do a proper clean install of Windows.
Also, can you please do one latest dump at a time, rather than all of the old dumps? It's confusing to me and I have to constantly check the time & date to find the latest dump. I ask this because the zip you've attached in your previous post to your latest is the one I've already analyzed, and the latest dump is still timed at 1:06 PM.
Also, can you please do one latest dump at a time, rather than all of the old dumps? It's confusing to me and I have to constantly check the time & date to find the latest dump. I ask this because the zip you've attached in your previous post to your latest is the one I've already analyzed, and the latest dump is still timed at 1:06 PM.
- Joined: Apr 2008
- Location: Guadalajara, Mexico
- Posts: 3,402
- Rep: 93 (Unique: 81)
- Select All Posts By This User
|
Vanessa
(18 items) |
| CPU | Motherboard | Graphics | RAM |
|---|---|---|---|
| Intel Core i5 2500k | Gigabyte GA-Z77-D3H | EVGA GTX 660ti SuperClocked | PNY Optima MD4096SD3-1333 |
| Hard Drive | Hard Drive | Hard Drive | Optical Drive |
| Western Digital WD500AAKX 500GB SATA | Seagate ST2000DL003 | ADATA AS510S3-120GM-C 120GB SSD | Lite-On iHAS224-06 |
| Cooling | OS | Monitor | Monitor |
| Cooler Master Hyper 212+ | Windows 7 Ultimate x64 | Samsung B1930 | Benq G92HDA |
| Power | Case | Audio | |
| Corsair TX750 750W PSU | Gray Acteck Octanux | Logitech Z623 2.1CH | |
| View all | |||
|
Vanessa
(18 items) |
| CPU | Motherboard | Graphics | RAM |
|---|---|---|---|
| Intel Core i5 2500k | Gigabyte GA-Z77-D3H | EVGA GTX 660ti SuperClocked | PNY Optima MD4096SD3-1333 |
| Hard Drive | Hard Drive | Hard Drive | Optical Drive |
| Western Digital WD500AAKX 500GB SATA | Seagate ST2000DL003 | ADATA AS510S3-120GM-C 120GB SSD | Lite-On iHAS224-06 |
| Cooling | OS | Monitor | Monitor |
| Cooler Master Hyper 212+ | Windows 7 Ultimate x64 | Samsung B1930 | Benq G92HDA |
| Power | Case | Audio | |
| Corsair TX750 750W PSU | Gray Acteck Octanux | Logitech Z623 2.1CH | |
| View all | |||
post #30 of 98
5/6/12 at 5:15pm
Latest dump is a 1e bugcheck pointing to the culprit Wdf01000.sys (WDF Dynamic - Kernel Mode Driver Framework Runtime), this is a core Windows file. After taking a quick look at the stack text, it mentions in multiple dumps of yours: USB PORT Xpdc worker.
For example, in the latest dump:
You read it from the bottom up. Whatever "USBPORT!USBPORT_Xdpc_Worker" is may be accessing corrupting memory ahead of Wdf01000.sys.
With this being said, let's enable Driver Verifier to see if there's a 3rd party driver creating all of these faults and to also eliminate software as the issue. What Driver Verifier essentially does is carefully watches and stresses all 3rd party non MS signed drivers to see if it finds a culprit. If you don't find a culprit within ~48 hours of PC use as you would regularly, or the verifier enabled dump shows no drivers, it's more than likely hardware related.
Second of all, dtsoftbus01.sys, sptd.sys and ASACPI.sys are no longer listed and loaded, so good work on that my friend!
Dump for reference:
For example, in the latest dump:
Quote:
STACK_TEXT:
fffff800`044e89a8 fffff800`02e7a67e : 00000000`00000000 fffff880`0401b308 fffff800`044e9120 fffff800`02eadc80 : nt!KeBugCheck
fffff800`044e89b0 fffff800`02ead94d : fffff800`0308b71c fffff800`02fc8078 fffff800`02e06000 fffff800`044e98c8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`044e89e0 fffff800`02eac725 : fffff800`02fcbed8 fffff800`044e8a58 fffff800`044e98c8 fffff800`02e06000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`044e8a10 fffff800`02ebd6a1 : fffff800`044e98c8 fffff800`044e9120 fffff800`00000000 fffffa80`08de8c80 : nt!RtlDispatchException+0x415
fffff800`044e90f0 fffff800`02e82302 : fffff800`044e98c8 fffffa80`094dda10 fffff800`044e9970 fffffa80`0953ce40 : nt!KiDispatchException+0x135
fffff800`044e9790 fffff800`02e80c0a : fffffa80`0963bd60 fffffa80`0963bb40 fffffa80`09529bed fffff880`06f47b28 : nt!KiExceptionDispatch+0xc2
fffff800`044e9970 fffff880`00f171d2 : fffffa80`08e00e70 00000000`00000000 fffffa80`0953de40 fffff800`033f0524 : nt!KiGeneralProtectionFault+0x10a
fffff800`044e9b00 fffff880`00eedc9b : fffffa80`0953ce40 fffffa80`0953ce40 fffffa80`0953ce50 fffffa80`0827a301 : Wdf01000!FxRequestBase::CompleteSubmitted+0x11e
fffff800`044e9b80 fffff880`00eeddc4 : 00000000`00000002 fffffa80`081c6d28 00000000`00000000 fffff880`04563f5d : Wdf01000!FxIoTarget::RequestCompletionRoutine+0x1cb
fffff800`044e9bf0 fffff800`02e6e845 : fffffa80`081c1100 fffffa80`081c6cb0 fffffa80`07605c00 fffff800`02fb0fbd : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c
fffff800`044e9c20 fffff800`02e866c1 : fffffa80`0827a4cb 00000000`00000000 00000000`00000000 00000000`00000050 : nt!IopUnloadSafeCompletion+0x55
fffff800`044e9c60 fffff880`04570631 : fffffa80`08000050 fffffa80`094deb00 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`044e9d50 fffff880`04570b0f : fffffa80`08313502 fffffa80`0827a320 00000000`ffffffff fffffa80`08000eb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff800`044e9e30 fffff880`0456e66f : fffffa80`08000eb0 fffffa80`080001a0 fffffa80`08001050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff800`044e9e90 fffff880`0455ff89 : fffffa80`08000050 00000000`00000000 fffffa80`08000e02 fffffa80`08000eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff800`044e9ed0 fffff800`02e8d40c : fffff800`02ff7e80 fffffa80`08000eb0 fffffa80`08000ec8 00000000`ffff0000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`044e9f00 fffff800`02e85e05 : 00000000`00000000 fffffa80`09f29880 00000000`00000000 fffff880`0455fdb0 : nt!KiRetireDpcList+0x1bc
fffff800`044e9fb0 fffff800`02e85c1c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`029e56f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
fffff800`044e89a8 fffff800`02e7a67e : 00000000`00000000 fffff880`0401b308 fffff800`044e9120 fffff800`02eadc80 : nt!KeBugCheck
fffff800`044e89b0 fffff800`02ead94d : fffff800`0308b71c fffff800`02fc8078 fffff800`02e06000 fffff800`044e98c8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`044e89e0 fffff800`02eac725 : fffff800`02fcbed8 fffff800`044e8a58 fffff800`044e98c8 fffff800`02e06000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`044e8a10 fffff800`02ebd6a1 : fffff800`044e98c8 fffff800`044e9120 fffff800`00000000 fffffa80`08de8c80 : nt!RtlDispatchException+0x415
fffff800`044e90f0 fffff800`02e82302 : fffff800`044e98c8 fffffa80`094dda10 fffff800`044e9970 fffffa80`0953ce40 : nt!KiDispatchException+0x135
fffff800`044e9790 fffff800`02e80c0a : fffffa80`0963bd60 fffffa80`0963bb40 fffffa80`09529bed fffff880`06f47b28 : nt!KiExceptionDispatch+0xc2
fffff800`044e9970 fffff880`00f171d2 : fffffa80`08e00e70 00000000`00000000 fffffa80`0953de40 fffff800`033f0524 : nt!KiGeneralProtectionFault+0x10a
fffff800`044e9b00 fffff880`00eedc9b : fffffa80`0953ce40 fffffa80`0953ce40 fffffa80`0953ce50 fffffa80`0827a301 : Wdf01000!FxRequestBase::CompleteSubmitted+0x11e
fffff800`044e9b80 fffff880`00eeddc4 : 00000000`00000002 fffffa80`081c6d28 00000000`00000000 fffff880`04563f5d : Wdf01000!FxIoTarget::RequestCompletionRoutine+0x1cb
fffff800`044e9bf0 fffff800`02e6e845 : fffffa80`081c1100 fffffa80`081c6cb0 fffffa80`07605c00 fffff800`02fb0fbd : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c
fffff800`044e9c20 fffff800`02e866c1 : fffffa80`0827a4cb 00000000`00000000 00000000`00000000 00000000`00000050 : nt!IopUnloadSafeCompletion+0x55
fffff800`044e9c60 fffff880`04570631 : fffffa80`08000050 fffffa80`094deb00 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`044e9d50 fffff880`04570b0f : fffffa80`08313502 fffffa80`0827a320 00000000`ffffffff fffffa80`08000eb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff800`044e9e30 fffff880`0456e66f : fffffa80`08000eb0 fffffa80`080001a0 fffffa80`08001050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff800`044e9e90 fffff880`0455ff89 : fffffa80`08000050 00000000`00000000 fffffa80`08000e02 fffffa80`08000eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff800`044e9ed0 fffff800`02e8d40c : fffff800`02ff7e80 fffffa80`08000eb0 fffffa80`08000ec8 00000000`ffff0000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`044e9f00 fffff800`02e85e05 : 00000000`00000000 fffffa80`09f29880 00000000`00000000 fffff880`0455fdb0 : nt!KiRetireDpcList+0x1bc
fffff800`044e9fb0 fffff800`02e85c1c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`029e56f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
You read it from the bottom up. Whatever "USBPORT!USBPORT_Xdpc_Worker" is may be accessing corrupting memory ahead of Wdf01000.sys.
With this being said, let's enable Driver Verifier to see if there's a 3rd party driver creating all of these faults and to also eliminate software as the issue. What Driver Verifier essentially does is carefully watches and stresses all 3rd party non MS signed drivers to see if it finds a culprit. If you don't find a culprit within ~48 hours of PC use as you would regularly, or the verifier enabled dump shows no drivers, it's more than likely hardware related.
Second of all, dtsoftbus01.sys, sptd.sys and ASACPI.sys are no longer listed and loaded, so good work on that my friend!
Dump for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Cardbox\Downloads\050612-19734-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e06000 PsLoadedModuleList = 0xfffff800`0304a650
Debug session time: Sun May 6 19:19:07.923 2012 (UTC - 4:00)
System Uptime: 0 days 0:43:58.515
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : Wdf01000.sys ( Wdf01000!FxRequestBase::CompleteSubmitted+11e )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP:
+6530383435393239
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR: 0x1E_0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff800044e98c8 -- (.exr 0xfffff800044e98c8)
ExceptionAddress: fffff88000f171d2 (Wdf01000!FxRequestBase::CompleteSubmitted+0x000000000000011e)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff800044e9970 -- (.trap 0xfffff800044e9970)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=f2c23e8eaafc5bc1 rbx=0000000000000000 rcx=fffffa80094dea90
rdx=fffffa80094dda10 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000f171d2 rsp=fffff800044e9b00 rbp=0000000000000000
r8=fffffa80094dda00 r9=0000000000000000 r10=fffffa8008de8c80
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
Wdf01000!FxRequestBase::CompleteSubmitted+0x11e:
fffff880`00f171d2 ff5018 call qword ptr [rax+18h] ds:5f03:f2c23e8e`aafc5bd9=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e7a67e to fffff80002e82c50
STACK_TEXT:
fffff800`044e89a8 fffff800`02e7a67e : 00000000`00000000 fffff880`0401b308 fffff800`044e9120 fffff800`02eadc80 : nt!KeBugCheck
fffff800`044e89b0 fffff800`02ead94d : fffff800`0308b71c fffff800`02fc8078 fffff800`02e06000 fffff800`044e98c8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`044e89e0 fffff800`02eac725 : fffff800`02fcbed8 fffff800`044e8a58 fffff800`044e98c8 fffff800`02e06000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`044e8a10 fffff800`02ebd6a1 : fffff800`044e98c8 fffff800`044e9120 fffff800`00000000 fffffa80`08de8c80 : nt!RtlDispatchException+0x415
fffff800`044e90f0 fffff800`02e82302 : fffff800`044e98c8 fffffa80`094dda10 fffff800`044e9970 fffffa80`0953ce40 : nt!KiDispatchException+0x135
fffff800`044e9790 fffff800`02e80c0a : fffffa80`0963bd60 fffffa80`0963bb40 fffffa80`09529bed fffff880`06f47b28 : nt!KiExceptionDispatch+0xc2
fffff800`044e9970 fffff880`00f171d2 : fffffa80`08e00e70 00000000`00000000 fffffa80`0953de40 fffff800`033f0524 : nt!KiGeneralProtectionFault+0x10a
fffff800`044e9b00 fffff880`00eedc9b : fffffa80`0953ce40 fffffa80`0953ce40 fffffa80`0953ce50 fffffa80`0827a301 : Wdf01000!FxRequestBase::CompleteSubmitted+0x11e
fffff800`044e9b80 fffff880`00eeddc4 : 00000000`00000002 fffffa80`081c6d28 00000000`00000000 fffff880`04563f5d : Wdf01000!FxIoTarget::RequestCompletionRoutine+0x1cb
fffff800`044e9bf0 fffff800`02e6e845 : fffffa80`081c1100 fffffa80`081c6cb0 fffffa80`07605c00 fffff800`02fb0fbd : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c
fffff800`044e9c20 fffff800`02e866c1 : fffffa80`0827a4cb 00000000`00000000 00000000`00000000 00000000`00000050 : nt!IopUnloadSafeCompletion+0x55
fffff800`044e9c60 fffff880`04570631 : fffffa80`08000050 fffffa80`094deb00 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`044e9d50 fffff880`04570b0f : fffffa80`08313502 fffffa80`0827a320 00000000`ffffffff fffffa80`08000eb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff800`044e9e30 fffff880`0456e66f : fffffa80`08000eb0 fffffa80`080001a0 fffffa80`08001050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff800`044e9e90 fffff880`0455ff89 : fffffa80`08000050 00000000`00000000 fffffa80`08000e02 fffffa80`08000eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff800`044e9ed0 fffff800`02e8d40c : fffff800`02ff7e80 fffffa80`08000eb0 fffffa80`08000ec8 00000000`ffff0000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`044e9f00 fffff800`02e85e05 : 00000000`00000000 fffffa80`09f29880 00000000`00000000 fffff880`0455fdb0 : nt!KiRetireDpcList+0x1bc
fffff800`044e9fb0 fffff800`02e85c1c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`029e56f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
STACK_COMMAND: kb
FOLLOWUP_IP:
Wdf01000!FxRequestBase::CompleteSubmitted+11e
fffff880`00f171d2 ff5018 call qword ptr [rax+18h]
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: Wdf01000!FxRequestBase::CompleteSubmitted+11e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Wdf01000
IMAGE_NAME: Wdf01000.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc19f
FAILURE_BUCKET_ID: X64_0x1E_0_Wdf01000!FxRequestBase::CompleteSubmitted+11e
BUCKET_ID: X64_0x1E_0_Wdf01000!FxRequestBase::CompleteSubmitted+11e
Followup: MachineOwner
---------
- Can anyone help me read these minidump files?
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Can anyone help me read these minidump files?
Currently, there are 1618 Active Users
(377 Members and 1241 Guests)
Recent Discussions
- › Affordable upgrade from 560Ti 21 seconds ago
- › [Nerd Reactor] Don't update your PS3 44 seconds ago
- › Official NZXT Switch 810 thread 1 minute ago
- › [Official] ASUS ROG Rampage IV X79 Owner's Club 1 minute ago
- › Nvidia Quadro Driver 320.27 WHQL 1 minute ago
- › Which 770's to get? 1 minute ago
- › [FFN] Square Considering Final Fantasy XV On PCs But Will Require... 1 minute ago
- › [Official] Screenshot of Your Games Thread 2 minutes ago
- › [HELP] MSI P67 gd-53 post error 98 2 minutes ago
- › Ivy Bridge Overclocking Guide ► Asus Motherboards 4 minutes ago
View: New Posts | All Discussions
Recent Reviews
- › Anker Laser Gaming Mouse with 2000DPI, 7 Programmable Button, 5... by Totally Dubbed
- › Anker Wireless Mouse, 3 Adjustable DPI Levels, 2000 DPI, 6 Buttons,... by Totally Dubbed
- › 16GB G.Skill DDR3 PC3-17000 RipjawsZ Series for Intel X79... by nleksan
- › Intel Core i5-3570K 3.4GHz LGA1155 by Tex1954
- › The Incredible Adventures of Van Helsing by iARDAs
- › Skyworth 39E780U UHD tv by maarten12100
- › S.T.R.I.K.E. 7 Gaming Keyboard for PC by hatlesschimp
- › Corsair Obsidian 350D by Oliver1234
- › CrossOver BLACK TUNE 2735AMG IPS LED by RSMJR87
- › Samsung 840 PRO Series MZ-7PD256 256GB 2.5-inch SSD by Drpillz624
View: More Reviews
New Articles
- › ASUS ROG Poseidon by Amar
- › ASUS Transformer Book Trio : a weird Combination by Amar
- › FreeBSD HTPC and Home Server by CaptainBlame
- › Can AMD hardware in New Consoles leverage... by Amar
- › The Future of PC Gaming .. by dava4444
- › GTX 780 Overclocking! by Amar
- › METRO 2033 STARTUP CRASH FIX WORKS by xiangelo
- › Why are DNS Servers Important? How to make... by exzacklyright
- › Titanium Backup Guide For Newbies by exzacklyright
- › How to install ADB (Android Debug Bridge) by exzacklyright
View: New Articles | All Articles
Home | Reviews | Forums | Articles | My Profile
About Overclock.net | Join the Community | Advertise | Contact Us | All Staff
© 2013 Shogun Interactive Development Overclock.net is powered by Huddler Tech | FAQ | Support | Privacy | ToS | DMCA | Site Map
About Overclock.net | Join the Community | Advertise | Contact Us | All Staff
© 2013 Shogun Interactive Development Overclock.net is powered by Huddler Tech | FAQ | Support | Privacy | ToS | DMCA | Site Map
