New
#11
These would seem to be available.. oddly, listed for Win 10, but drivers dated '11
"Moederbord
Acer Aspire ES1-571 (U3E1)"
Acer Aspire ES1-571 Laptop Windows 10 Driver, Utility, Manual | Notebook Driver Software
These would seem to be available.. oddly, listed for Win 10, but drivers dated '11
"Moederbord
Acer Aspire ES1-571 (U3E1)"
Acer Aspire ES1-571 Laptop Windows 10 Driver, Utility, Manual | Notebook Driver Software
Not really odd: from 2016 3rd month 11th day.
Description Version Size Date Intel AMT Driver 11.0.0.1155 60.7 MB 2016/03/11
Oh, in the UK we put the year last, so when I scanned down quickly and saw lots of '11s - there are a couple of 21's though. Chinese order is 'big to small' (y/m/d). Also a bit unusual to actually have a good selection of drivers for Win 10.
Attachment 79392
I re-installed the drivers but it is still the same. I've uploaded a new log. I hope you can see some progress or something
I'm not entirely sure what the problem is, a Windows network driver is allocating a Memory Descriptor List (MDL) which describes the memory buffer to the specified virtual memory address for the network driver, the Memory Management tries to allocate the MDL to nonpaged pool where after a pagefault occurs, however when taking a look at the IRQL it seems to be at level 2 which doesn't allow a pagefault to be occured.
So the crash occurs because a pagefault happened at this IRQL, but it is unclear to me why a pagefault occurs.
IRQL = Interrupt Request Level, the priority scheme Windows uses when processing everything.
I'd like to try a memory diagnostics test, if this test does not show any error then I would suggest that you remove Norton as a test to see if that improves anything.
I would want you to remove as much as possible 3rd party security programs, because they show up a lot in crashes that are network related. If you've removed all 3rd party security programs and the crash is still happening then it certainly is a bug in the network drivers, all that you can do then is report it to Acer so they can fix this problem.
Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums
Note
MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.
Make a photo of the result and post it.
Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.
Code:Child-SP RetAddr : Args to Child : Call Site ffffd001`cf7b2448 fffff803`817e5c34 : 00000000`00000050 fffff6fb`400037a8 00000000`00000000 fffff6fb`7da00018 : nt!KeBugCheckEx ffffd001`cf7b2450 fffff803`816bcb84 : 00000000`00000000 fffff6fb`400037a8 00000000`00000000 ffffd001`00000000 : nt! ?? ::FNODOBFM::`string'+0x10b34 ffffd001`cf7b25d0 fffff803`817cf9bc : fffff801`b2efbd90 00000000`0000ffff 00000000`00000000 00000000`00266bd8 : nt!MmAccessFault+0x2e4 ffffd001`cf7b2730 fffff803`81740bc7 : 00000000`00000000 00000000`00000780 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13c (TrapFrame @ ffffd001`cf7b2730) ffffd001`cf7b28c8 fffff801`ad551a21 : ffffe001`2d800000 00000000`deadbeef ffffe001`2a34a000 00000000`4cd73891 : nt!MmBuildMdlForNonPagedPool+0x87 ffffd001`cf7b28f0 fffff801`b2203c0f : ffffe001`290c5140 fffff803`816fa713 ffffe001`290c5040 fffff803`817cb7bf : ndis!NdisAllocateMdl+0x31 ffffd001`cf7b2930 ffffe001`290c5140 : fffff803`816fa713 ffffe001`290c5040 fffff803`817cb7bf 00000000`0000017c : bcmwl63a+0xe3c0f ffffd001`cf7b2938 fffff803`816fa713 : ffffe001`290c5040 fffff803`817cb7bf 00000000`0000017c fffff801`b21e5fec : 0xffffe001`290c5140 ffffd001`cf7b2940 fffff803`816fa159 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwapThread+0x1a3 ffffd001`cf7b29f0 fffff803`816f9dc5 : 00000000`00000000 00000000`00000003 ffff4f2f`d8612d98 00000000`00000000 : nt!KiCommitThreadWait+0x149 ffffd001`cf7b2a80 fffff801`b22d5281 : ffffe001`00000020 ffffe001`2a34a000 00000000`00000000 ffffd001`cf7b2be0 : nt!KeWaitForSingleObject+0x375 ffffd001`cf7b2b40 ffffe001`00000020 : ffffe001`2a34a000 00000000`00000000 ffffd001`cf7b2be0 00000000`00000000 : bcmwl63a+0x1b5281 ffffd001`cf7b2b48 ffffe001`2a34a000 : 00000000`00000000 ffffd001`cf7b2be0 00000000`00000000 00000000`00000000 : 0xffffe001`00000020 ffffd001`cf7b2b50 00000000`00000000 : ffffd001`cf7b2be0 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffe001`2a34a000 Bugcheck code 00000050 Arguments fffff6fb`400037a8 00000000`00000000 00000000`00000000 00000000`00000006 Debug session time: Thu May 12 08:43:57.051 2016 (UTC + 2:00) System Uptime: 0 days 0:26:02.020 1: kd> !irql Debugger saved IRQL for processor 0x1 -- 2 (DISPATCH_LEVEL)
Hello axe0, I'm sorry for the late answer. After your last reaction I removed my Norton and tried the Bittorrent program again. My computer shutted down again so I reinstalled Norton and downloaded memtest.
A couple of days later I ran bitt. again (on a friends internet connection) and my pc didn't crash. I decided to wait and try to use te program more and until now my pc didn't crash anymore. So I guess that reinstalling Norton fixed the problem. Could that be possible?
I would like to thank you again for your support. I least you guys help the people and communicate with them. That's not something that can allways be said about Microsoft support...
Keep up the good work geniusses!