beta 3.2 issue

My first BSOD with PG! I uninstalled the old PG version and installed the new beta 3.2 without incident. Learning mode worked great. Upon reboot the BSOD occurred restricting access to windows each time. Only until removing PG in safe mode corrected the problem. Currently, I am back to v3.150. I am using XP Pro SP2.

 

same here

 

Hi,

Not any help without any further information !
Please EMAIL us the exact information shown on the bluescreen

If you can't get it, disable the automatic reboot so you have time to write it down.

Something to try, disable protection and then use Device Manager, in VIEW change to "show hidden devices" and then find procguard under "non plug and play"

It's start method will be SYSTEM, change to AUTOMATIC and press OK. Then check it to confirm you actually changed it. You can't change it while the driver is loaded, so if it wont change then reboot once with protection disabled to be sure.

Then enable protection and see if you can reproduce the BSOD with the driver starting as Automatic not System ?

 

OK Gavin, here's some info. Sorry about the delay at first. I didn't know how you wanted to handle the troubleshooting.

Strange but better news! I can't reproduce the BSOD. This time after uninstalling the old PG I didn't reinstall the beta and start fresh with learning mode. I loaded my old Protection and Security list and rebooted with no errors. As you asked I changed procguard to AUTOMATIC and enabled protection with no errors. I then rebooted with no errors. I changed procguard back to SYSTEM, enabled, and rebooted again with no errors. So far so good.

 

I had exactly the same problem with BSOD and new PG 3.2 beta, so uninstalled it. After seeing this thread, I re-installed PG 3.2 beta and on the first reboot I didn't get a BSOD. Unfortunately, on subsequent reboots I did get a BSOD every time during boot (ie. before log-on screen).

Booting to Safe-Mode and changing start method to AUTOMATIC fixed the problem - No BSOD after several reboots.

Changing start method back to SYSTEM resulted in BSOD again.

Changing back to AUTOMATIC resulted in no BSOD.

The info in the BSOD is as follows:

Code:

*** STOP: 0x0000007E (0xC0000005, 0x00000000, 0xF895941c, 0xF8959118)

I am currently testing the new KAV 2006 beta, which might cause problems I suppose (KAV was disabled during PG installation).

HTH

 

Update:

One thing I didn't try was to completely shut down my computer and restart again to see if PG was still working good. I got a BSOD again this time. Here's the code:

***STOP:0x0000007E(0xC0000005,0xC00012D,0xF8A66408,0xF8A66104)

I restarted and tried to load windows normally instead of safe mode to change procguard to Automatic. Windows loaded normally with PG working again. I shutdown again and booted back to windows without error.

I don't know if this is related or not but I've not had anything misbehaving recently or BSOD's until the start of the new beta.

 

It's been my experience that KAV2006's Proactive Defense conflicts severely with Process Guard and System Safety Monitor (BSODs on logout, BSODs whenever answering Deny to a PG Execution prompt) whether enabled or not. I'd recommend reporting any such conflict at the KAV forum.

 

I've never had any such problems when running PG 3.15. It's only since I've installed 3.2 that the BSOD problem has arisen.

 

Ok thanks ! this is an old issue we have managed to reproduce (sometimes). This information should help, and as expected PG will be 100% stable with the driver starting a little later (Automatic)

 

Sounds good Gavin. I might as well change the driver over to Automatic now so I won't have any more error screens periodically.

 

Can we expect a second beta of PG 3.2 to check known problems are fixed before final is released ?

 

Second beta appears to have fixed the BSOD issue when starting as SYSTEM. Can Wayne/Gavin confirm something has been done to fix this issue ?

 

I tried the trial version of KAV and it gave me all sorts of problems..BSOD right after the install. I removed it and everything was back to normal.

 

I`ve said in another topic that I`m not having any BSOD`s. The new beta seems to be working great so far...on my machine.