BSOD on CIS 3.11.108364.552

Hi! I recently updated my CIS to version 3.11.108364.552 via automatic updates, and since then my pc crashes to bsod at least once a day, no matter what I’m doing, in a seemingly random fashion. Yesterday I was so pissed off I decided to backup data, format and reinstall Vista. I then reinstalled some basic apps including CIS, fresh install of version 3.11.108364.552. Last time it BSODed (about an hour ago) I got a nice

STOP: 0x00000000D1 (0x000000000000000008, 0x000000000000000002, 0x000000000000000001, 0xFFFFF980072EEFA4)
inspect.sys address FFFFF980072EEFA4 base at FFFFF980072ED000, datestamp 4A8EB7B9

and I’m including crash dump of the last three BSODs I had since yesterday hard drive format. I have a genuine Vista x64 Business install. Until yesterday I had SP2 installed, now I don’t since I’m still downloading the 1.5+ gb of SP1+SP2.
Please help me, I have an important job to deliver asap and my pc keeps crashing… it’s frustrating!

[attachment deleted by admin]

Hello seebrock3r
Looks like it’s pointing all 3 times to inspect.sys the firewall driver for CIS.
2 times it seems to relate to Azureus.exe also, maybe you can try to not run that for a while and see how it goes ? otherwise I’d advise to run the Windows Firewall for the duration of you important project.

You can also go back to the 3.10.x install if that was stable for you:

Can you post the dumps also on this post ?

That’s closer watched specifically for BSOD’s.

BugCheck C2, {7, 113d, 4090009, fffffa8008775d00}
Probably caused by : inspect.sys ( inspect+1fde )

The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.

PROCESS_NAME: spybotsd162.tmp

BugCheck D1, {8, 2, 1, fffff9800a6d1fa4} Probably caused by : inspect.sys ( inspect+1fa4 )

An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.

PROCESS_NAME: Azureus.exe

BugCheck C2, {7, 113d, 40d000c, fffffa8008435390} Probably caused by : inspect.sys ( inspect+1fde )

PROCESS_NAME: Azureus.exe

It just crashed again… I had nothing else open than Google Chrome. BSOD this time was:

STOP: 0x000000C2 (0x00000000000000007, 0x0000000000000D008, 0xFFFFFA8006988B60)

This same kind of BSOD appeared before (if I recall it right, the last BSOD before formatting was exactly like this). Now I’m uninstalling 3.11 and installing an older version until someone confirms me this has been solved, because I can’t work like this on a pc that keeps crashing…
I hadn’t Vuze open at least half of the times it crashed, because I thought it could be opening too many connections, and I saw that was not the point since BSODs continued appearing. The first two BSODs had it open since I was testing my theory with the freshly installed OS to see if the problem was gone - and evidently it wasn’t :frowning:
Attached are the four minidumps of the 4 crashes that happened since yesterday late afternoon, when I reinstalled Vista. I’m posting them on the other topic, too.
Thank you for your great help!

[attachment deleted by admin]

Bad Pool Caller has usually nothing to do with software on your computer.
It indicates a problem with your page file. You better recreate that file and then see if other BSOD’s appear.

I installed temporarily ESET Smart Security 4 trial and updated all drivers (especially the network card’s) and now it seems to work ok. I don’t know if this has to be attributed to the new software or to the updated drivers…

Well Firewall and NIC driver are very close to each other… could very well be.

In fact I updated the drivers because I saw in WinDbg dump analysis that in at least one of the crashes was involved Realtek’s rtlh64.sys. After lots of efforts I finally managed to get the latest driver version (Gigabyte page only had an outdated version, Realtek’s didn’t even load… phew!), so I suspect that could have done the trick.
The point is, I’ve had that same driver for some months and I haven’t had any BSOD before, so I guess it may be the interaction of a buggy driver with the newer versions of CIS that brought the bug into life (assuming CIS hasn’t got any bug - which I’d not say is true for sure, after all). I’ll test the new driver with CIS asap when I’m over with that urgent project…
Thank you again for your support