![]() |
![]() |
![]() |
|||||
![]() |
![]() |
![]() |
![]() |
![]() |
|||
| Welcome
to Tech Support Forum home to more then 136,000 problems solved. Issues
have included: Spyware, Malware, Virus Issues, Windows, Microsoft,
Linux, Networking, Security, Hardware, and Gaming Getting your
problem solved is as easy as: 1. Registering for a free account 2. Asking your question 3. Receiving an answer Registered members: * See fewer ads. * And much more..
|
| Want to know how to post a question? click here | Having problems with spyware and pop-ups? First Steps |
|
|||||||
| Windows 2000 Pro / NT Workstation Support Find support for Windows 2000 Pro / NT Workstation here |
![]() |
|
|
Thread Tools |
|
|
#1 (permalink) |
|
Registered User
Join Date: Mar 2008
Posts: 4
OS: Windows 2000
|
Blue Screen of Death
When ever I access certian web pages my computer crashes and shows a blue sceen with the following error message
*** STOP: 0x0000001E (0xC0000005,0xF7407002,0x00000000,0x1CAF 4028) KMODE_EXCEPTION_NOT_HANDLED *** Address F7407002 base at F740400, DateStamp 38439a2a - trid3d.dll Beginning dump of physical memory. Physical memory dump complete. Contact your system administrator or technical support group. I have been led to believe this may be a problem with my video card. Im running Windows 2000 service pack 4 and my video card is a Trident Video Accelerator CyberBlade i7. Any help with this would be greatly appreciated as it is getting very frustrating. Cheers-Rawdon |
|
|
|
|
|
#2 (permalink) | |
|
Moderator, Microsoft Support
Join Date: Sep 2007
Location: New Jersey, USA
Posts: 2,664
OS: Vista SP1, XP Pro, XP Home, Windows 95, DOS, IBM 390 TSO/ISPF
|
Re: Blue Screen of Death
Quote:
Hi Rawdon. . . Welcome to the Tech Support Forum! It has been a while since I have used Windows 2000. I usually respond to threads in the Vista and XP TSF forums, but I analyze system crashes and believe that I may be able to help you, so please bear with me. The blue screen that you refer to is actually called "The Blue Screen of Death" (BSOD). Each time a BSOD appears it [should] leaves a memory dump behind that I process with a debugger and hopefully provide you with the name of a driver or piece of software or hardware that is the most probable cause of your system crashes. There are, of course, no guarantees. The memory dump files should be located in c:\%SystemRoot%\Minidump, with %SystemRoot% being the name of the folder containing the Windows files - usually c:\windows\minidump\ - the dump files will be named similar to "Mini032108-01.dmp". Get them all - regardless of the number. I will also need system and program information to aid me in the dump analysis. Please download Belarc Advisor, install it and run it. A report will appear in an Internet browser window. I would like for you to save this report in "mht" format (Top right of IE screen; Page; Saved as; save as mht). You can download Belarc HERE. However, before allowing preying eyes to view this report, please be sure to delete the information related to your product key codes located about ½way down the report. I prefer the dumps and the Belarc report be together in one zip file and attached to your next post. If you are not familiar with the zip process, then send all dump files and the Belarc report as separate files attached to an email and send it to me at TSFjcgriff2*at*gmail.com - replace the "*at*" with "@". My results will be posted here in this thread. I will need some time to process the dumps as I am currently working on others. Also, this is a holiday weekend and I don't expect to be around very much until early next week. Should you have any questions regarding the aforementioned, please POST again or send me a PM. Regards. . . JC
__________________
![]() SysInternals Suite • BSOD Bug Checks • Media Fire • Belarc Advisor • MS TechNet • Microsoft NTDE/CPR • MSDN 4d 69 63 72 6f 73 6f 66 74 - 20 - 56 69 73 74 61 / 58 50 - 20 - 53 75 70 70 6f 72 74 |
|
|
|
|
|
|
#4 (permalink) |
|
Moderator, Microsoft Support
Join Date: Sep 2007
Location: New Jersey, USA
Posts: 2,664
OS: Vista SP1, XP Pro, XP Home, Windows 95, DOS, IBM 390 TSO/ISPF
|
Re: Blue Screen of Death
Hi again RawdonWallace, I picked up the 41 minidump files from the zip file. As previously mentioned, I do have many others to get through first (about 200 or so). Furthermore, I must download about 200MB in additional files required to process these dumps from Microsoft that are specific to Windows 2000. Not a problem, though. Also, I would like the Belarc report that I requested saved in "mht" format (Top right of IE screen; Page; Saved as; save as "mht"). You can download Belarc HERE. However, before attaching to your post please be sure to delete the information related to your product key codes located about ½way down the report. Please note that I will need a few days to process these 41 dumps, so please be patient. Should you wish a status, feel free to PM me anytime - but please include a link to this thread. OK? Regards. . . JC
__________________
![]() SysInternals Suite • BSOD Bug Checks • Media Fire • Belarc Advisor • MS TechNet • Microsoft NTDE/CPR • MSDN 4d 69 63 72 6f 73 6f 66 74 - 20 - 56 69 73 74 61 / 58 50 - 20 - 53 75 70 70 6f 72 74 |
|
|
|
|
|
#5 (permalink) |
|
Moderator, Microsoft Support
Join Date: Sep 2007
Location: New Jersey, USA
Posts: 2,664
OS: Vista SP1, XP Pro, XP Home, Windows 95, DOS, IBM 390 TSO/ISPF
|
Re: Blue Screen of Death
Hi Rawdon, I have finally finished processing all 41 memory dumps. Indications are your suspicions contained in your original post are correct - 36 of the 41 (87.8%) BSODs resulted from a memory leak failure of the Dynamic Link Library (DLL) driver " trid3d.dll". Here is my analysis of said dumps: Code:
03/06/2008 11:17 PM trid3d.dll 65,536 Mini030708-01.dmp 03/08/2008 02:32 PM trid3d.dll 65,536 Mini030808-01.dmp 03/08/2008 03:11 PM trid3d.dll 65,536 Mini030808-02.dmp 03/09/2008 05:27 PM trid3d.dll 65,536 Mini030908-01.dmp 03/09/2008 06:01 PM trid3d.dll 65,536 Mini030908-02.dmp 03/10/2008 11:28 AM trid3d.dll 65,536 Mini031008-01.dmp 03/10/2008 12:20 PM ntoskrnl.exe 65,536 Mini031008-02.dmp 03/10/2008 12:52 PM ntoskrnl.exe 65,536 Mini031008-03.dmp 03/10/2008 08:50 PM win32k.sys 65,536 Mini031008-04.dmp 03/10/2008 10:23 PM ntoskrnl.exe 65,536 Mini031008-05.dmp 03/11/2008 12:32 PM trid3d.dll 65,536 Mini031108-01.dmp 03/11/2008 02:59 PM trid3d.dll 65,536 Mini031108-02.dmp 03/11/2008 07:38 PM trid3d.dll 65,536 Mini031108-03.dmp 03/11/2008 10:23 PM trid3d.dll 65,536 Mini031108-04.dmp 03/12/2008 11:57 AM trid3d.dll 65,536 Mini031208-01.dmp 03/12/2008 12:22 PM trid3d.dll 65,536 Mini031208-02.dmp 03/12/2008 05:47 PM trid3d.dll 65,536 Mini031208-03.dmp 03/12/2008 07:17 PM trid3d.dll 65,536 Mini031208-04.dmp 03/13/2008 09:49 PM trid3d.dll 65,536 Mini031308-01.dmp 03/15/2008 01:33 PM trid3d.dll 65,536 Mini031508-01.dmp 03/16/2008 07:07 PM trid3d.dll 65,536 Mini031608-01.dmp 03/16/2008 07:33 PM trid3d.dll 65,536 Mini031608-02.dmp 03/16/2008 07:43 PM trid3d.dll 65,536 Mini031608-03.dmp 03/17/2008 01:51 PM trid3d.dll 65,536 Mini031708-01.dmp 03/17/2008 07:43 PM trid3d.dll 65,536 Mini031708-02.dmp 03/18/2008 01:02 PM trid3d.dll 65,536 Mini031808-01.dmp 03/18/2008 02:11 PM trid3d.dll 65,536 Mini031808-02.dmp 03/18/2008 04:57 PM trid3d.dll 65,536 Mini031808-03.dmp 03/18/2008 08:23 PM trid3d.dll 65,536 Mini031808-04.dmp 03/19/2008 12:03 PM trid3d.dll 65,536 Mini031908-01.dmp 03/19/2008 08:17 PM trid3d.dll 65,536 Mini031908-02.dmp 03/19/2008 11:09 PM ntoskrnl.exe 65,536 Mini031908-03.dmp 03/20/2008 09:21 AM trid3d.dll 65,536 Mini032008-01.dmp 03/20/2008 01:44 PM trid3d.dll 65,536 Mini032008-02.dmp 03/21/2008 05:38 PM trid3d.dll 65,536 Mini032108-01.dmp 03/21/2008 09:55 PM trid3d.dll 65,536 Mini032108-02.dmp 03/21/2008 10:33 PM trid3d.dll 65,536 Mini032108-03.dmp 03/21/2008 10:38 PM trid3d.dll 65,536 Mini032108-04.dmp 03/21/2008 11:07 PM trid3d.dll 65,536 Mini032108-05.dmp 03/22/2008 09:51 AM trid3d.dll 65,536 Mini032208-01.dmp 03/23/2008 03:29 PM trid3d.dll 65,536 Mini032308-01.dmp I found it both interesting and unusual that the memory dumps did not provide a version number for this faulting module. I double checked that the debugging software was in fact specific to Windows 2000. So it is possible that an updated version may be available. You can find the website for Viarena HERE. In addition, HERE is a troubleshooting page from that same website specific to your display adaptor. As for the other five system crashes related to "ntoskrnl.exe" and "win32k.sys" - These both are Windows system NT Kernel mode files and do interact with various device drivers including video. One is an executable and the other a driver. It is likely that the video driver was simply not the primary probable cause in these events, but nonetheless a contributing factor. I would advise not worrying about addressing these five crash instances at this time; however, should the display adapter driver issue be remedied and subsequent BSODs occur, then those new dumps can be analyzed for additional information. To be on the safe side, I would also recommend performing a memory test - if you haven't already. MemTest86 is used throughout this Forum. It can be found HERE. Finally, regarding my second request for the Belarc report - apologies to you. For some reason, copying the unzipped files left the Belarc mht report as a link to this thread. When I went back and clicked on the unzipped Belarc file still in the temporary unzip folder (prior to copying to another directory), it brought up the report itself. Very strange. I guess this will be something I'll look into another day as my curiosity has been peaked! I have never had a problem copying files from the unzipped temp file to the final directory before. If you have any additional questions, please let me know. Regards. . . JC
__________________
![]() SysInternals Suite • BSOD Bug Checks • Media Fire • Belarc Advisor • MS TechNet • Microsoft NTDE/CPR • MSDN 4d 69 63 72 6f 73 6f 66 74 - 20 - 56 69 73 74 61 / 58 50 - 20 - 53 75 70 70 6f 72 74 |
|
|
|
|
|
#6 (permalink) |
|
Registered User
Join Date: Mar 2008
Posts: 4
OS: Windows 2000
|
Re: Blue Screen of Death
Thank you so much for your help. What would you recomend as a solution for the Cyberblade driver? (if you mentioned one I missed or didnt understand it, I'm not very compuer literate haha).
Last edited by RawdonWallace : 03-27-2008 at 03:10 AM. |
|
|
|
|
|
#7 (permalink) | ||
|
Moderator, Microsoft Support
Join Date: Sep 2007
Location: New Jersey, USA
Posts: 2,664
OS: Vista SP1, XP Pro, XP Home, Windows 95, DOS, IBM 390 TSO/ISPF
|
Re: Blue Screen of Death
Quote:
Hi again. . . In reflection, I would say that my instructions are cryptic at best - but not intentional as such, I assure you! I suggest that the video driver be the first to be addressed. The DLL module, "trid3d.dll", was directly at fault for the overwhelming majority of the BSODs that you encountered. As my previous post states, it is a KLE/PLE Display Driver by VIA Technologies, Inc., for your system's Trident Video Accelerator CyberBlade-i7 card. You would need to first determine the version number of your video driver(s) via Device Manager. Then proceed to the Viarena website HERE and look for the drivers specific to your video card. Check the version number and date. If a newer one is available, I would install it to see if it curtails the BSOD epidemic. In addition, HERE is a troubleshooting page from that same website specific to your display adapter where you may find additional information helpful to you given the exact nature of any problems you are having with video. Since the other five crashes could indirectly implicate the video driver, I would not bother addressing those at this time outside of performing a system memory test using MemTest86 found HERE. It is entirely possible that an installed software program may be causing the video driver to fault. But I found no other third party modules mentioned within the dump analysis. So the video card is what we look toward as being the primary BSOD cause. Something about the card, the driver or a software program that is interacting with the driver does not agree with your system. Updating the video drivers in this case would be the first plan of attack. Curiosity question, though - is this a fresh Windows 2000 install? If so, what was the reason? Should the BSODs reappear after these measures are in place, gather up the usual dump file suspects, a new Belarc report and zip them all up and attach to a POST. If you have any additional questions, please let me know. Regards. . . JC
__________________
![]() SysInternals Suite • BSOD Bug Checks • Media Fire • Belarc Advisor • MS TechNet • Microsoft NTDE/CPR • MSDN 4d 69 63 72 6f 73 6f 66 74 - 20 - 56 69 73 74 61 / 58 50 - 20 - 53 75 70 70 6f 72 74 |
||
|
|
|
![]() |
| Thread Tools | |
|
|