Windows 7 crashing at boot up

[tjobeid]

I am running on windows vista , i did an upgrade to windows 7 during boot up right when i get the windows 7 logo it freezes or it goes to a the blue screen.
I did a debug and attached the file if someone can help thanks.

 

[nate42nd]

Can you boot into safe mode to see if it's a driver causing the issue?

 

[torrentg]

I am running on windows vista , i did an upgrade to windows 7 during boot up right when i get the windows 7 logo it freezes or it goes to a the blue screen.
I did a debug and attached the file if someone can help thanks.

Rar the minidumps by copying to another folder first, then post here as attachment if Nate's fine suggestion does not work out.

C:\Windows\Minidump

 

[tjobeid]

when im booting up i have option A windows setup and B windows vista

as soon as i choose safe mode it crashes. Or it goes to the loading menu and then crashes.
I also took out my sound card and tried booting but that didnt work , i thought it could be that my SC is acting up with 7.

 

[torrentg]

Boot into Vista and go to HDD containing Win7 to get the dumps.

 

[tjobeid]

Here is what i got , i have no idea what to do with them ?

 

[torrentg]

Doesn't look so good. I think chances are high that your memory is going bad or is bad.

This is the error you are getting: code 0x50
PAGE_FAULT_IN_NONPAGED_AREA (50)


"Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory."

IMAGE_NAME: memory_corruption

You may read more about it here:

"Stop 0x50" Error Message While Installing Windows

In the article are steps you may take to attempt a resolution for your issue.
I suggest first before that, boot to Vista a run a Memtest on it for a solid 5 hours at least. Overnight is better.

Did you add any memory lately?

Keep us informed of results.

 

[tjobeid]

I dont think my memory is bad. I bult the pc not even a year ago. SOme of the top of the line parts. I have 4 Gigs of ram that work great on vista. Never had issues with my ram.

 

[torrentg]

3 choices it seems then.

1) Reinstall Vista.
2) Take the pc to a repair shop.
3) Or run Memtest for a few hours at least to rule out RAM errors. Would be smart move based upon Microsoft's knowledge base.

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


Loading Dump File [E:\Temp\Rar$DI00.625\Mini100909-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Invalid directory table base value 0x0
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18226.x86fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0x8281a000 PsLoadedModuleList = 0x82931c70
Debug session time: Fri Oct  9 23:31:57.522 2009 (GMT-5)
System Uptime: 0 days 1:56:31.269
Loading Kernel Symbols
........................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {bc183847, 0, 828a9fd2, 2}

Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+23b )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: bc183847, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 828a9fd2, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000002, (reserved)

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82951868
Unable to read MiSystemVaType memory at 82931420
 bc183847 

FAULTING_IP: 
nt!MiAgeWorkingSet+23b
828a9fd2 0fb6420f        movzx   eax,byte ptr [edx+0Fh]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

CURRENT_IRQL:  0

TRAP_FRAME:  8c1ffa54 -- (.trap 0xffffffff8c1ffa54)
ErrCode = 00000000
eax=00000020 ebx=20202020 ecx=00000000 edx=bc183838 esi=c0001128 edi=c0803a78
eip=828a9fd2 esp=8c1ffac8 ebp=8c1ffc44 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!MiAgeWorkingSet+0x23b:
828a9fd2 0fb6420f        movzx   eax,byte ptr [edx+0Fh]     ds:0023:bc183847=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82874b54 to 828bf0f5

STACK_TEXT:  
8c1ffa3c 82874b54 00000000 bc183847 00000000 nt!MmAccessFault+0x10a
8c1ffa3c 828a9fd2 00000000 bc183847 00000000 nt!KiTrap0E+0xdc
8c1ffc44 828a994f 85db9e38 00000001 8c1ffc80 nt!MiAgeWorkingSet+0x23b
8c1ffc98 828a9384 00000002 8c1ffcb4 00000001 nt!MiProcessWorkingSets+0x1ff
8c1ffcd8 8285563a 00000000 8555b2d8 00000000 nt!MmWorkingSetManager+0x199
8c1ffd7c 829efb18 00000000 380669d7 00000000 nt!KeBalanceSetManager+0x12a
8c1ffdc0 82848a2e 82855510 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiAgeWorkingSet+23b
828a9fd2 0fb6420f        movzx   eax,byte ptr [edx+0Fh]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!MiAgeWorkingSet+23b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  49ac8fb4

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x50_nt!MiAgeWorkingSet+23b

BUCKET_ID:  0x50_nt!MiAgeWorkingSet+23b

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: bc183847, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 828a9fd2, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000002, (reserved)

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82951868
Unable to read MiSystemVaType memory at 82931420
 bc183847 

FAULTING_IP: 
nt!MiAgeWorkingSet+23b
828a9fd2 0fb6420f        movzx   eax,byte ptr [edx+0Fh]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

CURRENT_IRQL:  0

TRAP_FRAME:  8c1ffa54 -- (.trap 0xffffffff8c1ffa54)
ErrCode = 00000000
eax=00000020 ebx=20202020 ecx=00000000 edx=bc183838 esi=c0001128 edi=c0803a78
eip=828a9fd2 esp=8c1ffac8 ebp=8c1ffc44 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!MiAgeWorkingSet+0x23b:
828a9fd2 0fb6420f        movzx   eax,byte ptr [edx+0Fh]     ds:0023:bc183847=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82874b54 to 828bf0f5

STACK_TEXT:  
8c1ffa3c 82874b54 00000000 bc183847 00000000 nt!MmAccessFault+0x10a
8c1ffa3c 828a9fd2 00000000 bc183847 00000000 nt!KiTrap0E+0xdc
8c1ffc44 828a994f 85db9e38 00000001 8c1ffc80 nt!MiAgeWorkingSet+0x23b
8c1ffc98 828a9384 00000002 8c1ffcb4 00000001 nt!MiProcessWorkingSets+0x1ff
8c1ffcd8 8285563a 00000000 8555b2d8 00000000 nt!MmWorkingSetManager+0x199
8c1ffd7c 829efb18 00000000 380669d7 00000000 nt!KeBalanceSetManager+0x12a
8c1ffdc0 82848a2e 82855510 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiAgeWorkingSet+23b
828a9fd2 0fb6420f        movzx   eax,byte ptr [edx+0Fh]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!MiAgeWorkingSet+23b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  49ac8fb4

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x50_nt!MiAgeWorkingSet+23b

BUCKET_ID:  0x50_nt!MiAgeWorkingSet+23b

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

 

[tjobeid]

Ram tested fine ..

 

[usasma]

I'd suggest running Driver Verifier:

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 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"
- Select "Automatically select unsigned drivers" and click "Next"
If no drivers show up, then 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.


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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.


More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
​

 

[tjobeid]

Drivers seam fine no errors. I dont know what the hell is going on. My pc works perfect with vista.

 

[usasma]

Let Driver Verifier run for at least a day of normal usage. If it doesn't give a crash then, we'll select some more drivers - but that will slow the system down a lot!

 

[bluefalcon]

hi there i have been having the same problem with my computer i run 8 gb of ram not you cheap stuff so you wouldnt expect it to cr--p out but beleave me it does so out come my 8 gbs of ram replaced it with only 4gb of top ram cleared my cmos reset my setting and wam she sparked into life this has happened a few times to me in the past due to a 24000 3D MARK 06 its haed on your gear there you go thanks for reading this happy computing