BUGCHECK 0x1A & 0xC1 Issue
Hi! I've started to experience BSODs on a quite fresh, 2 week old, installation of Win7, that I'm hoping someone can help me with.
The first one was bugcheck 1A, with the following WinDbg output from minidump:
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41284, 23f2e001, 185d9, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ad3 )
Followup: MachineOwner
2: kd> !analyze -v
* Bugcheck Analysis *
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 0000000023f2e001
Arg3: 00000000000185d9
Arg4: fffff70001080000
Debugging Details:
BUGCHECK_STR: 0x1a_41284
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff80002b28727 to fffff80002ad1bc0
STACK_TEXT:
fffff880`0bf2a7d8 fffff800`02b28727 : 00000000`0000001a 00000000`00041284 00000000`23f2e001 00000000`000185d9 : nt!KeBugCheckEx
fffff880`0bf2a7e0 fffff800`02b02ef0 : fffff700`01080000 dd900001`6a936867 ea900003`2a906c66 fffff680`001598d8 : nt! ?? ::FNODOBFM::`string'+0x4ad3
fffff880`0bf2a820 fffff800`02abe3df : fffffa80`00000000 00000000`240b8fff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x4e8
fffff880`0bf2a9e0 fffff800`02ad0e53 : ffffffff`ffffffff 00000000`030be2a0 00000000`030be268 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0bf2aae0 00000000`77c2149a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`030be1d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c2149a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4ad3
fffff800`02b28727 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4ad3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 521ea035
IMAGE_VERSION: 6.1.7601.18247
FAILURE_BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ad3
BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ad3
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x1a_41284_nt!_??_::fnodobfm::_string_+4ad3
FAILURE_ID_HASH: {be05fdaa-4306-87c0-1518-88e378a4f79a}
Followup: MachineOwner
While chasing that one, I followed instructions at http://mikemstech.blogspot.com/2011/12/enable-driver-verifier-to-help-identify.html and installed verifier. When the next crash occurred (about 12 hours later), I got the following out of minidump:
4: kd> !analyze -v
* Bugcheck Analysis *
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption. Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: fffff980a5f94a90, address trying to free
Arg2: fffff980a5f94355, address where one bit is corrupted
Arg3: 000000000023c578, (reserved)
Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error
Debugging Details:
BUGCHECK_STR: 0xC1_32
SPECIAL_POOL_CORRUPTION_TYPE: 32
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff80002b11cb3 to fffff80002a82bc0
STACK_TEXT:
fffff880`033475b8 fffff800`02b11cb3 : 00000000`000000c1 fffff980`a5f94a90 fffff980`a5f94355 00000000`0023c578 : nt!KeBugCheckEx
fffff880`033475c0 fffff800`02b8a903 : fffff6fc`c0535040 00000980`00000000 00000000`00000000 fffff980`a5f94e00 : nt!MiCheckSpecialPoolSlop+0x83
fffff880`03347600 fffff800`02bb5975 : 00000000`0000077f 00000000`4666744e ffffffff`e6c71d80 fffff980`a5f94a90 : nt!MmFreeSpecialPool+0x1d3
fffff880`03347740 fffff800`02f29a3b : fffff880`033478b0 00000000`00010282 fffff980`a5f94a90 fffff980`9eaf6e40 : nt!ExDeferredFreePool+0xf6d
fffff880`033477f0 fffff880`014c5f86 : fffff880`033478b0 00000000`00000000 fffff980`9eaf6e40 fffff980`9eaf6e40 : nt!VerifierExFreePool+0x1b
fffff880`03347820 fffff880`01442332 : fffff800`02c28280 fffff880`03347a01 fffff880`033478a1 fffff980`a5f94a90 : Ntfs!NtfsDeleteFcb+0x3f6
fffff880`03347880 fffff880`014c7a2c : fffff980`9eaf6e40 fffffa80`0ea6e180 fffff980`a5f94a90 fffff980`a5f94ed0 : Ntfs!NtfsTeardownFromLcb+0x1e2
fffff880`03347910 fffff880`0144aa52 : fffff980`9eaf6e40 fffff980`9eaf6e40 fffff980`a5f94a90 fffff800`02c28200 : Ntfs!NtfsTeardownStructures+0xcc
fffff880`03347990 fffff880`014d72d3 : fffff980`9eaf6e40 fffff980`a5f94a90 fffff980`a5f94a90 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2
fffff880`033479d0 fffff880`01529d32 : fffff980`9eaf6e40 fffff980`a5f94bc0 fffff980`a5f94a90 fffffa80`0ea6e180 : Ntfs!NtfsCommonClose+0x353
fffff880`03347aa0 fffff800`02a8c261 : 00000000`00000000 fffff800`02d79101 fffffa80`0d608800 fffffa80`00000002 : Ntfs!NtfsFspCloseInternal+0x186
fffff880`03347b70 fffff800`02d1f2ea : 00000000`00000000 fffffa80`0d608850 00000000`00000080 fffffa80`0cb91240 : nt!ExpWorkerThread+0x111
fffff880`03347c00 fffff800`02a738e6 : fffff880`009b3180 fffffa80`0d608850 fffff880`009be040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03347c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiCheckSpecialPoolSlop+83
fffff800`02b11cb3 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiCheckSpecialPoolSlop+83
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 521ea035
IMAGE_VERSION: 6.1.7601.18247
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xC1_32_VRF_nt!MiCheckSpecialPoolSlop+83
BUCKET_ID: X64_0xC1_32_VRF_nt!MiCheckSpecialPoolSlop+83
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0xc1_32_vrf_nt!micheckspecialpoolslop+83
FAILURE_ID_HASH: {505f65de-e587-f68a-e712-37e9b5717292}
Followup: MachineOwner
At this point I'm stuck as I don't see the name of the offending driver, and can't figure out how to get one.
Please help!
Here is the link to the zip file containing both minidumps: https://onedrive.live.com/redir?resid=CF6086BD502CB79D!134&authkey=!AO5I1x3ruPUauCA&ithint=file%2c.zip
LBm2sys
First we need the actual DMP file to examine (instructions below).
Second, you can change the set of drivers being examined to "all" to force the issue
Third, you may also want to run memtest to see if it is actually the RAM
We do need the actual DMP file as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.
Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
If you have any questions about the procedure please ask
If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't
know what it is you probably are not overclocking.
Since it is more likely to be a driver please run verifier first.
1-Driver verifier (for complete directions see our wiki here)
If verifier does not find the issue we can move on to this.
2-Memtest. (You can read more about running memtest here)
Co-Authored by JMH3143
Wanikiya and Dyami--Team Zigzag
Similar Messages
-
The computer has rebooted from a bugcheck, constant crash.
My newly built PC rebooted constantly and its driving me nuts, can anyone point me the reason? The errors are like this:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff8000db1f0c0, 0x0000000000000000, 0xffffffffffffffff). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 112114-8000-01.
I ve uploaded the most recent .dmp files here
http://1drv.ms/1xWeDon
if it helps. Will gladly upload anything you request, I just want to know if its my faulty hardware or software issue. If this is the wrong section, please move it where appropriate.
Thank you.KP
These were Related to ndisrd.sys NDISRD helper driver from NT Kernel Resources. This may be a part of the OS or it may be malware. I would run a system file check and malwarebytes
Please run a system file check (SFC)
All instructions are in our Wiki article below...
Should you have any questions please ask us.
System file check (SFC) Scan and Repair System Files
Please download the free version of Malwarebytes.
Update it immediately.
Do a full system scan
Let us know the results at the end.
http://www.malwarebytes.org/products
Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\New folder\112214-29468-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
Machine Name:
Kernel base = 0xfffff802`d307c000 PsLoadedModuleList = 0xfffff802`d3352370
Debug session time: Fri Nov 21 20:45:57.058 2014 (UTC - 5:00)
System Uptime: 0 days 0:00:15.828
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck C4, {40, 0, ffffcf80f31fcc10, 0}
*** WARNING: Unable to verify timestamp for ndisrd.sys
*** ERROR: Module load completed but symbols could not be loaded for ndisrd.sys
Probably caused by : ndisrd.sys ( ndisrd+2716 )
Followup: MachineOwner
0: kd> !analyze -v
* Bugcheck Analysis *
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000040, Acquiring a spinlock at IRQL < DISPATCH_LEVEL.
Arg2: 0000000000000000, Current IRQL
Arg3: ffffcf80f31fcc10, Spinlock address
Arg4: 0000000000000000
Debugging Details:
BUGCHECK_STR: 0xc4_40
CURRENT_IRQL: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: NetworkGenie.e
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
LAST_CONTROL_TRANSFER: from fffff802d36fe6b0 to fffff802d31cb1a0
STACK_TEXT:
ffffd000`20efd778 fffff802`d36fe6b0 : 00000000`000000c4 00000000`00000040 00000000`00000000 ffffcf80`f31fcc10 : nt!KeBugCheckEx
ffffd000`20efd780 fffff802`d37048e7 : fffff800`4cd921b0 ffffcf80`f3f24f70 ffffd000`20efd800 fffff802`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
ffffd000`20efd7c0 fffff800`4cd8e716 : ffffcf80`f31fcbc0 ffffd000`20efd868 00000000`00000000 fffff802`00000001 : nt!VerifierKeAcquireSpinLockAtDpcLevel+0x9b
ffffd000`20efd800 ffffcf80`f31fcbc0 : ffffd000`20efd868 00000000`00000000 fffff802`00000001 00000000`00000000 : ndisrd+0x2716
ffffd000`20efd808 ffffd000`20efd868 : 00000000`00000000 fffff802`00000001 00000000`00000000 fffff800`4cd8fb99 : 0xffffcf80`f31fcbc0
ffffd000`20efd810 00000000`00000000 : fffff802`00000001 00000000`00000000 fffff800`4cd8fb99 00000000`00010001 : 0xffffd000`20efd868
STACK_COMMAND: kb
FOLLOWUP_IP:
ndisrd+2716
fffff800`4cd8e716 ?? ???
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: ndisrd+2716
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ndisrd
IMAGE_NAME: ndisrd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e707f81
FAILURE_BUCKET_ID: 0xc4_40_VRF_ndisrd+2716
BUCKET_ID: 0xc4_40_VRF_ndisrd+2716
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xc4_40_vrf_ndisrd+2716
FAILURE_ID_HASH: {df7c0baf-f4d9-83e3-c876-e372e7f0e706}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag -
Windows 2008 Enterprise 32-bit Random Blue Screen 0x000000C4
Hello,
We have a customer with IBM x3500 M3 server, Windows 2008 Enterprise SP2 32-bit, 24GB RAM (Domain, file and print server, rdp server roles installed).
Since December 2013, they have been experiencing random reboots (once or twice a month), so I ran debug on the memory.dmp and found that ntkrpamp.exe wa scausing this issue:
Debug on memory.dmp file for January, 2014:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Debug\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\Win2008E.DVD
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (12 procs) Free x86 compatible
Product: LanManNt, suite: Enterprise TerminalServer
Built by: 6002.18881.x86fre.vistasp2_gdr.130707-1535
Machine Name:
Kernel base = 0x82233000 PsLoadedModuleList = 0x8234ac70
Debug session time: Wed Jan 8 08:24:19.852 2014 (UTC - 5:00)
System Uptime: 4 days 0:37:56.528
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis
Use !analyze -v to get detailed debugging information.
BugCheck 50, {f85c5048, 0, 823af2bf, 0}
Probably caused by : ntkrpamp.exe ( nt!CmpCheckKey+61b )
Followup: MachineOwner
9: kd> !analyze -v
* Bugcheck Analysis
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: f85c5048, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 823af2bf, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
READ_ADDRESS: f85c5048
FAULTING_IP:
nt!CmpCheckKey+61b
823af2bf 394724 cmp dword ptr [edi+24h],eax
MM_INTERNAL_CODE: 0
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: 97b7d9ec -- (.trap 0xffffffff97b7d9ec)
ErrCode = 00000000
eax=00000000 ebx=e6b30024 ecx=19ef8172 edx=00000035 esi=a559e6a8 edi=f85c5024
eip=823af2bf esp=97b7da60 ebp=97b7da8c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!CmpCheckKey+0x61b:
823af2bf 394724 cmp dword ptr [edi+24h],eax ds:0023:f85c5048=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 82280de4 to 822cb292
STACK_TEXT:
97b7d9d4 82280de4 00000000 f85c5048 00000000 nt!MmAccessFault+0x10b
97b7d9d4 823af2bf 00000000 f85c5048 00000000 nt!KiTrap0E+0xdc
97b7da8c 823b581a 01000001 009c4020 009c3f70 nt!CmpCheckKey+0x61b
97b7dabc 823b5e48 a559e6a8 01000001 00000006 nt!CmpCheckRegistry2+0x8c
97b7db04 823b086e 01000001 97b7dc60 8000a05c nt!CmCheckRegistry+0xf5
97b7db60 823b2fdd 97b7dbb4 00000005 00000000 nt!CmpInitializeHive+0x4c1
97b7dbd8 823b527d 97b7dc60 00000000 97b7dc4c nt!CmpInitHiveFromFile+0x19e
97b7dc18 823ab4c5 97b7dc60 00000000 97b7dc7b nt!CmpCmdHiveOpen+0x36
97b7dd14 823ab6fa 00000002 8232b5a0 00000002 nt!CmpFlushBackupHive+0x2fd
97b7dd38 8248acbd 8233513c 8e9462d8 822d8d4a nt!CmpSyncBackupHives+0x90
97b7dd44 822d8d4a 00000000 00000000 8e9462d8 nt!CmpPeriodicBackupFlushWorker+0x32
97b7dd7c 8240901c 00000000 8e585cb2 00000000 nt!ExpWorkerThread+0xfd
97b7ddc0 82271eee 822d8c4d 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!CmpCheckKey+61b
823af2bf 394724 cmp dword ptr [edi+24h],eax
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!CmpCheckKey+61b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 51da1840
FAILURE_BUCKET_ID: 0x50_nt!CmpCheckKey+61b
BUCKET_ID: 0x50_nt!CmpCheckKey+61b
Followup: MachineOwner
Based on google searches, driver verifier was recommended to be turned on to track driver with fault. I enabled verifier on all drivers, disabled automatic server reboot and today server crashed again.
here's the debug output of full memory.dmp file:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\windows\memory.dmp]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\Win2008E.DVD
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (12 procs) Free x86 compatible
Product: LanManNt, suite: Enterprise TerminalServer
Built by: 6002.18881.x86fre.vistasp2_gdr.130707-1535
Machine Name:
Kernel base = 0x82214000 PsLoadedModuleList = 0x8232bc70
Debug session time: Thu Feb 13 08:29:07.272 2014 (UTC - 5:00)
System Uptime: 3 days 23:15:45.259
Loading Kernel Symbols
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffdd00c). Type ".hh dbgerr001" for details
Loading unloaded module list
* Bugcheck Analysis
Use !analyze -v to get detailed debugging information.
BugCheck C4, {e2, af033d18, 2d0000, 0}
Page 6684ef not present in the dump file. Type ".hh dbgerr004" for details
Page 66a0f9 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : srvnet.sys ( srvnet!SrvNetWskSendData+c9 )
Followup: MachineOwner
9: kd> !analyze -v
* Bugcheck Analysis
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 000000e2, IRP field is a user-mode address but Irp->RequestorMode is KernelMode.
Arg2: af033d18, IRP address.
Arg3: 002d0000, User-mode address present as the value of an IRP field.
Arg4: 00000000
Debugging Details:
Page 6684ef not present in the dump file. Type ".hh dbgerr004" for details
Page 66a0f9 not present in the dump file. Type ".hh dbgerr004" for details
BUGCHECK_STR: 0xc4_e2
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: spoolsv.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 824ff5a7 to 822e19bd
STACK_TEXT:
eff67a20 824ff5a7 000000c4 000000e2 af033d18 nt!KeBugCheckEx+0x1e
eff67a40 824fea32 af033d18 002d0000 9930e2e0 nt!VerifierBugCheckIfAppropriate+0x32
eff67a58 824fe7e0 af033d18 9930e2e0 99269b80 nt!ViIrpCheckKernelAddressForIrp+0x51
eff67a70 824f766d 99269b80 af033458 99269b80 nt!VfBeforeCallDriver+0x3d
eff67a90 82258931 af033fa4 af033fe0 99269b80 nt!IovCallDriver+0x1ef
eff67aa4 9b01271a eff67adc aad3183f bd99d34c nt!IofCallDriver+0x1b
eff67aac aad3183f bd99d34c eff67ad0 00000002 afd!WskProAPISend+0x67
eff67adc aad31490 9b01d9d0 af033d18 af033458 srvnet!SrvNetWskSendData+0xc9
eff67afc aad779d2 d5b93018 af033458 00000030 srvnet!SrvNetSendData+0x4d
eff67b14 aadb45bd af033368 aad75459 af033d18 srv!SrvStartSend2+0xa3
eff67b40 aad7522d af033fa4 eff67b84 824f7d4d srv!SrvFsdRestartReadAndX+0x127
eff67b4c 824f7d4d 00000000 af033d18 af033368 srv!SrvFsdIoCompletionRoutine+0x1d
eff67b84 822bb0fb 00000000 af033d18 eff67bf0 nt!IovpLocalCompletionRoutine+0x16e
eff67bb8 824f7b95 824f7a77 ccb4e7c8 eff67c44 nt!IopfCompleteRequest+0x11d
eff67c28 981a30d9 c3fbc2d8 ccb4e7c8 909c9dd0 nt!IovCompleteRequest+0x11c
eff67c4c 824f76be 909c9dd0 ccb4e7c8 9efe80e8 Npfs!NpFsdWrite+0x53
eff67c70 82258931 ccb4e838 ccb4e7c8 909c9dd0 nt!IovCallDriver+0x23f
eff67c84 8245ae25 9efe8114 ccb4e7c8 ccb4e838 nt!IofCallDriver+0x1b
eff67ca4 82427b13 909c9dd0 9efe80e8 00000001 nt!IopSynchronousServiceTail+0x1d9
eff67d38 8225ec96 909c9dd0 00000a39 00000000 nt!NtWriteFile+0x6fc
eff67d38 77755d14 909c9dd0 00000a39 00000000 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
0549f880 00000000 00000000 00000000 00000000 0x77755d14
STACK_COMMAND: kb
FOLLOWUP_IP:
srvnet!SrvNetWskSendData+c9
aad3183f 53 push ebx
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: srvnet!SrvNetWskSendData+c9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: srvnet
IMAGE_NAME: srvnet.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4dbabc34
FAILURE_BUCKET_ID: 0xc4_e2_VRF_srvnet!SrvNetWskSendData+c9
BUCKET_ID: 0xc4_e2_VRF_srvnet!SrvNetWskSendData+c9
Followup: MachineOwner
Here's the output of mini dump file as well:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\windows\minidump\Mini021314-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\Win2008E.DVD
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (12 procs) Free x86 compatible
Product: LanManNt, suite: Enterprise TerminalServer
Built by: 6002.18881.x86fre.vistasp2_gdr.130707-1535
Machine Name:
Kernel base = 0x82214000 PsLoadedModuleList = 0x8232bc70
Debug session time: Thu Feb 13 08:29:07.272 2014 (UTC - 5:00)
System Uptime: 3 days 23:15:45.259
Loading Kernel Symbols
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis
Use !analyze -v to get detailed debugging information.
BugCheck C4, {e2, af033d18, 2d0000, 0}
Probably caused by : srvnet.sys ( srvnet!SrvNetWskSendData+c9 )
Followup: MachineOwner
9: kd> !analyze -v
* Bugcheck Analysis
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 000000e2, IRP field is a user-mode address but Irp->RequestorMode is KernelMode.
Arg2: af033d18, IRP address.
Arg3: 002d0000, User-mode address present as the value of an IRP field.
Arg4: 00000000
Debugging Details:
BUGCHECK_STR: 0xc4_e2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: spoolsv.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 824ff5a7 to 822e19bd
STACK_TEXT:
eff67a20 824ff5a7 000000c4 000000e2 af033d18 nt!KeBugCheckEx+0x1e
eff67a40 824fea32 af033d18 002d0000 9930e2e0 nt!VerifierBugCheckIfAppropriate+0x32
eff67a58 824fe7e0 af033d18 9930e2e0 99269b80 nt!ViIrpCheckKernelAddressForIrp+0x51
eff67a70 824f766d 99269b80 af033458 99269b80 nt!VfBeforeCallDriver+0x3d
eff67a90 82258931 af033fa4 af033fe0 99269b80 nt!IovCallDriver+0x1ef
eff67aa4 9b01271a eff67adc aad3183f bd99d34c nt!IofCallDriver+0x1b
eff67aac aad3183f bd99d34c eff67ad0 00000002 afd!WskProAPISend+0x67
eff67adc aad31490 9b01d9d0 af033d18 af033458 srvnet!SrvNetWskSendData+0xc9
eff67afc aad779d2 d5b93018 af033458 00000030 srvnet!SrvNetSendData+0x4d
eff67b14 aadb45bd af033368 aad75459 af033d18 srv!SrvStartSend2+0xa3
eff67b40 aad7522d af033fa4 eff67b84 824f7d4d srv!SrvFsdRestartReadAndX+0x127
eff67b4c 824f7d4d 00000000 af033d18 af033368 srv!SrvFsdIoCompletionRoutine+0x1d
eff67b84 822bb0fb 00000000 af033d18 eff67bf0 nt!IovpLocalCompletionRoutine+0x16e
eff67bb8 824f7b95 824f7a77 ccb4e7c8 eff67c44 nt!IopfCompleteRequest+0x11d
eff67c28 981a30d9 c3fbc2d8 ccb4e7c8 909c9dd0 nt!IovCompleteRequest+0x11c
eff67c4c 824f76be 909c9dd0 ccb4e7c8 9efe80e8 Npfs!NpFsdWrite+0x53
eff67c70 82258931 ccb4e838 ccb4e7c8 909c9dd0 nt!IovCallDriver+0x23f
eff67c84 8245ae25 9efe8114 ccb4e7c8 ccb4e838 nt!IofCallDriver+0x1b
eff67ca4 82427b13 909c9dd0 9efe80e8 00000001 nt!IopSynchronousServiceTail+0x1d9
eff67d38 8225ec96 909c9dd0 00000a39 00000000 nt!NtWriteFile+0x6fc
eff67d38 77755d14 909c9dd0 00000a39 00000000 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
0549f880 00000000 00000000 00000000 00000000 0x77755d14
STACK_COMMAND: kb
FOLLOWUP_IP:
srvnet!SrvNetWskSendData+c9
aad3183f 53 push ebx
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: srvnet!SrvNetWskSendData+c9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: srvnet
IMAGE_NAME: srvnet.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4dbabc34
FAILURE_BUCKET_ID: 0xc4_e2_VRF_srvnet!SrvNetWskSendData+c9
BUCKET_ID: 0xc4_e2_VRF_srvnet!SrvNetWskSendData+c9
Followup: MachineOwner
I'd like to know how to fix this. Server has up-to-date firmware and drivers from IBM. It's also up-to-date on all windows updates.
Any help is greatly appreciated.
WillThis one may help.
http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023(v=vs.85).aspx
I'd test the RAM and or get with IBM on best method to verify the hardware and drivers.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. -
Windows has recovered from an unexpected shutdown(blue screen) windows 7 ultimate 64 bit
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: 50
BCP1: FFFFF90043C98BEC
BCP2: 0000000000000001
BCP3: FFFFF9600025033E
BCP4: 0000000000000005
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\060614-25256-01.dmp
C:\Windows\Temp\WER-31699-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
please help
this happens after i add a 2gb ramYH
These were driver verified and Related to nvlddmkm.sys nVidia Display Driver. I would install the newest driver available (even if it is the same date as drivers do become corrupt)
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\060714-31793-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*H:\symbols*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.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`03a4c000 PsLoadedModuleList = 0xfffff800`03c8f670
Debug session time: Sat Jun 7 01:23:16.118 2014 (UTC - 4:00)
System Uptime: 0 days 0:03:21.913
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck C4, {f6, 17c, fffffa8005acab30, fffff8800f327295}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+9b295 )
Followup: MachineOwner
1: kd> !analyze -v
* Bugcheck Analysis *
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 000000000000017c, Handle value being referenced.
Arg3: fffffa8005acab30, Address of the current process.
Arg4: fffff8800f327295, Address inside the driver that is performing the incorrect reference.
Debugging Details:
BUGCHECK_STR: 0xc4_f6
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: nvspcaps64.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff80003f4f4ec to fffff80003ac1c00
STACK_TEXT:
fffff880`09fe3a38 fffff800`03f4f4ec : 00000000`000000c4 00000000`000000f6 00000000`0000017c fffffa80`05acab30 : nt!KeBugCheckEx
fffff880`09fe3a40 fffff800`03f64bf4 : 00000000`0000017c fffffa80`05acab30 00000000`00000004 fffff800`03aec83b : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`09fe3a80 fffff800`03d1c0e0 : 00000000`00000000 fffff880`09fe3cd0 fffff880`09fe3e00 fffff880`09fe3f88 : nt!VfCheckUserHandle+0x1b4
fffff880`09fe3b60 fffff800`03d76c31 : fffff8a0`0ab06000 00000000`00000002 fffffa80`018c9f30 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x202ae
fffff880`09fe3c30 fffff800`03ac0e93 : 00000000`0000017c 00000000`00000240 00000000`00000000 00000000`00000003 : nt!NtSetValueKey+0xe1
fffff880`09fe3d60 fffff800`03abd450 : fffff800`03f534db fffff880`0f327295 fffff880`09fe4afc 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`09fe3f68 fffff800`03f534db : fffff880`0f327295 fffff880`09fe4afc 00000000`00000000 fffff800`03abd450 : nt!KiServiceLinkage
fffff880`09fe3f70 fffff880`0f327295 : 00000000`00000008 fffff880`09fe4031 00000000`00000011 ffffffff`80000d38 : nt!VfZwSetValueKey+0x6b
fffff880`09fe3fc0 00000000`00000008 : fffff880`09fe4031 00000000`00000011 ffffffff`80000d38 fffff880`09fe4afc : nvlddmkm+0x9b295
fffff880`09fe3fc8 fffff880`09fe4031 : 00000000`00000011 ffffffff`80000d38 fffff880`09fe4afc fffff800`00000004 : 0x8
fffff880`09fe3fd0 00000000`00000011 : ffffffff`80000d38 fffff880`09fe4afc fffff800`00000004 00000000`00000000 : 0xfffff880`09fe4031
fffff880`09fe3fd8 ffffffff`80000d38 : fffff880`09fe4afc fffff800`00000004 00000000`00000000 00000000`00000000 : 0x11
fffff880`09fe3fe0 fffff880`09fe4afc : fffff800`00000004 00000000`00000000 00000000`00000000 00000000`0000017c : 0xffffffff`80000d38
fffff880`09fe3fe8 fffff800`00000004 : 00000000`00000000 00000000`00000000 00000000`0000017c 00000000`00120010 : 0xfffff880`09fe4afc
fffff880`09fe3ff0 00000000`00000000 : 00000000`00000000 00000000`0000017c 00000000`00120010 fffff880`09fe4a0a : 0xfffff800`00000004
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+9b295
fffff880`0f327295 488b4dcf mov rcx,qword ptr [rbp-31h]
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: nvlddmkm+9b295
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52b326bc
FAILURE_BUCKET_ID: X64_0xc4_f6_VRF_nvlddmkm+9b295
BUCKET_ID: X64_0xc4_f6_VRF_nvlddmkm+9b295
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0xc4_f6_vrf_nvlddmkm+9b295
FAILURE_ID_HASH: {b9cbc4df-f49a-e3ea-a7bf-8726e91f6c99}
Followup: MachineOwner
Other drivers needing updating
nvm62x64.sys 10/17/2008 5:01:06 PM fffff880`04400000 fffff880`04463d80 0x48f8fd12 0x00063d80
anodlwfx.sys 3/6/2009 6:10:08 AM fffff880`041b3000 fffff880`041bc000 0x49b0f680 0x00009000
Wanikiya and Dyami--Team Zigzag -
Flash Crashes across all browsers and recent fatal errors
This problem has basicly been going on for years and my operating system has been resintalled a couple of times before but basicly the problem is that adobe flash player (and Microsoft Silverlight) would crash a browser (IE, Chrome, and Firefox) often. I have tried the fixes ive read about but they didnt seem to work so I just decided to put up with it until I began getting fatal errors. I had my hardware checked out and there are no problems with and all my drivers are up to date.
Flash: 11.5.502.135
Windows 7 (64-bit)
HD 5570 and HD 6870 (upgraded from one to the other but problem still occurs)
Like I said I usually try to put up with flash (and silverlight) crashing my browser but now they crash the browse so badly it forces a bugcheck (or blue screen of death). I have tried to reload my operating system, then updated my drivers, and then in clean boot mode I still get pretty nasty crashes. I think the problem is within one of my drivers but I cant pinpoint which driver is the culprit.
Opened log file 'c:\debug.txt'
3: kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Expanded Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
3: kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000001
Arg3: fffffa8009f8a750
Arg4: 0000000000000000
Debugging Details:
BUGCHECK_STR: 0xc4_91
CUSTOMER_CRASH_COUNT: 6
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: iexplore.exe
CURRENT_IRQL: 1
LAST_CONTROL_TRANSFER: from fffff80002d3380a to fffff80002cdcfc0
STACK_TEXT:
fffff880`0b7a27d8 fffff800`02d3380a : 00000000`000000c4 00000000`00000091 00000000`00000001 fffffa80`09f8a750 : nt!KeBugCheckEx
fffff880`0b7a27e0 fffff800`02fc9b7f : fffff880`0b7a2860 fffff800`02c24768 00000084`00000003 fffff800`0307a0bb : nt! ?? ::FNODOBFM::`string'+0x4874
fffff880`0b7a2820 fffff800`02cce561 : 00000000`00000000 fffff880`0b6cd4f0 00000000`00000003 fffff880`037a4000 : nt!PspGetSetContextInternal+0x8f
fffff880`0b7a2dc0 fffff800`02ccfa37 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspGetSetContextSpecialApc+0xa1
fffff880`0b7a2ed0 fffff800`02cd2c3d : fffffa80`09f8a750 00000000`00000000 00000000`00000000 fffffa80`09f8a750 : nt!KiDeliverApc+0x1c7
fffff880`0b7a2f50 fffff800`02ce3d8f : 000007ff`fff84000 fffff880`0b7a3100 fffffa80`00000000 fffff800`02cdfe7a : nt!KiCommitThreadWait+0x3dd
fffff880`0b7a2fe0 fffff800`02ccedf4 : 00000000`00000000 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x19f
fffff880`0b7a3080 fffff800`02ccfa71 : fffffa80`09f8a750 fffffa80`09f8a7a0 00000000`00000000 00000000`00000000 : nt!KiSuspendThread+0x54
fffff880`0b7a30c0 fffff800`02cd2c3d : fffff880`009ec140 00000000`00000000 fffff800`02cceda0 00000000`00000000 : nt!KiDeliverApc+0x201
fffff880`0b7a3140 fffff800`02cdf4da : fffffa80`08a3a000 00000000`00000001 00000000`0000005e 00000000`00000000 : nt!KiCommitThreadWait+0x3dd
fffff880`0b7a31d0 fffff800`02fcf31f : fffff880`00000001 fffff880`0b7a3520 00000000`00000000 00000000`00000006 : nt!KeWaitForMultipleObjects+0x272
fffff880`0b7a3490 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpWaitForMultipleObjects+0x294
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4874
fffff800`02d3380a cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4874
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be
FAILURE_BUCKET_ID: X64_0xc4_91_nt!_??_::FNODOBFM::_string_+4874
BUCKET_ID: X64_0xc4_91_nt!_??_::FNODOBFM::_string_+4874
Followup: MachineOwner
rax=0000000000000001 rbx=fffff8800b6cda20 rcx=00000000000000c4
rdx=0000000000000091 rsi=fffff8800b6cdaa0 rdi=fffffa8009f8a750
rip=fffff80002cdcfc0 rsp=fffff8800b7a27d8 rbp=fffff8800b7a3c20
r8=0000000000000001 r9=fffffa8009f8a750 r10=fffff8800b6cda20
r11=fffff8800b7a27b0 r12=0000000000000001 r13=0000000000000000
r14=0000000000000000 r15=fffff8800b7a2ec0
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000246
nt!KeBugCheckEx:
fffff800`02cdcfc0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`0b7a27e0=c400000000000000
Child-SP RetAddr : Args to Child : Call Site
fffff880`0b7a27d8 fffff800`02d3380a : 00000000`000000c4 00000000`00000091 00000000`00000001 fffffa80`09f8a750 : nt!KeBugCheckEx
fffff880`0b7a27e0 fffff800`02fc9b7f : fffff880`0b7a2860 fffff800`02c24768 00000084`00000003 fffff800`0307a0bb : nt! ?? ::FNODOBFM::`string'+0x4874
fffff880`0b7a2820 fffff800`02cce561 : 00000000`00000000 fffff880`0b6cd4f0 00000000`00000003 fffff880`037a4000 : nt!PspGetSetContextInternal+0x8f
fffff880`0b7a2dc0 fffff800`02ccfa37 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspGetSetContextSpecialApc+0xa1
fffff880`0b7a2ed0 fffff800`02cd2c3d : fffffa80`09f8a750 00000000`00000000 00000000`00000000 fffffa80`09f8a750 : nt!KiDeliverApc+0x1c7
fffff880`0b7a2f50 fffff800`02ce3d8f : 000007ff`fff84000 fffff880`0b7a3100 fffffa80`00000000 fffff800`02cdfe7a : nt!KiCommitThreadWait+0x3dd
fffff880`0b7a2fe0 fffff800`02ccedf4 : 00000000`00000000 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x19f
fffff880`0b7a3080 fffff800`02ccfa71 : fffffa80`09f8a750 fffffa80`09f8a7a0 00000000`00000000 00000000`00000000 : nt!KiSuspendThread+0x54
fffff880`0b7a30c0 fffff800`02cd2c3d : fffff880`009ec140 00000000`00000000 fffff800`02cceda0 00000000`00000000 : nt!KiDeliverApc+0x201
fffff880`0b7a3140 fffff800`02cdf4da : fffffa80`08a3a000 00000000`00000001 00000000`0000005e 00000000`00000000 : nt!KiCommitThreadWait+0x3dd
fffff880`0b7a31d0 fffff800`02fcf31f : fffff880`00000001 fffff880`0b7a3520 00000000`00000000 00000000`00000006 : nt!KeWaitForMultipleObjects+0x272
fffff880`0b7a3490 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpWaitForMultipleObjects+0x294
start end module name
fffff800`00ba8000 fffff800`00bb2000 kdcom kdcom.dll Sat Feb 05 08:52:49 2011 (4D4D8061)
fffff800`02c15000 fffff800`02c5e000 hal hal.dll Sat Nov 20 05:00:25 2010 (4CE7C669)
fffff800`02c5e000 fffff800`03246000 nt ntkrnlmp.exe Thu Aug 30 08:11:58 2012 (503F82BE)
fffff880`00c07000 fffff880`00c14000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 18:29:09 2009 (4A5BDF65)
fffff880`00c14000 fffff880`00c28000 PSHED PSHED.dll Mon Jul 13 18:32:23 2009 (4A5BE027)
fffff880`00c28000 fffff880`00c86000 CLFS CLFS.SYS Mon Jul 13 16:19:57 2009 (4A5BC11D)
fffff880`00c86000 fffff880`00d46000 CI CI.dll Sat Nov 20 05:12:36 2010 (4CE7C944)
fffff880`00d46000 fffff880`00da2000 volmgrx volmgrx.sys Sat Nov 20 01:20:43 2010 (4CE792EB)
fffff880`00da2000 fffff880`00dcc000 ataport ataport.SYS Sat Nov 20 01:19:15 2010 (4CE79293)
fffff880`00dcc000 fffff880`00de7000 raspppoe raspppoe.sys Mon Jul 13 17:10:17 2009 (4A5BCCE9)
fffff880`00e00000 fffff880`00e1a000 mountmgr mountmgr.sys Sat Nov 20 01:19:21 2010 (4CE79299)
fffff880`00e1a000 fffff880`00e23000 atapi atapi.sys Mon Jul 13 16:19:47 2009 (4A5BC113)
fffff880`00e23000 fffff880`00e2e000 amdxata amdxata.sys Fri Mar 19 09:18:18 2010 (4BA3A3CA)
fffff880`00e41000 fffff880`00f03000 Wdf01000 Wdf01000.sys Wed Jul 25 19:25:13 2012 (5010AA89)
fffff880`00f03000 fffff880`00f13000 WDFLDR WDFLDR.SYS Wed Jul 25 19:29:04 2012 (5010AB70)
fffff880`00f13000 fffff880`00f6a000 ACPI ACPI.sys Sat Nov 20 01:19:16 2010 (4CE79294)
fffff880`00f6a000 fffff880`00f73000 WMILIB WMILIB.SYS Mon Jul 13 16:19:51 2009 (4A5BC117)
fffff880`00f73000 fffff880`00f7d000 msisadrv msisadrv.sys Mon Jul 13 16:19:26 2009 (4A5BC0FE)
fffff880`00f7d000 fffff880`00fb0000 pci pci.sys Sat Nov 20 01:19:11 2010 (4CE7928F)
fffff880`00fb0000 fffff880`00fbd000 vdrvroot vdrvroot.sys Mon Jul 13 17:01:31 2009 (4A5BCADB)
fffff880`00fbd000 fffff880`00fd2000 partmgr partmgr.sys Fri Mar 16 22:06:09 2012 (4F641BC1)
fffff880`00fd2000 fffff880`00fe7000 volmgr volmgr.sys Sat Nov 20 01:19:28 2010 (4CE792A0)
fffff880`00fe7000 fffff880`00fee000 pciide pciide.sys Mon Jul 13 16:19:49 2009 (4A5BC115)
fffff880`00fee000 fffff880`00ffe000 PCIIDEX PCIIDEX.SYS Mon Jul 13 16:19:48 2009 (4A5BC114)
fffff880`01000000 fffff880`01072000 cng cng.sys Fri Aug 24 08:47:16 2012 (5037A204)
fffff880`01072000 fffff880`010d0000 asmtxhci asmtxhci.sys Wed Dec 08 02:14:06 2010 (4CFF5A6E)
fffff880`010df000 fffff880`0112b000 fltmgr fltmgr.sys Sat Nov 20 01:19:24 2010 (4CE7929C)
fffff880`0112b000 fffff880`0113f000 fileinfo fileinfo.sys Mon Jul 13 16:34:25 2009 (4A5BC481)
fffff880`0113f000 fffff880`0119d000 msrpc msrpc.sys Sat Nov 20 01:21:56 2010 (4CE79334)
fffff880`0119d000 fffff880`011c1000 rasl2tp rasl2tp.sys Sat Nov 20 02:52:34 2010 (4CE7A872)
fffff880`011c1000 fffff880`011f0000 ndiswan ndiswan.sys Sat Nov 20 02:52:32 2010 (4CE7A870)
fffff880`01200000 fffff880`01211000 pcw pcw.sys Mon Jul 13 16:19:27 2009 (4A5BC0FF)
fffff880`01211000 fffff880`0121b000 Fs_Rec Fs_Rec.sys Wed Feb 29 19:41:06 2012 (4F4EEFD2)
fffff880`0121b000 fffff880`01231000 AgileVpn AgileVpn.sys Mon Jul 13 17:10:24 2009 (4A5BCCF0)
fffff880`0123d000 fffff880`013e0000 Ntfs Ntfs.sys Fri Aug 31 08:14:14 2012 (5040D4C6)
fffff880`013e0000 fffff880`013fb000 ksecdd ksecdd.sys Fri Jun 01 19:50:23 2012 (4FC97F6F)
fffff880`01400000 fffff880`0142b000 ksecpkg ksecpkg.sys Fri Aug 24 08:48:29 2012 (5037A24D)
fffff880`0142b000 fffff880`0148c000 aswSP aswSP.SYS Tue Oct 30 15:44:06 2012 (50905836)
fffff880`0148c000 fffff880`014a1000 amdppm amdppm.sys Mon Jul 13 16:19:25 2009 (4A5BC0FD)
fffff880`014ad000 fffff880`0159f000 ndis ndis.sys Wed Aug 22 08:11:46 2012 (5034F6B2)
fffff880`0159f000 fffff880`015ff000 NETIO NETIO.SYS Wed Aug 22 08:11:28 2012 (5034F6A0)
fffff880`01600000 fffff880`0163a000 fvevol fvevol.sys Sat Nov 20 01:24:06 2010 (4CE793B6)
fffff880`0163a000 fffff880`01650000 disk disk.sys Mon Jul 13 16:19:57 2009 (4A5BC11D)
fffff880`01650000 fffff880`01680000 CLASSPNP CLASSPNP.SYS Sat Nov 20 01:19:23 2010 (4CE7929B)
fffff880`016b6000 fffff880`016e0000 cdrom cdrom.sys Sat Nov 20 01:19:20 2010 (4CE79298)
fffff880`016e0000 fffff880`018e1000 tcpip tcpip.sys Wed Oct 03 08:09:34 2012 (506C552E)
fffff880`018e1000 fffff880`0192b000 fwpkclnt fwpkclnt.sys Wed Aug 22 08:10:49 2012 (5034F679)
fffff880`0192b000 fffff880`01977000 volsnap volsnap.sys Sat Nov 20 01:20:08 2010 (4CE792C8)
fffff880`01977000 fffff880`0197f000 spldr spldr.sys Mon May 11 09:56:27 2009 (4A0858BB)
fffff880`0197f000 fffff880`019b9000 rdyboost rdyboost.sys Sat Nov 20 01:43:10 2010 (4CE7982E)
fffff880`019b9000 fffff880`019cb000 mup mup.sys Mon Jul 13 16:23:45 2009 (4A5BC201)
fffff880`019cb000 fffff880`019d4000 hwpolicy hwpolicy.sys Sat Nov 20 01:18:54 2010 (4CE7927E)
fffff880`019d4000 fffff880`019fa000 tunnel tunnel.sys Sat Nov 20 02:51:50 2010 (4CE7A846)
fffff880`02c00000 fffff880`02c1d000 serial serial.sys Mon Jul 13 17:00:40 2009 (4A5BCAA8)
fffff880`02c1d000 fffff880`02c38000 wanarp wanarp.sys Sat Nov 20 02:52:36 2010 (4CE7A874)
fffff880`02c38000 fffff880`02c4c000 termdd termdd.sys Sat Nov 20 03:03:40 2010 (4CE7AB0C)
fffff880`02c4c000 fffff880`02c9d000 rdbss rdbss.sys Sat Nov 20 01:27:51 2010 (4CE79497)
fffff880`02c9d000 fffff880`02ca9000 nsiproxy nsiproxy.sys Mon Jul 13 16:21:02 2009 (4A5BC15E)
fffff880`02ca9000 fffff880`02cb4000 mssmbios mssmbios.sys Mon Jul 13 16:31:10 2009 (4A5BC3BE)
fffff880`02cb4000 fffff880`02cc3000 discache discache.sys Mon Jul 13 16:37:18 2009 (4A5BC52E)
fffff880`02cc4000 fffff880`02d4d000 afd afd.sys Tue Dec 27 19:59:20 2011 (4EFA9418)
fffff880`02d4d000 fffff880`02d5d000 aswrdr2 aswrdr2.sys Mon Oct 08 01:23:43 2012 (50728D8F)
fffff880`02d5d000 fffff880`02da2000 netbt netbt.sys Sat Nov 20 01:23:18 2010 (4CE79386)
fffff880`02da2000 fffff880`02dab000 wfplwf wfplwf.sys Mon Jul 13 17:09:26 2009 (4A5BCCB6)
fffff880`02dab000 fffff880`02dd1000 pacer pacer.sys Sat Nov 20 02:52:18 2010 (4CE7A862)
fffff880`02dd1000 fffff880`02de7000 vwififlt vwififlt.sys Mon Jul 13 17:07:22 2009 (4A5BCC3A)
fffff880`02de7000 fffff880`02df6000 netbios netbios.sys Mon Jul 13 17:09:26 2009 (4A5BCCB6)
fffff880`03c00000 fffff880`03c2c000 RzSynapse RzSynapse.sys Wed Mar 23 23:24:20 2011 (4D8AE394)
fffff880`03c2c000 fffff880`03c3a000 kbdhid kbdhid.sys Sat Nov 20 02:33:25 2010 (4CE7A3F5)
fffff880`03c3a000 fffff880`03c48000 monitor monitor.sys Mon Jul 13 16:38:52 2009 (4A5BC58C)
fffff880`03c48000 fffff880`03c62c80 usbaudio usbaudio.sys Sat Nov 20 02:43:52 2010 (4CE7A668)
fffff880`03c63000 fffff880`03c6c000 aswFsBlk aswFsBlk.SYS Tue Oct 30 15:43:04 2012 (509057F8)
fffff880`03c77000 fffff880`03dae000 AE1200w764 AE1200w764.sys Mon Mar 28 17:22:08 2011 (4D912630)
fffff880`03dae000 fffff880`03dbb000 vwifibus vwifibus.sys Mon Jul 13 17:07:21 2009 (4A5BCC39)
fffff880`03dbb000 fffff880`03dc9000 hidusb hidusb.sys Sat Nov 20 02:43:49 2010 (4CE7A665)
fffff880`03dc9000 fffff880`03dd6000 mouhid mouhid.sys Mon Jul 13 17:00:20 2009 (4A5BCA94)
fffff880`03dd6000 fffff880`03df9000 luafv luafv.sys Mon Jul 13 16:26:13 2009 (4A5BC295)
fffff880`04200000 fffff880`04211000 blbdrive blbdrive.sys Mon Jul 13 16:35:59 2009 (4A5BC4DF)
fffff880`04220000 fffff880`04314000 aswSnx aswSnx.SYS Tue Oct 30 15:44:08 2012 (50905838)
fffff880`04314000 fffff880`0431d000 Null Null.SYS Mon Jul 13 16:19:37 2009 (4A5BC109)
fffff880`0431d000 fffff880`04324000 Beep Beep.SYS Mon Jul 13 17:00:13 2009 (4A5BCA8D)
fffff880`04324000 fffff880`04332000 vga vga.sys Mon Jul 13 16:38:47 2009 (4A5BC587)
fffff880`04332000 fffff880`04357000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 16:38:51 2009 (4A5BC58B)
fffff880`04357000 fffff880`04367000 watchdog watchdog.sys Mon Jul 13 16:37:35 2009 (4A5BC53F)
fffff880`04367000 fffff880`04370000 RDPCDD RDPCDD.sys Mon Jul 13 17:16:34 2009 (4A5BCE62)
fffff880`04370000 fffff880`04379000 rdpencdd rdpencdd.sys Mon Jul 13 17:16:34 2009 (4A5BCE62)
fffff880`04379000 fffff880`04382000 rdprefmp rdprefmp.sys Mon Jul 13 17:16:35 2009 (4A5BCE63)
fffff880`04382000 fffff880`0438d000 Msfs Msfs.SYS Mon Jul 13 16:19:47 2009 (4A5BC113)
fffff880`0438d000 fffff880`0439e000 Npfs Npfs.SYS Mon Jul 13 16:19:48 2009 (4A5BC114)
fffff880`0439e000 fffff880`043c0000 tdx tdx.sys Sat Nov 20 01:21:54 2010 (4CE79332)
fffff880`043c0000 fffff880`043cd000 TDI TDI.SYS Sat Nov 20 01:22:06 2010 (4CE7933E)
fffff880`043cd000 fffff880`043df000 aswTdi aswTdi.SYS Tue Oct 30 15:43:16 2012 (50905804)
fffff880`043df000 fffff880`043fd000 dfsc dfsc.sys Sat Nov 20 01:26:31 2010 (4CE79447)
fffff880`04400000 fffff880`04419000 HIDCLASS HIDCLASS.SYS Sat Nov 20 02:43:49 2010 (4CE7A665)
fffff880`04419000 fffff880`04421080 HIDPARSE HIDPARSE.SYS Mon Jul 13 17:06:17 2009 (4A5BCBF9)
fffff880`0442d000 fffff880`044a3000 atikmpag atikmpag.sys Thu Sep 27 18:12:52 2012 (5064F994)
fffff880`044a3000 fffff880`044f9000 USBPORT USBPORT.SYS Thu Mar 24 20:29:12 2011 (4D8C0C08)
fffff880`044f9000 fffff880`0450a000 usbehci usbehci.sys Thu Mar 24 20:29:04 2011 (4D8C0C00)
fffff880`0450a000 fffff880`04527000 parport parport.sys Mon Jul 13 17:00:40 2009 (4A5BCAA8)
fffff880`04527000 fffff880`045c7000 Rt64win7 Rt64win7.sys Tue Sep 27 07:50:33 2011 (4E81E2B9)
fffff880`045c7000 fffff880`045d7000 CompositeBus CompositeBus.sys Sat Nov 20 02:33:17 2010 (4CE7A3ED)
fffff880`045d7000 fffff880`045e3000 rzjoystk rzjoystk.sys Wed Mar 23 23:25:06 2011 (4D8AE3C2)
fffff880`045e3000 fffff880`045eb000 mshidkmdf mshidkmdf.sys Mon Jul 13 17:06:24 2009 (4A5BCC00)
fffff880`045eb000 fffff880`045f7000 ndistapi ndistapi.sys Mon Jul 13 17:10:00 2009 (4A5BCCD8)
fffff880`04a00000 fffff880`04a3d000 portcls portcls.sys Mon Jul 13 17:06:27 2009 (4A5BCC03)
fffff880`04a3d000 fffff880`04a5f000 drmk drmk.sys Mon Jul 13 18:01:25 2009 (4A5BD8E5)
fffff880`04a5f000 fffff880`04a64200 ksthunk ksthunk.sys Mon Jul 13 17:00:19 2009 (4A5BCA93)
fffff880`04a9a000 fffff880`04abb000 raspptp raspptp.sys Sat Nov 20 02:52:31 2010 (4CE7A86F)
fffff880`04abb000 fffff880`04ad5000 rassstp rassstp.sys Mon Jul 13 17:10:25 2009 (4A5BCCF1)
fffff880`04ad5000 fffff880`04ae4000 kbdclass kbdclass.sys Mon Jul 13 16:19:50 2009 (4A5BC116)
fffff880`04ae4000 fffff880`04af3000 mouclass mouclass.sys Mon Jul 13 16:19:50 2009 (4A5BC116)
fffff880`04af3000 fffff880`04af4480 swenum swenum.sys Mon Jul 13 17:00:18 2009 (4A5BCA92)
fffff880`04af5000 fffff880`04b38000 ks ks.sys Sat Nov 20 02:33:23 2010 (4CE7A3F3)
fffff880`04b38000 fffff880`04b4a000 umbus umbus.sys Sat Nov 20 02:44:37 2010 (4CE7A695)
fffff880`04b4a000 fffff880`04ba4000 usbhub usbhub.sys Thu Mar 24 20:29:25 2011 (4D8C0C15)
fffff880`04ba4000 fffff880`04bb9000 NDProxy NDProxy.SYS Sat Nov 20 02:52:20 2010 (4CE7A864)
fffff880`04bb9000 fffff880`04bd4000 AtihdW76 AtihdW76.sys Fri May 11 01:25:40 2012 (4FACCD04)
fffff880`05600000 fffff880`056f4000 dxgkrnl dxgkrnl.sys Sat Nov 20 01:50:50 2010 (4CE799FA)
fffff880`056f4000 fffff880`0617d000 atikmdag atikmdag.sys Thu Sep 27 19:14:57 2012 (50650821)
fffff880`0617d000 fffff880`061c3000 dxgmms1 dxgmms1.sys Sat Nov 20 01:49:53 2010 (4CE799C1)
fffff880`061c3000 fffff880`061e7000 HDAudBus HDAudBus.sys Sat Nov 20 02:43:42 2010 (4CE7A65E)
fffff880`061e7000 fffff880`061f2000 usbohci usbohci.sys Thu Mar 24 20:29:03 2011 (4D8C0BFF)
fffff880`061f2000 fffff880`061fe000 serenum serenum.sys Mon Jul 13 17:00:33 2009 (4A5BCAA1)
fffff880`06208000 fffff880`062d1000 HTTP HTTP.sys Sat Nov 20 01:24:30 2010 (4CE793CE)
fffff880`062d1000 fffff880`062ef000 bowser bowser.sys Tue Feb 22 20:55:04 2011 (4D649328)
fffff880`062ef000 fffff880`06307000 mpsdrv mpsdrv.sys Mon Jul 13 17:08:25 2009 (4A5BCC79)
fffff880`06307000 fffff880`06334000 mrxsmb mrxsmb.sys Tue Apr 26 19:40:38 2011 (4DB78226)
fffff880`06334000 fffff880`06382000 mrxsmb10 mrxsmb10.sys Fri Jul 08 19:46:28 2011 (4E17C104)
fffff880`06382000 fffff880`063a6000 mrxsmb20 mrxsmb20.sys Tue Apr 26 19:39:37 2011 (4DB781E9)
fffff880`063a6000 fffff880`063d8000 AODDriver2 AODDriver2.sys Thu Apr 05 02:23:37 2012 (4F7D6499)
fffff880`06a0e000 fffff880`06a6a000 HdAudio HdAudio.sys Sat Nov 20 02:44:23 2010 (4CE7A687)
fffff880`06a6a000 fffff880`06a78000 crashdmp crashdmp.sys Mon Jul 13 17:01:01 2009 (4A5BCABD)
fffff880`06a78000 fffff880`06a84000 dump_dumpata dump_dumpata.sys Mon Jul 13 16:19:47 2009 (4A5BC113)
fffff880`06a84000 fffff880`06a8d000 dump_atapi dump_atapi.sys Mon Jul 13 16:19:47 2009 (4A5BC113)
fffff880`06a8d000 fffff880`06aa0000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 16:21:51 2009 (4A5BC18F)
fffff880`06aa0000 fffff880`06aac000 Dxapi Dxapi.sys Mon Jul 13 16:38:28 2009 (4A5BC574)
fffff880`06aac000 fffff880`06ace000 asmthub3 asmthub3.sys Wed Dec 08 02:14:14 2010 (4CFF5A76)
fffff880`06ace000 fffff880`06aeb000 usbccgp usbccgp.sys Thu Mar 24 20:29:14 2011 (4D8C0C0A)
fffff880`06aeb000 fffff880`06aecf00 USBD USBD.SYS Thu Mar 24 20:28:59 2011 (4D8C0BFB)
fffff880`06aed000 fffff880`06b0f000 aswMonFlt aswMonFlt.sys Tue Oct 30 15:43:09 2012 (509057FD)
fffff880`06b0f000 fffff880`06b24000 lltdio lltdio.sys Mon Jul 13 17:08:50 2009 (4A5BCC92)
fffff880`06b24000 fffff880`06b77000 nwifi nwifi.sys Mon Jul 13 17:07:23 2009 (4A5BCC3B)
fffff880`06b77000 fffff880`06b8a000 ndisuio ndisuio.sys Sat Nov 20 02:50:08 2010 (4CE7A7E0)
fffff880`06b8a000 fffff880`06ba2000 rspndr rspndr.sys Mon Jul 13 17:08:50 2009 (4A5BCC92)
fffff880`07414000 fffff880`074ba000 peauth peauth.sys Mon Jul 13 18:01:19 2009 (4A5BD8DF)
fffff880`074ba000 fffff880`074c5000 secdrv secdrv.SYS Wed Sep 13 06:18:38 2006 (4508052E)
fffff880`074c5000 fffff880`074f6000 srvnet srvnet.sys Thu Apr 28 20:05:35 2011 (4DBA2AFF)
fffff880`074f6000 fffff880`07508000 tcpipreg tcpipreg.sys Wed Oct 03 09:07:26 2012 (506C62BE)
fffff880`07508000 fffff880`07571000 srv2 srv2.sys Thu Apr 28 20:05:46 2011 (4DBA2B0A)
fffff880`08aa7000 fffff880`08ab2000 asyncmac asyncmac.sys Mon Jul 13 17:10:13 2009 (4A5BCCE5)
fffff880`08ac2000 fffff880`08b5a000 srv srv.sys Thu Apr 28 20:06:06 2011 (4DBA2B1E)
fffff880`08b75000 fffff880`08bab000 fastfat fastfat.SYS Mon Jul 13 16:23:28 2009 (4A5BC1F0)
fffff880`08be1000 fffff880`08bfa000 WudfPf WudfPf.sys Wed Jul 25 19:26:45 2012 (5010AAE5)
fffff960`000c0000 fffff960`003d6000 win32k win32k.sys Wed Nov 21 19:26:12 2012 (50AD9B54)
fffff960`005b0000 fffff960`005ba000 TSDDD TSDDD.dll unavailable (00000000)
fffff960`00690000 fffff960`006b7000 cdd cdd.dll Sat Nov 20 04:55:34 2010 (4CE7C546)
Unloaded modules:
fffff880`08a00000 fffff880`08a36000 WUDFRd.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00036000
fffff880`08b5a000 fffff880`08b75000 USBSTOR.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0001B000
fffff880`08a36000 fffff880`08aa7000 spsys.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00071000
fffff880`08a36000 fffff880`08aa7000 spsys.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00071000
fffff880`08bab000 fffff880`08be1000 WUDFRd.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00036000
fffff880`01680000 fffff880`0168e000 crashdmp.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000E000
fffff880`0168e000 fffff880`0169a000 dump_ataport
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000C000
fffff880`0169a000 fffff880`016a3000 dump_atapi.s
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00009000
fffff880`016a3000 fffff880`016b6000 dump_dumpfve
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00013000
Closing open log file c:\debug.txtI left it at 10.0.12.36
From: computermachine <[email protected]>
Reply-To: <[email protected]>
Date: Mon, 6 Jul 2009 13:51:31 -0400
To: "Kelly, Suzanne (Agency)" <[email protected]>
Conversation: Flash Plug-in Crashes across all browsers
despite re-install
Subject: Flash Plug-in Crashes across all browsers despite
re-install
what version of flash is working now?
Date: Mon, 6 Jul 2009 08:24:06 -0600
From: mailto:[email protected]
To: mailto:[email protected]
Subject: Flash Player Flash Plug-in Crashes across all browsers despite
re-install
I support a bunch of Mac users and one of them (10.5.7 MBP) ran into this same
problem last week with both Safari and Firefox crashing with the flash player
plugin. If I removed the Flash Player plugin and the .xpt file there was no
crashing but no flash either. I used a combination of different suggestions and
here's what finally worked (so far anyway):
Show package contents for Firefox/Contents/MacOS/components and Get Info
changing perms for read/write for everyone.
Re-installed shockwave plugin using the customized full install (this made no
sense to me since I had made no change to shockwave but as I was testing the
browsers I was prompted to install it, so I did)
Repaired permissions
The version of the Flash Player plugin that ended up installed on this Mac is
10.0.12.36. I started off installing the newer and recommended 10.0.22.87
version but it didn't fix anything. I inadvertently went backwards as I moved
plugins in and out of the Library. I didn't want to change anything once it was
working so I left it at the older version. I hope this helps someone else. -
MSI GTX 560 ti TwinFrozr II\OC
Sometimes, independently of the load GPU image can "break\artefacts", green boxes appear on image. After that video driver tried to restart. Drivers using from 301.42 to 314.21.
I do clear install ALL versions of driver from 301.42 WHQL to 314.21 on windows 7 x64, and On Ubuntu\Mint i test 304.43, 304.51 and 304.84 but i have failing on any versions. i.e. up-to-date doesn't solve my problem.
I change frequency\voltage in afterburner, but it doesn't solve my problem too.
"Falling" at all versions. In linux drivers doesn't restart and i need to reboot my pc my powerswitch.
How can i solve solve the problem? Maybe new bios? (now i have 70.24.2E.00.02) MSI support tell my that i need update drivers *facepalm*
Sorry for bad english.
gpu N560GTX-Ti Twin Frozr II/OC
s/n 602-V238-370B1203008755and some time (one or two times in month) after video crashing drivers don't restart, and i see bsod...
Code: [Select]
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supp
orted by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffffa80159a2740
Arg4: 0000000000000000
Debugging Details:
BUGCHECK_STR: 0xc4_91
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: HD-LogRotator.
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800034e1fc0
STACK_TEXT:
fffff800`00b9cff8 00000000`00000000 : 00000000`00000000 00000000`00000000 000000
00`00000000 00000000`00000000 : nt!KeBugCheckEx
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: ZEROED_STACK
Followup: MachineOwner
or
Code: [Select]
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supp
orted by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffffa80149c3b50
Arg4: 0000000000000000
Debugging Details:
BUGCHECK_STR: 0xc4_91
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: FlashPlayerPlu
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800034cdc40
STACK_TEXT:
fffff800`00b9cfe8 00000000`00000000 : 00000000`00000000 00000000`00000000 000000
00`00000000 00000000`00000000 : nt!KeBugCheckEx
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: ZEROED_STACK
Followup: MachineOwner -
DRIVER_VERIFIER_DETECTED_VIOLATION_0x000000c4 VerifierExt.sys+12487
Ca you help me with this BSOD ? I'm having with windows 7 and windows 8.1
DRIVER_VERIFIER_DETECTED_VIOLATION
Bug Check code : 0x000000c4
Parameter : 00000000`00091001 fffff800`00243e40 ffffe000`021dda10 ffffe000`021dda98
Caused by address : VerifierExt.sys+12487
Minidump : https://www.dropbox.com/s/0atp4x4fk029pu4/040714-5500-01.dmp
IRQL_NOT_LESS_OR_EQUAL
Bug Check code : 0x0000000a
Parameter :00000000`00106eec 00000000`0000000e 00000000`00000001 fffff802`74419873
Caused by address : hal.dll+5873
Minidump : https://www.dropbox.com/s/c0m4na2iirmcesf/040614-4390-01.dmp
This is my pc :
cpu Intel Core i5-4430 3GHz Socket 1150 84W con GPU HD Graphics 4600 Boxed
Mobo AsRock H87M Pro4 Socket 1150 Intel H87 DDR3 SATA3 USB3 MicroATX
VGA Sapphire dual x OC AMD Radeon HD 7870
RAM DDR3 Corsair Vengeance Low Profile CML8GX3M2A1600C9 1600MHz 8GB (2x4GB) CL9 EK00019073
SSD Samsung 840 EVO Basic 120GB Lettura 540MB/s Scrittura 410MB/s SATA3
Hard Disk 3.5" Western Digital Green 4TB 64MB SATA IIINakumbo
Unsure what you mean by "in win 7 & win 8"
The verified DMP was in win 8 and Related to
wfplwfs.sys WFP NDIS 6.30 Lightweight Filter Driver from Microsoft Corporation As a start I would run a system file check
Please run a system file check (SFC)
All instructions are in our Wiki article below...
Should you have any questions please ask us.
System file check (SFC) Scan and Repair System Files
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\040714-5500-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff800`69211000 PsLoadedModuleList = 0xfffff800`694d5990
Debug session time: Mon Apr 7 15:26:55.690 2014 (UTC - 4:00)
System Uptime: 0 days 3:08:02.596
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck C4, {91001, fffff80000243e40, ffffe000021dda10, ffffe000021dda98}
Probably caused by : wfplwfs.sys ( wfplwfs!LwfLowerOidRequest+6e )
Followup: MachineOwner
1: kd> !analyze -v
* Bugcheck Analysis *
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000091001, ID of the 'NdisOidComplete' rule that was violated.
Arg2: fffff80000243e40, A pointer to the string describing the violated rule condition.
Arg3: ffffe000021dda10, Address of internal rule state (second argument to !ruleinfo).
Arg4: ffffe000021dda98, Address of supplemental states (third argument to !ruleinfo).
Debugging Details:
DV_VIOLATED_CONDITION: This OID should only be completed with NDIS_STATUS_NOT_ACCEPTED, NDIS_STATUS_REQUEST_ABORTED, NDIS_STATUS_SUCCESS, or NDIS_STATUS_PENDING.
DV_MSDN_LINK: http://go.microsoft.com/fwlink/?LinkId=278802
DV_RULE_INFO: 0x91001
BUGCHECK_STR: 0xc4_NdisOidComplete_XDV
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
LAST_CONTROL_TRANSFER: from fffff8000023e487 to fffff8006935eca0
STACK_TEXT:
ffffd000`23f21738 fffff800`0023e487 : 00000000`000000c4 00000000`00091001 fffff800`00243e40 ffffe000`021dda10 : nt!KeBugCheckEx
ffffd000`23f21740 fffff800`0022d637 : ffffd000`23f21880 ffffd000`23f21878 ffffe000`02bff000 00000000`0000000a : VerifierExt!SLIC_StatefulAbort+0x22b
ffffd000`23f21830 fffff800`0022ddb3 : ffffe000`021dda10 ffffffff`c000000d ffffcf80`03ec2f44 ffffe000`021dda10 : VerifierExt!SLIC_XdvNdisMiniportOidRequestHandler_exit_NdisOidComplete+0xc7
ffffd000`23f21870 fffff800`00b9b250 : ffffe000`021dc1a0 ffffcf80`03ec2f10 ffffe000`021d8400 ffffd000`00000000 : VerifierExt!XdvNdisMiniportOidRequestHandler_wrapper+0x777
ffffd000`23f218e0 fffff800`00af17c1 : ffffe000`021dc1a0 00000000`00000000 00000000`00000000 00000000`00000008 : ndis!ndisMInvokeOidRequest+0x22170
ffffd000`23f21920 fffff800`00af07e0 : 00000000`00000000 00000000`00000000 ffffd000`23f21b00 ffffcf80`03ec2f58 : ndis!ndisMDoOidRequest+0x3b9
ffffd000`23f21a00 fffff800`00af0c06 : 00000000`67326c57 00000000`67326c57 fffff800`00af1e01 00000000`c0000001 : ndis!ndisQueueOidRequest+0x4b0
ffffd000`23f21b90 fffff800`00f951b2 : ffffcf80`041caf10 00000000`fd01010b ffffcf80`041caf10 ffffe000`01ecac20 : ndis!NdisFOidRequest+0xc2
ffffd000`23f21c50 fffff800`00af1d3e : ffffcf80`03ec2f10 ffffcf80`001d8d70 00000000`00000000 00000000`00000000 : wfplwfs!LwfLowerOidRequest+0x6e
ffffd000`23f21c80 fffff800`692c93f9 : ffffd000`23f21fd0 ffffd000`23f1d000 00000000`00000000 00000000`00000000 : ndis!ndisFDoOidRequestInternal+0x2ee
ffffd000`23f21d80 fffff800`00af05ef : fffff800`00af1a50 ffffcf80`00fd2c70 00000000`00000002 00000000`00000011 : nt!KeExpandKernelStackAndCalloutInternal+0xe9
ffffd000`23f21ed0 fffff800`00af0c06 : 00000000`72636350 00000000`72636350 fffff800`00af1e01 00000000`c0000001 : ndis!ndisQueueOidRequest+0x2bf
ffffd000`23f22060 fffff800`017d0850 : ffffcf80`00f24f20 00000000`fd01010b ffffcf80`00f24f20 ffffd000`23f22750 : ndis!NdisFOidRequest+0xc2
ffffd000`23f22120 fffff800`00af1d3e : ffffcf80`041caf10 ffffcf80`0056ed90 00000000`fd01010b 00000000`00000000 : pacer!PcFilterRequest+0x5c
ffffd000`23f22150 fffff800`692c93f9 : ffffd000`23f224a0 ffffd000`23f1d000 00000000`00000000 00000000`00000000 : ndis!ndisFDoOidRequestInternal+0x2ee
ffffd000`23f22250 fffff800`00af05ef : fffff800`00af1a50 ffffcf80`00f0ac70 fffff6fb`7e000000 fffff6fc`00005d48 : nt!KeExpandKernelStackAndCalloutInternal+0xe9
ffffd000`23f223a0 fffff800`00af4a8e : ffffd000`23f22750 ffffe000`021dc1a0 ffffe000`021dc1a0 00000000`fd01010b : ndis!ndisQueueOidRequest+0x2bf
ffffd000`23f22530 fffff800`00ba9c33 : ffffe000`021dc1a0 ffffe000`021dd108 ffffd000`23f22750 00000000`00010246 : ndis!ndisQuerySetMiniportEx+0x10e
ffffd000`23f22590 fffff800`00b1c248 : 00000000`00000001 ffffe000`021dc1a0 00000000`00000000 ffffd000`23f22750 : ndis!ndisOidPMRemove+0x93
ffffd000`23f225d0 fffff800`00af221b : 00000000`00000001 ffffd000`23f22750 00000000`00000000 00000000`00000004 : ndis!ndisOidPMAddRemove+0x12ef8
ffffd000`23f22610 fffff800`00cb4e2b : ffffe000`01d84ad0 fffff800`692c44e1 00000000`00000000 00000000`00000000 : ndis!ndisMOidRequest+0x22b
ffffd000`23f22720 fffff800`00d588e1 : 00000000`00000000 00000000`c0000056 00000000`fd01010b ffffe000`01ecbab0 : tcpip!FlpNdisRequestUnderReference+0x8f
ffffd000`23f22890 fffff800`00d7a39c : ffffe000`01ecbab0 00000000`00000000 ffffe000`01e39570 ffffe000`01ecbdac : tcpip!FlpNdisRequest+0x6d
ffffd000`23f228e0 fffff800`00dd95cf : 00000000`00000050 ffffe000`00000002 00000000`00000000 00000000`00000000 : tcpip!FlpCleanupWolHandle+0x30
ffffd000`23f22930 fffff800`00d4f154 : ffffd000`23f229d0 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!FlpDisableWakeup+0x9fad3
ffffd000`23f22960 fffff800`00d3994a : 00000000`00000000 00000000`0000000a ffffe000`03f97290 00000000`00000000 : tcpip!FlSetInterface+0xec
ffffd000`23f229b0 fffff800`00d51d40 : ffffe000`03f972a8 00000000`00000000 fffff800`69211000 ffffe000`0176e180 : tcpip!IppSetWolOnInterface+0x42
ffffd000`23f22a20 fffff800`00d71294 : fffff800`694b0100 00000000`00000000 00000000`00000000 ffffe000`01d82e50 : tcpip!IppSetWolParametersWorker+0x9c
ffffd000`23f22a70 fffff800`00807035 : ffffe000`03f97290 fffff2a7`c57d34a7 ffffe000`0176e180 00000000`00000000 : tcpip!InetNsiWorkQueueRoutine+0x15
ffffd000`23f22aa0 fffff800`692b1a73 : ffffe000`01e30d40 ffffe000`01d82e50 00000000`00000000 ffffd000`23f22bd0 : NETIO!NetiopIoWorkItemRoutine+0x35
ffffd000`23f22af0 fffff800`692b21b9 : fffff800`696b2454 fffff800`692b1998 ffffd000`23f22bd0 ffffe000`01e30d40 : nt!IopProcessWorkItem+0xdb
ffffd000`23f22b50 fffff800`6929e2e4 : 00000000`00000002 ffffe000`0176e040 ffffe000`0176e040 ffffe000`000d0580 : nt!ExpWorkerThread+0x2b5
ffffd000`23f22c00 fffff800`693652c6 : fffff800`694ff180 ffffe000`0176e040 ffffe000`01769880 fffff800`6987cbda : nt!PspSystemThreadStartup+0x58
ffffd000`23f22c60 00000000`00000000 : ffffd000`23f23000 ffffd000`23f1d000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
wfplwfs!LwfLowerOidRequest+6e
fffff800`00f951b2 bb03010000 mov ebx,103h
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: wfplwfs!LwfLowerOidRequest+6e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: wfplwfs
IMAGE_NAME: wfplwfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5259df5e
IMAGE_VERSION: 6.3.9600.16427
BUCKET_ID_FUNC_OFFSET: 6e
FAILURE_BUCKET_ID: 0xc4_NdisOidComplete_XDV_VRF_wfplwfs!LwfLowerOidRequest
BUCKET_ID: 0xc4_NdisOidComplete_XDV_VRF_wfplwfs!LwfLowerOidRequest
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xc4_ndisoidcomplete_xdv_vrf_wfplwfs!lwfloweroidrequest
FAILURE_ID_HASH: {49dbb057-371a-cacb-a812-a729cc032602}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag -
Good Evening everybody,
I have several bsod with my pc, can you please help analyze the dump files -->https://onedrive.live.com/?cid=C520DC11D5E5D983&id=C520DC11D5E5D983!267
I tried the memtest and it has not found any error.
My pc is an Asus g750jx and as worked fine since a year.
the first bsod was the tuesday 7/10/2014...
thanks in advance.
Salento.Salento9
I have seen these before I believe.
Driver verified and Related to wfplwfs.sys WFP NDIS 6.30 Lightweight Filter Driver from Microsoft Corporation. Like I said, since it is a system file you should START by running a system file check. I have no idea if you have or what its results
were.
If You did not post this elsewhere my apologies.
Please run a system file check (SFC)
All instructions are in our Wiki article below...
Should you have any questions please ask us.
System file check (SFC) Scan and Repair System Files
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\New folder\122814-3875-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*h:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*h:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
Machine Name:
Kernel base = 0xfffff800`5bc83000 PsLoadedModuleList = 0xfffff800`5bf59370
Debug session time: Sun Dec 28 14:22:54.067 2014 (UTC - 5:00)
System Uptime: 0 days 0:00:14.898
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck C4, {9100e, fffff8000bcd5d90, ffffcf81fbe92f20, ffffcf81fbe92f98}
Probably caused by : wfplwfs.sys ( wfplwfs!LwfLowerOidRequest+6e )
Followup: MachineOwner
5: kd> !analyze -v
* Bugcheck Analysis *
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 000000000009100e, ID of the 'NdisOidDoubleRequest' rule that was violated.
Arg2: fffff8000bcd5d90, A pointer to the string describing the violated rule condition.
Arg3: ffffcf81fbe92f20, Address of internal rule state (second argument to !ruleinfo).
Arg4: ffffcf81fbe92f98, Address of supplemental states (third argument to !ruleinfo).
Debugging Details:
DV_VIOLATED_CONDITION: Double OID request detected at MiniportOidRequest.
DV_MSDN_LINK: http://go.microsoft.com/fwlink/?LinkId=287231
DV_RULE_INFO: 0x9100E
BUGCHECK_STR: 0xc4_NdisOidDoubleRequest_XDV
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff8000bcd0487 to fffff8005bdd21a0
STACK_TEXT:
ffffd000`2308d998 fffff800`0bcd0487 : 00000000`000000c4 00000000`0009100e fffff800`0bcd5d90 ffffcf81`fbe92f20 : nt!KeBugCheckEx
ffffd000`2308d9a0 fffff800`0bcbfae0 : ffffcf81`fbe92f20 00000000`00000000 ffffcf82`11ab6f10 00000000`00000000 : VerifierExt!SLIC_StatefulAbort+0x22b
ffffd000`2308da90 fffff800`0c6fe6e8 : ffffe000`63b641a0 ffffcf82`11ab6f10 ffffcf81`fbb3aba0 00000000`00000000 : VerifierExt!XdvNdisMiniportOidRequestHandler_wrapper+0x4a4
ffffd000`2308db00 fffff800`0c6503a3 : ffffe000`63b641a0 ffffd000`2308dbb9 ffffcf82`11ab6f10 00000000`00000000 : ndis!ndisMInvokeOidRequest+0x2263c
ffffd000`2308db40 fffff800`0c651324 : 00000000`00000000 ffffe000`63b641a0 ffffcf82`11ab6f58 00000000`00000000 : ndis!ndisMDoOidRequest+0x39b
ffffd000`2308dc20 fffff800`0c65175e : 00000000`67326c57 00000000`67326c57 fffff800`0c6509a5 00000000`00000000 : ndis!ndisQueueOidRequest+0x4c4
ffffd000`2308ddc0 fffff800`0cba719e : ffffcf82`11ae8f10 00000000`0d010308 ffffcf82`11ae8f10 ffffcf82`121f6c20 : ndis!NdisFOidRequest+0xc2
ffffd000`2308de80 fffff800`0c6508de : ffffcf82`11ab6f10 ffffcf81`f7be4d70 00000000`00000000 fffff800`5bd4fddd : wfplwfs!LwfLowerOidRequest+0x6e
ffffd000`2308deb0 fffff800`5bd3ef46 : ffffd000`2308e1a0 ffffd000`2308a000 00000000`00000000 ffffcf82`00000000 : ndis!ndisFDoOidRequestInternal+0x2ee
ffffd000`2308dfb0 fffff800`0c651131 : fffff800`0c6505f0 ffffcf82`121b8c70 00000000`00000002 fffff800`0c6509a5 : nt!KeExpandKernelStackAndCalloutInternal+0xe6
ffffd000`2308e0a0 fffff800`0c65175e : fffff800`646e5756 00000000`646e5756 fffff800`0c6509a5 ffffcf82`11aaec01 : ndis!ndisQueueOidRequest+0x2d1
ffffd000`2308e240 fffff800`0d3a3923 : ffffcf82`06a50c20 00000000`0d010308 ffffcf82`06a50c20 ffffcf82`1203aca0 : ndis!NdisFOidRequest+0xc2
ffffd000`2308e300 fffff800`0d3a3b4b : ffffcf82`06a50c01 ffffcf82`06a50c20 ffffcf82`11ae8f10 00000000`00000000 : vwififlt!FilterOidRequestCommon+0x2b3
ffffd000`2308e370 fffff800`0c6508de : ffffcf81`f8f0ed80 00000000`0d010308 00000000`00000000 fffff800`5bf46d80 : vwififlt!FilterOidRequest+0x15b
ffffd000`2308e3c0 fffff800`5bd3ef46 : ffffd000`2308e6b0 ffffd000`2308a000 00000000`00000000 00000000`00000000 : ndis!ndisFDoOidRequestInternal+0x2ee
ffffd000`2308e4c0 fffff800`0c651131 : fffff800`0c6505f0 ffffcf82`11aaec70 00000000`00000400 fffff800`0ec0845f : nt!KeExpandKernelStackAndCalloutInternal+0xe6
ffffd000`2308e5b0 fffff800`0c65175e : 00000000`0d010308 00000000`00000001 ffffd000`2308e920 00000000`00000000 : ndis!ndisQueueOidRequest+0x2d1
ffffd000`2308e750 fffff800`0ec08650 : 00000000`00000008 00000000`00000000 ffffcf82`1138c810 ffffcf82`06a50c20 : ndis!NdisFOidRequest+0xc2
ffffd000`2308e810 fffff800`0ec08b7d : fffff800`0ec5c3f0 ffffcf82`06a50c10 ffffcf82`1138c85c 00000000`00000000 : nwifi!Dot11Request+0x140
ffffd000`2308e850 fffff800`0ec27a90 : 00000000`00000040 00000000`00000001 ffffcf82`1138c85c 00000000`00000000 : nwifi!PtRequestAdapterSync+0xa9
ffffd000`2308e8f0 fffff800`0ec01ccf : ffffe000`65fe4010 ffffe000`65fe4010 ffffcf82`1138c85c ffffcf82`1138c85c : nwifi!ExtSTABootup+0x90
ffffd000`2308ec70 fffff800`0ec10cdc : ffffcf82`1138c810 ffffcf82`1138c810 ffffcf82`1138c810 ffffe000`65fe4010 : nwifi!Dot11InitMiniport+0x303
ffffd000`2308ecf0 fffff800`0c6f5636 : ffffcf82`11ad0c70 ffffd000`2308ef20 ffffcf82`111b0d80 ffffe000`00000001 : nwifi!FilterAttach+0x43c
ffffd000`2308edb0 fffff800`0c7296a9 : ffffe000`63b65160 ffffcf82`111b0d80 00000000`00000000 ffffd000`2308ef30 : ndis!ndisFInvokeAttach+0x36
ffffd000`2308ede0 fffff800`0c6f59fb : ffffcf81`fea30f80 00000000`00000000 ffffe000`63b655e8 ffffe000`63b641a0 : ndis!ndisAttachFilterInner+0x901
ffffd000`2308f1b0 fffff800`0c6e51aa : 00000000`00000001 00000000`00000000 00000000`00000002 00000000`00000000 : ndis!ndisAttachFilter+0x4b
ffffd000`2308f2b0 fffff800`0c6e547c : ffffe000`63b641a0 ffffe000`63b641a0 ffffd000`2308f500 ffffe000`63b655e8 : ndis!Ndis::BindEngine::Iterate+0x75a
ffffd000`2308f4c0 fffff800`0c6e3708 : ffffe000`63b655e8 fffff800`0ec5e080 ffffd000`2308f540 fffff800`0ec5e080 : ndis!Ndis::BindEngine::UpdateBindings+0x64
ffffd000`2308f4f0 fffff800`0c6e55b7 : ffffe000`63b655e8 ffffcf81`fea34fb8 ffffcf81`f497cfc0 fffff800`0ec5e080 : ndis!Ndis::BindEngine::DispatchPendingWork+0x50
ffffd000`2308f520 fffff800`0c71faa6 : ffffcf81`fea4af88 00000000`00010286 ffffd000`2308f598 00000000`00000018 : ndis!Ndis::BindEngine::ApplyBindChanges+0x37
ffffd000`2308f570 fffff800`0c6f3cae : ffffcf81`fea4afd8 fffff800`0ec5e080 ffffcf81`fea34fb8 ffffe000`63b641a0 : ndis!<lambda_1ce06b2b40968439b229a98218e85867>::operator()+0x1b
ffffd000`2308f5a0 fffff800`0c6f3bef : 00000000`00000000 fffff800`0ec5e080 ffffcf82`111b0d80 ffffcf81`fea34fb0 : ndis!NDIS_BIND_DRIVER_BASE::ForEachLink+0x9e
ffffd000`2308f5f0 fffff800`0c6f824e : ffffcf82`111b0d80 fffff800`0ec5e080 00000000`00000010 fffff800`0c6f8208 : ndis!NDIS_BIND_DRIVER_BASE::SetRunningDriverIsReady+0x3f
ffffd000`2308f620 fffff800`0c66e74b : 00000000`00000000 fffff800`0ec5e080 ffffd000`00000000 ffffcf82`111b0d80 : ndis!NDIS_BIND_FILTER_DRIVER::SetRunningDriver+0x46
ffffd000`2308f670 fffff800`0ec6438f : ffffe000`65fb4000 00000000`00000000 00000000`00000000 00000000`00000200 : ndis!NdisFRegisterFilterDriver+0x3af
ffffd000`2308f710 fffff800`5c0c7441 : ffffcf82`11374e60 ffffe000`65fb4000 ffffcf81`f40fefb0 ffffffff`000001c8 : nwifi!DriverEntry+0x1f3
ffffd000`2308f850 fffff800`5c138cee : ffffcf82`00a3a9c0 00000000`00000000 fffff800`5bf32300 ffffcf82`00a3a880 : nt!IopLoadDriver+0x555
ffffd000`2308fb10 fffff800`5bcf25e3 : fffff800`00000000 ffffffff`80000930 fffff800`5c138ca0 ffffcf82`00a3a880 : nt!IopLoadUnloadDriver+0x4e
ffffd000`2308fb50 fffff800`5bd81e70 : ffffd000`d35163c0 ffffcf82`00a3a880 ffffcf82`00a3a880 ffffcf81`efcd6900 : nt!ExpWorkerThread+0x293
ffffd000`2308fc00 fffff800`5bdd87c6 : ffffd000`d350a180 ffffcf82`00a3a880 ffffd000`d35163c0 97979797`97979797 : nt!PspSystemThreadStartup+0x58
ffffd000`2308fc60 00000000`00000000 : ffffd000`23090000 ffffd000`2308a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
wfplwfs!LwfLowerOidRequest+6e
fffff800`0cba719e bb03010000 mov ebx,103h
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: wfplwfs!LwfLowerOidRequest+6e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: wfplwfs
IMAGE_NAME: wfplwfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 531ae165
IMAGE_VERSION: 6.3.9600.17042
BUCKET_ID_FUNC_OFFSET: 6e
FAILURE_BUCKET_ID: 0xc4_NdisOidDoubleRequest_XDV_VRFK_wfplwfs!LwfLowerOidRequest
BUCKET_ID: 0xc4_NdisOidDoubleRequest_XDV_VRFK_wfplwfs!LwfLowerOidRequest
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xc4_ndisoiddoublerequest_xdv_vrfk_wfplwfs!lwfloweroidrequest
FAILURE_ID_HASH: {8eb5825d-42fe-dd3b-bd17-77e88cf2ae44}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag -
Still getting Blue Screen of Death every start up !
hello there i have crashed every time i boot up "turn on not restart" to the windows with BSOD with different errors :
BAD_POOL_HEADER , kernel security check failure , memory mangment , NTFS_FILE_SYSTEM
and other.
those BSOD's comes every startup i mean every time i turn on my pc but after the windows collect the inf. and restart
, i boot normally into windows , but on next day i turn my pc on , i get an error BSOD then restart after collect info. then boot to windows normally .
my PC :
i5-4670K | 2x GTX 760 SC EVGA ACX SLI | ASUS Z87-A | 4x 4 GB Corsair Vengeance 1600mhz | Seasonic Gold X-850W | 120 Samsung 840 SSD | WD 1TB Blue | Corsair C70 Black Case | Windows 8.1 PRO x64 Monitor DELL U2312HM | RAZER
2013 accessoryMeryqat
The one driver verified DMP file was related to your video driver (nvlddmkm.sys). There is a known problem with the december 2013 driver (yours). I would install a much older driver (say 6 months) until a new and less buggy driver is released.
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\New folder\030714-20734-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff800`47605000 PsLoadedModuleList = 0xfffff800`478c9990
Debug session time: Fri Mar 7 08:47:56.423 2014 (UTC - 5:00)
System Uptime: 0 days 0:01:42.124
Loading Kernel Symbols
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
Use !analyze -v to get detailed debugging information.
BugCheck C4, {f6, 224, ffffe000045b1900, fffff80001d42295}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+9b295 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 0000000000000224, Handle value being referenced.
Arg3: ffffe000045b1900, Address of the current process.
Arg4: fffff80001d42295, Address inside the driver that is performing the incorrect reference.
Debugging Details:
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_STR: 0xc4_f6
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: nvspcaps64.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
LAST_CONTROL_TRANSFER: from fffff80047c716a8 to fffff80047752ca0
STACK_TEXT:
ffffd000`27381758 fffff800`47c716a8 : 00000000`000000c4 00000000`000000f6 00000000`00000224 ffffe000`045b1900 : nt!KeBugCheckEx
ffffd000`27381760 fffff800`47c76f98 : ffffe000`045b1900 00000000`00000000 00000000`00000000 fffff800`47c803ac : nt!VerifierBugCheckIfAppropriate+0x3c
ffffd000`273817a0 fffff800`47b3ee73 : 00000000`000000c0 ffffe000`001759e0 ffffd000`27381c20 00000000`00000000 : nt!VfCheckUserHandle+0x1b8
ffffd000`27381880 fffff800`479af5d5 : ffffe000`045bec00 ffffc000`00000002 ffffe000`001759e0 ffffd000`27381900 : nt! ?? ::NNGAKEGL::`string'+0x10503
ffffd000`27381920 fffff800`479f2861 : 00000000`00000000 00000000`00000000 ffffd000`27381950 00000000`00000000 : nt!ObReferenceObjectByHandle+0x25
ffffd000`27381970 fffff800`479f21d1 : ffffc000`099727d0 ffffc000`099727a0 00000000`00000000 ffffc000`099727d0 : nt!CmObReferenceObjectByHandle+0x29
ffffd000`273819b0 fffff800`4775e4b3 : ffffc000`00086c50 ffffd000`27381bc0 00000000`00000000 fffff800`479d0a4e : nt!NtSetValueKey+0x135
ffffd000`27381b30 fffff800`47756900 : fffff800`01d42295 00000000`00000008 ffffd000`27381db1 00000000`00000013 : nt!KiSystemServiceCopyEnd+0x13
ffffd000`27381d38 fffff800`01d42295 : 00000000`00000008 ffffd000`27381db1 00000000`00000013 ffffffff`80000b88 : nt!KiServiceLinkage
ffffd000`27381d40 00000000`00000008 : ffffd000`27381db1 00000000`00000013 ffffffff`80000b88 ffffd000`273829ac : nvlddmkm+0x9b295
ffffd000`27381d48 ffffd000`27381db1 : 00000000`00000013 ffffffff`80000b88 ffffd000`273829ac ffffd000`00000004 : 0x8
ffffd000`27381d50 00000000`00000013 : ffffffff`80000b88 ffffd000`273829ac ffffd000`00000004 00000000`00000000 : 0xffffd000`27381db1
ffffd000`27381d58 ffffffff`80000b88 : ffffd000`273829ac ffffd000`00000004 00000000`00000000 ffffe000`00154880 : 0x13
ffffd000`27381d60 ffffd000`273829ac : ffffd000`00000004 00000000`00000000 ffffe000`00154880 00000000`00000224 : 0xffffffff`80000b88
ffffd000`27381d68 ffffd000`00000004 : 00000000`00000000 ffffe000`00154880 00000000`00000224 fffff800`00160014 : 0xffffd000`273829ac
ffffd000`27381d70 00000000`00000000 : ffffe000`00154880 00000000`00000224 fffff800`00160014 ffffd000`273828ba : 0xffffd000`00000004
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+9b295
fffff800`01d42295 488b4dcf mov rcx,qword ptr [rbp-31h]
SYMBOL_STACK_INDEX: 9
SYMBOL_NAME: nvlddmkm+9b295
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52b326bc
FAILURE_BUCKET_ID: 0xc4_f6_nvlddmkm+9b295
BUCKET_ID: 0xc4_f6_nvlddmkm+9b295
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xc4_f6_nvlddmkm+9b295
FAILURE_ID_HASH: {ef78d4e5-5a2f-ec7e-90e0-5dacbf4d6f2e}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag -
One of the main reasons I bought this MSI Motherboard (790FX-GD70), was because of the "Simple" bios update procedure. MSI still has the live update on-line on their site advertising like it's a great thing.
Is MSI doing false advertising? Is the newest version any better?
I have not tried to use it yet since reading all the problems here. I know you don't have to flash your bios, but why not have the latest one? I am having some memory problems and thought maybe the latest bios would help.
What is the real answer? Anyone know? If I contact MSI are they going to tell me their Live Update On-line works well?
Anyway, thanks for listening.
cusafrYes, I have been to the OCZ web site and have tried many different suggested settings. Last night my system froze in BIOS. Had to reboot and set like for the first time. This morning BSOD right after POST.
Did a memtest last night-no errors. Did a checkdisk test-no errors.
Currently have the 8GB (4x2) AMD Black Edition memory modules set at 8-8-8-24-2t.
Any ideas?
cusafr
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 12/13/2009 7:54:55 PM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880082FB718, 0xFFFFF880082FAF70, 0xFFFFF880012B4E8F)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\121309-13057-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Sun 12/13/2009 1:30:51 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002A6CA09, 0xFFFFF88009A83CD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\121309-14118-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Sat 12/12/2009 9:50:41 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xBE (0xFFFFF88001B41000, 0x800000021CA0A021, 0xFFFFF88006E7D970, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Dump file: C:\Windows\Minidump\121209-14757-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Fri 12/11/2009 2:30:50 AM your computer crashed
This was likely caused by the following module: tvichw64.sys
Bugcheck code: 0xC4 (0xF6, 0x290, 0xFFFFFA80029011D0, 0xFFFFF8800890AB7A)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Dump file: C:\Windows\Minidump\121009-20794-01.dmp
On Fri 12/11/2009 2:10:50 AM your computer crashed
This was likely caused by the following module: tvichw64.sys
Bugcheck code: 0xC4 (0xF6, 0x258, 0xFFFFFA8004D4BB30, 0xFFFFF8800A0C7B7A)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Dump file: C:\Windows\Minidump\121009-22167-01.dmp
On Fri 12/11/2009 1:35:22 AM your computer crashed
This was likely caused by the following module: unknown_image
Bugcheck code: 0xC4 (0xF6, 0x290, 0xFFFFFA800508DB30, 0xFFFFF880099BCB7A)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Dump file: C:\Windows\Minidump\121009-20607-01.dmp
On Thu 12/10/2009 11:39:47 PM your computer crashed
This was likely caused by the following module: tvichw64.sys
Bugcheck code: 0xC4 (0xF6, 0x290, 0xFFFFFA8004AC8B30, 0xFFFFF8800827EB7A)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Dump file: C:\Windows\Minidump\121009-21528-01.dmp
On Thu 12/10/2009 11:30:11 PM your computer crashed
This was likely caused by the following module: tvichw64.sys
Bugcheck code: 0xC4 (0xF6, 0x290, 0xFFFFFA8004467060, 0xFFFFF88009ACFB7A)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Dump file: C:\Windows\Minidump\121009-23166-01.dmp
On Thu 12/10/2009 7:05:43 PM your computer crashed
This was likely caused by the following module: elrawdsk.sys
Bugcheck code: 0xC4 (0xF6, 0x37C, 0xFFFFFA80045422E0, 0xFFFFF880084E1C12)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Dump file: C:\Windows\Minidump\121009-24008-01.dmp
file path: C:\Windows\system32\drivers\elrawdsk.sys
product: RawDisk
company: EldoS Corporation
description: RawDisk Driver. Allows write access to raw disk sectors for user mode applications in Windows 2000, XP, 2003, Vista, 2008.
On Thu 12/10/2009 7:01:14 PM your computer crashed
This was likely caused by the following module: elrawdsk.sys
Bugcheck code: 0xC4 (0xF6, 0x404, 0xFFFFFA8004B97630, 0xFFFFF88007164C12)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Dump file: C:\Windows\Minidump\121009-24663-01.dmp
file path: C:\Windows\system32\drivers\elrawdsk.sys
product: RawDisk
company: EldoS Corporation
description: RawDisk Driver. Allows write access to raw disk sectors for user mode applications in Windows 2000, XP, 2003, Vista, 2008.
On Thu 12/10/2009 6:57:45 PM your computer crashed
This was likely caused by the following module: elrawdsk.sys
Bugcheck code: 0xC4 (0xF6, 0x5E4, 0xFFFFFA8004AEF660, 0xFFFFF880081AFC12)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Dump file: C:\Windows\Minidump\121009-26910-01.dmp
file path: C:\Windows\system32\drivers\elrawdsk.sys
product: RawDisk
company: EldoS Corporation
description: RawDisk Driver. Allows write access to raw disk sectors for user mode applications in Windows 2000, XP, 2003, Vista, 2008.
On Thu 12/10/2009 6:29:41 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xC1 (0xFFFFF900C6608630, 0xFFFFF900C66080B2, 0x93A9C8, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
Dump file: C:\Windows\Minidump\121009-23134-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
Conclusion
12 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. -
MSI GT70 0ND-444US dreaded GPU issues
Hello guys, so i've had my 0ND-444US for about two years now and within the last 6 months i've been getting BSODs (GRAPHICS_DRIVER_TDR_FAULT) when trying to game (nvidia 675m). I've formatted windows, re-pasted gpu heatsink, and tried different drivers with the same result everytime. I've done some research and it sounds like these should've been recalled by MSI as a lot of people have this issue.
My question really is...What are my options? Do I take a $300-$400 gamble on a GPU upgrade? Do I try to repurchase the same junk 675m card?
Here are a couple of my dmp files:
Code: [Select]
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffe0005ec684d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff801119cc608, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
Debugging Details:
FAULTING_IP:
nvlddmkm+9a3608
fffff801`119cc608 48ff258159edff jmp qword ptr [nvlddmkm+0x878f90 (fffff801`118a1f90)]
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
STACK_TEXT:
ffffd000`7cd50a78 fffff801`109f8fac : 00000000`00000116 ffffe000`5ec684d0 fffff801`119cc608 ffffffff`c000009a : nt!KeBugCheckEx
ffffd000`7cd50a80 fffff801`109ed08d : fffff801`119cc608 ffffe000`6078cbb0 ffffe000`5ec684d0 00000000`00000001 : dxgkrnl!TdrBugcheckOnTimeout+0xec
ffffd000`7cd50ac0 fffff801`109ed582 : ffffe000`6078d240 ffffd000`7cd50b20 00000000`00000002 00000000`00000001 : dxgkrnl!ADAPTER_RENDER::Reset+0x1f5
ffffd000`7cd50af0 fffff801`109f8919 : ffffe000`5fd30100 fffff801`10acbe78 ffffe000`5ec72c70 ffffe000`5fd33000 : dxgkrnl!DXGADAPTER::Reset+0x416
ffffd000`7cd50b60 fffff801`10ae4fde : fffff801`10acbc90 ffffe000`5fd33000 fffff801`6188f000 00000000`00000000 : dxgkrnl!TdrResetFromTimeout+0x15
ffffd000`7cd50b90 fffff801`10acbd1d : ffffe000`5fd33000 00000000`00000080 ffffe000`613d3500 ffffe000`00000000 : dxgmms1!VidSchiRecoverFromTDR+0x1a
ffffd000`7cd50bc0 fffff801`6195e794 : ffffd000`7afd23c0 ffffe000`613d3500 ffffd000`7cd50c90 fffff801`619e637d : dxgmms1!VidSchiWorkerThread+0x8d
ffffd000`7cd50c00 fffff801`619e95c6 : ffffd000`7afc6180 ffffe000`613d3500 ffffd000`7afd23c0 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`7cd50c60 00000000`00000000 : ffffd000`7cd51000 ffffd000`7cd4b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+9a3608
fffff801`119cc608 48ff258159edff jmp qword ptr [nvlddmkm+0x878f90 (fffff801`118a1f90)]
SYMBOL_NAME: nvlddmkm+9a3608
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 539a4345
FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x116_image_nvlddmkm.sys
FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
Followup: MachineOwner
Code: [Select]
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffe00060d3b4d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff800ce852608, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
Debugging Details:
FAULTING_IP:
nvlddmkm+9a3608
fffff800`ce852608 48ff258159edff jmp qword ptr [nvlddmkm+0x878f90 (fffff800`ce727f90)]
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
STACK_TEXT:
ffffd000`23312a78 fffff800`cd92cfac : 00000000`00000116 ffffe000`60d3b4d0 fffff800`ce852608 ffffffff`c000009a : nt!KeBugCheckEx
ffffd000`23312a80 fffff800`cd92108d : fffff800`ce852608 ffffe000`62399010 ffffe000`60d3b4d0 00000000`00000001 : dxgkrnl!TdrBugcheckOnTimeout+0xec
ffffd000`23312ac0 fffff800`cd921582 : ffffe000`623a4540 ffffd000`23312b20 00000000`00000002 00000000`00000001 : dxgkrnl!ADAPTER_RENDER::Reset+0x1f5
ffffd000`23312af0 fffff800`cd92c919 : ffffe000`625b0100 ffffffff`fffe7960 ffffe000`61266010 ffffe000`625b4000 : dxgkrnl!DXGADAPTER::Reset+0x416
ffffd000`23312b60 fffff800`ccc5afde : fffff800`ccc41c90 ffffe000`625b4000 fffff800`8fa1e000 00000000`00000000 : dxgkrnl!TdrResetFromTimeout+0x15
ffffd000`23312b90 fffff800`ccc41d1d : ffffe000`625b4000 00000000`00000080 ffffe000`62bcb880 ffffe000`00000000 : dxgmms1!VidSchiRecoverFromTDR+0x1a
ffffd000`23312bc0 fffff800`8faed794 : ffffd001`8f73b3c0 ffffe000`62bcb880 ffffd000`23312c90 fffff800`8fb7537d : dxgmms1!VidSchiWorkerThread+0x8d
ffffd000`23312c00 fffff800`8fb785c6 : ffffd001`8f72f180 ffffe000`62bcb880 ffffd001`8f73b3c0 2d6b6361`50656761 : nt!PspSystemThreadStartup+0x58
ffffd000`23312c60 00000000`00000000 : ffffd000`23313000 ffffd000`2330d000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+9a3608
fffff800`ce852608 48ff258159edff jmp qword ptr [nvlddmkm+0x878f90 (fffff800`ce727f90)]
SYMBOL_NAME: nvlddmkm+9a3608
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 539a4345
FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x116_image_nvlddmkm.sys
FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
Followup: MachineOwnerQuote from: SiddVicious on 22-September-14, 06:01:44
Thank you for the recommendation for the 680m, I'll start looking into what it costs.
Can my 1762 easily upgrade to the 680m?
There shouldn't be a problem, As long as it's an MSI card. That's usually the 'tough' part. Many people buy the ones that claim they are "MSI/DELL/CLEVO", but they aren't always 100% compatible then. If you truly want it to work, and work well, I'd look into verifying without a shadow of a doubt that it is an MSI based card. -
[CLOSED] snd-hda-Intel model mono/stereo and alsamixer issues
DROPPED: I just installed the Windows disc that came with the laptop and the official drivers, while they work better (a 6 channel wav plays fine in the speakers, linux only plays 2 of them) the most important issues like mono output only in the headphones jack is repeated. It seems the hardware problem. I don't know how I break it, but I did.
When I installed Arch linux about this laptop about two years ago everything was working OK. "aplay /usr/share/sounds/alsa/Front_Right.wav" (and left) played in the corresponding speakers and headphones. "alsamixer" used to have two volume control bars per control, for left and right.
I can't pinpoint the moment but sometime in the last few months everything is playing as mono. Now alsamixer shows only one volume bar per control and "Master" can only to be (un)muted as mono. I can still mute the "Speaker" control individually using '<' and '>'. The "Headphone" volume control is ignored, neither volume nor mute work. And the strangest thing: when I mute the left Speaker it also mutes the headphones.
I never did any alsa configuration and so I'm assuming the model auto detection is broken. I tried a few model= options without luck. The problem is the laptop is brandless (pseudo-olivetti 750). Perhaps with some luck someone can help me identify which model should I use.
Physical Description:
The laptop has to on-board speakers and two jacks on the front, one labeled with a Microhone (slash) two things I cannot recognize and the other labeled SPDIF OUT (slash) Headphones. (I tried the only model described as 2-jack in the wiki guide without luck).
# lspci -v | grep -A11 Audio
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
Subsystem: Uniwill Computer Corp Device 907e
Flags: bus master, fast devsel, latency 0, IRQ 27
Memory at f0000000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC883 Analog [ALC883 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 1: ALC883 Digital [ALC883 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 6: Si3054 Modem [Si3054 Modem]
Subdevices: 1/1
Subdevice #0: subdevice #0
# aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
default:CARD=Intel
HDA Intel, ALC883 Analog
Default Audio Device
front:CARD=Intel,DEV=0
HDA Intel, ALC883 Analog
Front speakers
surround40:CARD=Intel,DEV=0
HDA Intel, ALC883 Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=Intel,DEV=0
HDA Intel, ALC883 Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=Intel,DEV=0
HDA Intel, ALC883 Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=Intel,DEV=0
HDA Intel, ALC883 Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=Intel,DEV=0
HDA Intel, ALC883 Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=Intel,DEV=0
HDA Intel, ALC883 Digital
IEC958 (S/PDIF) Digital Audio Output
# aplay -D default /usr/share/sounds/alsa/Front_Left.wav
Playing WAVE '/usr/share/sounds/alsa/Front_Left.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
#aplay -D front /usr/share/sounds/alsa/Front_Left.wav
aplay: main:608: audio open error: Device or resource busy
# lsof /dev/dsp
# (nothing)
# amixer
Simple mixer control 'Master',0
Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
Playback channels: Mono
Limits: Playback 0 - 31
Mono: Playback 31 [100%] [0.00dB] [on]
Simple mixer control 'Headphone',0
Capabilities: pvolume pswitch penum
Playback channels: Front Left - Front Right
Limits: Playback 0 - 31
Mono:
Front Left: Playback 31 [100%] [0.00dB] [on]
Front Right: Playback 31 [100%] [0.00dB] [on]
Simple mixer control 'Speaker',0
Capabilities: pvolume pswitch penum
Playback channels: Front Left - Front Right
Limits: Playback 0 - 31
Mono:
Front Left: Playback 31 [100%] [0.00dB] [on]
Front Right: Playback 31 [100%] [0.00dB] [on]
Simple mixer control 'PCM',0
Capabilities: pvolume penum
Playback channels: Front Left - Front Right
Limits: Playback 0 - 255
Mono:
Front Left: Playback 255 [100%] [0.00dB]
Front Right: Playback 255 [100%] [0.00dB]
Simple mixer control 'Mic',0
Capabilities: pvolume pswitch penum
Playback channels: Front Left - Front Right
Limits: Playback 0 - 31
Mono:
Front Left: Playback 0 [0%] [-34.50dB] [off]
Front Right: Playback 0 [0%] [-34.50dB] [off]
Simple mixer control 'Mic Boost',0
Capabilities: volume penum
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 3
Front Left: 0 [0%]
Front Right: 0 [0%]
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [off]
Simple mixer control 'IEC958 Default PCM',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Simple mixer control 'Beep',0
Capabilities: pvolume pswitch penum
Playback channels: Front Left - Front Right
Limits: Playback 0 - 31
Mono:
Front Left: Playback 0 [0%] [-34.50dB] [off]
Front Right: Playback 0 [0%] [-34.50dB] [off]
Simple mixer control 'Capture',0
Capabilities: cvolume cswitch penum
Capture channels: Front Left - Front Right
Limits: Capture 0 - 31
Front Left: Capture 16 [52%] [12.00dB] [off]
Front Right: Capture 16 [52%] [12.00dB] [off]
Simple mixer control 'Caller ID',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [off]
Simple mixer control 'Off-hook',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [off]
Thanks for any help, I tried most of the models listed as ALC883 (and some others) without luck, is there any other option that could cause this issues?
Last edited by dresb (2011-02-07 16:29:50)Thanks a lot for the hint! codec#0 was the modem while this is from codec#1:
# cat /proc/asound/card0/codec#1
Codec: Realtek ALC883
Address: 1
Function Id: 0x1
Vendor Id: 0x10ec0883
Subsystem Id: 0x1584907e
Revision Id: 0x100002
No Modem Function Group found
Default PCM:
rates [0x560]: 44100 48000 96000 192000
bits [0xe]: 16 20 24
formats [0x1]: PCM
Default Amp-In caps: N/A
Default Amp-Out caps: N/A
GPIO: io=2, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
Node 0x02 [Audio Output] wcaps 0x11: Stereo
Converter: stream=5, channel=0
PCM:
rates [0x560]: 44100 48000 96000 192000
bits [0xe]: 16 20 24
formats [0x1]: PCM
Node 0x03 [Audio Output] wcaps 0x11: Stereo
Device: name="ALC883 Analog", type="Audio", device=0
Converter: stream=5, channel=0
PCM:
rates [0x560]: 44100 48000 96000 192000
bits [0xe]: 16 20 24
formats [0x1]: PCM
Node 0x04 [Audio Output] wcaps 0x11: Stereo
Converter: stream=0, channel=0
PCM:
rates [0x560]: 44100 48000 96000 192000
bits [0xe]: 16 20 24
formats [0x1]: PCM
Node 0x05 [Audio Output] wcaps 0x11: Stereo
Converter: stream=0, channel=0
PCM:
rates [0x560]: 44100 48000 96000 192000
bits [0xe]: 16 20 24
formats [0x1]: PCM
Node 0x06 [Audio Output] wcaps 0x211: Stereo Digital
Control: name="IEC958 Playback Con Mask", index=0, device=0
Control: name="IEC958 Playback Pro Mask", index=0, device=0
Control: name="IEC958 Playback Default", index=0, device=0
Control: name="IEC958 Playback Switch", index=0, device=0
Control: name="IEC958 Default PCM Playback Switch", index=0, device=0
Device: name="ALC883 Digital", type="SPDIF", device=1
Converter: stream=0, channel=0
Digital:
Digital category: 0x0
PCM:
rates [0x560]: 44100 48000 96000 192000
bits [0x1e]: 16 20 24 32
formats [0x1]: PCM
Node 0x07 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x08 [Audio Input] wcaps 0x10011b: Stereo Amp-In
Device: name="ALC883 Analog", type="Audio", device=0
Amp-In caps: ofs=0x08, nsteps=0x1f, stepsize=0x05, mute=1
Amp-In vals: [0x90 0x90]
Converter: stream=0, channel=0
SDI-Select: 0
PCM:
rates [0x160]: 44100 48000 96000
bits [0x6]: 16 20
formats [0x1]: PCM
Connection: 1
0x23
Node 0x09 [Audio Input] wcaps 0x10011b: Stereo Amp-In
Amp-In caps: ofs=0x08, nsteps=0x1f, stepsize=0x05, mute=1
Amp-In vals: [0x00 0x00]
Converter: stream=0, channel=0
SDI-Select: 0
PCM:
rates [0x160]: 44100 48000 96000
bits [0x6]: 16 20
formats [0x1]: PCM
Connection: 1
0x22
Node 0x0a [Audio Input] wcaps 0x100391: Stereo Digital
Converter: stream=0, channel=0
SDI-Select: 0
Digital:
Digital category: 0x0
PCM:
rates [0x560]: 44100 48000 96000 192000
bits [0x1e]: 16 20 24 32
formats [0x1]: PCM
Unsolicited: tag=00, enabled=0
Connection: 1
0x1f
Node 0x0b [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
Control: name="Mic Playback Volume", index=0, device=0
Control: name="Mic Playback Switch", index=0, device=0
Control: name="Beep Playback Volume", index=0, device=0
Control: name="Beep Playback Switch", index=0, device=0
Amp-In caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1
Amp-In vals: [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80]
Connection: 10
0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x14 0x15 0x16 0x17
Node 0x0c [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
Control: name="Headphone Playback Switch", index=0, device=0
Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-In vals: [0x00 0x00] [0x00 0x00]
Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=0
Amp-Out vals: [0x1f 0x1f]
Connection: 2
0x02 0x0b
Node 0x0d [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
Control: name="Speaker Playback Switch", index=0, device=0
Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-In vals: [0x00 0x00] [0x00 0x00]
Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=0
Amp-Out vals: [0x1f 0x1f]
Connection: 2
0x03 0x0b
Node 0x0e [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out
Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-In vals: [0x00 0x00] [0x00 0x00]
Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=0
Amp-Out vals: [0x00 0x00]
Connection: 2
0x04 0x0b
Node 0x0f [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out
Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-In vals: [0x00 0x00] [0x00 0x00]
Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=0
Amp-Out vals: [0x00 0x00]
Connection: 2
0x05 0x0b
Node 0x10 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x11 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x12 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x13 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x14 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-Out vals: [0x00 0x00]
Pincap 0x0000003e: IN OUT HP Detect Trigger
Pin Default 0x0121101f: [Jack] HP Out at Ext Rear
Conn = 1/8, Color = Black
DefAssociation = 0x1, Sequence = 0xf
Pin-ctls: 0xc0: OUT HP
Unsolicited: tag=04, enabled=1
Connection: 5
0x0c 0x0d* 0x0e 0x0f 0x26
Node 0x15 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-Out vals: [0x00 0x00]
Pincap 0x0000003e: IN OUT HP Detect Trigger
Pin Default 0x99130110: [Fixed] Speaker at Int ATAPI
Conn = ATAPI, Color = Unknown
DefAssociation = 0x1, Sequence = 0x0
Misc = NO_PRESENCE
Pin-ctls: 0x00:
Unsolicited: tag=00, enabled=0
Connection: 5
0x0c 0x0d* 0x0e 0x0f 0x26
Node 0x16 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-Out vals: [0x80 0x80]
Pincap 0x0000003e: IN OUT HP Detect Trigger
Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
Conn = 1/8, Color = Black
DefAssociation = 0xf, Sequence = 0x0
Misc = NO_PRESENCE
Pin-ctls: 0x20: IN
Unsolicited: tag=00, enabled=0
Connection: 5
0x0c 0x0d 0x0e* 0x0f 0x26
Node 0x17 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-Out vals: [0x80 0x80]
Pincap 0x0000003e: IN OUT HP Detect Trigger
Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
Conn = 1/8, Color = Black
DefAssociation = 0xf, Sequence = 0x0
Misc = NO_PRESENCE
Pin-ctls: 0x20: IN
Unsolicited: tag=00, enabled=0
Connection: 5
0x0c 0x0d 0x0e 0x0f* 0x26
Node 0x18 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
Control: name="Mic Boost", index=0, device=0
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-Out vals: [0x80 0x80]
Pincap 0x0000173e: IN OUT HP Detect Trigger
Vref caps: HIZ 50 GRD 80
Pin Default 0x01a19830: [Jack] Mic at Ext Rear
Conn = 1/8, Color = Pink
DefAssociation = 0x3, Sequence = 0x0
Pin-ctls: 0x24: IN VREF_80
Unsolicited: tag=00, enabled=0
Connection: 5
0x0c* 0x0d 0x0e 0x0f 0x26
Node 0x19 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-Out vals: [0x80 0x80]
Pincap 0x0000173e: IN OUT HP Detect Trigger
Vref caps: HIZ 50 GRD 80
Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
Conn = 1/8, Color = Black
DefAssociation = 0xf, Sequence = 0x0
Misc = NO_PRESENCE
Pin-ctls: 0x20: IN VREF_HIZ
Unsolicited: tag=00, enabled=0
Connection: 5
0x0c* 0x0d 0x0e 0x0f 0x26
Node 0x1a [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-Out vals: [0x80 0x80]
Pincap 0x0000173e: IN OUT HP Detect Trigger
Vref caps: HIZ 50 GRD 80
Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
Conn = 1/8, Color = Black
DefAssociation = 0xf, Sequence = 0x0
Misc = NO_PRESENCE
Pin-ctls: 0x20: IN VREF_HIZ
Unsolicited: tag=00, enabled=0
Connection: 5
0x0c* 0x0d 0x0e 0x0f 0x26
Node 0x1b [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-Out vals: [0x80 0x80]
Pincap 0x0000173e: IN OUT HP Detect Trigger
Vref caps: HIZ 50 GRD 80
Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
Conn = 1/8, Color = Black
DefAssociation = 0xf, Sequence = 0x0
Misc = NO_PRESENCE
Pin-ctls: 0x20: IN VREF_HIZ
Unsolicited: tag=00, enabled=0
Connection: 5
0x0c* 0x0d 0x0e 0x0f 0x26
Node 0x1c [Pin Complex] wcaps 0x400001: Stereo
Pincap 0x00000020: IN
Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
Conn = 1/8, Color = Black
DefAssociation = 0xf, Sequence = 0x0
Misc = NO_PRESENCE
Pin-ctls: 0x00:
Node 0x1d [Pin Complex] wcaps 0x400000: Mono
Pincap 0x00000020: IN
Pin Default 0x9983013f: [Fixed] Line In at Int ATAPI
Conn = ATAPI, Color = Unknown
DefAssociation = 0x3, Sequence = 0xf
Misc = NO_PRESENCE
Pin-ctls: 0x00:
Node 0x1e [Pin Complex] wcaps 0x400300: Mono Digital
Pincap 0x00000010: OUT
Pin Default 0x01451120: [Jack] SPDIF Out at Ext Rear
Conn = Optical, Color = Black
DefAssociation = 0x2, Sequence = 0x0
Misc = NO_PRESENCE
Pin-ctls: 0x00:
Connection: 1
0x06
Node 0x1f [Pin Complex] wcaps 0x400200: Mono Digital
Pincap 0x00000020: IN
Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
Conn = 1/8, Color = Black
DefAssociation = 0xf, Sequence = 0x0
Misc = NO_PRESENCE
Pin-ctls: 0x00:
Node 0x20 [Vendor Defined Widget] wcaps 0xf00040: Mono
Processing caps: benign=0, ncoeff=17
Processing Coefficient: 0x4000
Coefficient Index: 0x0b
Node 0x21 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x22 [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out
Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-In vals: [0x00 0x00] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80]
Amp-Out caps: N/A
Amp-Out vals: [0x00 0x00]
Connection: 11
0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x14 0x15 0x16 0x17 0x0b
Node 0x23 [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out
Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-In vals: [0x00 0x00] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80]
Amp-Out caps: N/A
Amp-Out vals: [0x00 0x00]
Connection: 11
0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x14 0x15 0x16 0x17 0x0b
Node 0x24 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x25 [Audio Output] wcaps 0x11: Stereo
Converter: stream=0, channel=0
PCM:
rates [0x560]: 44100 48000 96000 192000
bits [0xe]: 16 20 24
formats [0x1]: PCM
Node 0x26 [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out
Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-In vals: [0x00 0x00] [0x00 0x00]
Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=0
Amp-Out vals: [0x00 0x00]
Connection: 2
0x25 0x0b
I assume the combination Vendor Id: 0x10ec0883 + Subsystem Id: 0x1584907e is what I should be looking for right? Google gave me three resuts from alsa project's DB: http://www.google.com/search?q=0x10ec08 … e&filter=0 resulting in two more models to try:
model=laptop (I'm almost certain I tried this already)
model=lenovo
I also didn't knew about alsa-info.sh so I downloaded, ran it and got this http://www.alsa-project.org/db/?f=9f7e7 … bf5c3ad9ea including:
!!DMI Information
Manufacturer: Standard
Product Name: L50IIX
L50IIX seems to be a board made by Uniwill and used by various companies which adds even more possible models:
model=uniwill
model=uniwill-m31
model=fujitsu
model=lifebook
model=fujitsu-pi2515
model=fujitsu-xa3530
It seems I have a lot of testing to do later, I will report back the results and hopefully will provide a solution for any lost soul who comes across this post in the future. Thank you. -
Windows Server 2008 R2 SP1 BSOD 0x1a with CLFS.sys
Hello,
I've got a BSOD on a Windows Server 2008 R2 with SP1 installed. Analyzed the dump and could
see a Bug-check of 0x1a which means "MEMORY_MANAGEMENT".
Further analysis on this dump shows me, that this probably is caused by the CLFS.sys, which
is the Common Log File System Driver. This CLFS.sys is installed with date:
Tue Jul 14 01:19:57 2009
I have now searched trough MS Support pages and resources and also the Internet, but I found no
information about an update for this or a newer version. It's nearby impossible to find newer versions
for specific files in i.e. Hot-fixes.
Do you know this issue with the 0x1a BSOD and CLFS.sys and/or do you know a newer version ?
Any help would be very appreciated!
Thanks and regards plus have a nice day !
TinoHi Tino,
Regarding to Bug Check 0x1A, please refer to following article.
Bug Check 0x1A: MEMORY_MANAGEMENT
Did you install any third-party application in this problematic server? Would you please let me know whether
the BSOD issue occurred regularly? Or just occurred suddenly? If the BSOD issue occurred regularly, please
perform a clean boot and check if this BSOD issue still exists.
In addition, please check if necessary updates need to be installed and drivers need to be updated. Please
run sfc /scannow command to scan all protected system files and check if find errors.
As you know, troubleshoot this kind of kernel crash issue, we need to analyze the crash dump file to narrow down the root cause of the issue. Actually, it is not effective
for us to debug the crash dump file here in the forum. If this issues is a state of emergency for you. Please contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.
To obtain the phone numbers for specific technology request, please refer to the web site listed below:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
àThis CLFS.sys is installed with date: Tue Jul 14 01:19:57 2009
àor do you know a newer version?
By the way, I checked the CLFS.sys in a Windows Server 2008 R2 in my Lab environment. It also created in July
2009.
Hope this helps.
Best regards,
Justin Gu -
Multiple operating system crashes- the computer has rebooted from a bugcheck
For last couple of months I have been facing multiple crashes every day. Looking for help diagnose it. The memory dump file is 797 MB. Is there an option wherein I can make any sense out of it under guidance from community here- or should i simply try
a clean install of win 8.1Hi grensmoothie,
Any update here?
You may follow the guide posted by Team Zigzag (http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_update/warning-disabling-the-new-windows-update-ui-may/dc846517-eca0-4960-b0ff-1eb7227223f5),
For BSOD related issue, we do need the dump file to give a proper suggestion.
Besides, if you would like to debug the dump file by yourself, you may follow the WIKI article below:
Windows Bugcheck Analysis
Best regards
Michael Shao
TechNet Community Support -
indows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (12 procs) Free x64
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0xfffff800`01847000 PsLoadedModuleList = 0xfffff800`01a0bdd0
Debug session time: Mon Nov 3 05:27:34.976 2014 (UTC - 5:00)
System Uptime: 81 days 16:48:21.023
* Bugcheck Analysis *
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff9600007f200, Address of the instruction which caused the bugcheck
Arg3: fffffa60155fff70, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
win32k!PFEOBJ::vFreepfdg+e8
fffff960`0007f200 0fba60300f bt dword ptr [rax+30h],0Fh
CONTEXT: fffffa60155fff70 -- (.cxr 0xfffffa60155fff70)
rax=000000000002f6bc rbx=0000000000000000 rcx=fffff900c1fad250
rdx=fffffa82bc20a330 rsi=fffff900c327a940 rdi=fffffa6015600820
rip=fffff9600007f200 rsp=fffffa60156007d0 rbp=0000000000000000
r8=0000000000000000 r9=000000000003fb36 r10=0000000000000000
r11=fffffa82aa1d6bb0 r12=0000000000000000 r13=0000000000000000
r14=000000000000491f r15=0000000000000001
iopl=0 nv up ei pl nz na pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010203
win32k!PFEOBJ::vFreepfdg+0xe8:
fffff960`0007f200 0fba60300f bt dword ptr [rax+30h],0Fh ds:002b:00000000`0002f6ec=????????
Resetting default scope
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT_SERVER
BUGCHECK_STR: 0x3B
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff96000244030 to fffff9600007f200
STACK_TEXT:
fffffa60`156007d0 fffff960`00244030 : 00000000`00000000 fffffa82`bc20a300 00000000`00000001 00000000`0000491f : win32k!PFEOBJ::vFreepfdg+0xe8
fffffa60`15600800 fffff960`0024e647 : 00000000`00000000 fffff900`c0092000 fffff900`c0010000 00000000`00000000 : win32k!RFONTOBJ::vDeleteRFONT+0x210
fffffa60`15600860 fffff960`0024e2ba : 00000000`00000000 fffff900`c1eb4010 fffff900`c1eb4010 fffff900`c2c773a0 : win32k!vRestartKillRFONTList+0xab
fffffa60`156008b0 fffff960`000f9bc2 : fffff900`c08ac998 fffff900`c2685350 00000000`00000000 fffff900`00000001 : win32k!PFTOBJ::bUnloadWorkhorse+0x196
fffffa60`15600930 fffff960`000fa7a1 : fffff900`c08ac910 00000000`00000000 00000000`00000001 00000000`00000001 : win32k!vCleanupPrivateFonts+0x72
fffffa60`15600970 fffff960`000eebc4 : 00000000`00000000 00000000`00000000 fffff900`c2621180 00000000`ffffffff : win32k!NtGdiCloseProcess+0x479
fffffa60`156009d0 fffff960`000ee42b : 00000000`00000000 fffff900`c2621180 00000000`00000000 00000000`00000000 : win32k!GdiProcessCallout+0x1f4
fffffa60`15600a50 fffff800`01afa77c : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa82`aa1d6bb0 : win32k!W32pProcessCallout+0x6f
fffffa60`15600a80 fffff800`01afcc7d : 00000000`00000000 fffffa82`aa1d6b01 00000000`00000000 00000000`00000000 : nt!PspExitThread+0x41c
fffffa60`15600b70 fffff800`01aed942 : 00000000`00000000 00000000`0000000c 00000000`fffdd000 fffff880`0000000c : nt!PspTerminateThreadByPointer+0x4d
fffffa60`15600bc0 fffff800`018a0f33 : fffffa82`ab4eac10 fffffa82`aa1d6bb0 fffffa60`15600ca0 00000000`fffdd000 : nt!NtTerminateProcess+0xfa
fffffa60`15600c20 00000000`779d6e5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0007ded8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779d6e5a
FOLLOWUP_IP:
win32k!PFEOBJ::vFreepfdg+e8
fffff960`0007f200 0fba60300f bt dword ptr [rax+30h],0Fh
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!PFEOBJ::vFreepfdg+e8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4de794fc
STACK_COMMAND: .cxr 0xfffffa60155fff70 ; kb
FAILURE_BUCKET_ID: X64_0x3B_win32k!PFEOBJ::vFreepfdg+e8
BUCKET_ID: X64_0x3B_win32k!PFEOBJ::vFreepfdg+e8
Followup: MachineOwnerHi,
Would you please let me know whether had done any change before this issue occurred? For examples, install
any third-party application (chrome.exe) or any other? Meanwhile, would you please let me confirm whether this issue occurred regularly?
For Bug Check 0x3B, it indicates that an exception happened while executing a routine that transitions from
non-privileged code to privileged code. For more details, please refer to following article and check if can help you.
Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION
Please update drivers and install all necessary Windows Updates, then monitor the result. If this issue still
exists, please perform a
clean boot. Any difference?
By the way, it may be not effective for us to debug the crash dump file here in the forum. If this issues is a state of emergency for you. Please contact Microsoft Customer
Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.
To obtain the phone numbers for specific technology request, please refer to the web site listed below:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
Hope this helps.
Best regards,
Justin Gu
Maybe you are looking for
-
Error Starting Weblogic Server as a Win2K service
Hi I am unable to start Weblogic Server 6.1 as a Windows 2000 Server service. Installation as NT service is successful and I used the password as "weblogic" for the system user. But then when I try to start the service it gives the following error co
-
Need help: wired ports cycling (no, 10M, 100M)...
I ahve the WRTP54G purchased as part of a Vonage package. Has been working great for last 7 months. Just recently, I had an issue with a laptop wired connection, where all of the 4 wired ports cycle about 2-3 seconds through no connect, 10M, 100M. I'
-
is there a way to add a profile to my lightroom for the Canon 24-86 3.5-4.5
-
Ipad mini charger explode , why apple authorize service center said that physical damage were not included in warranty.. it was product failure !!
-
Calendar issue in german,spanish and Italian
I am using class GregorianCalendar but in languages german,spanish and Italian strange problem happens. In these languages, for the months whose day 1 is Sunday (per normal/default (US) calendar), day 1 is shown as Monday. This is true for Feb 2004 a