Hi,I`m experiencing a problem with Windows 7!
Last night I installed windows 7 ultimate x86 and sometimes the screen goes blue with something writen on it but i cant read what it sais because it restarts very fast.
This happened to me when I tried to install Aion game(installed with no problems on XP)and it happened again today when I tried to copy Aion game folder from a drive to another.
This one was caused by hardware. Probably memory.
I would
download memtestx86 snd run it for 5 passes.
run a system file check
type cmd in search>right click and run as admin>sfc /scannow
If you are overclocking STOP
Ken
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\021110-22546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82818000 PsLoadedModuleList = 0x82957570
Debug session time: Thu Feb 11 07:58:15.255 2010 (GMT-5)
System Uptime: 0 days 5:29:00.615
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {800, 2, 1, 8286da60}
Probably caused by : hardware
Followup: MachineOwner
---------
*** Possible invalid call from 828ab6a2 ( nt!MiUnlinkPageFromLockedList+0x19b )
*** Expected target 8286da30 ( nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x0 )
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: 00000800, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 8286da60, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82977700
Unable to read MiSystemVaType memory at 829570c0
00000800
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeAcquireQueuedSpinLockAtDpcLevel+20
8286da60 8908 mov dword ptr [eax],ecx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: 80e3bae0 -- (.trap 0xffffffff80e3bae0)
ErrCode = 00000002
eax=00000800 ebx=08000000 ecx=80e3bb68 edx=829780d1 esi=83fb4ea0 edi=829780c0
eip=8286da60 esp=80e3bb54 ebp=80e3bb7c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!KeAcquireQueuedSpinLockAtDpcLevel+0x20:
8286da60 8908 mov dword ptr [eax],ecx ds:0023:00000800=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 828ab6a7 to 8286da60
POSSIBLE_INVALID_CONTROL_TRANSFER: from 828ab6a2 to 8286da30
TWO_BIT_ERROR: 1
STACK_TEXT:
80e3bb50 828ab6a7 83fb4ea0 00000001 c0233f48 nt!KeAcquireQueuedSpinLockAtDpcLevel+0x20
80e3bb7c 82886a27 00000000 c0233f48 82943d00 nt!MiUnlinkPageFromLockedList+0x1a0
80e3bbac 82879f71 00000001 8cfd2000 c0233f48 nt!MiResolveTransitionFault+0x537
80e3bc24 82877e13 8cfd2000 00000000 00000000 nt!MiDispatchFault+0x545
80e3bc98 828a41d7 00000001 8cfd2000 00000000 nt!MmAccessFault+0x128f
80e3bd10 828b019d 8472fd48 c0233f4c 00000000 nt!MiInPageSingleKernelStack+0x16c
80e3bd44 8287d917 8472fdbc 80e3bd90 829ffd16 nt!KiInSwapKernelStacks+0x41
80e3bd50 829ffd16 00000000 b5c82376 00000000 nt!KeSwapProcessOrStack+0x78
80e3bd90 828a1159 8287d89f 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: .trap 0xffffffff80e3bae0 ; kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: TWO_BIT_CPU_CALL_ERROR
Followup: MachineOwner
---------
*** Possible invalid call from 828ab6a2 ( nt!MiUnlinkPageFromLockedList+0x19b )
*** Expected target 8286da30 ( nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x0 )
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: 00000800, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 8286da60, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82977700
Unable to read MiSystemVaType memory at 829570c0
00000800
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeAcquireQueuedSpinLockAtDpcLevel+20
8286da60 8908 mov dword ptr [eax],ecx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: 80e3bae0 -- (.trap 0xffffffff80e3bae0)
ErrCode = 00000002
eax=00000800 ebx=08000000 ecx=80e3bb68 edx=829780d1 esi=83fb4ea0 edi=829780c0
eip=8286da60 esp=80e3bb54 ebp=80e3bb7c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!KeAcquireQueuedSpinLockAtDpcLevel+0x20:
8286da60 8908 mov dword ptr [eax],ecx ds:0023:00000800=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 828ab6a7 to 8286da60
POSSIBLE_INVALID_CONTROL_TRANSFER: from 828ab6a2 to 8286da30
TWO_BIT_ERROR: 1
STACK_TEXT:
80e3bb50 828ab6a7 83fb4ea0 00000001 c0233f48 nt!KeAcquireQueuedSpinLockAtDpcLevel+0x20
80e3bb7c 82886a27 00000000 c0233f48 82943d00 nt!MiUnlinkPageFromLockedList+0x1a0
80e3bbac 82879f71 00000001 8cfd2000 c0233f48 nt!MiResolveTransitionFault+0x537
80e3bc24 82877e13 8cfd2000 00000000 00000000 nt!MiDispatchFault+0x545
80e3bc98 828a41d7 00000001 8cfd2000 00000000 nt!MmAccessFault+0x128f
80e3bd10 828b019d 8472fd48 c0233f4c 00000000 nt!MiInPageSingleKernelStack+0x16c
80e3bd44 8287d917 8472fdbc 80e3bd90 829ffd16 nt!KiInSwapKernelStacks+0x41
80e3bd50 829ffd16 00000000 b5c82376 00000000 nt!KeSwapProcessOrStack+0x78
80e3bd90 828a1159 8287d89f 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: .trap 0xffffffff80e3bae0 ; kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: TWO_BIT_CPU_CALL_ERROR
Followup: MachineOwner
---------
*** Possible invalid call from 828ab6a2 ( nt!MiUnlinkPageFromLockedList+0x19b )
*** Expected target 8286da30 ( nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x0 )