Vist gets a blue screen - Pls Help

C

cory

Member
I installed Vista and XP into a dual boot configuration, and they can both boot. When i boot into XP it works perfect. But after I boot into XP and try to go back into Vista I get a blue screen when I type my password. I have to boot vista into safe mode and let it recover before i can boot into Vista with no problems. Vista boots fine until i boot into XP again, then the problem starts gain.
 
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {b9d548d5-011a-11dc-8f06-cf8ad8d7ca21}
displayorder {current}
{5560b7c7-1974-11dc-ab36-00123fe134e3}
toolsdisplayorder {memdiag}
timeout 9

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Windows Vista
locale en-US
inherit {bootloadersettings}
osdevice partition=C:
systemroot \Windows
resumeobject {b9d548d5-011a-11dc-8f06-cf8ad8d7ca21}
nx OptIn

Windows Legacy OS Loader
------------------------
identifier {5560b7c7-1974-11dc-ab36-00123fe134e3}
device partition=C:
path \ntldr
description Microsoft Windows XP
 
This is the info it gives me when I reboot Vista in Safe mode.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: 0000C85C
BCP2: 00000002
BCP3: 00000001
BCP4: 81C118A3
OS Version: 6_0_6000
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini061307-05.dmp
C:\Users\Cory\AppData\Local\Temp\WER-66921-0.sysdata.xml
C:\Users\Cory\AppData\Local\Temp\WER7B07.tmp.version.txt
 
sorry guys, figured it out, i opened that dump file in notepad
it was complete jibberish but i looked around and saw an old driver i was using to overclock my gpu. I knew it wasnt supposed to be there so i removed it and it fixed everything.
 
Let me guess, ATiTool? It gave me the same problem too :smile:

I'm glad you got it to work. Just to be sure, I ran the dump file you posted in the other thread (please don't open multiple threads!), and this is what I got:

Code: 
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: 0000c85c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 81c118a3, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d11780
 0000c85c 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiCheckForControlAreaDeletion+3e
81c118a3 890a            mov     dword ptr [edx],ecx

CUSTOMER_CRASH_COUNT:  5

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  csrss.exe

TRAP_FRAME:  8955bc3c -- (.trap 0xffffffff8955bc3c)
ErrCode = 00000000
eax=002c80c4 ebx=8365cc58 ecx=00001000 edx=fffff000 esi=002c6000 edi=002c8000
eip=81e8945c esp=8955bcb0 ebp=8955bcb8 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!ProbeForWrite+0x39:
81e8945c 8a06            mov     al,byte ptr [esi]          ds:0023:002c6000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from 81c118a3 to 81c8fc44

STACK_TEXT:  
8955ba64 81c118a3 badb0d00 0000c85c 81cace2d nt!KiTrap0E+0x2ac
8955bad8 81c1dc02 81d12340 8262048c 00013705 nt!MiCheckForControlAreaDeletion+0x3e
8955bb14 81c1184f 8262048c ffffffff 00000016 nt!MiRestoreTransitionPte+0x13d
8955bb28 81c117a4 8277fbd8 ffffffff 8277fed8 nt!MiRemoveStandbyPage+0x88
8955bb38 81caee46 8376a020 00000016 8376a1f0 nt!MiRemoveLowestPriorityStandbyPage+0x24
8955bb6c 81cbd2ab 00000016 c0001630 00000080 nt!MiRemovePageZeroPreferred+0x1a8
8955bbac 81cab7ed 00000000 002c6000 c0001630 nt!MiResolveDemandZeroFault+0x2d5
8955bc24 81c8fa74 00000000 002c6000 00000000 nt!MmAccessFault+0x19fb
8955bc24 81e8945c 00000000 002c6000 00000000 nt!KiTrap0E+0xdc
8955bcb8 81d930bc 002c5fd8 00001ff4 00000001 nt!ProbeForWrite+0x39
8955bd38 81c8c96a 82e36d98 00000000 00000000 nt!NtReadFile+0x91
8955bd38 77440f34 82e36d98 00000000 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
04adf340 00000000 00000000 00000000 00000000 0x77440f34


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiCheckForControlAreaDeletion+3e
81c118a3 890a            mov     dword ptr [edx],ecx

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiCheckForControlAreaDeletion+3e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4549ae00

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_W_nt!MiCheckForControlAreaDeletion+3e

BUCKET_ID:  0xA_W_nt!MiCheckForControlAreaDeletion+3e

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


According to that particular dump file, it was caused by memory corruption. This does not necessarily mean that your memory is to blame, you usually have to check 3 or 4 dump files to get a driver name.

However, if you still get BSODs, then you should probably run the Windows Memory Diagnostics Tool (press tab at the bootloader).
 
Back
Top