Intermittent System Lockups/BSoD

djhawk · Dec 25, 2010

I have an acer aspire 4730Z with vista home premium 32bit OEM. For a while now it has had intermittent problems with either total lockups (screen freezes still displaying whatever was up, no response to any input at all) or BSoD.

I have previously reinstalled the OS from the original manufacturer discs without any apparent effect on the problem, so I believe it to be hardware related.

Attached are the files I collected following the instructions in the posting instructions for this forum.

Any help is greatly appreciated, thank you!

richc46 · Dec 25, 2010

Code:

icrosoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_SystemHealthReport[1].zip\Windows_NT6_BSOD_jcgriff2\Mini081710-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Machine Name:
Kernel base = 0x82644000 PsLoadedModuleList = 0x8275bc70
Debug session time: Tue Aug 17 06:25:13.505 2010 (GMT-5)
System Uptime: 0 days 8:06:22.388
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {4, 2, 1, 8265d4b3}
Probably caused by : i8042prt.sys ( i8042prt!I8xCompletePendedRequest+3e )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
 bit 0 : value 0 = read operation, 1 = write operation
 bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 8265d4b3, address which referenced memory
Debugging Details:
------------------
 
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8277b868
Unable to read MiSystemVaType memory at 8275b420
 00000004 
CURRENT_IRQL:  2
FAULTING_IP: 
nt!KeRemoveDeviceQueue+45
8265d4b3 894204          mov     dword ptr [edx+4],eax
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
TRAP_FRAME:  82739a50 -- (.trap 0xffffffff82739a50)
ErrCode = 00000002
eax=866625fc ebx=00000000 ecx=85560400 edx=00000000 esi=866625f8 edi=00000000
eip=8265d4b3 esp=82739ac4 ebp=82739ad8 iopl=0         nv up ei ng nz ac po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010293
nt!KeRemoveDeviceQueue+0x45:
8265d4b3 894204          mov     dword ptr [edx+4],eax ds:0023:00000004=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from 8265d4b3 to 82691fd9
STACK_TEXT:  
82739a50 8265d4b3 badb0d00 00000000 000001ff nt!KiTrap0E+0x2e1
82739ad8 8265d5a9 866625f8 86662598 00000000 nt!KeRemoveDeviceQueue+0x45
82739aec 8265d54d 00000000 86662650 86662598 nt!IopStartNextPacket+0x26
82739b00 8265d622 86662598 8754b368 82739b2c nt!IopStartNextPacketByKeyEx+0x64
82739b10 8eed39ce 86662598 00000000 86662650 nt!IoStartNextPacket+0x2e
82739b2c 8eed413c 86662598 8754b368 00000000 i8042prt!I8xCompletePendedRequest+0x3e
82739b68 826ee30b 86662700 86662598 dc2c0110 i8042prt!I8042TimeOutDpc+0x194
82739c88 826edecb 82739cd0 8a514b02 82739cd8 nt!KiTimerListExpire+0x367
82739ce8 826ee635 00000000 00000000 001c8b3d nt!KiTimerExpiration+0x22a
82739d50 826ec89d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
82739d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
i8042prt!I8xCompletePendedRequest+3e
8eed39ce 6a18            push    18h
SYMBOL_STACK_INDEX:  5
SYMBOL_NAME:  i8042prt!I8xCompletePendedRequest+3e
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: i8042prt
IMAGE_NAME:  i8042prt.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  47918f5d
FAILURE_BUCKET_ID:  0xA_i8042prt!I8xCompletePendedRequest+3e
BUCKET_ID:  0xA_i8042prt!I8xCompletePendedRequest+3e
Followup: MachineOwner
---------
0: kd> lmtsmn
start    end        module name
8068c000 806d2000   acpi     acpi.sys     Sat Apr 11 00:19:03 2009 (49E01A37)
8f0d2000 8f11a000   afd      afd.sys      Sat Apr 11 00:47:01 2009 (49E020C5)
8f464000 8f589980   AGRSM    AGRSM.sys    Fri Feb 29 15:13:36 2008 (47C86770)
8eef0000 8ef1d000   Apfiltr  Apfiltr.sys  Mon Feb 18 08:09:37 2008 (47B98391)
8f8ec000 8f8eeb00   aswFsBlk aswFsBlk.SYS Mon Jun 28 16:32:32 2010 (4C2906E0)
8f8d5000 8f8ec000   aswMonFlt aswMonFlt.sys Mon Jun 28 16:32:55 2010 (4C2906F7)
8f5f8000 8f5fc100   aswRdr   aswRdr.SYS   Mon Jun 28 16:33:12 2010 (4C290708)
8f80b000 8f831c00   aswSP    aswSP.SYS    Mon Jun 28 16:37:28 2010 (4C290808)
8f0b4000 8f0bdc00   aswTdi   aswTdi.SYS   Mon Jun 28 16:37:50 2010 (4C29081E)
80797000 8079f000   atapi    atapi.sys    Sat Apr 11 00:39:09 2009 (49E01EED)
8079f000 807bd000   ataport  ataport.SYS  Sat Apr 11 00:39:10 2009 (49E01EEE)
8071c000 80726000   BATTC    BATTC.SYS    Sat Jan 19 00:32:45 2008 (47918B7D)
8f5a9000 8f5b0000   Beep     Beep.SYS     Sat Jan 19 00:49:10 2008 (47918F56)
8048c000 80494000   BOOTVID  BOOTVID.dll  Sat Jan 19 02:27:15 2008 (4791A653)
ab495000 ab4ae000   bowser   bowser.sys   Sat Jan 19 00:28:26 2008 (47918A7A)
96880000 9688e000   cdd      cdd.dll      unavailable (00000000)
b0b1b000 b0b31000   cdfs     cdfs.sys     Sat Jan 19 00:28:02 2008 (47918A62)
8ef28000 8ef40000   cdrom    cdrom.sys    Sat Apr 11 00:39:17 2009 (49E01EF5)
804d5000 805b5000   CI       CI.dll       Sat Apr 11 02:25:22 2009 (49E037D2)
8a7a6000 8a7c7000   CLASSPNP CLASSPNP.SYS Sat Apr 11 00:39:05 2009 (49E01EE9)
80494000 804d5000   CLFS     CLFS.SYS     Sat Apr 11 00:13:51 2009 (49E018FF)
8eece000 8eed1780   CmBatt   CmBatt.sys   Sat Jan 19 00:32:47 2008 (47918B7F)
80719000 8071b900   compbatt compbatt.sys Sat Jan 19 00:32:47 2008 (47918B7F)
8f87f000 8f88c000   crashdmp crashdmp.sys Sat Apr 11 00:39:12 2009 (49E01EF0)
8a7c7000 8a7d0000   crcdisk  crcdisk.sys  Sat Jan 19 00:50:29 2008 (47918FA5)
8f1c9000 8f1e0000   dfsc     dfsc.sys     Sat Apr 11 00:14:12 2009 (49E01914)
8a795000 8a7a6000   disk     disk.sys     Sat Apr 11 00:39:14 2009 (49E01EF2)
8f43f000 8f464000   drmk     drmk.sys     Sat Jan 19 01:53:02 2008 (47919E4E)
8f88c000 8f897000   dump_dumpata dump_dumpata.sys Sat Apr 11 00:39:09 2009 (49E01EED)
8f897000 8f8a1000   dump_msahci dump_msahci.sys Sat Apr 11 00:39:11 2009 (49E01EEF)
8f8a1000 8f8ab000   Dxapi    Dxapi.sys    Sat Jan 19 00:36:12 2008 (47918C4C)
8ece2000 8ed83000   dxgkrnl  dxgkrnl.sys  Thu Sep 24 21:27:14 2009 (4ABC1C72)
8a76e000 8a795000   ecache   ecache.sys   Sat Apr 11 00:40:12 2009 (49E01F2C)
807d5000 807e5000   fileinfo fileinfo.sys Sat Jan 19 00:34:27 2008 (47918BE3)
805b5000 805e7000   fltmgr   fltmgr.sys   Sat Apr 11 00:13:59 2009 (49E01907)
8f599000 8f5a2000   Fs_Rec   Fs_Rec.SYS   Sat Jan 19 00:27:57 2008 (47918A5D)
8a4f7000 8a512000   fwpkclnt fwpkclnt.sys Sat Apr 11 00:45:42 2009 (49E02076)
82611000 82644000   hal      halmacpi.dll Sat Apr 11 00:13:13 2009 (49E018D9)
8a521000 8a5ae000   HDAudBus HDAudBus.sys Sat Apr 11 00:42:41 2009 (49E01FC1)
ab40b000 ab478000   HTTP     HTTP.sys     Sat Feb 20 15:53:31 2010 (4B804BCB)
8eed2000 8eee5000   i8042prt i8042prt.sys Sat Jan 19 00:49:17 2008 (47918F5D)
8e406000 8ece2000   igdkmd32 igdkmd32.sys Wed Jun 02 12:37:38 2010 (4C0688D2)
ab5c9000 ab5d1000   int15    int15.sys    Tue Sep 30 17:50:14 2008 (48E29F16)
8a512000 8a521000   intelppm intelppm.sys Sat Jan 19 00:27:20 2008 (47918A38)
b0b31000 b0b47b80   jmcr     jmcr.sys     Thu May 29 08:21:32 2008 (483E9FCC)
8eee5000 8eef0000   kbdclass kbdclass.sys Sat Jan 19 00:49:14 2008 (47918F5A)
80404000 8040b000   kdcom    kdcom.dll    Sat Apr 11 02:25:29 2009 (49E037D9)
8f000000 8f02a000   ks       ks.sys       Sat Apr 11 00:38:47 2009 (49E01ED7)
8a20b000 8a27c000   ksecdd   ksecdd.sys   Mon Jun 15 08:48:53 2009 (4A364335)
8f99f000 8f9af000   lltdio   lltdio.sys   Sat Jan 19 00:55:03 2008 (479190B7)
8f8ba000 8f8d5000   luafv    luafv.sys    Sat Jan 19 00:30:35 2008 (47918AFB)
8040b000 8047b000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Sat Apr 11 02:23:19 2009 (49E03757)
8f58c000 8f599000   modem    modem.sys    Sat Jan 19 00:57:16 2008 (4791913C)
8ef1d000 8ef28000   mouclass mouclass.sys Sat Jan 19 00:49:14 2008 (47918F5A)
8077f000 8078f000   mountmgr mountmgr.sys Sat Jan 19 00:49:13 2008 (47918F59)
ab4ae000 ab4c3000   mpsdrv   mpsdrv.sys   Sat Jan 19 00:54:45 2008 (479190A5)
ab4c3000 ab4e4000   mrxdav   mrxdav.sys   Sat Apr 11 00:14:39 2009 (49E0192F)
ab4e4000 ab503000   mrxsmb   mrxsmb.sys   Tue Feb 23 06:10:12 2010 (4B83B794)
ab503000 ab53c000   mrxsmb10 mrxsmb10.sys Tue Feb 23 06:10:17 2010 (4B83B799)
ab53c000 ab554000   mrxsmb20 mrxsmb20.sys Tue Feb 23 06:10:12 2010 (4B83B794)
807bd000 807c7000   msahci   msahci.sys   Sat Apr 11 00:39:11 2009 (49E01EEF)
8f5ed000 8f5f8000   Msfs     Msfs.SYS     Sat Jan 19 00:28:08 2008 (47918A68)
806db000 806e3000   msisadrv msisadrv.sys Sat Jan 19 00:32:51 2008 (47918B83)
8ef51000 8ef80000   msiscsi  msiscsi.sys  Sat Apr 11 00:40:07 2009 (49E01F27)
8a387000 8a3b2000   msrpc    msrpc.sys    Sat Apr 11 00:37:32 2009 (49E01E8C)
8f02a000 8f034000   mssmbios mssmbios.sys Sat Jan 19 00:32:55 2008 (47918B87)
8a75f000 8a76e000   mup      mup.sys      Sat Apr 11 00:14:12 2009 (49E01914)
8a27c000 8a387000   ndis     ndis.sys     Sat Apr 11 00:45:52 2009 (49E02080)
8efe3000 8efee000   ndistapi ndistapi.sys Sat Jan 19 00:56:24 2008 (47919108)
8f9d9000 8f9e3000   ndisuio  ndisuio.sys  Sat Jan 19 00:55:40 2008 (479190DC)
8a5ae000 8a5d1000   ndiswan  ndiswan.sys  Sat Apr 11 00:46:31 2009 (49E020A7)
8f076000 8f087000   NDProxy  NDProxy.SYS  Sat Jan 19 00:56:28 2008 (4791910C)
8f162000 8f170000   netbios  netbios.sys  Sat Jan 19 00:55:45 2008 (479190E1)
8f11a000 8f14c000   netbt    netbt.sys    Sat Apr 11 00:45:35 2009 (49E0206F)
8a3b2000 8a3ed000   NETIO    NETIO.SYS    Sat Apr 11 00:46:21 2009 (49E0209D)
8ee08000 8ee6f000   netr28   netr28.sys   Tue Jul 01 01:16:37 2008 (4869BDB5)
8f087000 8f095000   Npfs     Npfs.SYS     Sat Apr 11 00:14:01 2009 (49E01909)
8f1bf000 8f1c9000   nsiproxy nsiproxy.sys Sat Jan 19 00:55:50 2008 (479190E6)
82644000 829fd000   nt       ntkrpamp.exe Tue Jun 08 10:36:44 2010 (4C0E557C)
8a60e000 8a71e000   Ntfs     Ntfs.sys     Sat Apr 11 00:14:34 2009 (49E0192A)
8ef40000 8ef48000   NTIDrvr  NTIDrvr.sys  Wed Jan 30 20:30:42 2008 (47A124C2)
8f5a2000 8f5a9000   Null     Null.SYS     Sat Jan 19 00:49:12 2008 (47918F58)
8f9af000 8f9d9000   nwifi    nwifi.sys    Sat Apr 11 00:43:27 2009 (49E01FEF)
8f14c000 8f162000   pacer    pacer.sys    Sat Apr 11 00:45:51 2009 (49E0207F)
8070a000 80719000   partmgr  partmgr.sys  Sat Apr 11 00:39:19 2009 (49E01EF7)
806e3000 8070a000   pci      pci.sys      Sat Apr 11 00:19:16 2009 (49E01A44)
807c7000 807d5000   PCIIDEX  PCIIDEX.SYS  Sat Apr 11 00:39:09 2009 (49E01EED)
b0a0c000 b0aea000   peauth   peauth.sys   Mon Oct 23 04:55:32 2006 (453C8384)
8f412000 8f43f000   portcls  portcls.sys  Sat Apr 11 00:42:48 2009 (49E01FC8)
807e5000 807ee000   psdfilter psdfilter.sys Mon Feb 18 08:49:54 2008 (47B98D02)
b0aea000 b0af3000   PSDNServ PSDNServ.sys Mon Feb 18 08:50:35 2008 (47B98D2B)
b0af3000 b0b05000   PSDVdisk PSDVdisk.sys Mon Feb 18 08:50:56 2008 (47B98D40)
8047b000 8048c000   PSHED    PSHED.dll    Sat Apr 11 02:25:32 2009 (49E037DC)
8f095000 8f09e000   rasacd   rasacd.sys   Sat Jan 19 00:56:31 2008 (4791910F)
8efcc000 8efe3000   rasl2tp  rasl2tp.sys  Sat Jan 19 00:56:33 2008 (47919111)
8efee000 8effd000   raspppoe raspppoe.sys Sat Apr 11 00:46:30 2009 (49E020A6)
8ede7000 8edfb000   raspptp  raspptp.sys  Sat Jan 19 00:56:34 2008 (47919112)
8a5d1000 8a5e6000   rassstp  rassstp.sys  Sat Apr 11 00:46:40 2009 (49E020B0)
8f183000 8f1bf000   rdbss    rdbss.sys    Sat Apr 11 00:14:26 2009 (49E01922)
8f5dd000 8f5e5000   RDPCDD   RDPCDD.sys   Sat Jan 19 01:01:08 2008 (47919224)
8f5e5000 8f5ed000   rdpencdd rdpencdd.sys Sat Jan 19 01:01:09 2008 (47919225)
8f9e3000 8f9f6000   rspndr   rspndr.sys   Sat Jan 19 00:55:03 2008 (479190B7)
8f206000 8f411140   RTKVHDA  RTKVHDA.sys  Fri Jun 20 04:56:49 2008 (485B70D1)
8ee6f000 8ee91000   Rtlh86   Rtlh86.sys   Tue Jun 10 06:54:34 2008 (484E5D6A)
8eea8000 8eece000   SCSIPORT SCSIPORT.SYS Sat Jan 19 00:49:44 2008 (47918F78)
b0b05000 b0b0f000   secdrv   secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528)
8f0be000 8f0d2000   smb      smb.sys      Sat Apr 11 00:45:22 2009 (49E02062)
8a757000 8a75f000   spldr    spldr.sys    Thu Jun 21 20:29:17 2007 (467B17DD)
8f8ef000 8f99f000   spsys    spsys.sys    Tue Mar 10 13:10:28 2009 (49B69F04)
ab57b000 ab5c9000   srv      srv.sys      Fri Jun 18 11:04:55 2010 (4C1B8B17)
ab554000 ab57b000   srv2     srv2.sys     Fri Jun 18 11:04:43 2010 (4C1B8B0B)
ab478000 ab495000   srvnet   srvnet.sys   Fri Dec 11 06:43:10 2009 (4B22304E)
8ef80000 8efc1000   storport storport.sys Sat Apr 11 00:39:19 2009 (49E01EF7)
8effd000 8effe380   swenum   swenum.sys   Sat Jan 19 00:49:20 2008 (47918F60)
8a40d000 8a4f7000   tcpip    tcpip.sys    Wed Jun 16 09:45:41 2010 (4C18D585)
b0b0f000 b0b1b000   tcpipreg tcpipreg.sys Tue Dec 08 12:26:18 2009 (4B1E8C3A)
8efc1000 8efcc000   TDI      TDI.SYS      Sat Jan 19 00:57:10 2008 (47919136)
8f09e000 8f0b4000   tdx      tdx.sys      Sat Apr 11 00:45:56 2009 (49E02084)
8a5e6000 8a5f6000   termdd   termdd.sys   Sat Apr 11 00:51:14 2009 (49E021C2)
96860000 96869000   TSDDD    TSDDD.dll    unavailable (00000000)
8a600000 8a609000   tunmp    tunmp.sys    Sat Jan 19 00:55:40 2008 (479190DC)
8a7f2000 8a7fd000   tunnel   tunnel.sys   Thu Feb 18 06:28:13 2010 (4B7D244D)
8078f000 80797000   UBHelper UBHelper.sys Wed Jan 30 20:30:26 2008 (47A124B2)
8f034000 8f041000   umbus    umbus.sys    Sat Jan 19 00:53:40 2008 (47919064)
8f832000 8f849000   usbccgp  usbccgp.sys  Sat Jan 19 00:53:29 2008 (47919059)
8f58a000 8f58b700   USBD     USBD.SYS     Sat Jan 19 00:53:17 2008 (4791904D)
8edd8000 8ede7000   usbehci  usbehci.sys  Sat Apr 11 00:42:52 2009 (49E01FCC)
8f041000 8f076000   usbhub   usbhub.sys   Sat Apr 11 00:43:14 2009 (49E01FE2)
8ed9a000 8edd8000   USBPORT  USBPORT.SYS  Sat Apr 11 00:42:55 2009 (49E01FCF)
8ed8f000 8ed9a000   usbuhci  usbuhci.sys  Sat Jan 19 00:53:20 2008 (47919050)
8f849000 8f869b80   usbvideo usbvideo.sys Sat Jan 19 00:53:38 2008 (47919062)
8f5b0000 8f5bc000   vga      vga.sys      Sat Jan 19 00:52:06 2008 (47919006)
8f5bc000 8f5dd000   VIDEOPRT VIDEOPRT.SYS Sat Jan 19 00:52:10 2008 (4791900A)
80726000 80735000   volmgr   volmgr.sys   Sat Jan 19 00:49:51 2008 (47918F7F)
80735000 8077f000   volmgrx  volmgrx.sys  Sat Apr 11 00:39:25 2009 (49E01EFD)
8a71e000 8a757000   volsnap  volsnap.sys  Sat Apr 11 00:39:37 2009 (49E01F09)
8f170000 8f183000   wanarp   wanarp.sys   Sat Jan 19 00:56:31 2008 (4791910F)
8ed83000 8ed8f000   watchdog watchdog.sys Sat Apr 11 00:22:43 2009 (49E01B13)
80603000 8067f000   Wdf01000 Wdf01000.sys Sat Jan 19 00:52:21 2008 (47919015)
8067f000 8068c000   WDFLDR   WDFLDR.SYS   Sat Jan 19 00:52:19 2008 (47919013)
96640000 96843000   win32k   win32k.sys   unavailable (00000000)
8ef48000 8ef51000   wmiacpi  wmiacpi.sys  Sat Jan 19 00:32:47 2008 (47918B7F)
806d2000 806db000   WMILIB   WMILIB.SYS   Sat Jan 19 00:53:08 2008 (47919044)

The reports that you have submitted reveal clues to the cause of your problem. They do not give a definitive answer. The more reports that we receive the more clues are made available improving our chances of finding a solution to your problem. You may have to experience several more BSODs until the final answer is discovered.

Update old drivers.

Code:

  peauth.sys   Mon Oct 23 04:55:32 2006 
 spldr.sys    Thu Jun 21 20:29:17 2007 
 NETw3v32.sys Wed Jul 25 13:27:27 2007

This is the third report that I have read (out of 3) that the cause is most likely drivers or memory.
Please update the old drivers and then take the memory test. If you fail the memory test do not take the driver verifier. Just correct the memory problems and wait to see if you continue to get BSODs.

If overclocking restore normal settings

SFC /scannow
System Files - SFC Command

Download memtest86 and test RAM
www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Run for 8 passes
If passes try a good stick in each slot for 3 passes
If fails do the same for 8 passes.

Scan with your Anti Virus

Update outdated listed drivers. If I have inadvertently listed any Microsoft Drivers, they can be ignored. If the list is extensive I have included the driver verifier test so that you may determine which drivers are in need of immediate attention.

How to Find Drivers
search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone - will help you search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- The most common drivers are listed on this page: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
and here
http://www.edbott.com/weblog/the-vista-master-driver-list/
To remove any left over driver remnants, especially from graphics cards, use driver sweeper
www.guru3d.com/category/driversweeper/
You can also locate information about your driver using this information
http://www.sevenforums.com/tutorials/96442-device-manager-finding-unknown-devices.html

Driver Verifier Inst
Since the driver that crashed you has not been listed you should run driver verifier
Please run Verifier with these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Enable the driver verifier
www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html

djhawk · Dec 26, 2010

Thank you very much for your assistance Richard. The first two driver's listed appear to be microsoft system drivers so I have not done anything with them. Searching on the third identifies it as the intel wireless network driver, and I have now updated that from the intel downloads page.

I then ran memtests on my single stick of RAM (2GB) in each of the two available slots. Both tests resulted in no errors after 8 passes.

Next I ran the SFC /scannow command that you listed. The resulting output was:

Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log

I have zipped up that log file and attached it to this post.

I haven't yet run a full scan with my antivirus (avast free home edition) or run the driver verifier. Those two things will be my next steps and I will post again after that.

Thanks,
-David

richc46 · Dec 26, 2010

When SFC finds errors run it 3 times. Very often it cannot fix all errors at once. Then post back
I quickly checked the log and some repairs have been made.
Follow all my instructions the best you can. Then if you get BSODs again, give me the new report and carefully detail what you have NOT done.

Good luck

djhawk · Dec 28, 2010

After running the sfc /scannow command multiple times the only relevant entries in the log seem to be:

2010-12-28 07:56:02, Info CSI 0000053b [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2010-12-28 07:56:02, Info CSI 0000053d [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2010-12-28 07:56:02, Info CSI 0000053e [SR] This component was referenced by [l:158{79}]"Package_16_for_KB948465~31bf3856ad364e35~x86~~6.0.1.18005.948465-49_neutral_GDR"

According to this kb article it sounds like those are erroneous errors and can be ignored.

I'll continue to the driver verifier next as I have time.

djhawk · Jan 1, 2011

We had to run with the verifier all day before getting a BSoD. Before that there were a few system lockups though. Do you think the lock ups and the BSoDs are being caused by the same problem?

I've used the BSOD file collection program again after disabling the verifier, and attached everything to this post.

richc46 · Jan 1, 2011

You did very good my friend. The BSOD was caused by the verifier and the driver was from avast
Make a system restore point
Use the uninstall tool
avast! Uninstall Utility
to uninstall Avast.
In its place download and use malwarebytes and Microsoft Security Essentials.
http://www.microsoft.com/security_essentials/
Turn off verifier
If you continue to get BSOD, enable the verifier and when it BSODs again,give me both reports

djhawk · Jan 1, 2011

Thank you, I am doing that now. I'm very surprised since I've been running avast on several machines for a while without any issues.

Do you believe that the avast driver was also causing the complete system lockups? (these have been much more frequent than the BSoDs).

richc46 · Jan 1, 2011

That is very possible. Everyone on the BSOD squad knows that almost every anti virus other than MSE can cause a lot of problems; freezing, crashes, slow etc. Lets see how it goes with MSE and if you get the freezing just come back to and we will fix that too.

djhawk · Jan 1, 2011

Many thanks and a Happy New Year!

I will absolutely return if any problems continue.

djhawk · Jan 3, 2011

Well sad news. The system lock ups have continued. As I described earlier they do not give a BSoD, simply a frozen unresponsive screen that displays whatever was last being done. It seems like it might happen more often when the laptop is moved or comes out of sleep mode, but it happens at other times too. I wondered if it could be a hard-drive issue and I used a HD scanning utility on the Hiren boot CD, but it found no errors. And of course I've already gone through all the troubleshooting earlier in this thread.

What do you think I should try next?

richc46 · Jan 3, 2011

From one of my old posts.
Go to search type device manager and look for any yellow warning markers
Download and run malwarebytes, a full scan after you update
Run antivirus scan
Check memory with memtest86
Make sure that you are not over heating.
Try in safe mode; report back if it works properly.
Try a clean boot
Make sure PSU is working properly
If overclocking, restore to original
Test hard drive at company website.

Check back and I will get you some links that you can use for the above
http://www.geekstogo.com/forum/topic...ing-memtest86/
How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7
Malwarebytes
SpeedFan - Access temperature sensor in your computer

Me Bad!
Almost forgot. Type event viewer, in search (by start button) and look for errors that may show the cause of the problem.
Go into event viewer and look for critical errors relating to the problem

You want to look for critical errors (they have red in the left column ).
When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.

This seems like a lot, but go slow, ask questiions and you will be up and running.

djhawk · Jan 3, 2011

Okay here's what I have so far or had already done.

No warnings in device manager.
Already updated and did a full scan both with malwarebytes and MSE.
Already checked memory with 8 passes on memtest86.
Already tried a clean install from factory OS.
Not overclocking.
Already checked the event viewer, but the lock-ups don't leave anything there.

So that leaves me with:
Make sure that you are not over heating. (I will try your SpeedFan link)
Try in safe mode; report back if it works properly. (I can try using it for a while in safe mode with networking to just browse online since that's what it's normally used for)
Make sure PSU is working properly (How do I do this? Just check the voltage with my multimeter where it plugs into the laptop?)
Test hard drive at company website. (It's a WD drive so do I want this Data Lifeguard Diagnostics download?) http://support.wdc.com/product/download.asp?groupid=702&sid=3〈=en
Edit: Forgot a Clean Boot. I will try your link for that too.

Thanks
-David

djhawk · Jan 8, 2011

Okay, my wife has been using the laptop all week mostly in safe mode. We haven't had it lock up at all while in safe mode, but a few times when it was out of safe mode we did have lockups. What's the next step? Follow the clean boot guide that you posted?

(I'm sure from speedfan that it isn't overheating, and the WD hard drive test came back fine)

richc46 · Jan 8, 2011

Yes, lets hope it work with clean boot, then we can solve easily.
If it does not work, it probably a corrupted driver.

djhawk · Jan 31, 2011

Well I got back to looking at our laptop this weekend. I did a clean boot with no non-microsoft apps or services running at startup. After using it for a while the laptop still had a freeze up. At this point I got fed up and just formatted the system partition and installed windows 7 professional over it. Just now, with only a few basic apps and not even all drivers installed, it froze in exactly the same fashion on a fresh install of 7.

So far our biggest clues seem to be that it would not freeze while in safe mode, the freezes seem to occur more often when the laptop is moved, and the information that I just mentioned about a freeze on a clean boot and on windows 7 as well.

richc46 · Jan 31, 2011

If it does not lock up in safe mode, it is not harware but must be a software problem.
It locks up in clean boot. I would guess it is a driver. Try this driver verifier test and report back

Driver Verifier Inst
Since the driver that crashed you has not been listed you should run driver verifier
Please run Verifier with these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Enable the driver verifier
www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html

Read the warnings that are given regarding this test and take note, if a bad driver is found you will BSOD. Continue the test for 24 hours.

djhawk · Feb 1, 2011

Okay, we got another blue screen today while running the verifier. I've attached the .dmp from it.

richc46 · Feb 1, 2011

Use the Verifier for 24 hours. This dump did not indicate a driver, but a code 124, which is hardware. I would like confirmation before we start with the hardware tests.

ilikefree · Feb 1, 2011

The lockup when you moved the computer is a possible loose connection or something like that, but sounds like a hardware issue.
I would follow Richc46 process of elimination first as he has a good reputation with these issues.

Intermittent System Lockups/BSoD

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

Attachments

My Computer

My Computer

My Computer