Fresh install BSODs

I decided to install v3.0.5.159 into a snapshot that still had 3.0.1.65 installed.

However, this version was not loaded at boot, because it was set to 'Manual' mode via services.msc.

Basically, Prevx was not running whenever this snapshot was loaded.

Before installing the latest release (v3.0.5.159), I removed v 3.0.1.65 via Control Panel > 'Add or Remove Programs' then rebooted.

This appeared to be successful.

I then ran the installer for the latest official release and this is when I had a BSOD. It occurred after clicking 'yes' to accept the license terms during the running of the install wizard.

I did a hard restart and got another BSOD at startup.

I tried again and got the another BSOD.

I then rebooted into "Safe Mode with networking", and using "System Restore" got the system restored to an earlier restore point.

See the following event logs:

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 3/06/2010
Time: 9:31:56 AM
User: N/A
Computer: XXXX-ZZZZZZZZZZ
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0x80540a44, 0xb54497f0, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini060310-01.dmp.


Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 3/06/2010
Time: 9:35:40 AM
User: N/A
Computer: XXXX-ZZZZZZZZZZ
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0x80540a44, 0xb50b31b0, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini060310-02.dmp.


Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 3/06/2010
Time: 9:39:29 AM
User: N/A
Computer: XXXX-ZZZZZZZZZZ
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0x80540a44, 0xb5094890, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini060310-03.dmp.

Joe, just say the word and I will email the 'MiniDumps' to you.

 

The word! I'll definite be interested in taking a closer look at as many minidumps as you can provide.

Thank you!

 

Email sent...please keep me posted.

 

I think the failure occurred because, v3.0.1.165 was set on manual and also, the license had long expired. I did a restart from START > Run > services.msc and it asked to renew protection, so I entered my new/current license details.

Then, I did an over the top install of the current beta v3.0.5.160, which as you can see appears to have succeeded.

Sweet as...

 

Prevx had just completed a scan and I was trying to save it, when my SSM thru up a popup letting me know that Prevx was about to update again...talk about machine gun updates, 2 in less than a few hours apart.

 

Are you still getting BSOD's with this build?

TH

 

Hi TH

The initial problem that I had, has not occurred again, and since there have been a couple of subsequent beta releases, I have now skipped v3.0.5.159.

As you can see from the screenshots in my previous post, the last is of a Winpatrol popup indicating a BHO change in Prevx v3.0.5.161

P.S. I hoped you enjoyed your dinner.

 

Good to here and yes my Dinner was great Thanks!

TH