|
Moderator, Microsoft Support
Join Date: Sep 2007
Location: New Jersey, USA
Posts: 4,778
OS: Vista SP1 x64, x86 / XP SP3 Pro, Media, Home, / Win 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
As you may be aware, "trid3d.dll" is a KLE/PLE Display Driver by VIA Technologies, Inc. It is the driver for your system's Trident Video Accelerator CyberBlade-i7. It appeared to me that you have a fresh install of Windows 2000 SP4 with SP5 Update Rollup-1 (Update Rollup 1 for Windows 2000 SP4) as most Windows Updates occurred on 03-05-08. If this is the case, it is possible that an older version of this driver was either installed directly or indirectly over a newer version (that you installed) by Windows itself.
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
__________________
If you were expecting a reply from me and I have not yet done so, please send me a PM with a link to your thread.
|