BSODs possibly due to Peerblock? minidumps included

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Just having uTorrent and Peerblock open
2. Try to fiddle with uTorrent while it downloads, minimize it and try to
close it...
3. It just make my Windows XP (32bit SP3) BSOD and reboot...

What version of PeerBlock are you using? 1.0
On what operating system? Windows XP SP3 32bit

Please provide any additional information below.

I include the 3 latest minidumps created by Windows in a ZIP file, and
Peerblock.log. Please verify the minidumps to see if crashes are caused by
PeerBlock 1.0

Quick computer specs: AMD Athlon 64 2.2Ghz, 2 x 1gb DDR400 (dual-channel)

Original issue reported on code.google.com by therapto...@gmail.com on 2 Jan 2010 at 12:01

Attachments:

• peerblock.log
• Minidumps.zip

[GoogleCodeExporter]

My uTorrent version is v3.5.1, a stable version.

after checking with the Microsoft debugger tool, it seem like the same file
(ntoskrnl.exe) crashed in the 3 minidumps with a different NT+ with some 
numbers and
letters in (), always different everytime.

The time stamps always seem to be during the AM time between 4h and 7h am.

My computer always reboot fine after a BSOD, Windows is not telling me about a
missing or corrupted ntoskrnl.exe file.

My previous minidumps are about an Nvidia video driver, so it doesn't matter 
with
Peerblock...and i think i fixed the problem with an update.

So i would like to know if Peerblock is causing my PC to crash/BSOD like that...

Original comment by therapto...@gmail.com on 2 Jan 2010 at 1:15

[GoogleCodeExporter]

Does this only happen using when fiddling around with uTorrent?

If it does, you might want to get the official uTorrent which is at version 
1.8.5

http://www.utorrent.com/

Original comment by nightstalkerz on 2 Jan 2010 at 1:43

[GoogleCodeExporter]

There is no uTorrent v 3.5.1  (latest stable release is 1.8.5 (build 17414), 
latest
untable/beta releases are 2.0/2.1)

Original comment by ineedali...@gmail.com on 2 Jan 2010 at 1:47

[GoogleCodeExporter]

ah yes sorry, it's uTorrent v1.8.5. Very sorry...

Well, i also noticed it happen during the morning between 4am and 7am. During 
the
morning of Dec.25, i was reading a new manga i received, and my computer just
rebooted by itself, while i had uTorrent downloading files and PeerBlock open.

As i said before, i don't think i had this problem before with PeerGuardian, 
before
updating to PeerBlock.

Original comment by therapto...@gmail.com on 3 Jan 2010 at 12:17

[GoogleCodeExporter]

i will try running uTorrent without PeerBlock for a while maybe a week or two, 
so
i'll see if the problem is really caused by PeerBlock or not.

I think it might be possible that a software could make a critical Windows file
crash, thus making Windows crash and BSOD...

Original comment by therapto...@gmail.com on 4 Jan 2010 at 12:18

[GoogleCodeExporter]

yes, it seem like the BSODs was caused by PeerBlock! i used uTorrent v1.8.5 
alone now
and my computer never crashed!

Original comment by therapto...@gmail.com on 17 Jan 2010 at 1:10

[GoogleCodeExporter]

Hmm, looks like memory corruption...  =;(  NOT good.  Will continue looking into
these crashes.  Might need to start running PeerBlock through Driver Verifier 
in a VM
or something to try and chase down issues that could be causing this.

Original comment by peerbloc...@gmail.com on 17 Jan 2010 at 1:20

• Changed state: Accepted

[GoogleCodeExporter]

i often play games that require a lot of memory, and i never had a BSOD, so i 
don't
think it's corrupted memory. I have done a few tests in MemTest86+ v1.70 and my 
2 RAM
sticks doesn't seem to have corrupted memory on them (2 x Kingston 1gb DDR400 
PC3200).

I never had a BSOD before caused by stable game releases. The only game crashes 
i
encountered was in Entropia Universe (now called Planet Calypso) with the tons 
of
drivers issues and bugs, and also tons of complains because of constant crashes 
with
Nvidia video cards drivers.

So i think there's a programming problem in PeerBlock. I noticed in the 
programmer
blog that there seem to have a very rare crash bug that might cause a BSOD. 
That bug
might not be that rare though, it's just that most peoples are not reporting it
thinking it's something else or just Windows bug or something (ignorance is 
bliss...)

Original comment by therapto...@gmail.com on 17 Jan 2010 at 2:18

[GoogleCodeExporter]

I meant that since you've made a good case for PeerBlock being the root cause 
of this
problem, our driver is likely the problem here.  We're probably scribbling all 
over
the heap or something.  Hence the reason I noted that we should start running 
Driver
Verifier to help chase down whatever we're doing wrong.  

Driver Verifier will intentionally crash your system as soon as it suspects
wrongdoing on the part of your driver, hopefully letting us trap the error as it
happens instead of trying to backtrack from already-corrupted memory.  
(Corrupted
meaning "been overwritten by a different process", not "bad memory"...)  We 
know that
Driver Verifier complains about at least some aspects of our driver already, we
simply haven't yet really had much of a reason to go hunting for bugs there 
though -
the problem it most often complains about is generally benign.

Sorry for the confusion...

Original comment by peerbloc...@gmail.com on 17 Jan 2010 at 2:23

[GoogleCodeExporter]

i'm glad this is not taken lightly

Original comment by therapto...@gmail.com on 17 Jan 2010 at 2:50

[GoogleCodeExporter]

This has been bugging me for a week now. Thought it was my memory or external 
drive
error, but they were confirmed fine after memtesting and scanning thedisk. I 
kept
getting bsod with just utorrent 1.8.5 and PeerBlock as the only things open in 
Vista.
Will try running utorrent without PeerBlock and see what happens.

Original comment by brigadi...@googlemail.com on 17 Jan 2010 at 12:20

[GoogleCodeExporter]

Update: My BSOD is not related to Peerblock as it still happened without 
Peerblock
running. Going to investigate if my wireless network driver needs updating 
next...

Original comment by brigadi...@googlemail.com on 17 Jan 2010 at 1:35

[GoogleCodeExporter]

well my computer did crashed this morning...but this time the "probable cause" 
(as it
says in WinDbg) is a file called "ipnat.sys", so the crash is different from 
the ones
i previously reported here.

And i wasn't running Peerblock when it crashed, only uTorrent v1.8.5

Original comment by therapto...@gmail.com on 17 Jan 2010 at 3:36

[GoogleCodeExporter]

I've been running Peer Block for over a month now, and I've been experiencing 
the same thing (memory corruption caused by Peer Block), but only when I'm 
running process- and memory-intense applications. (Namely, this occurs 
regularly when running multiple EVE-Online clients and long-running Python 
scripts.)

I'm running on an Intel duo-core 3.00 GHz. (This is entirely unrelated to the 
known EVE-Online dual-core bug that requires affinity to be set for each client 
- running with affinities set and Peer Block off produces no error.)

Minidump attached.

Original comment by dambri...@gmail.com on 4 Aug 2010 at 9:07

Attachments:

• Mini080410-02.dmp

[GoogleCodeExporter]

Have you uncheckt that speed limiter in the utorrent settings? It may do some 
problems. For me it blocks complete the download speed. An it creates also 
stability problems sometimes.

Under setting "Brandwith Managment". Try once with uncheck this.

Original comment by claude.k...@gmail.com on 15 Aug 2010 at 8:05

[GoogleCodeExporter]

@theraptor01

Could you run a chkdsk on your hard drive as it seems like your crashes might 
be to do with a bad hard drive.

Original comment by nightstalkerz on 29 Aug 2010 at 8:50

[GoogleCodeExporter]

Anybody found a resolution to this problem?  It describes my situation exactly..

Original comment by BradleyG...@gmail.com on 10 Mar 2011 at 11:35

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

When I run PeerBlock, it always causes BSOD. Unluckily I checked Run When 
Windows Starts in installer. Now my Windows XP SP3 crashes each time I start my 
OS. I include 2 minidumps and peerblock.log created by Windows. I am currently 
running LUbuntu 10.04.3 LTS. I will delete peerblock.exe to prevent it from 
starting each time I boot Windows. That should solve the problem.

Original comment by q...@LIVE.COM on 21 Feb 2012 at 2:18

Attachments:

• Mini022112-01.dmp
• Mini022112-02.dmp
• peerblock.log