Andy Many professionals consider the error reporting in windows XP to be a complete waste of time and resources as it tells you nothing about nothing. a report like those you supplied could be generated if a program crashes for whatever reason and may not necessarily mean there's a real problem. when I tried sending the reports to Microsoft, all I got back was what seemed to be a standard reply telling me that a device driver had caused the problem but no further information was available. My thought was, if they could tell me it was a device driver that caused the problem, how come they couldn't tell me which device driver it was. It seemed like a fob off. Wally Harding RNIB Hi-tech support -----Original Message----- From: Andy Collins [mailto:Andy@xxxxxxxxxxxxxxxxxxx] Sent: 26 May 2004 20:26 To: access-uk@xxxxxxxxxxxxx Subject: [access-uk] Re: Re; error report Hi Justin - Thanks for the suggestion, found the following 2 entries [amongst others], I regularly have trouble with PowerDVD, but don't know how to sort it, and the one about JFW is interesting, and I'd be interested to see what others say, so here are 2 of the log entries: [by the way, there was nothing in there about drivers as commented upon in the error report] 18 April 2004 Applicatio n Error Faulting application powerdvd.exe, version 4.0.0.1813, faulting module appbarcom.dll, version 1.0.0.1, fault address 0x0000bb8b. 08 May 2004 Applicatio n Error Faulting application jfw.exe, version 5.0.621.0, faulting module jfw.exe, version 5.0.621.0, fault address 0x001244d0. Andy ----- Original Message ----- From: "Justin R" <mypc128@xxxxxxxxxxxx> To: <access-uk@xxxxxxxxxxxxx> Sent: Wednesday, May 26, 2004 7:38 PM Subject: [access-uk] Re; error report Hi Andy, have you and Debbie looked in the error log report? is that any good in understanding what's going on. its in the start menu under "help and Support" then can tab down to the link (if you the layout isn't set in classic view) "use tools to view you computer's information and diagnose problems". in that... you then have a list on the left, in that list, go to Advanced systems information. then, after that, go into the right pain view and select the link "view error log". not very easy to understand the logs but look for the date that your crash happened, get jaws etc. to read the log. maybe copy and past it here. it might help. Just a thought. all hte best, Justin Hi Debbie - Just to say, you're not on your own in this, It quite regularly happens for me too, and I've now stopped sending the error reports, but like you, have no idea which driver could be causing the problem, and I have checked for updates for drivers from the MS website. Sorry I can't help! Andy ----- Original -- This email has been verified as Virus free Virus Protection and more available at http://www.plus.net -- DISCLAIMER: NOTICE: The information contained in this email and any attachments is confidential and may be privileged. If you are not the intended recipient you should not use, disclose, distribute or copy any of the content of it or of any attachment; you are requested to notify the sender immediately of your receipt of the email and then to delete it and any attachments from your system. RNIB endeavours to ensure that emails and any attachments generated by its staff are free from viruses or other contaminants. However, it cannot accept any responsibility for any such which are transmitted. We therefore recommend you scan all attachments. Please note that the statements and views expressed in this email and any attachments are those of the author and do not necessarily represent those of RNIB. RNIB Registered Charity Number: 226227 Website: http://www.rnib.org.uk