Windows 7: Windows 7 x64 Ultimate Recurring BSOD

darith · 26 Apr 2011

Hi, I have a recurring BSOD on my Windows 7 x64 Ultimate OS. It is my work machine as I tend to leave it on after I leave work so I can access it remotely, but it has been crashing when I return in the morning consistently. Please help!

My Operating System Details
- Windows 7 x64 Ultimate
- This is not the original operating system that came with the machine (It was Windows Vista 32-bit)
- What is the age of system (hardware)? 4 Years Old
- What is the age of OS installation (have you re-installed the OS?) 5 Months Old

darith · 26 Apr 2011

Could the error reports suggest over heating at all?

usasma · 27 Apr 2011

After we're finished with this problem, please visit the HP website and update ALL drivers. Then visit Windows Update...Important Updates and download/install Service Pack 1

I suspect that the cause here is your Symantec Endpoint Protection. Please do the following:

Quote:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: KB Article Not Found
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's

You also have quite a few older drivers on the system (and they may have problems with Windows 7). Please do the following:
OLDER DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please update these drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

Quote:

Code:


amdxata.sys             Tue May 19 13:56:59 2009 (4A12F2EB)
DRVECDB.SYS             Fri Jul 21 14:21:08 2006 (44C11B14)
PxHlpa64.sys            Tue Jun 23 19:16:35 2009 (4A416253)
ENG64.SYS               Fri Mar 04 17:02:16 2011 (4D716168)
SRTSPX64.SYS            Mon Aug 10 23:31:44 2009 (4A80E620)
DLARTL_E.SYS            Thu Feb 08 23:04:36 2007 (45CBF2D4)
akshhl.sys              Fri Jul 20 05:30:59 2007 (46A080D3)
SRTSP64.SYS             Mon Aug 10 23:30:48 2009 (4A80E5E8)
SYMEVENT64x86.SYS       Wed Jun 24 16:19:12 2009 (4A428A40)
DLACDBHE.SYS            Thu Feb 08 23:05:10 2007 (45CBF2F6)
akshasp.sys             Mon Feb 02 10:47:42 2009 (4987159E)
wpsdrvnt.sys            Thu Sep 17 21:09:26 2009 (4AB2DDC6)
eeCtrl64.sys            Fri May 21 17:44:45 2010 (4BF6FECD)
EraserUtilRebootDrv.sys Fri May 21 17:44:45 2010 (4BF6FECD)
point64.sys             Tue Jun 29 04:54:31 2010 (4C29B4C7)
e1e6032e.sys            Tue Mar 24 14:17:23 2009 (49C923B3)
lmimirr.sys             Tue Apr 10 18:32:45 2007 (461C108D)
mcdbus.sys              Tue Feb 24 05:34:07 2009 (49A3CD1F)
teefer2.sys             Wed May 13 15:25:52 2009 (4A0B1EC0)
aksusb.sys              Wed Jan 28 10:02:53 2009 (4980739D)
RTKVHD64.sys            Tue Aug 04 05:50:52 2009 (4A78047C)
AKSCLASS.SYS            Tue Oct 27 13:32:46 2009 (4AE72EBE)
DLAUDFAE.SYS            Thu Oct 26 19:19:20 2006 (45414278)
DLAUDF_E.SYS            Thu Oct 26 19:19:00 2006 (45414264)
aksfridge.sys           Fri Sep 24 07:27:55 2010 (4C9C8B3B)
DRVEDDM.SYS             Fri Feb 09 15:34:03 2007 (45CCDABB)
DLADResE.SYS            Thu Oct 26 19:20:30 2006 (454142BE)
DLAIFS_E.SYS            Thu Oct 26 19:18:00 2006 (45414228)
DLAOPIOE.SYS            Thu Oct 26 19:20:01 2006 (454142A1)
DLAPoolE.SYS            Thu Oct 26 19:18:37 2006 (4541424D)
DLABMFSE.SYS            Thu Oct 26 19:19:26 2006 (4541427E)
DLABOIOE.SYS            Thu Oct 26 19:19:22 2006 (4541427A)
aksdf.sys               Wed Jul 21 11:59:49 2010 (4C471975)
WpsHelper.sys           Thu Sep 02 21:15:06 2010 (4C804C1A)
hardlock.sys            Mon Feb 02 10:34:08 2009 (49871270)
RaInfo.sys              Fri Jan 04 13:57:14 2008 (477E818A)
LMIRfsDriver.sys        Mon Jul 14 12:26:56 2008 (487B7E50)
covpnv64.sys            Mon Jan 25 16:18:26 2010 (4B5E0AA2)
nvlddmkm.sys            Fri Jul 09 17:15:58 2010 (4C37918E)
nvBridge.kmd            Fri Jul 09 17:07:54 2010 (4C378FAA)
dsNcAdpt.sys            Mon Mar 30 22:33:33 2009 (49D180FD)

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Apr 22 11:06:06.932 2011 (UTC - 4:00)
System Uptime: 0 days 0:03:14.711
Probably caused by : win32k.sys ( win32k!TimersProc+197 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xA_win32k!TimersProc+197
Bugcheck code 0000000A
Arguments ffffb800`0383dab0 00000000`00000002 00000000`00000001 fffff800`036cc0d6
BiosVersion =  5.07
BiosReleaseDate = 05/24/2007
CPUID:        "Intel(R) Core(TM)2 Quad CPU           @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Apr 22 11:01:14.950 2011 (UTC - 4:00)
System Uptime: 0 days 17:43:05.000
BugCheck D1, {fffff0800196bd14, 2, 8, fffff0800196bd14}
Probably caused by : cdrom.sys ( cdrom!RequestDispatchSpecialIoctls+23f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_cdrom!RequestDispatchSpecialIoctls+23f
Bugcheck code 000000D1
Arguments fffff080`0196bd14 00000000`00000002 00000000`00000008 fffff080`0196bd14
BiosVersion =  5.07
BiosReleaseDate = 05/24/2007
CPUID:        "Intel(R) Core(TM)2 Quad CPU           @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Apr 19 02:28:19.069 2011 (UTC - 4:00)
System Uptime: 3 days 21:58:59.966
*** WARNING: Unable to verify timestamp for teefer2.sys
*** ERROR: Module load completed but symbols could not be loaded for teefer2.sys
Probably caused by : teefer2.sys ( teefer2+7244 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_teefer2+7244
Bugcheck code 00000050
Arguments ffffe280`04181b30 00000000`00000000 fffff800`034a639c 00000000`00000007
BiosVersion =  5.07
BiosReleaseDate = 05/24/2007
CPUID:        "Intel(R) Core(TM)2 Quad CPU           @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

usasma · 27 Apr 2011

The error reports don't suggest overheating - but that's not something that we can usually identify (try going through your Event Viewer to see if there are any thermal events there).

But your description doesn't suggest overheating - you come in in the morning and it crashes. If it's overheating overnight, then it'd crash before you came in in the morning. Have you checked to make sure that the case is cleaned out and the fans are working? You can point a house fan into the case to see if that helps.

Windows 7: Windows 7 x64 Ultimate Recurring BSOD

Windows 7 x64 Ultimate Recurring BSOD problems?