Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: PLEASE READ BSOD mostly Graphics and Harddisk errors..at random times

26 Feb 2012   #1

Windows 7 Professional x64 bit
 
 
PLEASE READ BSOD mostly Graphics and Harddisk errors..at random times

Well, here's the system specs to start off...

OS: Windows 7 professional x64 new OS
Motherboard: Gigabyte Z68X-UD3H-B3 rev. 1.3
CPU: Intel Core i5-2500K x4 Clocked at 5801 MHz
RAM: 16gb Corsair Vengeance 1600MHz
Harddisk: Seagate 1TB Serial ATA HD 7200/64MB/SATA-6G
VGA: NVIDIA GeForce GTX 560 Ti
PSU: Corsair Enthusiast Series TX650 V2 650W 80+ Bronze
Cooling: Corsair Air Series A50 Performance CPU Cooler
Network: Realtek PCIe GBE Family Controller
Audio: Realtek High Definition Audio
DirectX 11

Hopefully that's enough.
Anyway I built this computer about 3 weeks ago and immediately had BSOD problems and graphics error kernel problems and whatnot. The graphics one I haven't seen in a little while now so hopefully I took care of that. Now I get random shut offs and blue screens. This is the newest error message: The driver detected a controller error on \Device\Harddisk1\DR2. So what I'm wondering is do I have the harddisk in the right Sata port? I thought I did according to the diagram, currently it's in SATA3_0/1 which is supposed to support Intel 6gb/s connectors...but maybe I should have it in the 3gb/s ones? Any help or ideas would be appreciated.
P.S. I've also ran memtest 86+ and there weren't any errors from that. Next I'm going to remove 3 of the mem sticks and run a test individually on each of those. Temps look great- under 30C for everything and I have ran a stress test for an hour and they stayed around 60C...Is it weird that Windows gives me a 5.9 rating for the Harddrive?


My System SpecsSystem Spec
.

26 Feb 2012   #2

Windows 7 Ultimate x64
 
 

Hi,

Please read the following and respond accordingly.

http://www.sevenforums.com/crashes-d...tructions.html
My System SpecsSystem Spec
26 Feb 2012   #3

Windows 7 Professional x64 bit
 
 
Bleh..I assumed what I posted was enough

I dont have any system reports saved but when i make them I'll post it.
My System SpecsSystem Spec
.


26 Feb 2012   #4

Windows 7 Professional x64 bit
 
 
System Report

Here's the system report...nothing unusual...and the Dump files
My System SpecsSystem Spec
26 Feb 2012   #5

Windows 7 Ultimate x64
 
 

The dump you've provided points to memory corruption, which can be caused by a few things. It's mostly caused by a driver / software issue, but it can be caused by failing memory as well.

Two tests I'd like you to run, Memtest and then Driver Verifier if Memtest comes back clean.

Quote:
Memtest:

Read the following to test your memory for errors.

Driver Verifier:

Read the following to enable Driver Verifier. Use Driver Second if Memtest finds nothing, as it's likely a software / driver issue, we just aren't being told what it is, and hopefully Driver Verifier will than force a crash if it finds the violating driver.

Before enabling Driver Verifier, my recommendation is to set a backup / restore point as in severe cases Driver Verifier can break your Windows. If you have difficulty getting into Windows, boot into Safe Mode and disable Driver Verifier there.
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\Dumps\Windows_NT6_BSOD_jcgriff2\022512-16348-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: 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`03009000 PsLoadedModuleList = 0xfffff800`0324e670
Debug session time: Sun Feb 26 01:20:39.422 2012 (UTC - 5:00)
System Uptime: 0 days 0:52:09.639
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d8a39ca79e, b3b7465ef61a85d8, fffff88001636880, 1}

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: a3a039d8a39ca79e, Reserved
Arg2: b3b7465ef61a85d8, Reserved
Arg3: fffff88001636880, 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 fffff80003085c40

STACK_TEXT:  
fffff880`033a1498 00000000`00000000 : 00000000`00000109 a3a039d8`a39ca79e b3b7465e`f61a85d8 fffff880`01636880 : nt!KeBugCheckEx


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !ndis
    fffff880016368eb - ndis!ndisQueuedMiniportDpcWorkItem+6b
    [ 8b:8a ]
1 error : !ndis (fffff880016368eb)

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
---------
My System SpecsSystem Spec
26 Feb 2012   #6

Windows 7 Professional x64 bit
 
 

Alrighty thanks. Yah I'll take out the 3 memory sticks and run it one at a time then. I ran memtest 86+ and the memory scanner windows comes with but the results were fine, that was with all 4 sticks in though. Thanks for the help, I'll let you know how it goes.
My System SpecsSystem Spec
26 Feb 2012   #7

Windows 7 Ultimate x64
 
 

My pleasure, keep me updated
My System SpecsSystem Spec
27 Feb 2012   #8

Windows 7 Professional x64 bit
 
 

So I ran memtest all night with the 4 in at the same time. It seems to be getting stuck during the 8th test at modulo 20. For some reason it'll just keep running that same test and it wont restart the testing process from there. It just stays at 100% total completed and restart the 8th test again. So I guess it's time to take them out one at a time and see if its a stick or a slot. Thanks again for the advice.
My System SpecsSystem Spec
27 Feb 2012   #9

Windows 7 Ultimate x64
 
 

Great idea, keep me updated.
My System SpecsSystem Spec
27 Feb 2012   #10

Windows 7 Professional x64 bit
 
 

Update again...so I ran each stick one at a time in the 4 slots and let memtest go through 2 full passes..no errors. I'll probably do 1 a night and let it go through the whole 7 passes as recommended but I had a question. My motherboard has 4 Sata connectors. 2 for intel 2 for marvel..each has a 6 gb/s and a 3 gb/s. I have the intel 6gb/s one so I connected my hard drive into that...but im wondering if its a sata port issue since one of my drivers tests said something about my harddisk, and if so what is the difference moving it from one intel port to the other? What would happen if I move it into the marvel 6bg/s port? Thanks
My System SpecsSystem Spec
Reply

 PLEASE READ BSOD mostly Graphics and Harddisk errors..at random times




Thread Tools



Similar help and support threads for2: PLEASE READ BSOD mostly Graphics and Harddisk errors..at random times
Thread Forum
BSOD at random times, idle or in-game (many different errors) BSOD Help and Support
BSOD at random times, errors: 0x00000050, 0x0000001a, 0x0000004e General Discussion
BSoD at random times and pink graphics at times, BSOD Help and Support
BSOD at random times, 2 times/day in the last 4 days BSOD Help and Support
BSOD at random times, other times just lock up BSOD Help and Support
BSOD at random times. Different types of Errors but mainly 0x0000007E BSOD Help and Support
Random BSOD errors happening at random times BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 05:56 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33