Help with random BSODs

  • Thread starter Thread starter Deleted member 651465
  • Start date Start date

Deleted member 651465

Deleted member 651465

Hi guys,

My system has been plagued with random BSODs for a while, and it's driving me mad. It can work anywhere from a few hours to a few minutes, and I've tried everything I usually would to figure it out. All hardware is running at stock speeds.

So far I've:
  • Ran Memtest for 4 days - no errors
  • Tried running memory at stock and on XMP profile
  • Ran Prime95 for 48hrs - no problems or lockups
  • Updated BIOS to latest version - done this twice since I've built the PC
  • Trawled the BIOS for obvious no-nos
  • Reformated the machine - same problem
  • Updated all drivers to the latest version*

*- I've asterisked this point because I've downloaded all drivers through the Asus motherboard download page (except for graphics drivers), so not sure if there are up to date drivers. To be honest, I wouldn't know where to start getting them "manually".

Each time the system BSODs, the error "CRITICAL_STUCTURE_CORRUPTION" appears and it reboots. I believe it's a driver issue causing this, as I never had issues in Windows 7.

I Googled the issue and saw some posts about running the Windows Driver Verifier, so whilst I followed a guide to get it up and running, and rebooted the machine.. I don't actually know how to view the results :o

To be honest, I'm at the point where I just want a working machine. So I've attached a Windows dump of the last crash, to see if anyone can give me a heads up http://db.tt/DBbnmErK

Help please :(
 
Bad HD ? have you run a surface scan on that ?
Tried HDTune, and no errors.

You tried "Who Crashed"? I can help pinpoint the problem...

http://www.resplendence.com/whocrashed

Here's what it says..

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 08/08/2013 16:22:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080813-18390-01.dmp
This was probably caused by the following module: ci.dll (0xFFFFF88000D2D000)
Bugcheck code: 0x109 (0xA3A039D8B554B6C6, 0xB3B7465F07D3531A, 0xFFFFF88000D2D000, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32\ci.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Code Integrity Module
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

This gives me no clues, other than it's a Microsoft module? :o
 
Last edited by a moderator:
Are you temps all ok? If you've got onboard graphics I'd take out your graphics card, just to eliminate it from the mix. Maybe cut down on your RAM too, even though the RAM itself is fine.

if you run from a windows live disc, does it still happen? I usually do that when I'm trying to decide between hardware and software issues, leave it on for several hours from live disc.

If it doesn't crash, that points to drivers. Then you'll just have pretty tedious job of trying to pin down which driver it is by removing them/disabling stuff one by one.

Edit: Obviously don't try lots of things at once, i.e. don't remove graphics card and then boot from live cd, do things incrementally.
 
It's a full watercooled system, so temps are fine. Full spec is:

014.JPG


Kit list
Corsair 650D
Intel 3930K
Asus P8X79 Pro
32GB Corsair Vengeance RAM
256GB Vertex 4 SSD
2x Seagate 3TB in RAID 0
2x Nvidia GTX680 4GB in SLI
Pioneer Blu-ray drive
Corsair AX1200 with cable braid kit
Dual bay res (hidden behind the stock fascias)
Laing D5 pump
XSPC EX240 rad
Phobya 200mm rad
Spectre Pro 200mm fan
3x Scythe GT1850s
XSPC Clearflex 7/16 tubing
EK compression fittings
EK supremacy nickel plexi cpu block
EK plexi FC680 waterblock
EK plexi dual parallel bridge
Mayhem Blue dye

I'm certain it's not hardware as it was all fine in Windows 7, and to be honest I don't have time to mess about testing each RAM stick for 24hrs.

I will check from a Windows Live disc but I don't hold any hope. For example, I switched on the machine for a good hour last night whilst testing the HDDs and using Who Crashed and it was all OK. I'd have to leave it for at least 24hrs to check stability.
 
Last edited by a moderator:
My debugger isn't working properly right now, but it looks like memory errors to me also. I would suggest updating your BIOS firmware and reseating your memory modules.

That is a very sexy rig, by the way.
 
Back
Top Bottom