UberG33K

Update:: I have since installed 5.01.006, and have not had the problem since. This problem only seems to present itself with the beta version. Just to avoid any longwinded debates again, I'm just posting this for reference purposes. Whether this is driver related or not, it only seems to occur when I have the beta version installed. The problem recurrs shortly after installing WB 5.01 beta. If you are running with a FireGL T2 on a mobile system, you may experience s

I'm not trying to argue here, I'm just telling you my findings. Considering I have verified that everything I have control over seems to be fully operational with the latest updates, the only correlation I could find was WB 5.01. I do not know enough about how your product interacts with the drivers/hardware to make any educated statements about what specifically is causing it, I'm simply stating that: A) I never had this problem prior to installing WB 5.01 B) I have the most cu

Ok, well as I've said.... the problem went away when I removed WB 5.01... I've never had an issue with any other application, and have a very stable system other than the problems that occured with WB 5.01 installed. I posted this information because I thought it would be of help. If it's a driver issue, it's a driver issue that only seems to occur with your software loaded. I have verified the hardware is fine. I have tested this hardware with many other applications, and run sever

I've got this installed on an IBM thinkpad T42P with an ATI FireGL T2 128MB. I've run full system diagnostics, and everything has passed including my video card. I have not had this problem since uninstalling WB 5.01, and prior to that my system was blue screening several times a day. I've rigorously tested it since removing 5.01 and reinstalling 4.6 without any problems. Prior to installing 5.01 I never had this error. I'm sure you know more about your software than I do, but I'v

I recently installed WB 5.01 Beta, and shortly thereafter, I started receiving BSODs on a regular basis. I could recreate the problem by downloading files in IE, or manipulating files with explorer (Move, copy, delete, etc) The BSOD stated: BAD_POOL_HEADER STOP: 0x000000019 After rebooting, and submitting the error to M$, they identified it as a problem with my video adapter. I verified that my drivers were current, and tried several other drivers to no av

After installing WB 5.01 Beta, I was getting Bad_Pool_Header errors very frequently. It occurred most when I was manipulating files (Moving, copying, deleting, or downloading) Whenever it would happen, I would get a BSOD Bad_Pool_Header Stop 0x00000019. After reverting back to WB 4.6 I have not had the problem. Windows Error reporting indicated it was a problem with my video driver. I have verified I am running the most current drivers for all hardware in my machine.