[SOLVED] Frequent BSODs on YouTube in Windows 8.1 x64

I just had another BSOD but I am not sure where the Kernal Dump file is, it doesn't seem to be in the minidump folder.
 
Sorry to post so many in a row, but how many kernal dumps do you need, I have 2 more that I have collected. I will upload them to the same folder as before.
 
Kernels are located in C:\Windows and are labeled MEMORY.DMP. You technically only have one (the latest) unless you've un-checked 'overwrite existing files' as by that option when you crash, the kernel is overwritten with the latest to save HDD space.

Regards,

Patrick
 
Great, thank you very much!

I downloaded all four::SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1) as we've seen above.

This indicates that the driver wrote to an invalid section of the special pool.

However, this time, we have a kernel!

Taking a look at the call stack:
Code: 
2: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffffd000`28d18468 fffff800`f4078f0e nt!KeBugCheckEx
01 ffffd000`28d18470 fffff800`f4079940 nt!MiCheckSpecialPoolSlop+0x8a
02 ffffd000`28d184b0 fffff800`f411f316 nt!MmFreeSpecialPool+0x14c
03 ffffd000`28d185e0 fffff800`003602b4 nt!ExFreePoolWithTag+0x1046
04 ffffd000`28d186b0 fffff800`f44ef128 VerifierExt!ExFreePoolWithTag_wrapper+0x10
05 ffffd000`28d186e0 fffff800`00e6f024 nt!VerifierExFreePoolWithTag+0x44
06 ffffd000`28d18710 fffff800`0400c6ec ndis!NdisFreeNetBufferList+0x124
07 ffffd000`28d18790 fffff800`04010b81 nwifi!Dot11FreeSendPacket+0xa0
08 ffffd000`28d187c0 fffff800`0400c62c nwifi!Dot11SendNBComplete+0x31
09 ffffd000`28d18810 fffff800`0400fee9 nwifi!Dot11SendCompletion+0x44
0a ffffd000`28d18840 fffff800`00e706b0 nwifi!Pt6SendComplete+0x1d
0b ffffd000`28d18870 fffff800`00ecc301 ndis!NdisMSendNetBufferListsComplete+0x1e0
0c ffffd000`28d189e0 fffff800`03370a06 ndis!ndisVerifierNdisMSendNetBufferListsComplete+0x21
0d ffffd000`28d18a20 fffff800`030d5c40 [COLOR=#ff0000][I][B]bcmwl63a+0x2bfa06[/B][/I][/COLOR]
0e ffffd000`28d18a90 fffff800`03376750 [COLOR=#ff0000][I][B]bcmwl63a+0x24c40[/B][/I][/COLOR]
0f ffffd000`28d18ac0 fffff800`f3f2da0e [COLOR=#ff0000][I][B]bcmwl63a+0x2c5750[/B][/I][/COLOR]
10 ffffd000`28d18af0 fffff800`f3f2e1b9 nt!IopProcessWorkItem+0x76
11 ffffd000`28d18b50 fffff800`f3f1a2e4 nt!ExpWorkerThread+0x2b5
12 ffffd000`28d18c00 fffff800`f3fe12c6 nt!PspSystemThreadStartup+0x58
13 ffffd000`28d18c60 00000000`00000000 nt!KiStartSystemThread+0x16

We have a few network related calls, specifically from nwifi, ndis, etc. VRF flagged the bcmwl63a.sys driver which we can see in the stack. This is the Broadcom 802.11 Network Adapter wireless driver.

Regarding network drivers, I can see:

-- e22w8x64.sys > Wed Mar 20 17:24:01 2013

^^ Killer Networks Ethernet Card driver.

&

-- bwcW8x64.sys > Wed Feb 13 12:25:48 2013

^^ Broadcom 802.11 Network Adapter wireless driver.

I imagine Killer is for LAN and the Broadcam is the WAN.

Are all of your network drivers up to date via Dell's website?

IRQL_NOT_LESS_OR_EQUAL (a)

This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high. The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

Code: 
1: kd> .bugcheck
Bugcheck code 0000000A
Arguments fffffd00`2a77d858 00000000`00000002 00000000`00000000 fffff800`113f7141

2nd parameter - IRQL 2

3rd parameter - 0 = 0x0, which equals READ (WRITE is 0x1). I believe it may have crashed attempting to write to fffffd002a77d858.

4th parameter - Failing instruction address.

*0xA crashes generally occur when there's a failure to access a memory address, which at lower IRQLs equals a page fault. IRQL 2 and higher, page faults cannot occur.

Let's look at the call stack:
Code: 
1: kd> kvnL
 # Child-SP          RetAddr           : Args to Child                                                           : Call Site
00 ffffd000`2a6ea018 fffff800`113607e9 : 00000000`0000000a fffffd00`2a77d858 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
01 ffffd000`2a6ea020 fffff800`1135f03a : 00000000`00000000 8000d563`7d481963 00000000`00000000 ffffd000`2a6ea160 : nt!KiBugCheckDispatch+0x69
02 ffffd000`2a6ea160 fffff800`113f7141 : 00000202`0018002b ffffd000`2a6ea340 00000000`00000000 fffff6e0`00076ba8 : nt!KiPageFault+0x23a (TrapFrame @ ffffd000`2a6ea160)
03 ffffd000`2a6ea2f0 fffff800`1136eae2 : fffff6e8`0011c158 ffffd000`2a6ea380 00000000`00000000 ffffd000`2a77d830 : nt!MiRaisedIrqlFault+0x185
04 ffffd000`2a6ea330 fffff800`1135ef2f : 00000000`00000001 fffff6e8`0011c158 ffffe000`104c3000 ffffd000`2a6ea470 : nt! ?? ::FNODOBFM::`string'+0x9942
05 ffffd000`2a6ea470 fffff800`1135dad0 : fffff800`11266e5d 00000000`00000000 fffff800`00000000 00000000`00000001 : nt!KiPageFault+0x12f (TrapFrame @ ffffd000`2a6ea470)
06 ffffd000`2a6ea608 fffff800`11266e5d : 00000000`00000000 fffff800`00000000 00000000`00000001 fffff680`000a6908 : nt!KeZeroPages+0x10
07 ffffd000`2a6ea610 fffff800`11235b6d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiZeroPhysicalPage+0x181
08 ffffd000`2a6ea660 fffff800`11237815 : ffffe000`0000007f 00000000`00000000 0000000f`ffffffff ffffe000`104c0e98 : nt!MiGetZeroedPages+0x265
09 ffffd000`2a6ea6d0 fffff800`1123a6f7 : 00000000`00000001 00000000`14d22000 ffffd000`2a6eab00 ffffc000`0ed76090 : nt!MiResolveDemandZeroFault+0x805
0a ffffd000`2a6ea7f0 fffff800`112394fb : ffffd000`2a6eaa88 00000000`14d22000 fffff680`000a6910 ffffe000`104c0de8 : nt!MiResolveProtoPteFault+0x5d7
0b ffffd000`2a6ea890 fffff800`11243124 : ffffe000`104c3080 00000000`00000000 00000000`00000000 ffffd000`2a6eaa50 : nt!MiDispatchFault+0x9ab
0c ffffd000`2a6ea9c0 fffff800`1135ef2f : 00000000`00000001 00000000`00b4dab8 ffffd000`00000001 ffffd000`2a6eab00 : nt!MmAccessFault+0x364
0d ffffd000`2a6eab00 00000000`51b2a058 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x12f (TrapFrame @ ffffd000`2a6eab00)
0e 00000000`00b4da44 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x51b2a058

Code: 
1: kd> .trap 0xffffd0002a6ea470
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd0002382b000
rdx=0000000000000020 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8001135dad0 rsp=ffffd0002a6ea608 rbp=0000000000000001
 r8=8000d5637d481963  r9=00000904c0000000 r10=000000000000003f
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KeZeroPages+0x10:
Page d5637d481 too large to be in the dump file.
fffff800`1135dad0 480fc301        movnti  qword ptr [rcx],rax ds:ffffd000`2382b000=????????????????

Code: 
1: kd> kvnL
  *** Stack trace for last set context - .thread/.cxr resets it
 # Child-SP          RetAddr           : Args to Child                                                           : Call Site
00 ffffd000`2a6ea608 fffff800`11266e5d : 00000000`00000000 fffff800`00000000 00000000`00000001 fffff680`000a6908 : nt!KeZeroPages+0x10
01 ffffd000`2a6ea610 fffff800`11235b6d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiZeroPhysicalPage+0x181
02 ffffd000`2a6ea660 fffff800`11237815 : ffffe000`0000007f 00000000`00000000 0000000f`ffffffff ffffe000`104c0e98 : nt!MiGetZeroedPages+0x265
03 ffffd000`2a6ea6d0 fffff800`1123a6f7 : 00000000`00000001 00000000`14d22000 ffffd000`2a6eab00 ffffc000`0ed76090 : nt!MiResolveDemandZeroFault+0x805
04 ffffd000`2a6ea7f0 fffff800`112394fb : ffffd000`2a6eaa88 00000000`14d22000 fffff680`000a6910 ffffe000`104c0de8 : nt!MiResolveProtoPteFault+0x5d7
05 ffffd000`2a6ea890 fffff800`11243124 : ffffe000`104c3080 00000000`00000000 00000000`00000000 ffffd000`2a6eaa50 : nt!MiDispatchFault+0x9ab
06 ffffd000`2a6ea9c0 fffff800`1135ef2f : 00000000`00000001 00000000`00b4dab8 ffffd000`00000001 ffffd000`2a6eab00 : nt!MmAccessFault+0x364
07 ffffd000`2a6eab00 00000000`51b2a058 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x12f (TrapFrame @ ffffd000`2a6eab00)
08 00000000`00b4da44 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x51b2a058

Definitely looks like a driver issue, most likely the wireless as we saw flagged in the *C1. A lot of page faults were occurring in the original stack, and disassembly doesn't appear very easy and/or possible. I get a memory access error when attempting to access the rip register.

I've checked the modules list left & right, and unless I am missing any, I can't seem to locate any security and/or firewall software installed? Just to be sure, do you have any?

Regards,

Patrick
 
For security and firewall I had BitDefender going, after the uninstall I figured that Windows Defender would take over. I will check and see if there is an updated driver for my wireless and ethernet cards, and if not I will uninstall and reinstall them.
 
Thanks for the information regarding your security situation, I figure that was the case. I just wanted to be extra sure.

Keep me updated.

Regards,

Patrick
 
Alright, it seems like Dell doesn't have any new drivers for the Broadcom Wireless Adapter, so I uninstalled it and let windows reinstall it on startup. I also uninstalled and reinstalled the Killer LAN driver and program as well. I will continue testing to see if it crashes again and keep you updated. Do you think BitDefender is safe to use after this if the issue is the network drivers, I know it was requesting a lot of bits of data for updates and such.
 
Keep me updated.

Regarding Bitdefender, I would be absolutely sure the crashes are solved before installing it.

Regards,

Patrick
 
Got another BSOD, uploaded another minidump file to the same folder along with its kernal dump. Hope it helps.
 
Just another update, MINIDUMP 5 and 6 are from today. Both are from IRQL_NOT_LESS_OR_EQUAL BSODs, hopefully this can help. If it is still the WAN driver, could you suggest methods to get the driver to install correctly?
 
I think I might have found something that was causing an issue, at some point my computer made multiple WAN and LAN devices in device manager and hid all of the ones that it couldn't find anymore. I uninstalled the bad ones and am going to give it another shot with verifier to see if I can get another crash.
 
Great, keep me updated.

Regarding future (hopefully not) crashes, please delete all of the ones we currently have. That way, we'll only have the latest ones to sift through, and not older ones we've already seen. Also, kernel-dumps at this point in your case with verifier enabled will give the most information.

Regards,

Patrick
 
No crashes yet after uninstalling the hidden devices and restarting. I think that might have taken care of it, been running with verifier for over a day and nothing has crashed yet. Thanks for all the help pinpointing the error and cause.
 
:thumbsup2:

Great work. Leave DV enabled for at least one more day, and then disable. You can then at that point consider it solved. Keep me updated.

Regards,

Patrick
 
Looks like I spoke too soon, but I think this was a different cause this time, uploading the dump files as I post this. The BSOD was a KMODE EXCEPTION NOT HANDLED I think.
 
Thanks!

The attached DMP file is of the KMODE_EXCEPTION_NOT_HANDLED (1e) bug check.

This indicates that a kernel-mode program generated an exception which the error handler did not catch.

If we take a look at the call stack:
Code: 
4: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
ffffd000`24734c08 fffff801`9c1e5ebf : 00000000`0000001e ffffffff`c0000005 fffff800`010851eb ffffd000`24735c68 : nt!KeBugCheckEx
ffffd000`24734c10 fffff801`9c170c66 : 00000000`00000000 00000000`00000000 00000000`00000005 fffff801`9c0e99c4 : nt!KiFatalFilter+0x1f
ffffd000`24734c50 fffff801`9c14eda6 : ffffd000`24735540 ffffe000`143e7828 00000000`00000000 fffff800`00faa3e2 : nt! ?? ::FNODOBFM::`string'+0xac6
ffffd000`24734ca0 fffff801`9c1671ed : 00000000`00000000 ffffd000`24734e40 ffffd000`24735c68 ffffd000`24734f88 : nt!_C_specific_handler+0x86
ffffd000`24734d10 fffff801`9c0ed595 : 00000000`00000000 ffffd000`24734e40 ffffd000`24735c68 fffff801`9c0eccff : nt!RtlpExecuteHandlerForException+0xd
ffffd000`24734d40 fffff801`9c0ee45b : ffffd000`24735c68 ffffd000`24735970 ffffd000`24735c68 00000000`00000010 : nt!RtlDispatchException+0x455
ffffd000`24735440 fffff801`9c16b8c2 : ffffd000`24735bc8 fffff801`9c094460 ffffe000`0d507640 fffff800`00000060 : nt!KiDispatchException+0x61f
ffffd000`24735b30 fffff801`9c169dfe : ffffe000`19e8e4d0 fffff800`0108c2b2 ffffd000`247360f0 fffff800`00f6b00d : nt!KiExceptionDispatch+0xc2
ffffd000`24735d10 fffff800`010851eb : fffff800`00ecc198 fffff800`00ecc198 fffff800`00ecc198 00000009`00000000 : nt!KiGeneralProtectionFault+0xfe (TrapFrame @ ffffd000`24735d10)
ffffd000`24735ea0 fffff800`010a5fb4 : ffffd000`24736020 00000000`00000001 ffffe000`0d507600 00000000`00000000 : tcpip!TcpBwManageTrackedData+0x1bb
ffffd000`24735f20 fffff800`010a44ef : ffffe000`0e7f9a30 fffff800`010980ff 00000000`0000027f 00000000`00000000 : tcpip!TcpDequeueTcbSend+0x8b4
ffffd000`247361a0 fffff800`01088540 : ffffcf80`09b04e60 ffffcf80`075d0b00 ffffd000`24736600 fffff801`9c674c41 : tcpip!TcpTcbFastDatagram+0x43f
ffffd000`247363f0 fffff800`010d7017 : ffffe000`11f0e5e0 fffff801`9c238b7c ffffd000`24736640 ffffe000`02b77bc8 : tcpip!TcpTcbReceive+0x160
ffffd000`24736540 fffff800`010876d5 : ffffd000`2394e06c ffffe000`02ca6000 00000000`00000000 ffffe000`02ba4fa0 : tcpip!TcpMatchReceive+0x1e7
ffffd000`247366d0 fffff800`0108ba6f : ffffe000`02c60240 ffffd000`2473e017 ffffd000`2473dfd8 00000000`0000dfd8 : tcpip!TcpPreValidatedReceive+0x385
ffffd000`247367d0 fffff800`0108bd73 : 00000000`00000007 ffffd000`24736a40 ffffd000`247371a0 00000000`00000000 : tcpip!IppDeliverListToProtocol+0x4f
ffffd000`24736890 fffff800`0109c1fc : 00000000`00000001 fffff800`036387a4 00000000`00000030 ffffd000`24736998 : tcpip!IppProcessDeliverList+0x63
ffffd000`24736930 fffff800`0109949a : 00000003`00000000 ffffcf80`17006e80 ffffe000`02ca6000 fffff800`03a00000 : tcpip!IppReceiveHeaderBatch+0x1fc
ffffd000`24736a60 fffff800`01098bfc : ffffe000`02fb1810 00000000`00000000 ffffd000`24736e01 00000000`00000000 : tcpip!IppFlcReceivePacketsCore+0x68a
ffffd000`24736de0 fffff800`01098895 : ffffe000`0e7f0002 00000000`00000000 fffff800`01098060 fffff800`00000001 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x31c
ffffd000`24736ec0 fffff801`9c0ca3f9 : fffff800`00000000 00000000`00000000 ffffe000`02cdbc10 ffffd000`24732000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x155
ffffd000`24736ff0 fffff800`01098016 : fffff800`01098740 ffffd000`24737170 ffffcf80`074a2c10 ffffd000`247371d0 : nt!KeExpandKernelStackAndCalloutInternal+0xe9
ffffd000`24737140 fffff800`00e47cde : 00000000`03ffbfff ffffd000`24737221 00000000`00000001 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0xb6
ffffd000`247371c0 fffff800`00e567f8 : 00000000`00000002 00000000`00000001 00000000`00000000 ffffcf80`00000001 : ndis!ndisMIndicateNetBufferListsToOpen+0x11e
ffffd000`24737280 fffff800`00e48cd5 : ffffe000`0c1581a0 ffffd000`24737401 00000000`00000000 00000000`00f28a4b : ndis!ndisMTopReceiveNetBufferLists+0x228
ffffd000`24737310 fffff800`032f35ca : ffffe000`0c234000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!NdisMIndicateReceiveNetBufferLists+0xba5
ffffd000`24737500 fffff800`0308a5f5 : ffffcf80`01de4500 ffffd000`2394e700 000067b9`00000000 00000070`00000001 : [COLOR=#ff0000][I][B]bcmwl63a+0x2c25ca[/B][/I][/COLOR]
ffffd000`247375f0 fffff800`03089b43 : ffffcf80`01dbefb0 00000000`00000030 ffffcf80`01de45c0 ffffd000`24737840 : [COLOR=#ff0000][I][B]bcmwl63a+0x595f5[/B][/I][/COLOR]
ffffd000`24737670 fffff800`030b25df : 00000014`00000000 ffffcf80`0c2ba000 00000000`00000001 00000000`00000001 : [COLOR=#ff0000][I][B]bcmwl63a+0x58b43[/B][/I][/COLOR]
ffffd000`24737770 fffff800`03088bdd : ffff8fcc`ad77f088 ffffcf80`01deecb0 ffffd000`2394e000 ffffcf80`01fb2f70 : [COLOR=#ff0000][I][B]bcmwl63a+0x815df[/B][/I][/COLOR]
ffffd000`247377d0 fffff800`03094546 : ffffd000`239f2000 ffffd000`2394e780 ffffd000`24737ac0 ffffcf80`01dd4e30 : [COLOR=#ff0000][I][B]bcmwl63a+0x57bdd[/B][/I][/COLOR]
ffffd000`24737960 fffff800`030d0bb9 : ffffcf80`00003c26 00000000`00000025 00000000`00000000 ffffd000`2394e780 : [COLOR=#ff0000][I][B]bcmwl63a+0x63546[/B][/I][/COLOR]
ffffd000`247379a0 fffff800`03105210 : 00000000`00000000 ffffcf80`525e5fe0 00000000`00000001 ffffd000`24737ac0 : [COLOR=#ff0000][I][B]bcmwl63a+0x9fbb9[/B][/I][/COLOR]
ffffd000`24737a00 fffff800`03055c20 : 00000000`00000000 ffffcf80`02062f00 fffff800`032f6723 ffffcdc5`a0987508 : [COLOR=#ff0000][I][B]bcmwl63a+0xd4210[/B][/I][/COLOR]
ffffd000`24737a90 fffff800`032f6750 : ffffe000`00000000 ffffe000`0c234000 ffffd000`208b9180 ffffe000`0d507740 : [COLOR=#ff0000][I][B]bcmwl63a+0x24c20[/B][/I][/COLOR]
ffffd000`24737ac0 fffff801`9c0b2a0e : ffffcf80`02066fb0 ffffe000`0c158050 00000000`00000000 ffffe000`02d89a90 : [COLOR=#ff0000][I][B]bcmwl63a+0x2c5750[/B][/I][/COLOR]
ffffd000`24737af0 fffff801`9c0b31b9 : fffff801`9c09e0fc fffff801`9c0b2998 ffffd000`24737bd0 ffffcf80`02066fb0 : nt!IopProcessWorkItem+0x76
ffffd000`24737b50 fffff801`9c09f2e4 : ffffe000`0fb45b30 ffffe000`0d507640 ffffe000`0d507640 ffffe000`00176400 : nt!ExpWorkerThread+0x2b5
ffffd000`24737c00 fffff801`9c1662c6 : ffffd000`208b9180 ffffe000`0d507640 ffffd000`208c5340 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`24737c60 00000000`00000000 : ffffd000`24738000 ffffd000`24732000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

^^ Broadcom 802.11 Network Adapter wireless driver, as we've seen already.

I don't see anything installed that could be causing network conflicts, so it's likely just the adapter itself. You said there was no driver from Dell, and it's only OEM, so can you for troubleshooting purposes go ahead and disable the wireless adapter (and/or remove it physically) to see if the crashes stop?

Regards,

Patrick
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top