Hi, I just got a new desktop, and on the 1st day of usage, already got a blue screen while playing a game (I had about 5-6 other applications running at the same time too, i.e. browser, instant messenger, etc). :( Can you tell me what this dump result means? I got the result from the WinDbg tool. Could it be a memory corruption--bad ram or ram not seated tightly? Thanks! Info from dialog box after rebooting: =========================================== Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional information about the problem: BCCode: 109 BCP1: A3A039D8ADF30620 BCP2: B3B7465F0071415E BCP3: FFFFF80000B95080 BCP4: 0000000000000002 OS Version: 6_1_7601 Service Pack: 1_0 Product: 768_1 Files that help describe the problem: C:\Windows\Minidump\092812-35162-01.dmp C:\Users\Linh\AppData\Local\Temp\WER-76939-0.sysdata.xml Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt Info from WinDbg tool: =========================================== CRITICAL_STRUCTURE_CORRUPTION (109) This bugcheck is generated when the kernel detects that critical kernel code or data have been corrupted. There are generally three causes for a corruption: 1) A driver has inadvertently or deliberately modified critical kernel code or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx 2) A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was booted. Normal breakpoints, "bp", can only be set if the debugger is attached at boot time. Hardware breakpoints, "ba", can be set at any time. 3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data. Arguments: Arg1: a3a039d8adf30620, Reserved Arg2: b3b7465f0071415e, Reserved Arg3: fffff80000b95080, Failure type dependent information Arg4: 0000000000000002, Type of corrupted region, can be 0 : A generic data region 1 : Modification of a function or .pdata 2 : A processor IDT 3 : A processor GDT 4 : Type 1 process list corruption 5 : Type 2 process list corruption 6 : Debug routine modification 7 : Critical MSR modification Debugging Details: ------------------ BUGCHECK_STR: 0x109 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800032d21c0 STACK_TEXT: fffff880`037b6498 00000000`00000000 : 00000000`00000109 a3a039d8`adf30620 b3b7465f`0071415e fffff800`00b95080 : nt!KeBugCheckEx STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: BAD_STACK Followup: MachineOwner

This error typically indicates that a driver corrupted or attempted to patch the kernel or that there was a RAM issue in the particular DIMM(s) holding the kernel mode code. This is typically not the only blue screen for a system if this is a hardware issue, but may also be accompanied by other blue screens indicating memory issues or driver-related memory corruption (often with a specific exception code of 0xc0000005 STATUS_ACCESS_VIOLATION). If it is solely due to the driver (and not a hardware issue), parameter 4 will be between 0 and 7 indicating what the driver was doing that is not allowed by Microsoft (viruses that attempt to patch the kernel may also cause this error). Further troubleshooting/fixes involve determining the nature of the problem (hardware v. software). If it is a hardware issue, troubleshooting falls along the lines of troubleshooting memory problems. If it is specifically due to a driver engaging in an unsupported practice, this driver should be updated to a current version or disabled. http://mikemstech.blogspot.it/2011/11/troubleshooting-memory-errors.html Marco Adamo

This error typically indicates that a driver corrupted or attempted to patch the kernel or that there was a RAM issue in the particular DIMM(s) holding the kernel mode code. This is typically not the only blue screen for a system if this is a hardware issue, but may also be accompanied by other blue screens indicating memory issues or driver-related memory corruption (often with a specific exception code of 0xc0000005 STATUS_ACCESS_VIOLATION). If it is solely due to the driver (and not a hardware issue), parameter 4 will be between 0 and 7 indicating what the driver was doing that is not allowed by Microsoft (viruses that attempt to patch the kernel may also cause this error). Further troubleshooting/fixes involve determining the nature of the problem (hardware v. software). If it is a hardware issue, troubleshooting falls along the lines of troubleshooting memory problems. If it is specifically due to a driver engaging in an unsupported practice, this driver should be updated to a current version or disabled. http://mikemstech.blogspot.it/2011/11/troubleshooting-memory-errors.html Marco Adamo

Alright, thanks Marco! It's only happened once so far (while playing a WOW-like game), and I've only been using the new desktop for about 1 day so far. I updated to the lastest drivers for my graphics card before playing the game. I'll start a log in case more blue screens happen.

Wow I wrote those posts in Addygol's response. I'm surprised people link to them... See here for my OP on this issue http://mikemstech.blogspot.com/2012/01/troubleshooting-0x109.html If it happens repeatedly AND the analysis is always inconclusive AND the memory test comes out ok. then you should enable driver verifier and see if the issue can be tired to a specific driver http://mikemstech.blogspot.com/2011/12/enable-driver-verifier-to-help-identify.html -- Mike Burr Mike's Technology and Finance Blog Learn to Troubleshoot Windows BSODs