Win 7 Upgrade today, then BSOD

[AMargh]

First, thanks in advance for any assistance. I've spent the day upgrading my ~3 year old Dell Inspiron 1525 from Vista to Windows 7 Home Premium, 32 bit. Only a couple hours after the fresh install, I got my first BSOD. FWIW, I did a complete repartitioning and reformat, and a complete fresh install of Win 7.

The machine was functional under Vista, but had become clogged and slow. It would always have an "unexpected shutdown" if left unattended overnight. The problems seem to occur most often when the system is allowed to sleep or hibernate. It was always generally pretty stable under Vista as long as you were actively using the system.

I always assumed my problems were related to Vista, but now it appears that they have followed me to Win 7 also.

Anyway, the typical zip file is attached. Any help would be very welcome!

Thanks!

 

[zigzag3143]

First, thanks in advance for any assistance. I've spent the day upgrading my ~3 year old Dell Inspiron 1525 from Vista to Windows 7 Home Premium, 32 bit. Only a couple hours after the fresh install, I got my first BSOD. FWIW, I did a complete repartitioning and reformat, and a complete fresh install of Win 7.

The machine was functional under Vista, but had become clogged and slow. It would always have an "unexpected shutdown" if left unattended overnight. The problems seem to occur most often when the system is allowed to sleep or hibernate. It was always generally pretty stable under Vista as long as you were actively using the system.

I always assumed my problems were related to Vista, but now it appears that they have followed me to Win 7 also.

Anyway, the typical zip file is attached. Any help would be very welcome!

Thanks!

This one was caused by memory corruption probably by a driver. You have old drivers (from vista?) that need updating.

If the problem continues we can run driver verifier to find which driver it is.

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/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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"
- 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).

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.

In the mean time if you want to check your memory (a good idea) you can run memtest.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86.com - Memory Diagnostic

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\041811-34928-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x82a1c000 PsLoadedModuleList = 0x82b66850
Debug session time: Mon Apr 18 21:36:04.697 2011 (GMT-4)
System Uptime: 0 days 0:01:41.601
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {c03f1bf0, 0, 0, 82aa172e}

Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+180 )

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: c03f1bf0, memory referenced
Arg2: 00000000, IRQL
Arg3: 00000000, 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: 82aa172e, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82b86718
Unable to read MiSystemVaType memory at 82b661a0
 c03f1bf0 

CURRENT_IRQL:  0

FAULTING_IP: 
nt!MiAgeWorkingSet+180
82aa172e 8b0f            mov     ecx,dword ptr [edi]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  8d34ba2c -- (.trap 0xffffffff8d34ba2c)
ErrCode = 00000000
eax=0000017f ebx=c0803304 ecx=c0802d08 edx=8930b600 esi=0023d000 edi=c03f1bf0
eip=82aa172e esp=8d34baa0 ebp=8d34bc10 iopl=0         nv up ei ng nz na pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010287
nt!MiAgeWorkingSet+0x180:
82aa172e 8b0f            mov     ecx,dword ptr [edi]  ds:0023:c03f1bf0=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82aa172e to 82a5d5cb

STACK_TEXT:  
8d34ba2c 82aa172e badb0d00 8930b600 00000000 nt!KiTrap0E+0x2cf
8d34bc10 82a9c94b 8930b600 00000001 00000001 nt!MiAgeWorkingSet+0x180
8d34bc5c 82a9c610 00000002 00000001 00000000 nt!MiProcessWorkingSets+0x25b
8d34bc88 82a94f2f 00000000 851c6158 00000000 nt!MmWorkingSetManager+0xa4
8d34bd50 82c25f5e 00000000 a4c6b549 00000000 nt!KeBalanceSetManager+0x1af
8d34bd90 82acd219 82a94d80 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiAgeWorkingSet+180
82aa172e 8b0f            mov     ecx,dword ptr [edi]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiAgeWorkingSet+180

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce78a09

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiAgeWorkingSet+180

BUCKET_ID:  0xA_nt!MiAgeWorkingSet+180

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

Old drivers needing update

rixdptsk.sys    11/14/2006 09:35:19 PM    0x96cd5000    0x96d26000    0x00051000    0x455a6ed7                            
OEM02Vfx.sys    3/5/2007 06:45:03 AM    0x8c245000    0x8c246d00    0x00001d00    0x45ebf4af                            
OEM02Dev.sys    10/10/2007 10:29:05 PM    0x8c20b000    0x8c244880    0x00039880    0x470d8a71                            
VSTCNXT3.SYS    10/15/2008 08:29:13 PM    0x82304000    0x823b9000    0x000b5000    0x48f68ad9                            
VSTAZL3.SYS    10/15/2008 08:30:03 PM    0x92f6d000    0x92faa000    0x0003d000    0x48f68b0b                            
VSTDPV3.SYS    10/15/2008 08:32:04 PM    0x82202000    0x82304000    0x00102000    0x48f68b84                            
spldr.sys    5/11/2009 12:13:47 PM    0x8b64b000    0x8b653000    0x00008000    0x4a084ebb                            
bcmwl6.sys    7/7/2009 08:44:47 PM    0x96a1e000    0x96c85000    0x00267000    0x4a53ebff

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 try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

 

[AMargh]

Wow, thanks for the quick reply and the great detail. I'll chase the drivers and see if that helps, and also likely try the memtest just to see if there is an issue there.

More details as I have them.

 

[AMargh]

I have an update and another question (of course).

I was able to update one of the drivers - rixdptsk.sys - which turned out to be for the integrated Ricoh SD/multi format card reader. In Device manager, this successfully resolved two separate "Base System Devices" that didn't have drivers. There are no remaining devices without drivers installed.

Unfortunately, I couldn't locate more recent versions of the rest of the drivers from either Dell or the device manufacturers. The items that remain on the list provided by zigzag relate to the modem, the integrated webcam, the network adapter, and finally a system file. I will continue to search for more recent versions.

Question: What is the source of the list of drivers provided by zigzag? I would like to monitor my progress by re-running the reports but I couldn't locate the info in the original zip file.

I also ran the memtest utility overnight. It was well into the 9th pass without a single memory error, so I guess this is good news. The BSOD has not reappeared, but I will continue to monitor and post any updates.