יום שני 27 פברואר 2012 02:49
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
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?
יום שני 27 פברואר 2012 14:25
As you possible have issues with your HDD, i would recommend contacting your manufacturer Technical Support.
You can also use Microsoft Skydrive to upload dump files (c:\windows\minidump) and post a link here so that I can debug it for you.
Another option is to contact Microsoft CSS for assistance.
יום שלישי 28 פברואר 2012 00:59sounds like a HDD or controller issue. It shouldn't matter what SATA port you use. What options do you have in the bios for configuring the drives? You may want to play around with those. check to make sure you have the latest chipset / disk controller drivers. also run a surface scan on that disk just to be sure of any disk corruption.
- הוצע כתשובה על-ידי Bill - MCSE יום שלישי 28 פברואר 2012 15:14
יום שלישי 28 פברואר 2012 03:16
<iframe title ="Preview" scrolling="no" marginheight="0" marginwidth="0" frameborder="0" width="98px" height="120px" style="padding:0;background-color:#fcfcfc;" src="</iframe">https://skydrive.live.com/embed?cid=59B168C07D6196A8&resid=59B168C07D6196A8%21107&authkey=AKZnmGfTogVrQVU"></iframe>
Hopefully I did that right. I've never used it before. Thanks for the help.
יום רביעי 29 פברואר 2012 12:33Hi,
Bug Check 0x109: CRITICAL_STRUCTURE_CORRUPTION)
This indicates that the kernel has detected critical kernel code or data corruption. 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.
Please try to perform a memory test to check if you could find any errors information:
Please also update all possible drivers and uninstall all programs that you don't use.
TechNet Community Support
יום חמישי 01 מרץ 2012 20:29
Yah I'm going through all the memory sticks now. I originally had all 4 in and ran memtest 86+ all night, but it seems to have gotten stuck on the third run. So now I've been running one stick at a time and letting it go over night because I think it's a bad stick. Thanks for the help. I'll keep this post updated when I figure out what the issue is.
- סומן כתשובה על-ידי Arthur XieMicrosoft Contingent Staff, Moderator יום שני 05 מרץ 2012 06:47