DarvinArroyo / peerblock

Automatically exported from code.google.com/p/peerblock
Other
0 stars 0 forks source link

ExInitializeNPagedLookasideList #417

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. (Maybe Have AVG Root-kit protection running in the background along with) 
Peerblock
2. Do things using the network connection (probably uTorrent)
3. Lightning may strike and give you BSOD 0x0a

What is the expected output? What do you see instead?
Expected that my computer would keep going.  It didn't.

What version of PeerBlock are you using? On what operating system? 32- or 
64-bit?
PB 1.1 Win7 both x86

Please provide any additional information below.  Make sure to attach
peerblock.log and/or any screenshots that would help explain your problem.

Issue seems resolved for me.  I turned off the AVG Root-kit Protection (which I 
have no idea why it was in the background anyway) and I've been fine ever 
since.  Just had two of the 0x0a crashes.

I went to techsupportforum and they traced the BSOD cause for me to a combo of 
AVG & Peerblock.  Link to thread is here:

http://www.techsupportforum.com/forums/f299/solved-recent-random-0x0a-bsods-on-d
ell-xps-m1530-laptop-619865.html
(Note, in post 6 I point to another site which advises some sort of driver 
signing override and I suggested I was going to take that method.  I did not. I 
only disabled AVG.)

In both of the dmp files within the .zip attached to the thread, the callstack 
shows pbfilter calling ExDeleteNPagedLookasideList as also mentioned in the 
thread referenced in post #3 of the TSF thread.

I'd point you to it in the dmp's but I don't have WDK on this computer, but 
I'll have access to it tomorrow though if that'd be helpful.

I'm not entirely sure it was a combo of AVG & pbfilter.  They'd been playing 
nicely since early 2011 when I switched from PG2 to PB.  Still, those are my 
only two BSODs in a year and they're two days apart and it points to PB.

Honestly, I was coming here to try to take a shot at this myself as I didn't 
know if PB was still being maintained.  That said, I have Zero OS & driver 
coding experience, and only have a year of classes and a year and a half 
working with C++ to rebuild some poorly coded internal company software almost 
a decade ago.  Since then, I've mainly stuck to PHP and troubleshooting some 
stuff in C#.  Basically, you can probably find the issue quicker than I can.

I realize it's not a top priority considering I couldn't reproduce when I 
wanted to back when it was happening, and it hasn't happened in two weeks.  If 
you'd like, I can dive through and see if I can point to the bug/cause.  I 
could probably give you a diff with a fix as well, but I'm betting that a fix 
by someone here is probably better than what my rusty hands can provide.

If we can find what's causing it, but can't find why, I'd probably say let 
sleeping BSODs lie.

Sorry for the long report.  Just wanted to bring you up to speed and save you 
some steps, maybe.  I've reattached the zip with the dmp's referenced above, 
and unfortunately my peerblock.log doesn't go back far enough.  Let me know 
anything else you need or anything I can do to help.

Original issue reported on code.google.com by ed.wu...@gmail.com on 4 Jan 2012 at 6:06

Attachments:

GoogleCodeExporter commented 8 years ago
And crap, sorry about the bad issue name, meant to fix that.  Also got the 
wrong function listed there.  To correct, this is an issue with 
ExDeleteNPagedLookasideList causing 0x0a BSODs on Win7 x86 with PeerBlock 1.1.  
Sorry!

Original comment by ed.wu...@gmail.com on 4 Jan 2012 at 6:09