Hi,Just looking for some input into this problem please...It's fair to say that since being built my PC regularly suffers from blue screens / lockups. I've learnt to live with it.I once borrowed an nVidia card (can't remember specs) but during testing (approx 2 weeks) problems were never encountered. However this was when I was running XP. Strangely after testing the nVidia and reinstalling the ATI, the problems became liveable (i.e. not very frequent).The release of the new 737 has made my problems slightly worse. Now, to be very clear, I am not saying there is anything wrong with the 737 - I suspect the load it places on my machine, stresses the machine. Again, not a fault of the 737.Also, I can make long flights using the PC. e.g. yesterday was 2 sectors (in the 737) - 4:45 and 5:45 using the same plane / situation. The PC never gave me any problems.Additionally I have flown 15 hour routes in the 747 / 10 hours in the 767 without any problems. So a variety of aircraft, with no problems.Certain things are just odd though, e.g. within 2 mins in the sim yesterday (before the 4:45 and 5:45 sectors & from cold), it had blue screened twice!Problems are not limited to FSX.... e.g. once backing up (to USB ext drive), caused a blue screen.Quite often, BSODs are very soon after power on / very early into a flight.Specs are in the signature.Temps as far as I can see are fine - highest cpu temp is 65 degrees c, but tends to be around 60 c.GPU was typically around 56 - 59 degress c.As far as drivers go, the graphics is upto date. Looking around for a chipset driver though (from GigaBytes web site) links me to just an old ATI (video driver) driver. Not sure if a driver exists?!Windows updates are up to date.Latest BIOS applied F8cAlthough I am now running Windows 7, I had similar lock ups on windows XP.One thing that has always struck me as odd, (i only found this out after buying the components) is that the RAM voltage runs at a minimum of 1.6v The Kingston RAM itself requires 1.5v Would this cause problems?Back to FSX, I think my bufferpools setting was originally incorrect. It was set to around 700 MB. I am no longer using bufferpools (usepools=0). By doing so, I have eliminated some odd graphics problems. Too early to say yet, but seems to have improved stability. (can add tweaks back at another time).Also, I am avoiding looking at outside views (of the plane) when flying - may help? I replay afterwards now (fsrecorder recenlty installed).Any help greatly appreciated. PC is just over 2 years old now. No overclocking has been attempted, BIOS runs with default settings.Thanks for reading,Carl Beeby

Do you have Win 7 configured to store minidumps? those are basically crash reports and will help us find what failed when Windows BSOD'edC:WindowsMinidump is the default location for the minidumps. If you have something recent there, you can use Blue Screen View to analize the crashes.Upload a minidump and I'll check it out for you, although the true experts are in the Windows 7 forums and it won't hurt asking there, I'll try to help where I can.BSODs are not always easy to tackle

HiThanks for reply, here is a preview of the BSOD codes - happy to upload the files if you wish. Adding to the 1st post, memtest ran for 12 hours no problems.RegardsCarl

HiThanks for reply, here is a preview of the BSOD codes - happy to upload the files if you wish.Adding to the 1st post, memtest ran for 12 hours no problems.RegardsCarl

Great, those are the minidumps, yes. Can you zip them and upload them here? I think you'll need to change the file extension to "pdf"

Here you go...Thanks again for taking a look.Carl

Both crashes seem related to this "secdrv.sys" driver.I googled it and it's used by windows for security / piracy prevention purposes. Is your Win 7 up to date?

Sorry, it's not secdrv.sys

The files in pink in the BSOD viewer are the files that caused the crash. NTOSKRNL.exe is identified in each crash. It relates to memory. I had this error constantly too when I first set up my system and began overclocking. My memory voltages were off. Look at NickN's article on setting up FSX and tuning it - http://www.simforums.com/Forums/topic29041.html. He has samples for memory speeds/timings and a good discussion of memory settings. Make sure your voltages, speeds and timings are correct in the BIOS. I too ran memtest w/o problem but the system still crashed occasionally until I manually changed some of the memory settings. I haven't seen a BSOD since setting up the system earlier this year.Best regards,Jim

I run the Win debugger to analyze the crash dumps and these are the results:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [F:DownloadsNew folder111311-26114-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: SRV*e:WinDBGsymbols*http://msdl.microsoft.com/download/symbolsExecutable search path is:Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506Machine Name:Kernel base = 0xfffff800`03015000 PsLoadedModuleList = 0xfffff800`0325a670Debug session time: Sun Nov 13 11:20:24.147 2011 (UTC + 1:00)System Uptime: 0 days 0:39:46.287Loading Kernel Symbols........................................................................................................................................................................Loading User SymbolsLoading unloaded module list.....********************************************************************************																			 **						Bugcheck Analysis									**																			 ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 7E, {ffffffffc0000005, fffff800030afdb8, fffff880021b6788, fffff880021b5fe0}Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31 )Followup: MachineOwner---------2: kd> !analyze -v********************************************************************************																			 **						Bugcheck Analysis									**																			 ********************************************************************************SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)This is a very common bugcheck.  Usually the exception address pinpointsthe driver/function that caused the problem.  Always note this addressas well as the link date of the driver/image that contains this address.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff800030afdb8, The address that the exception occurred atArg3: fffff880021b6788, Exception Record AddressArg4: fffff880021b5fe0, Context Record AddressDebugging Details:------------------EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.FAULTING_IP:nt!MmUnlockPages+3e8fffff800`030afdb8 f04d0fc1aa50020000 lock xadd qword ptr [r10+250h],r13EXCEPTION_RECORD:  fffff880021b6788 -- (.exr 0xfffff880021b6788)ExceptionAddress: fffff800030afdb8 (nt!MmUnlockPages+0x00000000000003e8)   ExceptionCode: c0000005 (Access violation)  ExceptionFlags: 00000000NumberParameters: 2   Parameter[0]: 0000000000000000   Parameter[1]: ffffffffffffffffAttempt to read from address ffffffffffffffffCONTEXT:  fffff880021b5fe0 -- (.cxr 0xfffff880021b5fe0)rax=0000000000000000 rbx=0000000000000002 rcx=00000000000000c9rdx=fffff88002f64180 rsi=fffffa800a1d5658 rdi=0000000000000000rip=fffff800030afdb8 rsp=fffff880021b69c0 rbp=0000000000000000r8=0000058000000000  r9=0000000000000000 r10=f7fffa8006eef060r11=0000000000000082 r12=0000000000000001 r13=ffffffffffffffffr14=fffffa800a1d5620 r15=fffffa800a1d5658iopl=0		 nv up ei ng nz ac po cycs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b			 efl=00010297nt!MmUnlockPages+0x3e8:fffff800`030afdb8 f04d0fc1aa50020000 lock xadd qword ptr [r10+250h],r13 ds:002b:f7fffa80`06eef2b0=????????????????Resetting default scopeCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULTPROCESS_NAME:  fsx.exeCURRENT_IRQL:  0ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.EXCEPTION_PARAMETER1:  0000000000000000EXCEPTION_PARAMETER2:  ffffffffffffffffREAD_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c4100ffffffffffffffffFOLLOWUP_IP:dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31fffff880`04833ed5 4c8b1ddcd1fdff  mov	 r11,qword ptr [dxgmms1!_imp_g_loggerInfo (fffff880`048110b8)]BUGCHECK_STR:  0x7ELAST_CONTROL_TRANSFER:  from fffff88004833ed5 to fffff800030afdb8STACK_TEXT:  fffff880`021b69c0 fffff880`04833ed5 : 00000002`03fb0082 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmUnlockPages+0x3e8fffff880`021b6a50 fffff880`04832cc3 : 00000000`00000000 fffff880`0482e642 fffffa80`000000d8 00000000`00000000 : dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+0x31fffff880`021b6a80 fffff880`0482d8e5 : fffff8a0`13be7890 fffff8a0`13be7890 fffffa80`0a1c3700 00000000`00000000 : dxgmms1!VIDMM_SEGMENT::UnlockAllocationBackingStore+0x87fffff880`021b6ae0 fffff880`0482025d : fffff8a0`13be7890 fffffa80`08b4d000 fffffa80`0a1c3740 fffffa80`08b4d000 : dxgmms1!VIDMM_APERTURE_SEGMENT::EvictResource+0x155fffff880`021b6b30 fffff880`0481b358 : fffffa80`06de4bd0 00000000`00000080 00000000`00000000 fffff880`021b6ca0 : dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x96dfffff880`021b6c50 fffff880`0483916d : fffffa80`00000000 fffffa80`08b1d010 00000000`0000000f fffff880`0483af09 : dxgmms1!VidMmiProcessTerminationCommand+0x4cfffff880`021b6ca0 fffff880`048383f8 : fffff800`00b96080 fffffa80`078d97c0 00000000`00000000 fffffa80`08b1d010 : dxgmms1!VidSchiSubmitDeviceCommand+0x39fffff880`021b6cd0 fffff880`04837e96 : 00000000`00000000 fffffa80`078d97c0 00000000`00000080 fffffa80`08b1d010 : dxgmms1!VidSchiSubmitQueueCommand+0xb0fffff880`021b6d00 fffff800`0332cfee : 00000000`051e1fbf fffffa80`08b19060 fffffa80`06a25040 fffffa80`08b19060 : dxgmms1!VidSchiWorkerThread+0xd6fffff880`021b6d40 fffff800`030835e6 : fffff800`03207e80 fffffa80`08b19060 fffff800`03215cc0 fffff880`01268a20 : nt!PspSystemThreadStartup+0x5afffff880`021b6d80 00000000`00000000 : fffff880`021b7000 fffff880`021b1000 fffff880`021b6680 00000000`00000000 : nt!KxStartSystemThread+0x16SYMBOL_STACK_INDEX:  1SYMBOL_NAME:  dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: dxgmms1IMAGE_NAME:  dxgmms1.sysDEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1STACK_COMMAND:  .cxr 0xfffff880021b5fe0 ; kbFAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31Followup: MachineOwner---------2: kd> lmvm dxgmms1start			 end				 module namefffff880`04800000 fffff880`04846000   dxgmms1	(pdb symbols)		  e:windbgsymbolsdxgmms1.pdb0901C357E9E846EE8C2FBCC8107163201dxgmms1.pdb	Loaded symbol image file: dxgmms1.sys	Mapped memory image file: e:windbgsymbolsdxgmms1.sys4CE799C146000dxgmms1.sys	Image path: dxgmms1.sys	Image name: dxgmms1.sys	Timestamp:		Sat Nov 20 10:49:53 2010 (4CE799C1)	CheckSum:		 00047A89	ImageSize:		00046000	File version:	 6.1.7601.17514	Product version:  6.1.7601.17514	File flags:	   0 (Mask 3F)	File OS:		  40004 NT Win32	File type:		3.7 Driver	File date:		00000000.00000000	Translations:	 0409.04b0	CompanyName:	  Microsoft Corporation	ProductName:	  Microsoft® Windows® Operating System	InternalName:	 dxgmms1.sys	OriginalFilename: dxgmms1.sys	ProductVersion:   6.1.7601.17514	FileVersion:	  6.1.7601.17514 (win7sp1_rtm.101119-1850)	FileDescription:  DirectX Graphics MMS	LegalCopyright:   © Microsoft Corporation. All rights reserved.

Apparently dxgmms1.sys (directX) crashed the system while running FSXthe other crash:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [F:DownloadsNew folder111311-29281-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: SRV*e:WinDBGsymbols*http://msdl.microsoft.com/download/symbolsExecutable search path is:Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506Machine Name:Kernel base = 0xfffff800`03057000 PsLoadedModuleList = 0xfffff800`0329c670Debug session time: Sun Nov 13 10:39:56.932 2011 (UTC + 1:00)System Uptime: 0 days 0:12:41.446Loading Kernel Symbols........................................................................................................................................................................Loading User SymbolsLoading unloaded module list.....********************************************************************************																			 **						Bugcheck Analysis									**																			 ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck BE, {fffff960002a4010, b9a00001cba9b021, fffff88008ebc780, b}Probably caused by : win32k.sys ( win32k!ENUMUNDERLAYS::bEnum+363 )Followup: MachineOwner---------1: kd> !analyze -v********************************************************************************																			 **						Bugcheck Analysis									**																			 ********************************************************************************ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)An attempt was made to write to readonly memory.  The guilty driver is on thestack trace (and is typically the current instruction pointer).When possible, the guilty driver's name (Unicode string) is printed onthe bugcheck screen and saved in KiBugCheckDriver.Arguments:Arg1: fffff960002a4010, Virtual address for the attempted write.Arg2: b9a00001cba9b021, PTE contents.Arg3: fffff88008ebc780, (reserved)Arg4: 000000000000000b, (reserved)Debugging Details:------------------CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULTBUGCHECK_STR:  0xBEPROCESS_NAME:  iexplore.exeCURRENT_IRQL:  0TRAP_FRAME:  fffff88008ebc780 -- (.trap 0xfffff88008ebc780)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=000000008023b7ef rbx=0000000000000000 rcx=fffff900c375c078rdx=fffff900c00c0010 rsi=0000000000000000 rdi=0000000000000000rip=fffff96000049cbf rsp=fffff88008ebc910 rbp=fffff88008ebce28r8=fffff88008ebce28  r9=fffff88008ebce38 r10=0000000000000000r11=fffff900c375c010 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0		 nv up ei pl nz na pe ncwin32k!ENUMUNDERLAYS::bEnum+0x363:fffff960`00049cbf ff154ba32500	call	qword ptr [win32k!_imp_PsGetCurrentThreadWin32Thread (fffff960`002a4010)] ds:fffff960`002a4010={nt!PsGetCurrentThreadWin32Thread (fffff800`030ee500)}Resetting default scopeLAST_CONTROL_TRANSFER:  from fffff8000307f5d2 to fffff800030d3c40STACK_TEXT:  fffff880`08ebc618 fffff800`0307f5d2 : 00000000`000000be fffff960`002a4010 b9a00001`cba9b021 fffff880`08ebc780 : nt!KeBugCheckExfffff880`08ebc620 fffff800`030d1d6e : 00000000`00000001 fffff960`002a4010 00000000`0000cc00 fffff900`c375c078 : nt! ?? ::FNODOBFM::`string'+0x45c6efffff880`08ebc780 fffff960`00049cbf : 00000000`00000000 fffffa80`077fb660 00000000`00000001 00000000`00000000 : nt!KiPageFault+0x16efffff880`08ebc910 fffff960`001a4f13 : fffff900`c00c0010 00000000`00000000 00000000`0000cccc fffff900`c00f6028 : win32k!ENUMUNDERLAYS::bEnum+0x363fffff880`08ebca30 fffff960`001a4f7c : fffff900`c00f6028 00000000`00000000 00000000`00000000 fffff880`08ebcc98 : win32k!SpBitBlt+0x843fffff880`08ebce20 fffff960`0025fb3b : fffff900`c073f810 fffff960`0008b9b1 f8000000`f8000000 07ffffff`07ffffff : win32k!SpCopyBits+0x44fffff880`08ebce90 fffff960`00234e6e : 00000084`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : win32k!OffCopyBits+0xc7fffff880`08ebcef0 fffff960`002351a3 : 00000000`00000000 fffff900`c073f828 00000000`00000000 fffff900`c23f5380 : win32k!MulBitBlt+0x666fffff880`08ebd150 fffff960`001f7034 : 00000000`00000000 00000000`00000000 fffff900`c0132010 fffff900`c2c36bd0 : win32k!MulCopyBits+0x14bfffff880`08ebd1e0 fffff960`00089b87 : 00000000`13011430 00000000`00000000 fffff880`08ebd520 00000000`0314caf8 : win32k!NtGdiBitBltInternal+0xc94fffff880`08ebd3c0 fffff800`030d2ed3 : fffffa80`08754c50 00000000`00000000 00000000`00000001 00000000`00000000 : win32k!NtGdiBitBlt+0x5bfffff880`08ebd430 00000000`7515fe5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000000`0314cad8 fffff800`030cb210 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7515fe5afffff880`08ebd880 fffff900`c0a8fb60 : 00000000`00000000 0000008d`000004fc fffff800`030dd82b 00000000`0000289b : nt!KiCallUserModefffff880`08ebd888 00000000`00000000 : 0000008d`000004fc fffff800`030dd82b 00000000`0000289b fffff880`08ebddb0 : 0xfffff900`c0a8fb60STACK_COMMAND:  kbFOLLOWUP_IP:win32k!ENUMUNDERLAYS::bEnum+363fffff960`00049cbf ff154ba32500	call	qword ptr [win32k!_imp_PsGetCurrentThreadWin32Thread (fffff960`002a4010)]SYMBOL_STACK_INDEX:  3SYMBOL_NAME:  win32k!ENUMUNDERLAYS::bEnum+363FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: win32kIMAGE_NAME:  win32k.sysDEBUG_FLR_IMAGE_TIMESTAMP:  4e658d5aFAILURE_BUCKET_ID:  X64_0xBE_win32k!ENUMUNDERLAYS::bEnum+363BUCKET_ID:  X64_0xBE_win32k!ENUMUNDERLAYS::bEnum+363Followup: MachineOwner---------1: kd> lmvm win32kstart			 end				 module namefffff960`00000000 fffff960`00313000   win32k	 (pdb symbols)		  e:windbgsymbolswin32k.pdbAA02F0D1D3FE4DCD82C925DAEB3866E92win32k.pdb	Loaded symbol image file: win32k.sys	Mapped memory image file: e:windbgsymbolswin32k.sys4E658D5A313000win32k.sys	Image path: win32k.sys	Image name: win32k.sys	Timestamp:		Tue Sep 06 05:02:50 2011 (4E658D5A)	CheckSum:		 0030D2B2	ImageSize:		00313000	File version:	 6.1.7601.17685	Product version:  6.1.7601.17685	File flags:	   0 (Mask 3F)	File OS:		  40004 NT Win32	File type:		3.7 Driver	File date:		00000000.00000000	Translations:	 0409.04b0	CompanyName:	  Microsoft Corporation	ProductName:	  Microsoft® Windows® Operating System	InternalName:	 win32k.sys	OriginalFilename: win32k.sys	ProductVersion:   6.1.7601.17685	FileVersion:	  6.1.7601.17685 (win7sp1_gdr.110905-1503)	FileDescription:  Multi-User Win32 Driver	LegalCopyright:   © Microsoft Corporation. All rights reserved.

The multi-user driver of Windows crashed in the iexplorer process (Internet Explorer)I'm still learning all this stuff, so I don't really know what this means exactly. Posting these reports in the Windows 7 forums may help

I run the Win debugger to analyze the crash dumps and these are the results:The multi-user driver of Windows crashed in the iexplorer process (Internet Explorer)I'm still learning all this stuff, so I don't really know what this means exactly. Posting these reports in the Windows 7 forums may help

OK thanks again for looking

The files in pink in the BSOD viewer are the files that caused the crash. NTOSKRNL.exe is identified in each crash. It relates to memory. I had this error constantly too when I first set up my system and began overclocking. My memory voltages were off. Look at NickN's article on setting up FSX and tuning it - http://www.simforums...topic29041.html. He has samples for memory speeds/timings and a good discussion of memory settings. Make sure your voltages, speeds and timings are correct in the BIOS. I too ran memtest w/o problem but the system still crashed occasionally until I manually changed some of the memory settings. I haven't seen a BSOD since setting up the system earlier this year.Best regards,Jim

Just interested in this Jim as I think (as I outlined in the OP) that the lowest voltage the board runs is 1.6v yet these sticks are designed (standard speeds) for 1.5v.Although RAM is running at defaults now, I have tried changing the speeds / voltage in the past and when done so, perhaps made the problem worse. So on that basis, wonder if it is being caused by RAM....RegardsCarl

Just interested in this Jim as I think (as I outlined in the OP) that the lowest voltage the board runs is 1.6v yet these sticks are designed (standard speeds) for 1.5v.Although RAM is running at defaults now, I have tried changing the speeds / voltage in the past and when done so, perhaps made the problem worse. So on that basis, wonder if it is being caused by RAM....RegardsCarl

I just got my memory settings in the bios set properly after almost a year. Stability testing of memory showed system was stable but still had periodic crashes. I've been working on the g3d CTD issue and discovered improper settings were the cause of my problems. You might check your virtual memory performance settings (page file). I have found that setting your own settings (unless you are a computer expert) only creates more problems. I found that 'System Managed Size' worked the best. The top setting where it says Windows will manage all harddrives automatically is buggy too.Best regards,Jim

I run the Win debugger to analyze the crash dumps and these are the results:

Which Win debugger is this?Can you also run it on a GD3.dll CTD over at this thread?Cheers,- jahman.

Which Win debugger is this?Can you also run it on a GD3.dll CTD over at this thread?Cheers,- jahman.

It's WinDBG, from the Windows SDK.You can attach an executable and there are some debug options, but I have no idea if it can be of any help for tracing CTD's. So far all I've managed to do is to analize BSOD dumps with it

It's WinDBG, from the Windows SDK.You can attach an executable and there are some debug options, but I have no idea if it can be of any help for tracing CTD's. So far all I've managed to do is to analize BSOD dumps with it

Doesn't a CTD generate a dump as well (likely in a different format, i.e. XML)?Cheers,- jahman.

Doesn't a CTD generate a dump as well (likely in a different format, i.e. XML)?Cheers,- jahman.

Looks like the CTD logs are stored in files with the .evtx & .etl extensions in the C:WindowsSystem32winevtLogs folder.Those are the logs that show up in the Event Viewer, not sure WinDBG can do anything with them