SFC found unrepairable files

2921 Views 18 Replies 2 Participants Last post by mgorman87, Apr 7, 2011

Stu_Munch

Discussion Starter · Mar 30, 2011

So, this is in the BSOD thread after seeing jcgriff tell someone else to move their questions about the CBS.log file here.

While trying to figure out issues with my DVD-ROM drive no longer existing as far as Windows is concerned (see thread here if you think you can help with that... please note the original poster's description as well as my description of the drive "working" during the BOOT process before Windows starts up), I ran across a suggestion of running SVC.exe and then looking at the log file created. Well, I can't read it, and there are a lot of lines that say "repair" or "repairing" but don't give me a usable file name to look into (at least that I can tell).

Please find, then, the jcgriff zip file with memory dumps, the CBS.log file, the autoruns.exe output file, and the perfmon.html file. Think that's about it. My question: what files are bad/needing repair, and how do I fix it? Or is it really necessary in my situation.

Also note: I haven't run the driver verifier built-in to Windows since this thread, simply because I've not added anything new and haven't had any issues lately (until a random BSOD the other day that is :4-dontkno).

Status: Not open for further replies.

1 - 19 of 19 Posts

mgorman87

· #2 · Mar 31, 2011 (Edited)

You may try a repair install. Insert your Vista DVD while in Windows and when the setup start choose to upgrade. This will essentially restore your computer to stock without losing any data.

After you run the repair install you may do another SFC /scannow through an elevated command prompt and see if the errors still exist.

After you do the above please enable driver verifier. It will help pin point a problem driver (if you have any)
http://www.techsupportforum.com/for...-windows-7-and-vista-bsod-related-473665.html

Code:

nvlddmkm.sys Wed Jun 24 09:12:07 2009 (4A422627)

Please update your video card drivers. They are very out of date.

A lot of your nVidia chipset drivers are out of date. I'm not sure what you have so go here and let it scan your computer and install any updates it finds.

Please run memtest for 7-8 passes.

Run all three Prime95 tests for a couple hours each. Make sure to watch your temps for the first 15-20 minutes.

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Mike\Downloads\Windows7_Vista_jcgriff2 (4)\Windows7_Vista_jcgriff2\Mini032911-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.18327.x86fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0x83a46000 PsLoadedModuleList = 0x83b5dc70
Debug session time: Tue Mar 29 01:56:33.069 2011 (UTC - 4:00)
System Uptime: 0 days 3:29:59.660
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {68938e3, 1b, 1, 83aedb43}

Probably caused by : ntkrpamp.exe ( nt!KeWaitForMultipleObjects+396 )

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: 068938e3, memory referenced
Arg2: 0000001b, 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: 83aedb43, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 83b7d868
Unable to read MiSystemVaType memory at 83b5d420
 068938e3 

CURRENT_IRQL:  1b

FAULTING_IP: 
nt!KeWaitForMultipleObjects+396
83aedb43 8902            mov     dword ptr [edx],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  lsass.exe

TRAP_FRAME:  91b168b4 -- (.trap 0xffffffff91b168b4)
ErrCode = 00000002
eax=88d45188 ebx=890c3a70 ecx=8938e3c9 edx=068938e3 esi=83b3e920 edi=890c39e8
eip=83aedb43 esp=91b16928 ebp=91b16970 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
nt!KeWaitForMultipleObjects+0x396:
83aedb43 8902            mov     dword ptr [edx],eax  ds:0023:068938e3=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 83aedb43 to 83a93fd9

STACK_TEXT:  
91b168b4 83aedb43 badb0d00 068938e3 00000000 nt!KiTrap0E+0x2e1
91b16970 83c79c83 0000001e 91b16aa8 00000001 nt!KeWaitForMultipleObjects+0x396
91b16bfc 83c799f2 0000001e 00000001 00000001 nt!ObpWaitForMultipleObjects+0x256
91b16d48 83a90c7a 0000001e 003eaf50 00000001 nt!NtWaitForMultipleObjects+0xcc
91b16d48 77ce5ca4 0000001e 003eaf50 00000001 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
00f7f818 00000000 00000000 00000000 00000000 0x77ce5ca4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KeWaitForMultipleObjects+396
83aedb43 8902            mov     dword ptr [edx],eax

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KeWaitForMultipleObjects+396

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4cb710d6

FAILURE_BUCKET_ID:  0xA_nt!KeWaitForMultipleObjects+396

BUCKET_ID:  0xA_nt!KeWaitForMultipleObjects+396

Followup: MachineOwner
---------

0: kd> lmntsm
start    end        module name
8f6a1000 8f6ae080   1394BUS  1394BUS.SYS  Sat Jan 19 00:53:27 2008 (47919057)
8060a000 80650000   acpi     acpi.sys     Sat Apr 11 00:19:03 2009 (49E01A37)
911ab000 911f3000   afd      afd.sys      Sat Apr 11 00:47:01 2009 (49E020C5)
8b91b000 8b92b000   amdk8    amdk8.sys    Sat Jan 19 00:27:20 2008 (47918A38)
9153e000 91540b00   aswFsBlk aswFsBlk.SYS Wed Feb 23 09:54:54 2011 (4D651FBE)
91506000 9153e000   aswMonFlt aswMonFlt.sys Wed Feb 23 09:55:01 2011 (4D651FC5)
911f3000 911f7200   aswRdr   aswRdr.SYS   Wed Feb 23 09:55:09 2011 (4D651FCD)
910a3000 91101000   aswSnx   aswSnx.SYS   Wed Feb 23 09:56:53 2011 (4D652035)
9146a000 914b1880   aswSP    aswSP.SYS    Wed Feb 23 09:56:43 2011 (4D65202B)
9118d000 91196f00   aswTdi   aswTdi.SYS   Wed Feb 23 09:55:48 2011 (4D651FF4)
80722000 8072a000   atapi    atapi.sys    Sat Apr 11 00:39:09 2009 (49E01EED)
8072a000 80748000   ataport  ataport.SYS  Sat Apr 11 00:39:10 2009 (49E01EEE)
8fc03000 8fd8b2e0   athw     athw.sys     Fri Jun 04 23:29:02 2010 (4C09C47E)
81890000 818dd000   ATMFD    ATMFD.DLL    Sat Jan 08 01:28:49 2011 (4D280421)
8069a000 806a4000   BATTC    BATTC.SYS    Sat Jan 19 00:32:45 2008 (47918B7D)
91111000 91118000   Beep     Beep.SYS     Sat Jan 19 00:49:10 2008 (47918F56)
80426000 8042e000   BOOTVID  BOOTVID.dll  Sat Jan 19 02:27:15 2008 (4791A653)
9e996000 9e9af000   bowser   bowser.sys   Sat Jan 19 00:28:26 2008 (47918A7A)
90cfd000 90d07000   BthEnum  BthEnum.sys  Sat Apr 11 00:43:09 2009 (49E01FDD)
90d21000 90d30000   bthmodem bthmodem.sys Sat Apr 11 00:43:10 2009 (49E01FDE)
90d07000 90d21000   bthpan   bthpan.sys   Sat Jan 19 00:53:44 2008 (47919068)
90c0b000 90c8b000   bthport  bthport.sys  Sat Apr 11 00:43:09 2009 (49E01FDD)
90be5000 90bf2000   BTHUSB   BTHUSB.sys   Sat Apr 11 00:43:08 2009 (49E01FDC)
91008000 91088000   btwaudio btwaudio.sys Tue Sep 04 15:38:00 2007 (46DDB418)
90d30000 90d97000   btwavdt  btwavdt.sys  Thu Jul 12 19:04:57 2007 (4696B399)
91088000 9108a500   btwrchid btwrchid.sys Thu Jul 12 19:06:31 2007 (4696B3F7)
81880000 8188e000   cdd      cdd.dll      unavailable (00000000)
8f7c7000 8f7fa000   CHDRT32  CHDRT32.sys  Tue Mar 04 13:31:57 2008 (47CD959D)
8046f000 8054f000   CI       CI.dll       Sat Apr 11 02:25:22 2009 (49E037D2)
8bbb2000 8bbd3000   CLASSPNP CLASSPNP.SYS Sat Apr 11 00:39:05 2009 (49E01EE9)
8042e000 8046f000   CLFS     CLFS.SYS     Sat Apr 11 00:13:51 2009 (49E018FF)
8bbfc000 8bbff780   CmBatt   CmBatt.sys   Sat Jan 19 00:32:47 2008 (47918B7F)
80697000 80699900   compbatt compbatt.sys Sat Jan 19 00:32:47 2008 (47918B7F)
914b2000 914bf000   crashdmp crashdmp.sys Sat Apr 11 00:39:12 2009 (49E01EF0)
8bbd3000 8bbdc000   crcdisk  crcdisk.sys  Sat Jan 19 00:50:29 2008 (47918FA5)
91453000 9146a000   dfsc     dfsc.sys     Sat Apr 11 00:14:12 2009 (49E01914)
8bba1000 8bbb2000   disk     disk.sys     Sat Apr 11 00:39:14 2009 (49E01EF2)
8b9d4000 8b9f9000   drmk     drmk.sys     Sat Jan 19 01:53:02 2008 (47919E4E)
914ca000 914d2000   dump_atapi dump_atapi.sys Sat Apr 11 00:39:09 2009 (49E01EED)
914bf000 914ca000   dump_dumpata dump_dumpata.sys Sat Apr 11 00:39:09 2009 (49E01EED)
914d2000 914dc000   Dxapi    Dxapi.sys    Sat Jan 19 00:36:12 2008 (47918C4C)
90534000 905d4000   dxgkrnl  dxgkrnl.sys  Thu Jan 20 08:50:57 2011 (4D383DC1)
8bb7a000 8bba1000   ecache   ecache.sys   Sat Apr 11 00:40:12 2009 (49E01F2C)
a0bba000 a0be2000   fastfat  fastfat.SYS  Sat Apr 11 00:13:52 2009 (49E01900)
8077a000 8078a000   fileinfo fileinfo.sys Sat Jan 19 00:34:27 2008 (47918BE3)
80748000 8077a000   fltmgr   fltmgr.sys   Sat Apr 11 00:13:59 2009 (49E01907)
91101000 9110a000   Fs_Rec   Fs_Rec.SYS   Sat Jan 19 00:27:57 2008 (47918A5D)
8b8f7000 8b912000   fwpkclnt fwpkclnt.sys Sat Apr 11 00:45:42 2009 (49E02076)
83a13000 83a46000   hal      halmacpi.dll Sat Apr 11 00:13:13 2009 (49E018D9)
8f604000 8f691000   HDAudBus HDAudBus.sys Sat Apr 11 00:42:41 2009 (49E01FC1)
8b92d000 8b93d000   HIDCLASS HIDCLASS.SYS Sat Apr 11 00:42:47 2009 (49E01FC7)
8b93d000 8b943380   HIDPARSE HIDPARSE.SYS Sat Jan 19 00:53:16 2008 (4791904C)
90bdc000 90be5000   hidusb   hidusb.sys   Sat Apr 11 00:42:48 2009 (49E01FC8)
905f3000 905f7180   HpqKbFiltr HpqKbFiltr.sys Mon Jun 18 18:12:03 2007 (46770333)
8b92b000 8b92cc00   HpqRemHid HpqRemHid.sys Wed Jul 11 11:30:21 2007 (4694F78D)
9e90c000 9e979000   HTTP     HTTP.sys     Sat Feb 20 15:53:31 2010 (4B804BCB)
905e0000 905f3000   i8042prt i8042prt.sys Sat Jan 19 00:49:17 2008 (47918F5D)
a0b8c000 a0bb2000   ipnat    ipnat.sys    Sat Jan 19 00:56:28 2008 (4791910C)
8fd8c000 8fd97000   kbdclass kbdclass.sys Sat Jan 19 00:49:14 2008 (47918F5A)
8f778000 8f781000   kbdhid   kbdhid.sys   Sat Apr 11 00:38:40 2009 (49E01ED0)
8040e000 80415000   kdcom    kdcom.dll    Sat Apr 11 02:25:29 2009 (49E037D9)
8f737000 8f761000   ks       ks.sys       Sat Apr 11 00:38:47 2009 (49E01ED7)
8b603000 8b674000   ksecdd   ksecdd.sys   Mon Jun 15 08:48:53 2009 (4A364335)
8078a000 80798100   Lbd      Lbd.sys      Thu Feb 03 09:23:42 2011 (4D4ABA6E)
9e8b5000 9e8c5000   lltdio   lltdio.sys   Sat Jan 19 00:55:03 2008 (479190B7)
914eb000 91506000   luafv    luafv.sys    Sat Jan 19 00:30:35 2008 (47918AFB)
a0a6b000 a0a6e180   mdmxsdk  mdmxsdk.sys  Mon Jun 19 17:26:59 2006 (449716A3)
90bb7000 90bc4000   modem    modem.sys    Sat Jan 19 00:57:16 2008 (4791913C)
914dc000 914eb000   monitor  monitor.sys  Sat Jan 19 00:52:19 2008 (47919013)
8fdd2000 8fddd000   mouclass mouclass.sys Sat Jan 19 00:49:14 2008 (47918F5A)
90ca2000 90caa000   mouhid   mouhid.sys   Sat Jan 19 00:49:16 2008 (47918F5C)
80712000 80722000   mountmgr mountmgr.sys Sat Jan 19 00:49:13 2008 (47918F59)
9e9af000 9e9c4000   mpsdrv   mpsdrv.sys   Sat Jan 19 00:54:45 2008 (479190A5)
9e9c4000 9e9e5000   mrxdav   mrxdav.sys   Sat Apr 11 00:14:39 2009 (49E0192F)
9155b000 9157a000   mrxsmb   mrxsmb.sys   Tue Feb 23 06:10:12 2010 (4B83B794)
9157a000 915b3000   mrxsmb10 mrxsmb10.sys Tue Feb 23 06:10:17 2010 (4B83B799)
9e9e5000 9e9fd000   mrxsmb20 mrxsmb20.sys Tue Feb 23 06:10:12 2010 (4B83B794)
91155000 91160000   Msfs     Msfs.SYS     Sat Jan 19 00:28:08 2008 (47918A68)
80659000 80661000   msisadrv msisadrv.sys Sat Jan 19 00:32:51 2008 (47918B83)
8fb01000 8fb30000   msiscsi  msiscsi.sys  Sat Apr 11 00:40:07 2009 (49E01F27)
8b77f000 8b7aa000   msrpc    msrpc.sys    Sat Apr 11 00:37:32 2009 (49E01E8C)
8f761000 8f76b000   mssmbios mssmbios.sys Sat Jan 19 00:32:55 2008 (47918B87)
8bb6b000 8bb7a000   mup      mup.sys      Sat Apr 11 00:14:12 2009 (49E01914)
8b674000 8b77f000   ndis     ndis.sys     Sat Apr 11 00:45:52 2009 (49E02080)
8fb71000 8fb7c000   ndistapi ndistapi.sys Sat Jan 19 00:56:24 2008 (47919108)
9e8ef000 9e8f9000   ndisuio  ndisuio.sys  Sat Jan 19 00:55:40 2008 (479190DC)
8fb7c000 8fb9f000   ndiswan  ndiswan.sys  Sat Apr 11 00:46:31 2009 (49E020A7)
8f7b6000 8f7c7000   NDProxy  NDProxy.SYS  Sat Jan 19 00:56:28 2008 (4791910C)
90dc9000 90dd7000   netbios  netbios.sys  Sat Jan 19 00:55:45 2008 (479190E1)
90d97000 90dc9000   netbt    netbt.sys    Sat Apr 11 00:45:35 2009 (49E0206F)
8b7aa000 8b7e5000   NETIO    NETIO.SYS    Sat Apr 11 00:46:21 2009 (49E0209D)
91160000 9116e000   Npfs     Npfs.SYS     Sat Apr 11 00:14:01 2009 (49E01909)
91449000 91453000   nsiproxy nsiproxy.sys Sat Jan 19 00:55:50 2008 (479190E6)
83a46000 83e00000   nt       ntkrpamp.exe Thu Oct 14 10:16:54 2010 (4CB710D6)
8ba0b000 8bb1b000   Ntfs     Ntfs.sys     Sat Apr 11 00:14:34 2009 (49E0192A)
9110a000 91111000   Null     Null.SYS     Sat Jan 19 00:49:12 2008 (47918F58)
8fe02000 905335c0   nvlddmkm nvlddmkm.sys Wed Jun 24 09:12:07 2009 (4A422627)
8fa01000 8fb00600   nvmfdx32 nvmfdx32.sys Fri Aug 01 14:37:49 2008 (489357FD)
8b94d000 8b94ff00   nvsmu    nvsmu.sys    Fri Feb 16 10:50:31 2007 (45D5D2C7)
9e8c5000 9e8ef000   nwifi    nwifi.sys    Sat Apr 11 00:43:27 2009 (49E01FEF)
8f691000 8f6a0300   ohci1394 ohci1394.sys Sat Apr 11 00:43:04 2009 (49E01FD8)
9108b000 910a1000   pacer    pacer.sys    Sat Apr 11 00:45:51 2009 (49E0207F)
80688000 80697000   partmgr  partmgr.sys  Sat Apr 11 00:39:19 2009 (49E01EF7)
a0bb2000 a0bb9d80   PCANDIS5 PCANDIS5.SYS Tue Sep 23 11:32:09 2003 (3F706779)
80661000 80688000   pci      pci.sys      Sat Apr 11 00:19:16 2009 (49E01A44)
806fd000 80704000   pciide   pciide.sys   Sat Apr 11 00:39:10 2009 (49E01EEE)
80704000 80712000   PCIIDEX  PCIIDEX.SYS  Sat Apr 11 00:39:09 2009 (49E01EED)
a0a6f000 a0b4d000   peauth   peauth.sys   Mon Oct 23 04:55:32 2006 (453C8384)
90caa000 90cb2800   point32  point32.sys  Tue Jun 29 04:54:24 2010 (4C29B4C0)
8b9a7000 8b9d4000   portcls  portcls.sys  Sat Apr 11 00:42:48 2009 (49E01FC8)
80415000 80426000   PSHED    PSHED.dll    Sat Apr 11 02:25:32 2009 (49E037DC)
9116e000 91177000   rasacd   rasacd.sys   Sat Jan 19 00:56:31 2008 (4791910F)
8fde8000 8fdff000   rasl2tp  rasl2tp.sys  Sat Jan 19 00:56:33 2008 (47919111)
8fb9f000 8fbae000   raspppoe raspppoe.sys Sat Apr 11 00:46:30 2009 (49E020A6)
8fbae000 8fbc2000   raspptp  raspptp.sys  Sat Jan 19 00:56:34 2008 (47919112)
8fbc2000 8fbd7000   rassstp  rassstp.sys  Sat Apr 11 00:46:40 2009 (49E020B0)
9140d000 91449000   rdbss    rdbss.sys    Sat Apr 11 00:14:26 2009 (49E01922)
91145000 9114d000   RDPCDD   RDPCDD.sys   Sat Jan 19 01:01:08 2008 (47919224)
9114d000 91155000   rdpencdd rdpencdd.sys Sat Jan 19 01:01:09 2008 (47919225)
90cd4000 90cfd000   rfcomm   rfcomm.sys   Sat Apr 11 00:43:12 2009 (49E01FE0)
8f6c0000 8f6d1000   rimmptsk rimmptsk.sys Thu Jun 25 03:58:09 2009 (4A432E11)
8f6d1000 8f6e5000   rimsptsk rimsptsk.sys Thu Jun 25 03:10:46 2009 (4A4322F6)
8f6af000 8f6c0000   risdptsk risdptsk.sys Wed Jul 09 00:27:28 2008 (48743E30)
8f6e5000 8f737000   rixdptsk rixdptsk.sys Thu Jun 25 03:25:57 2009 (4A432685)
9e8f9000 9e90c000   rspndr   rspndr.sys   Sat Jan 19 00:55:03 2008 (479190B7)
a0b4d000 a0b57000   secdrv   secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528)
8bb64000 8bb6b000   SmartDefragDriver SmartDefragDriver.sys Wed Feb 23 03:37:47 2011 (4D64C75B)
91197000 911ab000   smb      smb.sys      Sat Apr 11 00:45:22 2009 (49E02062)
8bb5c000 8bb64000   spldr    spldr.sys    Thu Jun 21 20:29:17 2007 (467B17DD)
9e805000 9e8b5000   spsys    spsys.sys    Tue Mar 10 13:10:28 2009 (49B69F04)
915b3000 915db000   srv2     srv2.sys     Mon Sep 06 09:45:21 2010 (4C84F071)
9e979000 9e996000   srvnet   srvnet.sys   Mon Sep 06 09:45:18 2010 (4C84F06E)
8fb30000 8fb71000   storport storport.sys Sat Apr 11 00:39:19 2009 (49E01EF7)
905fa000 905fb380   swenum   swenum.sys   Sat Jan 19 00:49:20 2008 (47918F60)
8fd97000 8fdd1680   SynTP    SynTP.sys    Thu May 27 17:40:25 2010 (4BFEE6C9)
8fbd7000 8fbe2000   tap0901  tap0901.sys  Fri May 07 11:26:23 2010 (4BE4311F)
8b80d000 8b8f7000   tcpip    tcpip.sys    Wed Jun 16 09:45:41 2010 (4C18D585)
a0b57000 a0b63000   tcpipreg tcpipreg.sys Tue Dec 08 12:26:18 2009 (4B1E8C3A)
8fddd000 8fde8000   TDI      TDI.SYS      Sat Jan 19 00:57:10 2008 (47919136)
91177000 9118d000   tdx      tdx.sys      Sat Apr 11 00:45:56 2009 (49E02084)
8fbe2000 8fbe8200   teamviewervpn teamviewervpn.sys Thu Nov 29 03:27:19 2007 (474E77E7)
8fbe9000 8fbf9000   termdd   termdd.sys   Sat Apr 11 00:51:14 2009 (49E021C2)
81860000 81869000   TSDDD    TSDDD.dll    Sat Jan 19 01:01:09 2008 (47919225)
8b912000 8b91b000   tunmp    tunmp.sys    Sat Jan 19 00:55:40 2008 (479190DC)
8ba00000 8ba0b000   tunnel   tunnel.sys   Thu Feb 18 06:28:13 2010 (4B7D244D)
8f76b000 8f778000   umbus    umbus.sys    Sat Jan 19 00:53:40 2008 (47919064)
90c8b000 90ca2000   usbccgp  usbccgp.sys  Sat Jan 19 00:53:29 2008 (47919059)
905f8000 905f9700   USBD     USBD.SYS     Sat Jan 19 00:53:17 2008 (4791904D)
8b998000 8b9a7000   usbehci  usbehci.sys  Sat Apr 11 00:42:52 2009 (49E01FCC)
8f781000 8f7b6000   usbhub   usbhub.sys   Sat Apr 11 00:43:14 2009 (49E01FE2)
8b950000 8b95a000   usbohci  usbohci.sys  Sat Apr 11 00:42:52 2009 (49E01FCC)
8b95a000 8b998000   USBPORT  USBPORT.SYS  Sat Apr 11 00:42:55 2009 (49E01FCF)
90bc4000 90bd9000   USBSTOR  USBSTOR.SYS  Sat Apr 11 00:42:55 2009 (49E01FCF)
90cb3000 90cd3b80   usbvideo usbvideo.sys Sat Jan 19 00:53:38 2008 (47919062)
91118000 91124000   vga      vga.sys      Sat Jan 19 00:52:06 2008 (47919006)
91124000 91145000   VIDEOPRT VIDEOPRT.SYS Sat Jan 19 00:52:10 2008 (4791900A)
806a4000 806b3000   volmgr   volmgr.sys   Sat Jan 19 00:49:51 2008 (47918F7F)
806b3000 806fd000   volmgrx  volmgrx.sys  Sat Apr 11 00:39:25 2009 (49E01EFD)
8bb23000 8bb5c000   volsnap  volsnap.sys  Sat Apr 11 00:39:37 2009 (49E01F09)
80799000 807d6000   VSTAZL3  VSTAZL3.SYS  Wed Oct 15 20:30:03 2008 (48F68B0B)
90b02000 90bb7000   VSTCNXT3 VSTCNXT3.SYS Wed Oct 15 20:29:13 2008 (48F68AD9)
90a00000 90b02000   VSTDPV3  VSTDPV3.SYS  Wed Oct 15 20:32:04 2008 (48F68B84)
90dd7000 90dea000   wanarp   wanarp.sys   Sat Jan 19 00:56:31 2008 (4791910F)
905d4000 905e0000   watchdog watchdog.sys Sat Apr 11 00:22:43 2009 (49E01B13)
8bb1b000 8bb23000   wd       wd.sys       Sat Jan 19 00:52:18 2008 (47919012)
90bd9000 90bdbd00   wdcsam   wdcsam.sys   Wed Apr 16 04:27:02 2008 (4805B856)
8054f000 805c0000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
805c0000 805ce000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
81640000 81843000   win32k   win32k.sys   Fri Dec 31 08:56:47 2010 (4D1DE11F)
8b944000 8b94d000   wmiacpi  wmiacpi.sys  Sat Jan 19 00:32:47 2008 (47918B7F)
80650000 80659000   WMILIB   WMILIB.SYS   Sat Jan 19 00:53:08 2008 (47919044)
91541000 9155b000   WudfPf   WudfPf.sys   Mon Jul 13 19:50:13 2009 (4A5BC835)
a0b63000 a0b83480   WUDFRd   WUDFRd.sys   Mon Jul 13 19:50:44 2009 (4A5BC854)
a0b84000 a0b8c000   xaudio   xaudio.sys   Thu Oct 18 18:36:53 2007 (4717E005)

Unloaded modules:
a0a05000 a0a53000   srv.sys 
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0004E000
a0a53000 a0a6b000   parport.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00018000
8bbdc000 8bbe9000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000D000
8bbe9000 8bbf4000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000B000
8bbf4000 8bbfc000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00008000
9108b000 910a3000   cdrom.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00018000

See less See more

Stu_Munch

Discussion Starter · #3 · Apr 4, 2011

OK, been sick for a couple days, but I'm back.

Um, here's the deal with HP's - no Windows DVD. I have a recovery partition on my computer from which I can do a complete factory reset, reinstall software/drivers, that kind of thing, but no Windows "Repair". Now, I DID make a Windows Vista Recovery Disc from an iso I found online... would THAT have some "repair" function?

As for the NVIDIA drivers, those ARE the latest. When I posted about a previous BSOD issue, I looked for the updated ones... 2009 was the last release for the GeForce 7150M / nForce 630M chipset. Apparently it's so unsupported that the auto-detect page you linked to couldn't find / recognize it.

I'll run the Memtest here in a bit... I have to do the USB Linux option since my DVD-ROM only works on POST, but not once Windows starts (see the link I posted previously for THAT whole issue).

Will also run the Prime95 tests... but which ones should I run? And what will that do? From what I can tell, it'll simply tell me if my processor is working right. Am I missing something else?

After I do those two, then I'll do the Driver Verifier.

Thanks.

See less See more

mgorman87

· #4 · Apr 4, 2011

Prime95 stress tests your CPU and it also tests your memory. Please run all three tests for a couple hours each.

All a repair install does is reinstall stock everything (system files, drivers, etc). So I'm not sure if any of the disks you have will suffice.

Stu_Munch

Discussion Starter · #5 · Apr 4, 2011

Well, the recovery partition does give me the option to recovery factory installed programs and factory installed drivers... or, again, a complete factory restore. So you're right, short of doing a factory restore, doubt I can do the repair option you suggested. Plus, I can't use that Recovery Disc because my DVD-ROM doesn't work... my BIOS isn't even recognizing it anymore. So yet another problem I'll have to address.

Now with the Prime95, you're saying I should run it as a stress test, NOT as the standard prime number finder thingie? It gave me the option on install, and chose to do just the standard running, NOT the stress test (since it was talking about using it for overclocking purposes). If I need to do the stress test (or, as the program calls it, the Torture Test) specifically, let me know. Just FYI, there's no "time" option for the Torture Test, just how many runs I want it to do (2 being the default). How many should I tell it to do to get it to run long enough?

The Memtest I'll have to run when I go to bed tonight, because to do it I have to boot into Linux from my Linux USB key.

See less See more

mgorman87

· #6 · Apr 4, 2011

Here is a good guide on running Prime95
CPU - Stress Test with Prime95 - Windows 7 Forums

Stu_Munch

Discussion Starter · #7 · Apr 5, 2011

Update:

- Ran Memtest overnight (about six to seven hours) with no errors detected.
- Started the first Prime95 test, left for a few minutes, and apparently overheated, because my computer had shut down by the time I got back. Haven't bothered running the other two, because I can't just sit here watching to see if it gets too hot... plus, I don't know what temp my comp shuts down at, and which temp it uses to decide WHEN to shut down: core, GPU, hard drive, or another one.
- Will run the Driver Verifier here in a few minutes.

Assuming the Driver Verifier doesn't find anything, what can I do about the errors found by svc.exe?

mgorman87

· #8 · Apr 5, 2011

Stu_Munch said:
Update:

- Ran Memtest overnight (about six to seven hours) with no errors detected.
- Started the first Prime95 test, left for a few minutes, and apparently overheated, because my computer had shut down by the time I got back. Haven't bothered running the other two, because I can't just sit here watching to see if it gets too hot... plus, I don't know what temp my comp shuts down at, and which temp it uses to decide WHEN to shut down: core, GPU, hard drive, or another one.
- Will run the Driver Verifier here in a few minutes.

Assuming the Driver Verifier doesn't find anything, what can I do about the errors found by svc.exe?

You can use a program like Speedfan to monitor your temps. If your CPU is overheating then that's something that needs to be addressed. Try taking a small fan and pointing it in the case and run the tests again. Make sure you run all 3 tests.

Stu_Munch

Discussion Starter · #9 · Apr 5, 2011

Yeah, I've got Speedfan. Unfortunately, my system doesn't allow it to control the fan speeds. And it DOES overheat, even with the internal fan blowing full-force AND a 7" laptop fan sitting underneath. Think I'll pull out the big room fan and have it blow on it tonight while it's doing everything.

And while overheating IS an issue, I can't see that affecting the files that are corrupted/unrepairable. What do I do about those?

mgorman87

· #10 · Apr 5, 2011

Type this command in an elevated command prompt
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >%userprofile%\Desktop\sfcdetails.txt

and then upload that file here. It willl tell us what files are corrupted.

Stu_Munch

Discussion Starter · #11 · Apr 5, 2011

Actually, if you look in the zip file I attached to my first post, the CBS.log file is in there. I can do another one, but then it would be different from what I had when I first ran it, and so don't know if it would reflect what was going on at the time.

mgorman87

· #12 · Apr 5, 2011

Stu_Munch said:
Actually, if you look in the zip file I attached to my first post, the CBS.log file is in there. I can do another one, but then it would be different from what I had when I first ran it, and so don't know if it would reflect what was going on at the time.

Run the system file check again and then do
"findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >%userprofile%\Desktop\sfcdetails.txt" in command prompt

Stu_Munch

Discussion Starter · #13 · Apr 6, 2011

Just ran it again, and this time I'm told that "Windows Resource Protection did not find any integrity violations."

Now, the first time I did it, I didn't do an "official" elevated prompt. *shrugs* I'm the only account on my computer and set as an administrator. Can't see how that would make a difference, but that's why I'm the guy with the questions, not the answers. ;-)

But I attached the txt file anyway.

Had issues with the electricity on and off today in my apartment, so will try the Driver Verifier later tonight.

Stu_Munch

Discussion Starter · #14 · Apr 6, 2011

Ran the Driver Verifier, and it didn't get 10 seconds in and it blue screened on me. But oddly, there's no file in the windows\minidump directory to attach. Is this normal? I had to restart in Safe Mode, run verifier /reset so I could start Windows normally (per the BSOD link above), and am now back in Windows, but again, no dump file. Did the reset do that? Anyway, I wisely wrote down as much of the info as possible:

It was a SPECIAL_POOL error. The file was smartdefragdriver.sys, STOP 0x000000C2 (0x00000090, 0x00000419, 0x00000000, 0x86369564).

That enough info? If not, is there somewhere else I might find the dump file? Or actually make sure one is made? Thanks.

mgorman87

· #15 · Apr 6, 2011

Stu_Munch said:
Ran the Driver Verifier, and it didn't get 10 seconds in and it blue screened on me. But oddly, there's no file in the windows\minidump directory to attach. Is this normal? I had to restart in Safe Mode, run verifier /reset so I could start Windows normally (per the BSOD link above), and am now back in Windows, but again, no dump file. Did the reset do that? Anyway, I wisely wrote down as much of the info as possible:

It was a SPECIAL_POOL error. The file was smartdefragdriver.sys, STOP 0x000000C2 (0x00000090, 0x00000419, 0x00000000, 0x86369564).

That enough info? If not, is there somewhere else I might find the dump file? Or actually make sure one is made? Thanks.

Yes it is enough. Please uninstall your smart defrag software and re-enable driver verifier.

The file you uploaded shows that you had no errors in your system file scan

Stu_Munch

Discussion Starter · #16 · Apr 7, 2011

Ok, removed Smart Defrag, restarted with Verifier running... everything seems to be going fine now... but I don't see any kind of status screen or anything. I did the verifier /query command and it scrolled a bunch of drivers and info, but that's about it. Nothing saying that it was still running or anything. Will it automatically stop and let me know it's stopped, or is it one of those programs that keeps running until something DOES BSOD?

mgorman87

· #17 · Apr 7, 2011

Stu_Munch said:
Ok, removed Smart Defrag, restarted with Verifier running... everything seems to be going fine now... but I don't see any kind of status screen or anything. I did the verifier /query command and it scrolled a bunch of drivers and info, but that's about it. Nothing saying that it was still running or anything. Will it automatically stop and let me know it's stopped, or is it one of those programs that keeps running until something DOES BSOD?

It runs until you disable it no matter how many BSOD's it causes. But let it run for 48hrs without any BSOD before disabling.

Stu_Munch

Discussion Starter · #18 · Apr 7, 2011

Can I run the Prime95 tests with the verifier running? Or would it be best to run them separately?

Alright, 48 hours it is then! Update then.

mgorman87

· #19 · Apr 7, 2011

Stu_Munch said:
Can I run the Prime95 tests with the verifier running? Or would it be best to run them separately?

Alright, 48 hours it is then! Update then.

Verifier puts a lot of strain on your drivers to cause them to crash. I don't see why you couldn't run Prime95 with it enabled. Let us know the results of the testing

1 - 19 of 19 Posts

Status: Not open for further replies.