Windows Updates causing endless reboot loop

gord · 03-20-2009, 01:37 PM

Dell Latitude D830 laptop, Vista OS

I had to format and reinstall Windows and used Windows Update to install fixes. When it needed to reboot, I would occasionally get caught in an endless reboot loop. The computer would POST and the progress bar on the Windows loading screen would get about halfway across then blue screen and reboot. I am able to use my Windows CD to do a system restore but that would undo some updates. I changed the setting so it wouldn't automatically reboot and got these errors:

STOP: 0x0000007B (0x80403bA0, 0xC0000034, 0x00000000, 0x00000000)

**TriggerFinger** · 03-20-2009, 02:16 PM

If I am not mistaken 7B points to an inaccessible boot device, may be a defective hard drive. Since you are using DELL, may be it has a recovery partition that you can use to fix/undo any changes. Can you into Safe Mode? Did you try Last Known Good Configuration?

gord · 03-20-2009, 02:57 PM

I keep thinking that its the hard drive, but running the sfc command or chkdsk don't come up with any sector errors. I'm down to three recommended updates on WU and installing any one of them causes the reboot loop. I have my Dell Vista DVD and I use that to repair and do a system restore. Just going into safe mode or LKGC without the Windows DVD does not work.

**TriggerFinger** · 03-20-2009, 03:06 PM

You can run SeaTools or Hitach DFT (see HDD Diags link on my sig.) to test the HDD for hardware errors. Both have a CD image that you can burn into a blank CD (see HOW TO BURN AN ISO... link on my sig.). Btw, this makes the CD bootable which is good as you can run it outside of Windows.

I think you are on the right path of uninstalling the recent updates especially if the problem began ONLY after they were installed.

gord · 03-20-2009, 05:37 PM

Diagnostics in physical tests came up clean except for a File Structure Test. It failed with critical errors:

One or more file names contained errors
One or more errors were found in the index
One or more errors were found in metadata file records
Other errors were found

Prior to installing Vista, I zero filled the drive, installed straight from the Dell Vista CD and went straight to updating.

**TriggerFinger** · 03-20-2009, 05:40 PM

What test did you use?

gord · 03-20-2009, 06:10 PM

The one that came up with errors was the File Structure Test on the SeaTools CD.

**TriggerFinger** · 03-20-2009, 06:24 PM

Did the SMART test pass?

As for the file errors, may be a CHKDSK /R can help.

Try Vista's Startup Repair (you will need Vista disc). See this:
http://www.vistax64.com/tutorials/19...y-options.html

**jcgriff2** · 03-20-2009, 07:07 PM

What was the reason for doing the low-level format prior to the Vista install?

gord · 03-20-2009, 07:26 PM

@jfgriff2: I wanted to make sure there weren't any fragments left over from a standard format. I wanted to rule that out.

@TriggerFinger: SMART says it's fine and I've run 'chkdsk /f' and 'sfc /scannow' several times and there are no errors.

I am able to boot into Windows and use it as normal (nothing has changed here). The only problem is when I try to download and install the last three remaining 'recommended' updates in Windows Update. They will install fine, but when I reboot, the progress bar gets halfway across and blue screens. I am able to use the Vista DVD to repair and do a restore, but the updates are obviously wiped out.

**TriggerFinger** · 03-20-2009, 08:13 PM

I asked for HDD diagnostics so we can just rule out the hardware side. What updates are you trying to install anyway?

gord · 03-20-2009, 08:39 PM

They are:
KB941649 - resolves compatibility and reliability issues (like hell!)
KB941651 - reliability update for WMP11
KB943899 - reliability update for Vista

All listed as "recommended"

**TriggerFinger** · 03-20-2009, 09:29 PM

Hmmm... interesting. Read on the articles linked below

http://support.microsoft.com/kb/943899
http://support.microsoft.com/kb/941651
http://support.microsoft.com/kb/941649

If you scroll down to almost the bottom of the page, it says about some issues of each. Two of the 3 above have problems like:

Quote:

Hard disk drives may not be recognized after update 943899 is applied. Certain SATA hard disk drives are not recognized after a computer resumes from sleep or hibernation when v1.0 of update 934899 has been applied. The drives are sent incorrect data, and the data changes several hard disk settings. One of these settings is “power up on standby mode." This behavior keeps the hard disk from spinning, and the system will not start. This hard disk problem was resolved by v2.0 of update 943899 which was published on February 11, 2008.

and

Quote:

This package has been updated to version 2. An issue was identified in which certain computers that have specific older SATA (Serial ATA) controllers that use the AHCI (Advanced Host Controller Interface) protocol and SATA-connected CD or DVD drives may not start after the installation of the original version of this package. Version 2 of this package has removed the fix that caused this problem. If you are using a computer that experienced this issue, you can restart the computer by using a bootable Windows Vista DVD and by selecting the Repair/System Recovery options. If your computer has already installed the original version of this update and has successfully restarted, you do not have to install version 2 of this update.

It seems these remain UNRESOLVED yet.

gord · 03-20-2009, 10:04 PM

I installed the WMP11 update since that seemed harmless.

While I was installing iTunes I got another blue screen:

Bad Pool Caller
0x000000C2 (0x00000007, 0x0000113D, 0x00000000, 0xB3810008)

**TriggerFinger** · 03-20-2009, 10:09 PM

May be there is a dump file. Attach them zipped. They might help identify the cause.

gord · 03-20-2009, 11:04 PM

The dmp file and xml files are zipped.

**jcgriff2** · 03-21-2009, 03:43 AM

Hi -

The sole dump attached to post was from BSOD #4 for March 20 23:59 (GMT-4). The bugcheck -

0xc2 (0x7, 0x113d, 0x0, 0xb3810008), probable cause listed as ntkrpamp.exe, the NT Kernel, timestamp Wed Sep 17 21:56:32 2008.

0xc2 = BAD_POOL_CALLER = current thread is making a bad pool request. The 1st parm 0x7 tells us that the thread attempted to free memory which had already been freed.

I am somewhat puzzled by what I see in the dump. We have an NT Kernel dated Sept 2008 and a DirectX Kernel dated July 2007. This indicates Windows Updates have come in - at least SOME. What I find to be the primary problem here is the lack of Vista SP1. I queried dozens of loaded drivers from the dump and all come up as pre-SP1, many with a timestamp of November 2, 2006 - the dawn of Vista.

I find the OS listed as Windows Vista Ultimate Professional x86. Is Vista Ultimate the original OS on this Dell OEM system? When was the system purchased?

0xc2 could also be caused by failing hardware - like RAM or HDD. I did read the prior posts and see that you did run hardware tests. I would expect app hangs, app crashes and even BSODs when trying to install 2009 software like iTunes written with Vista SP1 in mind onto a pre-SP1 system.

I am unsure based on the info that I have exactly why the NT & DX kernels were updated, but SP1 was passed over. I usually find anti-virus &/or especially 3rd party firewalls to be the primary culprits. Neither the NT or DX Kernel drivers are SP1 modules.

The installation of SP1 must be the #1 priority as I have found it pointless to try and diagnose crashes in pre-SP1 systems. I would suggest at this time to start over - re-install Vista then allow ALL Windows Updates and Dell driver updates to come in. Once the OS is in and fully updated, then begin 3rd party program installations like anti-virus, iTunes, etc... I would not initially install WMP 11 unless it comes in via Windows Updates. The same goes for IE 8, which is now a production version (no longer a beta 'test' version). I would like to see a BSOD-free period of at least 24 hours before manually installing WMP 11 or IE 8. But that is your choice, of course.

Regards. . .

jcgriff2

.

dbug log

Code:


Opened log file 'D:\!!_Kernel_Dumps\gord_Vista_03-21-09_jcgriff2__\$99-dbug.txt'

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\!!_Kernel_Dumps\gord_Vista_03-21-09_jcgriff2__\Mini032009-04.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 Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16754.x86fre.vista_gdr.080917-1612
Machine Name:
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Fri Mar 20 23:59:38.175 2009 (GMT-4)
System Uptime: 0 days 1:48:35.108
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 113d, 0, b3810008}

GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0
*** ERROR: Module load completed but symbols could not be loaded for spldr.sys
*** WARNING: Unable to verify timestamp for secdrv.SYS
*** ERROR: Module load completed but symbols could not be loaded for secdrv.SYS
*** WARNING: Unable to verify timestamp for b57nd60x.sys
*** ERROR: Module load completed but symbols could not be loaded for b57nd60x.sys
*** WARNING: Unable to verify timestamp for bcmwl6.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmwl6.sys
*** WARNING: Unable to verify timestamp for igdkmd32.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
*** WARNING: Unable to verify timestamp for VSTAZL3.SYS
*** ERROR: Module load completed but symbols could not be loaded for VSTAZL3.SYS
*** WARNING: Unable to verify timestamp for drmk.sys
*** ERROR: Module load completed but symbols could not be loaded for drmk.sys
*** WARNING: Unable to verify timestamp for VSTCNXT3.SYS
*** ERROR: Module load completed but symbols could not be loaded for VSTCNXT3.SYS
*** WARNING: Unable to verify timestamp for VSTDPV3.SYS
*** ERROR: Module load completed but symbols could not be loaded for VSTDPV3.SYS
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*** WARNING: Unable to verify timestamp for TSDDD.dll
*** ERROR: Module load completed but symbols could not be loaded for TSDDD.dll
*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for spsys.sys - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for peauth.sys - 
GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0
Probably caused by : ntkrpamp.exe ( nt!ExFreePoolWithTag+17f )

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

1: kd> !analyze -v;r;kv;lmtn
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 0000113d, (reserved)
Arg3: 00000000, Memory contents of the pool block
Arg4: b3810008, Address of the block of pool being deallocated

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

GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0
GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0

POOL_ADDRESS: GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0
 b3810008 

BUGCHECK_STR:  0xc2_7

CUSTOMER_CRASH_COUNT:  4

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 81ce7ce8 to 81cd8781

STACK_TEXT:  
8819fa64 81ce7ce8 000000c2 00000007 0000113d nt!KeBugCheckEx+0x1e
8819fadc 80739cbb b3810008 6e664d46 8819faf8 nt!ExFreePoolWithTag+0x17f
8819faec 80739d0b b3810034 8819fb10 8073a030 fltmgr!FltpFreeFileNameInformation+0x17
8819faf8 8073a030 b3810034 84ff5a78 84325cb8 fltmgr!FltReleaseFileNameInformation+0x2b
8819fb10 8073a09f 84325cb8 00008000 ffffffff fltmgr!DeleteNameCacheNodes+0xfe
8819fb2c 8073d3d1 84ff5a78 84325cb8 84325cf8 fltmgr!FltpFreeNameCacheList+0x17
8819fb48 8073d5d6 84325cb8 84325cbc b3817690 fltmgr!CleanupStreamListCtrl+0x37
8819fb5c 81d7cd2c 84325cbc 881940d4 81ce7b69 fltmgr!DeleteStreamListCtrlCallback+0x5a
8819fb94 81b18f8d b3817690 00000000 b3817690 nt!FsRtlTeardownPerStreamContexts+0xd4
8819fbb0 81b2b3cd 00000705 b38175a0 b38175c8 Ntfs!NtfsDeleteScb+0x1f2
8819fbc8 81aa5c9d 84815008 b3817690 00000000 Ntfs!NtfsRemoveScb+0xc2
8819fbe4 81b3838d 84815008 b38175a0 00000000 Ntfs!NtfsPrepareFcbForRemoval+0x59
8819fc28 81aad3be 84815008 b3817690 b3817830 Ntfs!NtfsTeardownStructures+0x62
8819fc50 81b34217 84815008 b3817690 b3817830 Ntfs!NtfsDecrementCloseCounts+0xad
8819fcb0 81b1933a 84815008 b3817690 b38175a0 Ntfs!NtfsCommonClose+0x4d9
8819fd44 81c78fc0 00000000 00000000 8366fcf0 Ntfs!NtfsFspClose+0x117
8819fd7c 81e25556 00000000 88194680 00000000 nt!ExpWorkerThread+0xfd
8819fdc0 81c915fe 81c78ec3 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExFreePoolWithTag+17f
81ce7ce8 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExFreePoolWithTag+17f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  48d1b550

FAILURE_BUCKET_ID:  0xc2_7_nt!ExFreePoolWithTag+17f

BUCKET_ID:  0xc2_7_nt!ExFreePoolWithTag+17f

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

eax=881e313c ebx=0000113d ecx=000003b8 edx=81d2943c esi=881e3120 edi=b3810000
eip=81cd8781 esp=8819fa48 ebp=8819fa64 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000286
nt!KeBugCheckEx+0x1e:
81cd8781 8be5            mov     esp,ebp
ChildEBP RetAddr  Args to Child              
8819fa64 81ce7ce8 000000c2 00000007 0000113d nt!KeBugCheckEx+0x1e
8819fadc 80739cbb b3810008 6e664d46 8819faf8 nt!ExFreePoolWithTag+0x17f
8819faec 80739d0b b3810034 8819fb10 8073a030 fltmgr!FltpFreeFileNameInformation+0x17 (FPO: [1,0,0])
8819faf8 8073a030 b3810034 84ff5a78 84325cb8 fltmgr!FltReleaseFileNameInformation+0x2b (FPO: [1,0,0])
8819fb10 8073a09f 84325cb8 00008000 ffffffff fltmgr!DeleteNameCacheNodes+0xfe (FPO: [5,0,4])
8819fb2c 8073d3d1 84ff5a78 84325cb8 84325cf8 fltmgr!FltpFreeNameCacheList+0x17 (FPO: [3,0,0])
8819fb48 8073d5d6 84325cb8 84325cbc b3817690 fltmgr!CleanupStreamListCtrl+0x37 (FPO: [1,0,0])
8819fb5c 81d7cd2c 84325cbc 881940d4 81ce7b69 fltmgr!DeleteStreamListCtrlCallback+0x5a (FPO: [1,0,0])
8819fb94 81b18f8d b3817690 00000000 b3817690 nt!FsRtlTeardownPerStreamContexts+0xd4
8819fbb0 81b2b3cd 00000705 b38175a0 b38175c8 Ntfs!NtfsDeleteScb+0x1f2 (FPO: [1,1,4])
8819fbc8 81aa5c9d 84815008 b3817690 00000000 Ntfs!NtfsRemoveScb+0xc2 (FPO: [3,1,0])
8819fbe4 81b3838d 84815008 b38175a0 00000000 Ntfs!NtfsPrepareFcbForRemoval+0x59 (FPO: [4,0,0])
8819fc28 81aad3be 84815008 b3817690 b3817830 Ntfs!NtfsTeardownStructures+0x62 (FPO: [SEH])
8819fc50 81b34217 84815008 b3817690 b3817830 Ntfs!NtfsDecrementCloseCounts+0xad (FPO: [7,0,4])
8819fcb0 81b1933a 84815008 b3817690 b38175a0 Ntfs!NtfsCommonClose+0x4d9 (FPO: [SEH])
8819fd44 81c78fc0 00000000 00000000 8366fcf0 Ntfs!NtfsFspClose+0x117 (FPO: [SEH])
8819fd7c 81e25556 00000000 88194680 00000000 nt!ExpWorkerThread+0xfd
8819fdc0 81c915fe 81c78ec3 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
start    end        module name
80201000 80203900   compbatt compbatt.sys Thu Nov 02 04:35:03 2006 (4549ADB7)
80204000 8020d000   WMILIB   WMILIB.SYS   Thu Nov 02 04:54:53 2006 (4549B25D)
8020d000 8021a000   WDFLDR   WDFLDR.SYS   Wed Dec 05 21:21:19 2007 (47575C9F)
8021a000 80255000   CLFS     CLFS.SYS     Wed Dec 05 20:55:42 2007 (4757569E)
80255000 8025d000   BOOTVID  BOOTVID.dll  Thu Nov 02 05:39:29 2006 (4549BCD1)
8025d000 80266000   PSHED    PSHED.dll    Thu Nov 02 05:42:51 2006 (4549BD9B)
80266000 802c6000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Apr 23 23:40:05 2007 (462D7C15)
802c6000 802ce000   kdcom    kdcom.dll    Thu Nov 02 05:42:20 2006 (4549BD7C)
80404000 8040b000   intelide intelide.sys Fri Nov 17 01:21:26 2006 (455D54E6)
8040b000 8041b000   mountmgr mountmgr.sys Thu Nov 02 04:51:06 2006 (4549B17A)
8041b000 80425000   BATTC    BATTC.SYS    Thu Nov 02 04:35:00 2006 (4549ADB4)
80425000 80434000   volmgr   volmgr.sys   Thu Nov 02 04:51:44 2006 (4549B1A0)
80434000 80459000   pci      pci.sys      Thu Nov 02 04:35:13 2006 (4549ADC1)
80459000 80461000   msisadrv msisadrv.sys Thu Nov 02 04:35:08 2006 (4549ADBC)
80461000 804a4000   acpi     acpi.sys     Thu Nov 02 04:35:03 2006 (4549ADB7)
804a4000 8051f000   Wdf01000 Wdf01000.sys Wed Dec 05 21:21:28 2007 (47575CA8)
8051f000 80600000   CI       CI.dll       Mon Feb 18 23:59:14 2008 (47BA6222)
80602000 8060a000   spldr    spldr.sys    Wed Oct 25 18:40:44 2006 (453FE7EC)
8060a000 8070e000   ndis     ndis.sys     Thu Nov 02 04:57:33 2006 (4549B2FD)
8070e000 8071e000   fileinfo fileinfo.sys Thu Nov 02 04:36:47 2006 (4549AE1F)
8071e000 8074f000   fltmgr   fltmgr.sys   Thu Nov 02 04:30:58 2006 (4549ACC2)
8074f000 80758000   msahci   msahci.sys   Fri Nov 17 01:21:29 2006 (455D54E9)
80758000 80776000   ataport  ataport.SYS  Fri Nov 17 01:21:23 2006 (455D54E3)
80776000 8077e000   atapi    atapi.sys    Fri Nov 17 01:21:20 2006 (455D54E0)
8077e000 807c8000   volmgrx  volmgrx.sys  Thu Nov 02 04:51:54 2006 (4549B1AA)
807c8000 807f2000   pcmcia   pcmcia.sys   Thu Nov 02 04:35:13 2006 (4549ADC1)
807f2000 80800000   PCIIDEX  PCIIDEX.SYS  Fri Nov 17 01:21:21 2006 (455D54E1)
81a03000 81a0c000   crcdisk  crcdisk.sys  Thu Nov 02 04:52:27 2006 (4549B1CB)
81a0c000 81a1b000   mup      mup.sys      Thu Nov 02 04:31:04 2006 (4549ACC8)
81a1b000 81a2a000   partmgr  partmgr.sys  Thu Nov 02 04:51:47 2006 (4549B1A3)
81a2a000 81a94000   ksecdd   ksecdd.sys   Thu Nov 02 04:43:45 2006 (4549AFC1)
81a94000 81b9c000   Ntfs     Ntfs.sys     Sun Dec 16 04:31:37 2007 (4764F079)
81b9c000 81bd5000   NETIO    NETIO.SYS    Sun Jan 13 22:17:13 2008 (478AD439)
81bd5000 81c00000   msrpc    msrpc.sys    Thu Nov 02 04:50:16 2006 (4549B148)
81c00000 81fa1000   nt       ntkrpamp.exe Wed Sep 17 21:56:32 2008 (48D1B550)
81fa1000 81fd5000   hal      halmacpi.dll Tue Dec 19 22:31:08 2006 (4588AE7C)
87750000 87771000   CLASSPNP CLASSPNP.SYS Thu Nov 02 04:51:34 2006 (4549B196)
87771000 87782000   disk     disk.sys     Thu Nov 02 04:51:40 2006 (4549B19C)
87782000 877a5000   fvevol   fvevol.sys   Thu Nov 02 04:30:07 2006 (4549AC8F)
877a5000 877ca000   ecache   ecache.sys   Thu Nov 02 04:52:42 2006 (4549B1DA)
877ca000 87800000   volsnap  volsnap.sys  Thu Nov 02 04:52:11 2006 (4549B1BB)
88080000 88090000   lltdio   lltdio.sys   Thu Nov 02 04:56:48 2006 (4549B2D0)
880a0000 880af280   ohci1394 ohci1394.sys Thu Nov 02 04:55:16 2006 (4549B274)
88120000 88130000   NDProxy  NDProxy.SYS  Tue Jul 03 21:28:13 2007 (468AF7AD)
88130000 88140000   HIDCLASS HIDCLASS.SYS Thu Nov 02 04:55:00 2006 (4549B264)
881a4000 881b3000   raspppoe raspppoe.sys Thu Nov 02 04:58:12 2006 (4549B324)
884c5000 884c6380   swenum   swenum.sys   Thu Nov 02 04:51:15 2006 (4549B183)
884c7000 884c8700   USBD     USBD.SYS     Thu Aug 30 21:19:54 2007 (46D76CBA)
89c06000 89c11000   SMCLIB   SMCLIB.SYS   Thu Nov 02 04:51:25 2006 (4549B18D)
89c11000 89c18000   Beep     Beep.SYS     Thu Nov 02 04:51:03 2006 (4549B177)
89c18000 89c25000   crashdmp crashdmp.sys Thu Nov 02 04:51:36 2006 (4549B198)
89cad000 89cb9000   BTHUSB   BTHUSB.sys   Mon Apr 28 21:42:08 2008 (48167CF0)
89cd5000 89cd8780   CmBatt   CmBatt.sys   Thu Nov 02 04:35:03 2006 (4549ADB7)
89d08000 89d13000   tunnel   tunnel.sys   Wed Jun 06 22:57:03 2007 (466773FF)
89d33000 89d3b000   mouhid   mouhid.sys   Wed Dec 05 21:18:25 2007 (47575BF1)
89d6b000 89d73000   RDPCDD   RDPCDD.sys   Thu Nov 02 05:02:01 2006 (4549B409)
89d73000 89d7b000   rdpencdd rdpencdd.sys Thu Nov 02 05:02:01 2006 (4549B409)
8a223000 8a229380   HIDPARSE HIDPARSE.SYS Thu Nov 02 04:55:00 2006 (4549B264)
8a269000 8a270000   Null     Null.SYS     Thu Nov 02 04:51:05 2006 (4549B179)
8a270000 8a27a000   serenum  serenum.sys  Thu Nov 02 04:51:25 2006 (4549B18D)
8a27a000 8a284000   mssmbios mssmbios.sys Thu Nov 02 04:35:13 2006 (4549ADC1)
8a284000 8a28e000   nsiproxy nsiproxy.sys Thu Nov 02 04:57:30 2006 (4549B2FA)
8a28e000 8a298000   BthEnum  BthEnum.sys  Mon Apr 28 21:42:11 2008 (48167CF3)
8a2ca000 8a2d4000   Dxapi    Dxapi.sys    Thu Nov 02 04:38:17 2006 (4549AE79)
8a2e8000 8a2f2000   secdrv   secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528)
8a306000 8a310000   ndisuio  ndisuio.sys  Thu Nov 02 04:57:22 2006 (4549B2F2)
8a379000 8a382000   wmiacpi  wmiacpi.sys  Thu Nov 02 04:35:03 2006 (4549ADB7)
8a382000 8a38b000   Fs_Rec   Fs_Rec.SYS   Mon Apr 16 21:26:39 2007 (4624224F)
8a38b000 8a394000   rasacd   rasacd.sys   Thu Nov 02 04:58:13 2006 (4549B325)
8a3af000 8a3b8000   dump_msahci dump_msahci.sys Fri Nov 17 01:21:29 2006 (455D54E9)
8a3e5000 8a3ee000   hidusb   hidusb.sys   Thu Nov 02 04:55:01 2006 (4549B265)
8a3ee000 8a3f7000   tunmp    tunmp.sys    Wed Jun 06 22:56:53 2007 (466773F5)
8ac05000 8ac10000   kbdclass kbdclass.sys Wed Dec 05 21:18:23 2007 (47575BEF)
8ac10000 8ac1b000   mouclass mouclass.sys Wed Dec 05 21:18:22 2007 (47575BEE)
8ac1b000 8ac2e000   i8042prt i8042prt.sys Wed Dec 05 21:18:28 2007 (47575BF4)
8ac2e000 8ac3b080   1394BUS  1394BUS.SYS  Thu Nov 02 04:55:12 2006 (4549B270)
8ac3c000 8ac6b000   b57nd60x b57nd60x.sys Thu Feb 08 18:03:14 2007 (45CBAC32)
8ac6b000 8ace0000   bcmwl6   bcmwl6.sys   Tue Oct 03 22:38:08 2006 (45231E90)
8ace0000 8acf2000   HDAudBus HDAudBus.sys Sat Mar 24 14:54:34 2007 (460573EA)
8acf2000 8ad00000   usbehci  usbehci.sys  Thu Aug 30 21:19:59 2007 (46D76CBF)
8ad00000 8ad3d000   USBPORT  USBPORT.SYS  Thu Aug 30 21:20:03 2007 (46D76CC3)
8ad3d000 8ad48000   usbuhci  usbuhci.sys  Thu Aug 30 21:19:58 2007 (46D76CBE)
8ad48000 8ad55000   watchdog watchdog.sys Thu Nov 02 04:37:44 2006 (4549AE58)
8ad55000 8adf2000   dxgkrnl  dxgkrnl.sys  Mon Jul 02 21:01:10 2007 (46899FD6)
8adf2000 8ae00000   intelppm intelppm.sys Thu Nov 02 04:30:18 2006 (4549AC9A)
8ae08000 8ae13000   TDI      TDI.SYS      Thu Nov 02 04:58:46 2006 (4549B346)
8ae13000 8ae2b000   cdrom    cdrom.sys    Thu Nov 02 04:51:44 2006 (4549B1A0)
8ae33000 8ae3f000   vga      vga.sys      Thu Nov 02 04:53:56 2006 (4549B224)
8ae3f000 8ae4c000   modem    modem.sys    Thu Nov 02 04:58:52 2006 (4549B34C)
8ae4c000 8ae5b000   termdd   termdd.sys   Thu Nov 02 05:02:00 2006 (4549B408)
8ae5b000 8ae68000   umbus    umbus.sys    Thu Nov 02 04:55:24 2006 (4549B27C)
8ae68000 8ae7b000   raspptp  raspptp.sys  Thu Nov 02 04:58:14 2006 (4549B326)
8ae7b000 8ae9e000   ndiswan  ndiswan.sys  Thu Nov 02 04:58:13 2006 (4549B325)
8ae9e000 8aea9000   ndistapi ndistapi.sys Tue Jul 03 21:28:09 2007 (468AF7A9)
8aea9000 8aec0000   rasl2tp  rasl2tp.sys  Thu Nov 02 04:58:13 2006 (4549B325)
8aec0000 8af00000   storport storport.sys Thu Nov 02 04:51:45 2006 (4549B1A1)
8af00000 8af2b000   msiscsi  msiscsi.sys  Thu Nov 02 04:52:40 2006 (4549B1D8)
8af2b000 8af45000   serial   serial.sys   Thu Nov 02 04:51:29 2006 (4549B191)
8af45000 8b600000   igdkmd32 igdkmd32.sys Mon Feb 11 14:36:07 2008 (47B0A3A7)
8b802000 8b80d000   Msfs     Msfs.SYS     Thu Nov 02 04:30:56 2006 (4549ACC0)
8b82d000 8b84e000   VIDEOPRT VIDEOPRT.SYS Thu Nov 02 04:54:07 2006 (4549B22F)
8b84e000 8b88a000   VSTAZL3  VSTAZL3.SYS  Tue Jun 20 13:39:49 2006 (449832E5)
8b88a000 8b8af000   drmk     drmk.sys     Thu Nov 02 05:20:49 2006 (4549B871)
8b8af000 8b8dc000   portcls  portcls.sys  Thu Nov 02 04:55:02 2006 (4549B266)
8b8dc000 8b91b000   HdAudio  HdAudio.sys  Wed Nov 01 21:43:11 2006 (45494D2F)
8b91b000 8b94f000   usbhub   usbhub.sys   Thu Aug 30 21:20:18 2007 (46D76CD2)
8b94f000 8b979000   ks       ks.sys       Thu Nov 02 04:51:18 2006 (4549B186)
8b979000 8ba00000   rdpdr    rdpdr.sys    Thu Nov 02 05:02:58 2006 (4549B442)
8bc01000 8bc0d000   usbccid  usbccid.sys  Thu Nov 02 04:51:27 2006 (4549B18F)
8bc0d000 8bc22000   tdx      tdx.sys      Thu Nov 02 04:57:34 2006 (4549B2FE)
8bc22000 8bc3b000   fwpkclnt fwpkclnt.sys Thu Nov 02 04:57:26 2006 (4549B2F6)
8bc3b000 8bc49000   Npfs     Npfs.SYS     Thu Nov 02 04:30:57 2006 (4549ACC1)
8bc49000 8bcfc000   VSTCNXT3 VSTCNXT3.SYS Tue Jun 20 13:39:37 2006 (449832D9)
8bcfc000 8be00000   VSTDPV3  VSTDPV3.SYS  Tue Jun 20 13:41:01 2006 (4498332D)
8be03000 8be14000   rfcomm   rfcomm.sys   Thu Nov 02 04:55:22 2006 (4549B27A)
8be14000 8be2b000   dfsc     dfsc.sys     Thu Nov 02 04:31:04 2006 (4549ACC8)
8be2b000 8be3e000   wanarp   wanarp.sys   Tue Jul 03 21:28:16 2007 (468AF7B0)
8be3e000 8be4c000   netbios  netbios.sys  Thu Nov 02 04:57:26 2006 (4549B2F6)
8be4c000 8be62000   pacer    pacer.sys    Tue Jul 03 21:27:33 2007 (468AF785)
8be62000 8be94000   netbt    netbt.sys    Thu Nov 02 04:57:18 2006 (4549B2EE)
8be94000 8bedb000   afd      afd.sys      Thu Nov 02 04:58:41 2006 (4549B341)
8bedb000 8beef000   smb      smb.sys      Thu Nov 02 04:57:10 2006 (4549B2E6)
8bf2f000 8c000000   tcpip    tcpip.sys    Sun Jan 13 22:17:51 2008 (478AD45F)
8c0ac000 8c0bd000   dump_dumpfve dump_dumpfve.sys Thu Nov 02 04:30:04 2006 (4549AC8C)
8c0bd000 8c0c8000   dump_dumpata dump_dumpata.sys Thu Nov 02 04:51:34 2006 (4549B196)
8c0c8000 8c0de000   cdfs     cdfs.sys     Thu Nov 02 04:30:50 2006 (4549ACBA)
8c0de000 8c0f8000   bthpan   bthpan.sys   Thu Nov 02 04:55:27 2006 (4549B27F)
8c0f8000 8c132000   bthport  bthport.sys  Mon Apr 28 21:42:11 2008 (48167CF3)
8c172000 8c1c5000   csc      csc.sys      Mon Jun 18 20:48:27 2007 (467727DB)
8c1c5000 8c200000   rdbss    rdbss.sys    Thu Nov 02 04:31:24 2006 (4549ACDC)
90600000 90800000   win32k   win32k.sys   unavailable (00000000)
a0a00000 a0a09000   TSDDD    TSDDD.dll    unavailable (00000000)
a0a10000 a0a1e000   cdd      cdd.dll      unavailable (00000000)
a17a5000 a17c0000   luafv    luafv.sys    Thu Nov 02 04:33:07 2006 (4549AD43)
a2fc9000 a2fd4000   tcpipreg tcpipreg.sys Thu Nov 02 04:57:46 2006 (4549B30A)
a3305000 a3351000   srv      srv.sys      Mon Dec 15 22:14:35 2008 (49471D1B)
a3391000 a33b5000   srv2     srv2.sys     Thu Oct 25 21:40:47 2007 (4721459F)
a33b5000 a33c7000   mrxsmb20 mrxsmb20.sys Thu Oct 25 21:40:16 2007 (47214580)
a33c7000 a3400000   mrxsmb10 mrxsmb10.sys Mon Aug 25 21:11:57 2008 (48B3585D)
a3682000 a3710000   spsys    spsys.sys    Wed Oct 25 18:43:28 2006 (453FE890)
a3710000 a371f000   monitor  monitor.sys  Sun Dec 16 04:56:44 2007 (4764F65C)
a3c04000 a3c18000   mpsdrv   mpsdrv.sys   Wed Jun 06 22:55:55 2007 (466773BB)
a3c18000 a3c31000   bowser   bowser.sys   Thu Nov 02 04:31:11 2006 (4549ACCF)
a3c31000 a3c4c000   srvnet   srvnet.sys   Thu Oct 25 21:40:43 2007 (4721459B)
a3c4c000 a3cb2000   HTTP     HTTP.sys     Thu Nov 02 04:57:06 2006 (4549B2E2)
a3d44000 a3d62000   mrxsmb   mrxsmb.sys   Thu Oct 25 21:40:17 2007 (47214581)
a3d62000 a3d82000   mrxdav   mrxdav.sys   Fri Jan 11 20:45:54 2008 (47881BD2)
a3dc2000 a3dd5000   rspndr   rspndr.sys   Thu Nov 02 04:56:48 2006 (4549B2D0)
a3dd5000 a3e00000   nwifi    nwifi.sys    Thu Nov 02 04:55:41 2006 (4549B28D)
a4122000 a4200000   peauth   peauth.sys   Mon Oct 23 04:55:32 2006 (453C8384)

Unloaded modules:
a1636000 a1645000   monitor.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
908b1000 908c0000   monitor.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
89d83000 89d8b000   drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
89c18000 89c25000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
89c06000 89c11000   dump_pciidex
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8a370000 8a379000   dump_msahci.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
89ca8000 89cb9000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

gord · 03-21-2009, 12:49 PM

Somehow overnight the pesky two remaining updates installed and I wasn't caught in the reboot loop. Lo and behold, SP1 became available through WU and it installed. So now I'm completely up-to-date, but I'm not sure what I can do now to stress the system to check if I'm cured or not.

**jcgriff2** · 03-24-2009, 05:20 PM

Hi -

Great news to hear about the install of SP1.

To stress the system at least on some level - I usually open up many IE screens, start some downloads then start running a Vista system health report
START | perfmon /report

Playing Windows Media player - audio or video and running other apps will help to stress things. Any apps that you have that use alot of resources - MS Office apps, Internet, etc... will do. You can run perfmon report as often as you like, but only 1 instance at a time.

Regards. . .

jcgriff2

.

macRealty · 10-03-2009, 11:31 AM

I have this exact same issue with an Inspiron 1520 which is getting a HDD replacement (Seagate 250 GB MOMENTUS 7200.4).

All well until MS updates get applied.

Once 943899 gets applied it goes into constant reboot.

And it has taken 4 hours elimination of 100 updates to get here (including 3 restores).

I'd love to know who the hell compensates me for that time ?

03-20-2009, 01:37 PM	#1 (permalink)
gord Registered User Join Date: Apr 2005 Posts: 183 OS: Vista	Windows Updates causing endless reboot loop Dell Latitude D830 laptop, Vista OS I had to format and reinstall Windows and used Windows Update to install fixes. When it needed to reboot, I would occasionally get caught in an endless reboot loop. The computer would POST and the progress bar on the Windows loading screen would get about halfway across then blue screen and reboot. I am able to use my Windows CD to do a system restore but that would undo some updates. I changed the setting so it wouldn't automatically reboot and got these errors: STOP: 0x0000007B (0x80403bA0, 0xC0000034, 0x00000000, 0x00000000) __________________ Gigabyte GA-P35C-DS3R, Intel e6850, GeForce 8800 GTS, Antec TruePower Trio 650W

03-20-2009, 02:16 PM	#2 (permalink)
TriggerFinger Moderator Hardware Team Join Date: Jan 2008 Location: USA Posts: 11,826 OS: Vista SP1, XP SP3, PCLinuxOS2007	Re: Windows Updates causing endless reboot loop If I am not mistaken 7B points to an inaccessible boot device, may be a defective hard drive. Since you are using DELL, may be it has a recovery partition that you can use to fix/undo any changes. Can you into Safe Mode? Did you try Last Known Good Configuration? __________________ DBAN - Memtest86+ - BartPE - Linux LiveCD - ImgBurn - HDD Diags - Disk Copy HOW TO BURN AN ISO FILE

03-20-2009, 02:57 PM	#3 (permalink)
gord Registered User Join Date: Apr 2005 Posts: 183 OS: Vista	Re: Windows Updates causing endless reboot loop I keep thinking that its the hard drive, but running the sfc command or chkdsk don't come up with any sector errors. I'm down to three recommended updates on WU and installing any one of them causes the reboot loop. I have my Dell Vista DVD and I use that to repair and do a system restore. Just going into safe mode or LKGC without the Windows DVD does not work. __________________ Gigabyte GA-P35C-DS3R, Intel e6850, GeForce 8800 GTS, Antec TruePower Trio 650W

03-20-2009, 03:06 PM	#4 (permalink)
TriggerFinger Moderator Hardware Team Join Date: Jan 2008 Location: USA Posts: 11,826 OS: Vista SP1, XP SP3, PCLinuxOS2007	Re: Windows Updates causing endless reboot loop You can run SeaTools or Hitach DFT (see HDD Diags link on my sig.) to test the HDD for hardware errors. Both have a CD image that you can burn into a blank CD (see HOW TO BURN AN ISO... link on my sig.). Btw, this makes the CD bootable which is good as you can run it outside of Windows. I think you are on the right path of uninstalling the recent updates especially if the problem began ONLY after they were installed. __________________ DBAN - Memtest86+ - BartPE - Linux LiveCD - ImgBurn - HDD Diags - Disk Copy HOW TO BURN AN ISO FILE Last edited by TriggerFinger; 03-20-2009 at 03:07 PM.

03-20-2009, 05:37 PM	#5 (permalink)
gord Registered User Join Date: Apr 2005 Posts: 183 OS: Vista	Re: Windows Updates causing endless reboot loop Diagnostics in physical tests came up clean except for a File Structure Test. It failed with critical errors: One or more file names contained errors One or more errors were found in the index One or more errors were found in metadata file records Other errors were found Prior to installing Vista, I zero filled the drive, installed straight from the Dell Vista CD and went straight to updating. __________________ Gigabyte GA-P35C-DS3R, Intel e6850, GeForce 8800 GTS, Antec TruePower Trio 650W

03-20-2009, 05:40 PM	#6 (permalink)
TriggerFinger Moderator Hardware Team Join Date: Jan 2008 Location: USA Posts: 11,826 OS: Vista SP1, XP SP3, PCLinuxOS2007	Re: Windows Updates causing endless reboot loop What test did you use? __________________ DBAN - Memtest86+ - BartPE - Linux LiveCD - ImgBurn - HDD Diags - Disk Copy HOW TO BURN AN ISO FILE

03-20-2009, 06:10 PM	#7 (permalink)
gord Registered User Join Date: Apr 2005 Posts: 183 OS: Vista	Re: Windows Updates causing endless reboot loop The one that came up with errors was the File Structure Test on the SeaTools CD. __________________ Gigabyte GA-P35C-DS3R, Intel e6850, GeForce 8800 GTS, Antec TruePower Trio 650W

03-20-2009, 06:24 PM	#8 (permalink)
TriggerFinger Moderator Hardware Team Join Date: Jan 2008 Location: USA Posts: 11,826 OS: Vista SP1, XP SP3, PCLinuxOS2007	Re: Windows Updates causing endless reboot loop Did the SMART test pass? As for the file errors, may be a CHKDSK /R can help. Try Vista's Startup Repair (you will need Vista disc). See this: http://www.vistax64.com/tutorials/19...y-options.html __________________ DBAN - Memtest86+ - BartPE - Linux LiveCD - ImgBurn - HDD Diags - Disk Copy HOW TO BURN AN ISO FILE Last edited by TriggerFinger; 03-20-2009 at 06:37 PM.

03-20-2009, 07:07 PM	#9 (permalink)
jcgriff2 Moderator, Microsoft Supp Join Date: Sep 2007 Location: Palm Springs, California / Southern New Jersey Posts: 10,054 OS: Windows 7, Vista Ultimate My System	Re: Windows Updates causing endless reboot loop What was the reason for doing the low-level format prior to the Vista install? __________________ . . . . . . . . BSOD Posting Instructions B Expecting a reply and waiting > 36 hours ? Send a PM to me containing a link to your thread My availability will be limited through ~ December 1, 2009

03-20-2009, 07:26 PM	#10 (permalink)
gord Registered User Join Date: Apr 2005 Posts: 183 OS: Vista	Re: Windows Updates causing endless reboot loop @jfgriff2: I wanted to make sure there weren't any fragments left over from a standard format. I wanted to rule that out. @TriggerFinger: SMART says it's fine and I've run 'chkdsk /f' and 'sfc /scannow' several times and there are no errors. I am able to boot into Windows and use it as normal (nothing has changed here). The only problem is when I try to download and install the last three remaining 'recommended' updates in Windows Update. They will install fine, but when I reboot, the progress bar gets halfway across and blue screens. I am able to use the Vista DVD to repair and do a restore, but the updates are obviously wiped out. __________________ Gigabyte GA-P35C-DS3R, Intel e6850, GeForce 8800 GTS, Antec TruePower Trio 650W

03-20-2009, 08:13 PM	#11 (permalink)
TriggerFinger Moderator Hardware Team Join Date: Jan 2008 Location: USA Posts: 11,826 OS: Vista SP1, XP SP3, PCLinuxOS2007	Re: Windows Updates causing endless reboot loop I asked for HDD diagnostics so we can just rule out the hardware side. What updates are you trying to install anyway? __________________ DBAN - Memtest86+ - BartPE - Linux LiveCD - ImgBurn - HDD Diags - Disk Copy HOW TO BURN AN ISO FILE

03-20-2009, 08:39 PM	#12 (permalink)
gord Registered User Join Date: Apr 2005 Posts: 183 OS: Vista	Re: Windows Updates causing endless reboot loop They are: KB941649 - resolves compatibility and reliability issues (like hell!) KB941651 - reliability update for WMP11 KB943899 - reliability update for Vista All listed as "recommended" __________________ Gigabyte GA-P35C-DS3R, Intel e6850, GeForce 8800 GTS, Antec TruePower Trio 650W

03-20-2009, 10:04 PM	#14 (permalink)
gord Registered User Join Date: Apr 2005 Posts: 183 OS: Vista	Re: Windows Updates causing endless reboot loop I installed the WMP11 update since that seemed harmless. While I was installing iTunes I got another blue screen: Bad Pool Caller 0x000000C2 (0x00000007, 0x0000113D, 0x00000000, 0xB3810008) __________________ Gigabyte GA-P35C-DS3R, Intel e6850, GeForce 8800 GTS, Antec TruePower Trio 650W

03-20-2009, 10:09 PM	#15 (permalink)
TriggerFinger Moderator Hardware Team Join Date: Jan 2008 Location: USA Posts: 11,826 OS: Vista SP1, XP SP3, PCLinuxOS2007	Re: Windows Updates causing endless reboot loop May be there is a dump file. Attach them zipped. They might help identify the cause. __________________ DBAN - Memtest86+ - BartPE - Linux LiveCD - ImgBurn - HDD Diags - Disk Copy HOW TO BURN AN ISO FILE

03-21-2009, 12:49 PM	#18 (permalink)
gord Registered User Join Date: Apr 2005 Posts: 183 OS: Vista	Re: Windows Updates causing endless reboot loop Somehow overnight the pesky two remaining updates installed and I wasn't caught in the reboot loop. Lo and behold, SP1 became available through WU and it installed. So now I'm completely up-to-date, but I'm not sure what I can do now to stress the system to check if I'm cured or not. __________________ Gigabyte GA-P35C-DS3R, Intel e6850, GeForce 8800 GTS, Antec TruePower Trio 650W

03-24-2009, 05:20 PM	#19 (permalink)
jcgriff2 Moderator, Microsoft Supp Join Date: Sep 2007 Location: Palm Springs, California / Southern New Jersey Posts: 10,054 OS: Windows 7, Vista Ultimate My System	Re: Windows Updates causing endless reboot loop Hi - Great news to hear about the install of SP1. To stress the system at least on some level - I usually open up many IE screens, start some downloads then start running a Vista system health report START \| perfmon /report Playing Windows Media player - audio or video and running other apps will help to stress things. Any apps that you have that use alot of resources - MS Office apps, Internet, etc... will do. You can run perfmon report as often as you like, but only 1 instance at a time. Regards. . . jcgriff2 . __________________ . . . . . . . . BSOD Posting Instructions B Expecting a reply and waiting > 36 hours ? Send a PM to me containing a link to your thread My availability will be limited through ~ December 1, 2009

10-03-2009, 11:31 AM	#20 (permalink)
macRealty Registered User Join Date: Oct 2009 Posts: 1 OS: Vista	Re: Windows Updates causing endless reboot loop I have this exact same issue with an Inspiron 1520 which is getting a HDD replacement (Seagate 250 GB MOMENTUS 7200.4). All well until MS updates get applied. Once 943899 gets applied it goes into constant reboot. And it has taken 4 hours elimination of 100 updates to get here (including 3 restores). I'd love to know who the hell compensates me for that time ?