New
#21
Those are the settings I refer to yes :)
I assume you have checked all non-Microsoft drivers.
Yes, all non-Microsoft drivers are selected.
Well, I got a Blue Screen. Attached is the mini-dump file. Notice that Windows doesn't create a mini-dump for the original issue but does here.
Edit: I also uploaded the MEMORY.dmp in a zip to dropbox (too big for here...)
https://www.dropbox.com/s/rxkmojb0vw...EMORY.zip?dl=0
Last edited by teven0855; 05 Jul 2016 at 22:05. Reason: add MEMORY.dmp information
DV is enabled, but did NOT cause the crash.
Your broadcomm network driver is the cause, check the manufacturer of the device for driver updates.
Code:Child-SP RetAddr : Args to Child : Call Site fffff880`0bf86448 fffff800`034829a9 : 00000000`0000000a fffff980`5796af8c 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`0bf86450 fffff800`03481620 : fffffa80`06c93020 00000000`00000005 00000002`0c64e200 fffff880`0bf86750 : nt!KiBugCheckDispatch+0x69 fffff880`0bf86590 fffff880`05c3b66e : fffffa80`06c917b0 fffff800`00000230 00000000`00537923 fffff880`024b1c02 : nt!KiPageFault+0x260 (TrapFrame @ fffff880`0bf86590) fffff880`0bf86720 fffff880`024ba53d : 00000000`00000000 00000000`00000001 00000000`00000000 fffff980`45e90f10 : bcmvwl64+0x166e fffff880`0bf867c0 fffff880`024b1c14 : fffffa80`0c48b1a0 fffffa80`0c48b1a0 fffff980`45e90f58 00000000`00000000 : ndis!ndisMOidRequestToRequest+0x26d fffff880`0bf86830 fffff880`02425989 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0c48b200 : ndis! ?? ::DKGKHJNI::`string'+0x324d fffff880`0bf868e0 fffff880`02425cd9 : 00000000`00000001 fffff880`02486110 fffff880`02486100 fffffa80`0c48b1a0 : ndis!ndisFQueueRequestOnNext+0x389 fffff880`0bf86950 fffff880`057bf1c9 : fffff980`556f0f10 00000000`ffe41445 fffff980`556f0f10 00000000`00000000 : ndis!NdisFOidRequest+0xc9 fffff880`0bf86a30 fffff880`024ab582 : fffff980`45e90f10 fffff980`0b310c80 fffff980`543a4f80 00000000`00000000 : vpcnfltr!FilterOidRequest+0xf9 fffff880`0bf86a60 fffff880`0242a44c : fffff980`00000000 fffff880`02486110 fffff980`543a4f80 fffff980`0b310c80 : ndis!ndisFDoOidRequest+0x222 fffff880`0bf86b30 fffff800`0348d749 : fffff880`0242a400 fffff800`0362d280 fffffa80`10a6c210 00000000`00000002 : ndis!ndisDoOidRequests+0x4c fffff880`0bf86b70 fffff800`0371bbc6 : 00000000`00000000 fffffa80`10a6c210 00000000`00000080 fffffa80`06d12040 : nt!ExpWorkerThread+0x111 fffff880`0bf86c00 fffff800`034756a6 : fffff880`03d65180 fffffa80`10a6c210 fffffa80`06d3d610 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`0bf86c40 00000000`00000000 : fffff880`0bf87000 fffff880`0bf81000 fffff880`0bf868a0 00000000`00000000 : nt!KxStartSystemThread+0x16 Bugcheck code 000000D1 Arguments fffff980`5796af8c 00000000`00000002 00000000`00000001 fffff880`05c3b66e Debug session time: Wed Jul 6 01:21:32.465 2016 (UTC + 2:00) System Uptime: 0 days 23:42:20.340 0: kd> lmvm bcmvwl64 Browse full module list start end module name fffff880`05c3a000 fffff880`05c43000 bcmvwl64 (no symbols) Loaded symbol image file: bcmvwl64.sys Image path: \SystemRoot\system32\DRIVERS\bcmvwl64.sys Image name: bcmvwl64.sys Browse all global symbols functions data Timestamp: Sat Oct 22 01:22:44 2011 (4EA1FEC4) CheckSum: 00014DD5 ImageSize: 00009000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Try to reinstall the driver in that case.
Updating drivers is in many cases a +1 (meaning yes to your question) :)