BSOD at startup - Win7

[Sarkus]

Hi
It seems that each time I switch my PC on... it boots into Win7 and then I get a BSOD. It reboots and runs chkdsk, currently finds nothing, and boots into Win7 normally and all is well.

I've attached the various reports and files, and seems that chkdsk runs 'cos I have a "dirty bit", but I'm guessing that is caused by the BSOD rather being the cause.

I have an i5-750, Radeon HD5850, 4Gb Ram, all about one year old.
New install of Win7 Home Premium full version (x86).

Have been having the issues for a while, previously when running Win XP, and I hoped the new OS might solve it... but this hasn't been the case.


I have run Windows Memory Diagnostic and Memtest86+ on the RAM - no issues noted, although I only did 1 pass, partly due to time and partly 'cos my BSOD only seems to be an issue at initial boot.


Any help would be appreciated.
Cheers.

 

[zigzag3143]

Hi
It seems that each time I switch my PC on... it boots into Win7 and then I get a BSOD. It reboots and runs chkdsk, currently finds nothing, and boots into Win7 normally and all is well.

I've attached the various reports and files, and seems that chkdsk runs 'cos I have a "dirty bit", but I'm guessing that is caused by the BSOD rather being the cause.

I have an i5-750, Radeon HD5850, 4Gb Ram, all about one year old.
New install of Win7 Home Premium full version (x86).

Have been having the issues for a while, previously when running Win XP, and I hoped the new OS might solve it... but this hasn't been the case.


I have run Windows Memory Diagnostic and Memtest86+ on the RAM - no issues noted, although I only did 1 pass, partly due to time and partly 'cos my BSOD only seems to be an issue at initial boot.


Any help would be appreciated.
Cheers.

These were caused by memory corruption by an as yet un-named driver. Please run memtest and driver verifier


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.

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.

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\052611-17097-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 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16792.x86fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0x82a1c000 PsLoadedModuleList = 0x82b64810
Debug session time: Thu May 26 03:31:32.231 2011 (GMT-4)
System Uptime: 0 days 0:00:44.589
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
....
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041790, The subtype of the bugcheck.
Arg2: c0802058
Arg3: 0000ffff
Arg4: 00000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82ac11d0 to 82abc6e5

STACK_TEXT:  
8c502c14 82ac11d0 877a1030 877a1030 00000000 nt!MiDeleteAddressesInWorkingSet+0x389
8c502c40 82c651fe a89d96c3 86525a20 c0000005 nt!MmCleanProcessAddressSpace+0x8c
8c502cb4 82c99630 00000000 87756800 00000001 nt!PspExitThread+0x683
8c502ccc 82ac425b 87756800 8c502cf8 8c502d04 nt!PsExitSpecialApc+0x22
8c502d1c 82a5f4d4 00000001 00000000 8c502d34 nt!KiDeliverApc+0x28b
8c502d1c 77d86344 00000001 00000000 8c502d34 nt!KiServiceExit+0x64
WARNING: Frame IP not in any known module. Following frames may be wrong.
01d7fa34 00000000 00000000 00000000 00000000 0x77d86344


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiDeleteAddressesInWorkingSet+389
82abc6e5 cc              int     3

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiDeleteAddressesInWorkingSet+389

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fd915

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x1a_41790_nt!MiDeleteAddressesInWorkingSet+389

BUCKET_ID:  0x1a_41790_nt!MiDeleteAddressesInWorkingSet+389

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

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.