Hi everyone,
I'm new to this forum and hopefully someone can figure out what's going on with my computer.
My computer is experiencing BSOD at random times. On average, it's probably happening twice a week.
Here are my specs:
- Windows 7 Pro x64 OEM
- Hardware is pretty new. Core i5 2500K, Asus P8P67-M board, 8GB of RAM, XFX AMD 5850 Video card
Any help is appreciated!
Last edited by peugeot206; 19 Nov 2011 at 17:43. Reason: Forgot a file
Looks like a problem with your ram from here.
You should test it overnight with memtest86 and see what comes out.
RAM - Test with Memtest86+
Code:Probably caused by : memory_corruption Followup: memory_corruption --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: a3a039d89f39c784, Reserved Arg2: b3b7465ef1b79732, Reserved Arg3: fffff80003012324, Failure type dependent information Arg4: 0000000000000001, 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: CODE_CORRUPTION PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800030c5c40 STACK_TEXT: fffff880`03bb6498 00000000`00000000 : 00000000`00000109 a3a039d8`9f39c784 b3b7465e`f1b79732 fffff800`03012324 : nt!KeBugCheckEx STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -d !hal fffff8000301266f - hal!HalpMcaReadError+34b [ 00:20 ] 1 error : !hal (fffff8000301266f) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: ONE_BIT FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT Followup: memory_corruption ---------
Thanks, buddy. I will run that test and see what it says.
Much appreciated!
I did the MemTest but it didn't show any errors. I didn't stop until I accumulated 7 passes.
Any idea?
Sadly the list of problems after that gets kind of difficult to pin point. I would start looking at other possible causes of a hardware level fault.
For instance is your bios up to date?
Something that occured to me since your system was built recently, did you use old hard drives?
is it possible they could be reaching the end of their life span?
not old hard drives. They are relatively new (about a year old or so). But yes I haven't done a BIOS update so maybe it's time for me to look into those.
Should I do a clean installation of Windows? I surely hope it's not a hard drive problem with the prices being so high now
Look into the firmware first.
Also check firmware for your SSD if you have one ssd firmware has solved many problems for me, also helps to make sure you have 6gb/s rated cable connected to any ssd, this also helps prevent random errors.
Since it is memory corruption (often caused by a driver) might want to run driver verifier.
I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Thanks guys. I will try all your suggestions and will give an update once I have results.
Once again, I appreciate all your assistance.
Quote