A problem with hal.dll+12a3b - Windows 7 x64
- Thread starter ric80231
- Start date
I see Gigabyte's garbage software - Easy Saver, plus a lot of pending NPFs and Symantec on the raw stack after a working set list call.
Might be wise to enable verifier and see if we can catch anything, because for now it's just another unclassified 0x124.. zzzz.
Driver Verifier:
What is Driver Verifier?
Driver Verifier monitors Windows kernel-mode drivers, graphics drivers, and even 3rd party drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject the Windows drivers to a variety of stresses and tests to find improper behavior.
Essentially, if there's a 3rd party driver believed to be causing the issues at hand, enabling Driver Verifier will help us see which specific driver is causing the problem.
Before enabling Driver Verifier, it is recommended to create a System Restore Point:
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8/8.1 - Restore Point - Create in Windows 8
How to enable Driver Verifier:
Start > type "verifier" without the quotes > Select the following options -
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.
Important information regarding Driver Verifier:
- Perhaps the most important which I will now clarify as this has been misunderstood often, enabling Driver Verifier by itself is not! a solution, but instead a diagnostic utility. It will tell us if a driver is causing your issues, but again it will not outright solve your issues.
- If Driver Verifier finds a violation, the system will BSOD. To expand on this a bit more for the interested, specifically what Driver Verifier actually does is it looks for any driver making illegal function calls, causing memory leaks, etc. When and/if this happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled per my instructions above, it is monitoring all 3rd party drivers (as we have it set that way) and when it catches a driver attempting to do this, it will quickly flag that driver as being a troublemaker, and bring down the system safely before any corruption can occur.
- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will detect it in violation almost straight away, and as stated above, that will cause / force a BSOD.
If this happens, do not panic, do the following:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > Search > type "cmd" without the quotes.
- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
- Restart and boot into normal Windows.
If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > type "system restore" without the quotes.
- Choose the restore point you created earlier.
-- Note that Safe Mode for Windows 8/8.1 is a bit different, and you may need to try different methods: 5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1
How long should I keep Driver Verifier enabled for?
I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier. I will usually say whether or not I'd like for you to keep it enabled any longer.
My system BSOD'd with Driver Verifier enabled, where can I find the crash dumps?
- If you have the system set to generate Small Memory Dumps, they will be located in %systemroot%\Minidump.
- If you have the system set to generate Kernel Memory Dumps, it will be located in %systemroot% and labeled MEMORY.DMP.
Any other questions can most likely be answered by this article:
http://support.microsoft.com/kb/244617
Code:
fffff880`24774038 fffff880`0568cbd0 BHDrvx64+0x34bd0
fffff880`24774040 fffff700`01080000
fffff880`24774048 fffffa80`08cc5d40
fffff880`24774050 fffff680`003503b0
fffff880`24774058 fffffa80`1a31f898
fffff880`24774060 0000007f`fffffff8
fffff880`24774068 00000000`00002258
fffff880`24774070 fffff700`01080488
fffff880`24774078 fffff700`01080000
fffff880`24774080 00000000`00002258
fffff880`24774088 fffffa80`1a31f898
fffff880`24774090 00000000`00000d9d
fffff880`24774098 fffff800`032e1962 nt!MiUpdateWsle+0x1b2Might be wise to enable verifier and see if we can catch anything, because for now it's just another unclassified 0x124.. zzzz.
Driver Verifier:
What is Driver Verifier?
Driver Verifier monitors Windows kernel-mode drivers, graphics drivers, and even 3rd party drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject the Windows drivers to a variety of stresses and tests to find improper behavior.
Essentially, if there's a 3rd party driver believed to be causing the issues at hand, enabling Driver Verifier will help us see which specific driver is causing the problem.
Before enabling Driver Verifier, it is recommended to create a System Restore Point:
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8/8.1 - Restore Point - Create in Windows 8
How to enable Driver Verifier:
Start > type "verifier" without the quotes > Select the following options -
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.
Important information regarding Driver Verifier:
- Perhaps the most important which I will now clarify as this has been misunderstood often, enabling Driver Verifier by itself is not! a solution, but instead a diagnostic utility. It will tell us if a driver is causing your issues, but again it will not outright solve your issues.
- If Driver Verifier finds a violation, the system will BSOD. To expand on this a bit more for the interested, specifically what Driver Verifier actually does is it looks for any driver making illegal function calls, causing memory leaks, etc. When and/if this happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled per my instructions above, it is monitoring all 3rd party drivers (as we have it set that way) and when it catches a driver attempting to do this, it will quickly flag that driver as being a troublemaker, and bring down the system safely before any corruption can occur.
- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will detect it in violation almost straight away, and as stated above, that will cause / force a BSOD.
If this happens, do not panic, do the following:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > Search > type "cmd" without the quotes.
- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
- Restart and boot into normal Windows.
If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > type "system restore" without the quotes.
- Choose the restore point you created earlier.
-- Note that Safe Mode for Windows 8/8.1 is a bit different, and you may need to try different methods: 5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1
How long should I keep Driver Verifier enabled for?
I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier. I will usually say whether or not I'd like for you to keep it enabled any longer.
My system BSOD'd with Driver Verifier enabled, where can I find the crash dumps?
- If you have the system set to generate Small Memory Dumps, they will be located in %systemroot%\Minidump.
- If you have the system set to generate Kernel Memory Dumps, it will be located in %systemroot% and labeled MEMORY.DMP.
Any other questions can most likely be answered by this article:
http://support.microsoft.com/kb/244617
Jared
Sysnative Staff, BSOD Kernel Dump Expert
- Feb 3, 2014
- 1,591
Internal unclassified uncorrectable hardware error.
Although this seems different.
Network pipe IRPs associated with Nvidia Backend, probably being blocked by Norton.
As well as garbage Gigabyte software, I'm not surprised you're running into problems.
Yes, I would try Driver Verifier first to be sure.
Although this seems different.
Code:
Error : Internal unclassified (Proc 2 Bank 1)
Status : 0xbf80000000200401
Address : 0x00000000fee00040
Misc. : 0x0000000000000086
hal!_MCI_STATUS
+0x000 McaErrorCode : 0x5043 0101 0000 0100 0011
+0x002 ModelErrorCode : 0x5245
+0x004 OtherInformation : 0y11111110000001000010000 (0x7f0210)
+0x004 ActionRequired : 0y1
+0x004 Signalling : 0y1
+0x004 ContextCorrupt : 0y1
+0x004 AddressValid : 0y1
+0x004 MiscValid : 0y1
+0x004 ErrorEnabled : 0y1
+0x004 UncorrectedError : 0y1
+0x004 StatusOverFlow : 0y1
+0x004 Valid : 0y1
+0x000 QuadPart : 0xffff0210`52455043
2: kd> !irp fffffa80109c6cb0
Irp is active with 1 stacks 1 is current (= 0xfffffa80109c6d80)
No Mdl: No System Buffer: Thread fffffa8019a419f0: Irp stack trace.
cmd flg cl Device File Completion-Context
>[ d, 0] 5 1 fffffa80108c7940 fffffa8013234680 00000000-00000000 pending
\FileSystem\Npfs
Args: 00000000 00000000 00110008 00000000
2: kd> !fileobj fffffa8013234680
\9EA6F070-37D3-424D-84AB-39C2C9FB0621_1
Device Object: 0xfffffa80108c7940 \FileSystem\Npfs
Vpb is NULL
Flags: 0x40080
Named Pipe
Handle Created
FsContext: 0x00010101 FsContext2: 0xfffff8a0010a8b60
Private Cache Map: 0x00000001
CurrentByteOffset: 0
THREAD fffffa8019a419f0 Cid 2988.1d2c Teb: 000000007efa4000 Win32Thread: fffff900c1c30c10 WAIT: (UserRequest) UserMode Non-Alertable
fffffa80178f7490 NotificationEvent
IRP List:
fffffa801fbbfa30: (0006,0118) Flags: 00060800 Mdl: 00000000
fffffa801fbbfee0: (0006,0118) Flags: 00060800 Mdl: 00000000
fffffa801fbbe6b0: (0006,0118) Flags: 00060800 Mdl: 00000000
fffffa801f65b8f0: (0006,0118) Flags: 00060800 Mdl: 00000000
fffffa802016a2a0: (0006,0118) Flags: 00060800 Mdl: 00000000
fffffa802016a9c0: (0006,0118) Flags: 00060800 Mdl: 00000000
fffffa80201616b0: (0006,0118) Flags: 00060800 Mdl: 00000000
fffffa802016a010: (0006,0118) Flags: 00060800 Mdl: 00000000
fffffa801fbc4440: (0006,0118) Flags: 00060800 Mdl: 00000000
fffffa8020163b60: (0006,0118) Flags: 00060800 Mdl: 00000000
fffffa8020193ee0: (0006,0118) Flags: 00060800 Mdl: 00000000
fffffa802015a400: (0006,0118) Flags: 00060800 Mdl: 00000000
fffffa802018fd40: (0006,0118) Flags: 00060800 Mdl: 00000000
fffffa802016bd40: (0006,0118) Flags: 00060800 Mdl: 00000000
fffffa8020161b60: (0006,0118) Flags: 00060800 Mdl: 00000000
fffffa802017de10: (0006,0118) Flags: 00060800 Mdl: 00000000
fffffa802017b9c0: (0006,0118) Flags: 00060800 Mdl: 00000000
Not impersonating
DeviceMap fffff8a007e97b40
Owning Process fffffa8019ed78b0 Image: NvBackend.exe
Attached Process N/A Image: N/A
Wait Start TickCount 7724741 Ticks: 0
Context Switch Count 95571 IdealProcessor: 7 LargeStack
UserTime 00:00:00.234
KernelTime 00:00:02.511
Win32 Start Address 0x0000000000411dd0
Stack Init fffff8800e825c70 Current fffff8800e8257c0
Base fffff8800e826000 Limit fffff8800e81e000 Call 0
Priority 10 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP RetAddr : Args to Child : Call Site
fffff880`0e825800 fffff800`032d2602 : fffffa80`19a419f0 fffffa80`19a419f0 00000000`00000000 fffffa80`00000000 : nt!KiSwapContext+0x7a
fffff880`0e825940 fffff800`032d631f : 00000000`00000514 00000000`7efa4000 fffff880`000000da 00000000`03afeaf8 : nt!KiCommitThreadWait+0x1d2
fffff880`0e8259d0 fffff800`035c368e : fffffa80`19a41900 00000000`00000006 00000000`00000001 00000000`00000000 : nt!KeWaitForSingleObject+0x19f
fffff880`0e825a70 fffff800`032cdb53 : fffffa80`19a419f0 00000000`00000514 fffff880`0e825ab8 fffffa80`178f7490 : nt!NtWaitForSingleObject+0xde
fffff880`0e825ae0 00000000`74a52e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`0e825ae0)
00000000`03afead8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74a52e09Network pipe IRPs associated with Nvidia Backend, probably being blocked by Norton.
As well as garbage Gigabyte software, I'm not surprised you're running into problems.
Yes, I would try Driver Verifier first to be sure.
Interesting, as I don't have Easy Saver installed. The only Gigabyte applications I have installed are System Viewer, @Bios and App Centre.
Verifier is enabled as you requested. How long do you want me to leave it enabled?
Jared
Sysnative Staff, BSOD Kernel Dump Expert
- Feb 3, 2014
- 1,591
Code:
6: kd> .bugcheck
Bugcheck code 000000C1
Arguments fffff980`912eaf60 fffff980`912ea700 00000000`00e940a8 00000000`00000023
6: kd> kn
# Child-SP RetAddr Call Site
00 fffff880`0cd08b38 fffff800`0335d13a nt!KeBugCheckEx
01 fffff880`0cd08b40 fffff800`033d5fc3 nt!MiCheckSpecialPoolSlop+0x9a
02 fffff880`0cd08b80 fffff800`0340194b nt!MmFreeSpecialPool+0x1d3
03 fffff880`0cd08cc0 fffff880`06a969c5 nt!ExAllocatePoolWithTag+0x1683
04 fffff880`0cd08d70 fffff880`06cd62d4 nvlddmkm+0x1c09c5
05 fffff880`0cd08da0 fffff880`06cd60ee nvlddmkm+0x4002d4
06 fffff880`0cd08dd0 fffff880`06b30358 nvlddmkm+0x4000ee
07 fffff880`0cd08e10 fffff880`06ddd282 nvlddmkm+0x25a358
08 fffff880`0cd08ed0 fffff880`06acf7c8 nvlddmkm+0x507282
09 fffff880`0cd08f50 fffff880`06ad0c33 nvlddmkm+0x1f97c8
0a fffff880`0cd09020 fffff880`06a799bc nvlddmkm+0x1fac33
0b fffff880`0cd090a0 fffff880`069e7a09 nvlddmkm+0x1a39bc
0c fffff880`0cd09190 fffff880`069e7c80 nvlddmkm+0x111a09
0d fffff880`0cd09220 fffff880`0705c8b7 nvlddmkm+0x111c80
0e fffff880`0cd09250 fffff880`0705c33a nvlddmkm+0x7868b7
0f fffff880`0cd09340 fffff880`0705b90a nvlddmkm+0x78633a
10 fffff880`0cd09370 fffff880`0695f739 nvlddmkm+0x78590a
11 fffff880`0cd093d0 fffff880`0704a5f2 nvlddmkm+0x89739
12 fffff880`0cd09500 fffff880`05238e79 nvlddmkm+0x7745f2
13 fffff880`0cd095a0 fffff880`0523ad4e dxgkrnl!DXGADAPTER::DdiCloseAllocation+0x4d
14 fffff880`0cd095e0 fffff880`0523a65f dxgkrnl!DXGDEVICE::DestroyAllocations+0x2ca
15 fffff880`0cd096d0 fffff880`0523a8e1 dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3
16 fffff880`0cd09720 fffff880`0523eaec dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9
17 fffff880`0cd09770 fffff880`05241285 dxgkrnl!DXGDEVICE::DestroyAllocation+0x44c
18 fffff880`0cd09800 fffff960`001bb692 dxgkrnl!DxgkDestroyAllocation+0xa9d
19 fffff880`0cd09ab0 fffff800`032cab53 win32k!NtGdiDdDDIDestroyAllocation+0x12
1a fffff880`0cd09ae0 00000000`751d146a nt!KiSystemServiceCopyEnd+0x13
1b 00000000`0b92e678 00000000`00000000 0x751d146a
6: kd> dc fffff980912eaf60
fffff980`912eaf60 506b2000 00000000 506c2fff 00000000 . kP...../lP....
fffff980`912eaf70 506b2000 00000000 00000000 00000000 . kP............
fffff980`912eaf80 ffffffff 00000000 912eaf60 fffff980 ........`.......
fffff980`912eaf90 506b2000 00000000 506c2fff 00000000 . kP...../lP....
fffff980`912eafa0 00000001 00000000 bc312f88 fffff980 ........./1.....
fffff980`912eafb0 00000000 00000000 00000000 00000000 ................
fffff980`912eafc0 1ce00f60 fffff981 abbfef60 fffff981 `.......`.......
fffff980`912eafd0 bc312f60 fffff980 abbfef60 fffff981 `/1.....`.......
6: kd> !pool fffff980912eaf60
Pool page fffff980912eaf60 region is Special pool
Address fffff980912ea000 does not belong to any pool
Data start fffff980912eaf60, block size 0xa0
Pattern mismatch at fffff980912ea700: expected 0xe9, actual 0xa9
Block fffff980912eaf60 is a corrupted special pool allocation
6: kd> !poolval fffff980912eaf60
Pool page fffff980912eaf60 region is Special pool
Validating Pool headers for pool page: fffff980912eaf60
Pool page [ fffff980912ea000 ] is __inVALID.
Analyzing linked list...
[ fffff980912ea000 ]: invalid previous size [ 0xa8 ] should be [ 0x0 ]
Scanning for single bit errors...
None found
6: kd> dc fffff980912ea700
fffff980`912ea700 e9e9e9a9 e9e9e9e9 e9e9e9e9 e9e9e9e9 ................
fffff980`912ea710 e9e9e9e9 e9e9e9e9 e9e9e9e9 e9e9e9e9 ................
fffff980`912ea720 e9e9e9e9 e9e9e9e9 e9e9e9e9 e9e9e9e9 ................
fffff980`912ea730 e9e9e9e9 e9e9e9e9 e9e9e9e9 e9e9e9e9 ................
fffff980`912ea740 e9e9e9e9 e9e9e9e9 e9e9e9e9 e9e9e9e9 ................
fffff980`912ea750 e9e9e9e9 e9e9e9e9 e9e9e9e9 e9e9e9e9 ................
fffff980`912ea760 e9e9e9e9 e9e9e9e9 e9e9e9e9 e9e9e9e9 ................
fffff980`912ea770 e9e9e9e9 e9e9e9e9 e9e9e9e9 e9e9e9e9 ................
6: kd> !pool fffff980912ea700
Pool page fffff980912ea700 region is Special pool
Address fffff980912ea000 does not belong to any pool
Data start fffff980912eaf60, block size 0xa0
Pattern mismatch at fffff980912ea700: expected 0xe9, actual 0xa9
Block fffff980912ea700 is a corrupted special pool allocation
6: kd> !poolval fffff980912ea700
Pool page fffff980912ea700 region is Special pool
Validating Pool headers for pool page: fffff980912ea700
Pool page [ fffff980912ea000 ] is __inVALID.
Analyzing linked list...
[ fffff980912ea000 ]: invalid previous size [ 0xa8 ] should be [ 0x0 ]
Scanning for single bit errors...
None found
Module: nvlddmkm
Base Address: fffff880068d6000
Image Name: nvlddmkm.sys
Machine Type: 34404 (X64)
Time Stamp: 5581075a Wed Jun 17 06:36:26 2015
Size: ac9000
CheckSum: a850be
Characteristics: 22
Debug Data Dirs: Type Size VA Pointer
CODEVIEW 87, 5e2544, 5e1744 RSDS - GUID: {1E4F754A-38D0-4FB0-BA89-2E874DD69C99}
Age: 1, Pdb: C:\dvs\p4\build\sw\rel\gpu_drv\r352\r353_23\drivers\display\lddm\nvlddmkm\_out\wddm_amd64_release\nvlddmkm.pdb
?? 14, 5e25cc, 5e17cc [Data not mapped]
Image Type: MEMORY - Image read successfully from loaded memory.
Symbol Type: NONE - PDB not found from image header.
Load Report: no symbols loadedNot the dump I was hoping for, but it looks like the Nvidia driver corrupted the whole pool block.
Best to update or roll back the driver.
Keep driver verifier on for anything else. Hopefully we can find something regarding gigabyte or Norton.
Another memory.dmp. This is not a crash though, it was a hang, I found the machine displaying a blank, but active screen. It was totally unresponsive to mouse or keyboard. The stop time 22:40 is when I switched off the machine.
Haven't had time to revert to an earlier Nvidea driver!
Haven't had time to revert to an earlier Nvidea driver!
And again, this memory.dmp was the result of a BSOD that occured during the installation of Nvidia driver v347.88, I was trying to revert to a previous version. Nvidia GeForce experience now reports the driver as v347.88, but whether it is correctly installed is open to question.
Verifier is still active.
Verifier is still active.
The one you uploaded previously was a 0x116 VIDEO_TDR_ERROR (https://msdn.microsoft.com/en-us/library/windows/hardware/ff557263(v=vs.85).aspx). Given the randomness of these bugchecks, I'm starting to wonder about your PSU or power distribution inside your machine. I don't want to just blame hardware, but the video card isn't attached to the system except through the PCIE bus, so a TDR error would indicate connectivity to the driver and card failed, and a reset also failed (thus the bugcheck). While this can indicate a bad card, the fact that your system exhibits so many other bugchecks that I'm wondering if it isn't something more basic, like power.
https://forums.geforce.com/default/...nd-for-tdr-crashes-black-screens-etc/#3993428
https://forums.geforce.com/default/...nd-for-tdr-crashes-black-screens-etc/#3993428
Code:
2: kd> .bugcheck
Bugcheck code 00000116
Arguments fffffa80`159124e0 fffff880`06a02480 00000000`00000000 00000000`00000002
2: kd> !thread
THREAD fffffa8015d482e0 Cid 0004.12fc Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 2
Not impersonating
DeviceMap fffff8a000007d90
Owning Process fffffa800cab25d0 Image: System
Attached Process N/A Image: N/A
Wait Start TickCount 364177 Ticks: 0
Context Switch Count 3387 IdealProcessor: 2
UserTime 00:00:00.000
KernelTime 00:00:01.014
Win32 Start Address dxgmms1!VidSchiWorkerThread (0xfffff8800573bf3c)
Stack Init fffff8800ebc5c70 Current fffff880091e3c80
Base fffff8800ebc6000 Limit fffff8800ebc0000 Call 0
Priority 15 BasePriority 15 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP RetAddr : Args to Child : Call Site
fffff880`0ebc5888 fffff880`0566c134 : 00000000`00000116 fffffa80`159124e0 fffff880`06a02480 00000000`00000000 : nt!KeBugCheckEx
fffff880`0ebc5890 fffff880`0566be3e : fffff880`06a02480 fffffa80`159124e0 fffffa80`15a65010 fffffa80`15794110 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0ebc58d0 fffff880`05713f13 : fffffa80`159124e0 00000000`00000000 fffffa80`15a65010 fffffa80`15794110 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`0ebc5900 fffff880`0573dcf1 : 00000000`ffffffff 00000000`00058dc9 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0ebc59e0 fffff880`0573c437 : 00000000`00000102 00000000`00000006 00000000`00058dc9 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`0ebc5a10 fffff880`0570f2d2 : ffffffff`ff676980 fffffa80`15794110 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`0ebc5ab0 fffff880`0573bff6 : 00000000`00000000 fffffa80`15b24c70 00000000`00000080 fffffa80`15794110 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`0ebc5bc0 fffff800`03510456 : 00000000`fffffc32 fffffa80`15d482e0 fffffa80`0cab25d0 00000000`00000000 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0ebc5c00 fffff800`032682c6 : fffff880`03490180 fffffa80`15d482e0 fffff880`0349b0c0 00000000`00000246 : nt!PspSystemThreadStartup+0x5a
fffff880`0ebc5c40 00000000`00000000 : fffff880`0ebc6000 fffff880`0ebc0000 fffff880`091e3c80 00000000`00000000 : nt!KxStartSystemThread+0x16
2: kd> dt dxgkrnl!_TDR_RECOVERY_CONTEXT fffffa80159124e0 TimeoutReason
+0x010 TimeoutReason : 2 ( TdrReasonPreemptTimeout )
2: kd> u fffff88006a02480
nvlddmkm+0x13b480:
fffff880`06a02480 48ff25e9a55300 jmp qword ptr [nvlddmkm!nvDumpConfig+0x74a88 (fffff880`06f3ca70)]
fffff880`06a02487 cc int 3
fffff880`06a02488 e9bb51f2ff jmp nvlddmkm+0x60648 (fffff880`06927648)
fffff880`06a0248d cc int 3
fffff880`06a0248e cc int 3
fffff880`06a0248f cc int 3
fffff880`06a02490 48ff2599a55300 jmp qword ptr [nvlddmkm!nvDumpConfig+0x74a48 (fffff880`06f3ca30)]
fffff880`06a02497 cc int 3
2: kd> lmivm nvlddmkm
start end module name
fffff880`068c7000 fffff880`072d2000 nvlddmkm (export symbols) nvlddmkm.sys
Symbol file: nvlddmkm.sys
Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Fri Mar 13 09:39:56 2015 (550304CC)
CheckSum: 009CE879
ImageSize: 00A0B000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Last edited:
If you're curious about TDR (Timeout Detection and Recovery), here's a writeup on MSDN that explains it far better than I could at this point in the evening:
https://msdn.microsoft.com/en-us/Library/Windows/Hardware/ff570088(v=vs.85).aspx
https://msdn.microsoft.com/en-us/Library/Windows/Hardware/ff570088(v=vs.85).aspx
Last edited:
Update, still getting BSOD's, two so far today. Nvidia drivers reinstalled as the machine is useless without them,
Well, everything else has been replaced, the power supply is the only thing left from the original machine.
After reading this I've set the Image settings in the Nvidia control panel to balanced. (Yes I know, but I am clutching at straws.)
Does anybody else have any other suggestions?
Well, everything else has been replaced, the power supply is the only thing left from the original machine.
After reading this I've set the Image settings in the Nvidia control panel to balanced. (Yes I know, but I am clutching at straws.)
Does anybody else have any other suggestions?
SpeedFan is terrible. Use something like Speccy instead if you're looking to also view GPU temperatures - https://www.piriform.com/speccy
I prefer Open hardware monitor, but yes - SpeedFan isn't known to be the most accurate. Might want to validate with something else.
Open Hardware Monitor - Core temp, fan speed and voltages in a free software gadget
Open Hardware Monitor - Core temp, fan speed and voltages in a free software gadget
I am using AIDA64 Extreme to monitor temps and voltages. I hope that meets with your approval. With you all recommending different products it is very confusing. With AIDA I can at least log the items monitored to disk. What I would really like is a monitoring program where I can use another PC/Mac. Ipad for choice, to log the items of interest, I haven't found one I can log to yet. Just monitor.
Still getting BSOD's, approx once a day, Verifier is still active. I am slightly concerned about not including the Microsoft drivers in the drivers verifier is monitoring. There is an assumption there I am not convinced is valid.
Latest BSOD was a douzie, it happened whilst I was shuting down. No details, as no dump was recorded. It said it was making one, but there was nothing when I rebooted.
Still getting BSOD's, approx once a day, Verifier is still active. I am slightly concerned about not including the Microsoft drivers in the drivers verifier is monitoring. There is an assumption there I am not convinced is valid.
Latest BSOD was a douzie, it happened whilst I was shuting down. No details, as no dump was recorded. It said it was making one, but there was nothing when I rebooted.
This morning's BSOD happened whilst AIDA64 was logging and there is nothing unusual about the temps or anything else. I would attach a CSV file of the readings, but Sysnative keeps report that my CSV files are invalid. I could probably email it direct, if anybody wants to check my findings, I am not an expert after all.
The last readings were recorded at 10:33. I discovered the BSOD at 12:08 which is when the memory dumps are time stamped.
One thing I've noticed, if the PC does not go to sleep after 30 mins inactivity as it is setup to. Then a BSOD occurs;
When a BSOD occurs all the fans are running at high speed and the temps are very high. This is not recorded by logging software as the machine has hung. My evidence for this is that when rebooted the CPU temps are about 60-65C and dropping.
I shall provide a link to the memory.dmp when I have had time to zip it and upload it to DropBox.
The last readings were recorded at 10:33. I discovered the BSOD at 12:08 which is when the memory dumps are time stamped.
One thing I've noticed, if the PC does not go to sleep after 30 mins inactivity as it is setup to. Then a BSOD occurs;
- either after some period of not going to sleep,
- or when I return before it crashes, as soon as I log in.
When a BSOD occurs all the fans are running at high speed and the temps are very high. This is not recorded by logging software as the machine has hung. My evidence for this is that when rebooted the CPU temps are about 60-65C and dropping.
I shall provide a link to the memory.dmp when I have had time to zip it and upload it to DropBox.
Has Sysnative Forums helped you? Please consider donating to help us support the site!