Process Guard 3.4 BSOD

[linney]

I have installed Process Guard 3.4 on a XP Pro SP2 machine after successfully removing an earlier version of the program. The new install completed successfully. Learning Mode was used for several logons, logoffs and reboots, I then switched to Secure settings and checked the 4 Global Protection Options.

I am seeing BSOD (details below) involving the file Procguard.sys. This seems to be occurring when logging off from one user to log on to another user. Fast User Switching was not being used.

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 7/07/2006
Time: 10:30:12 AM
User: N/A
Computer: P4
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xf7a2ae8c, 0xba51385c, 0x00000000). A dump was saved in: F:\WINDOWS\Minidump\Mini070706-01.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.




Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 7/07/2006
Time: 10:46:12 AM
User: N/A
Computer: P4
Description:
Error code 1000008e, parameter1 c0000005, parameter2 f7b1ae8c, parameter3 f530085c, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 66 37 62 31 61 65 38 63 f7b1ae8c
0040: 2c 20 66 35 33 30 30 38 , f53008
0048: 35 63 2c 20 30 30 30 30 5c, 0000
0050: 30 30 30 30 0000



Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 7/07/2006
Time: 10:45:23 AM
User: N/A
Computer: P4
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xf7b1ae8c, 0xf530085c, 0x00000000). A dump was saved in: F:\WINDOWS\Minidump\Mini070706-02.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 7/07/2006
Time: 10:31:02 AM
User: N/A
Computer: P4
Description:
Error code 1000008e, parameter1 c0000005, parameter2 f7a2ae8c, parameter3 ba51385c, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 66 37 61 32 61 65 38 63 f7a2ae8c
0040: 2c 20 62 61 35 31 33 38 , ba5138
0048: 35 63 2c 20 30 30 30 30 5c, 0000
0050: 30 30 30 30 0000





ON THE BSOD I had the driver mentioned as procguard.sys on every occassion. Additional details have been sent to DiamondCS Support.

[Carver]

I found if I don't keep it in learning mode PG gete a little cranky, infact I still have it in learning mode ATM. Applications that I ran after I installed PG 3.4, if I disengage learning mode I get processes blocked. From the same application that I ran. I did get a bsod, but it can't be dirrectly atributed to PG. but it could have blocked a proccess that is needed for the computer to run.

[linney]

My problem seems to have been fixed (touch wood) by the excellent help from Support at DiamondCS (thanks Gavin) and the replacement of the driver, Procguard.sys, to a newer version.

[Carver]

-{ Quote: "My problem seems to have been fixed (touch wood) by the excellent help from Support at DiamondCS (thanks Gavin) and the replacement of the driver, Procguard.sys, to a newer version." }-
Glad to hear it, and my PG seems to have settled down.