Windows 7: Microsoft Flight Simulator x Accelerator Blue Screen of Death

erikschand · 13 Feb 2012

Help neededEverytime i play a game my computer crashed bluescreeni attach minidump and BSOD.txt files, let me hear from youOperating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.110622-1506)
Language: Danish (Regional Setting: Danish)
System Manufacturer: To Be Filled By O.E.M.
System Model: To Be Filled By O.E.M.
BIOS: BIOS Date: 01/05/09 14:14:00 Ver: 08.00.15
Motherboard: 750a SLI NVIDIA
Processor: AMD Phenom(tm) II X4 945 Processor (4 CPUs), ~3.0GHz
Memory: 8192MB RAM
Available OS Memory: 8192MB RAM
Page File: 1892MB used, 14487MB available
DirectX Version: DirectX 11
DX Setup Parameters: Not found
System DPI Setting: 96 DPI (100 percent)

writhziden · 15 Feb 2012

Code:

Loading Dump File [F:\BSODDmpFiles\erikschand\021412-29952-01\021412-29952-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0305b000 PsLoadedModuleList = 0xfffff800`032a0670
Debug session time: Tue Feb 14 05:17:24.146 2012 (GMT-7)
System Uptime: 0 days 1:05:36.848
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff800030f7e11, fffff880009a9968, fffff880009a91c0}

Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+181 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800030f7e11, The address that the exception occurred at
Arg3: fffff880009a9968, Exception Record Address
Arg4: fffff880009a91c0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!MiUnlinkFreeOrZeroedPage+181
fffff800`030f7e11 48893cc2        mov     qword ptr [rdx+rax*8],rdi

EXCEPTION_RECORD:  fffff880009a9968 -- (.exr 0xfffff880009a9968)
ExceptionAddress: fffff800030f7e11 (nt!MiUnlinkFreeOrZeroedPage+0x0000000000000181)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880009a91c0 -- (.cxr 0xfffff880009a91c0)
rax=fa00000000690624 rbx=fffffa8003ab9120 rcx=0000000000000008
rdx=fffffa8000000008 rsi=fffffa80078028f0 rdi=ffffffffffffffff
rip=fffff800030f7e11 rsp=fffff880009a9ba0 rbp=0000000000000006
 r8=0000000000000000  r9=0000000000000000 r10=fffffa8007802910
r11=fffff880009a9be0 r12=0000000000000000 r13=0000000000000001
r14=00000000ffffffff r15=0000000000000001
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
nt!MiUnlinkFreeOrZeroedPage+0x181:
fffff800`030f7e11 48893cc2        mov     qword ptr [rdx+rax*8],rdi ds:002b:cffffa80`03483128=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330a100
 ffffffffffffffff 

FOLLOWUP_IP: 
nt!MiUnlinkFreeOrZeroedPage+181
fffff800`030f7e11 48893cc2        mov     qword ptr [rdx+rax*8],rdi

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff8000309f9be to fffff800030f7e11

STACK_TEXT:  
fffff880`009a9ba0 fffff800`0309f9be : 00000000`000000ff 00000000`00000006 00000000`00000000 00000000`00000000 : nt!MiUnlinkFreeOrZeroedPage+0x181
fffff880`009a9c10 fffff800`03372fee : fffffa80`07931b60 00000000`00000080 fffffa80`07931040 fffff800`030c95d9 : nt!MmZeroPageThread+0x541
fffff880`009a9d40 fffff800`030c95e6 : fffff800`0324de80 fffffa80`07931b60 fffff800`0325bcc0 20000002`9881f609 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a98b0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiUnlinkFreeOrZeroedPage+181

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

STACK_COMMAND:  .cxr 0xfffff880009a91c0 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x7E_nt!MiUnlinkFreeOrZeroedPage+181

BUCKET_ID:  X64_0x7E_nt!MiUnlinkFreeOrZeroedPage+181

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

Possible causes are Memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
Thanks to Dave76 for help understanding possible causes.

We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

If you are overclocking any hardware, please stop.
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

If you swap any memory components, follow these steps for ESD safety:
1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.
Please follow the http://www.sevenforums.com/crashes-d...tructions.html to provide us with more information about your system and the crashes so we may provide more informed troubleshooting steps.

erikschand · 17 Feb 2012

Hi againi have testet my memory, and 8 gb pass and was ok, maybe it is the 12V battery it's to old? Also when i start my computer i have CMOS Bad Checksum, i also follow all instruction Shut down and turn off your computer. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops) Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. Once these steps have been followed, it is safe to remove and replace components within your computer.but still have blue scree crash , even when i start to check my computer with ESET Antivirus, then my computer crash, help

writhziden · 17 Feb 2012

When was the last time you cleared your CMOS? How To Clear CMOS (Reset BIOS) If you continue to get the CMOS Bad Checksum error after clearing the CMOS, I would recommend replacing the battery for it.

Also, our hands are tied trying to help until you follow the http://www.sevenforums.com/crashes-d...tructions.html

erikschand · 18 Feb 2012

Hi thereI took the 12V battery off, for 30 min. and turn the computer on nothing happend for 4 hours, then i turn of computer and then computer booted with

QS training failed on previous boot, reverted to slower DRAM speed Press F1 to Resumen, again i did, and again it say:CMOS Bad Checksum, the motherboard is brand new ???? help

writhziden · 18 Feb 2012

If the motherboard is brand new, I would suggest that you contact the manufacturer. They will provide support for it and troubleshooting steps for the problem you are facing.

Before you call, you may want to check all connections and make sure you do not have a connector on the wrong pins or a component/module/card that is not properly seated in its slot.

erikschand · 18 Feb 2012

Hi writhziden
Thank you very much, i'll will do that, thank you very much for your very good support, best regard erikschand

writhziden · 18 Feb 2012

You're welcome. Let us know if you find a resolution so others can benefit if they have similar problems.

Also, you may want to try flashing the BIOS with the newest update, but do not use a beta version. That can fix these problems, as well. If you already have the latest version, flash the BIOS with that version again.

Did you find out what the issue was regarding the motherboard?

Windows 7: Microsoft Flight Simulator x Accelerator Blue Screen of Death

Microsoft Flight Simulator x Accelerator Blue Screen of Death problems?