New Posts  All Forums:Forum Nav:

BSOD Error 1033

post #1 of 14
Thread Starter 
Hi guys,

I've been experiencing random BSODs on my new rig (as seen on my sig). Can someone kindly help me analyze what the dump file is saying? I can't nail down what the problem is! frown.gif

040912-11887-01.zip 25k .zip file

Any advice would be greatly appreciated!! thumb.gif
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-3960X Asus Rampage IV Extreme MSI GTX 560Ti OC G.Skill Ripjaws Z DDR3-2133  
Hard DriveHard DriveOptical DriveOS
Samsung F3 Spinpoint 1TB OCZ Vertex 3 Max IOPS 120GB Sony DRU-880S DVDRW Windows 7 Ultimate 
MonitorKeyboardPowerCase
Samsung 27SA850D Filco Ninja Brown Seasonic Platinum 1000W Silverstone TJ11 
MouseMouse PadAudio
Logitech G700 Razer Destructor Bowers & Wilkins MM-1 
  hide details  
Reply
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-3960X Asus Rampage IV Extreme MSI GTX 560Ti OC G.Skill Ripjaws Z DDR3-2133  
Hard DriveHard DriveOptical DriveOS
Samsung F3 Spinpoint 1TB OCZ Vertex 3 Max IOPS 120GB Sony DRU-880S DVDRW Windows 7 Ultimate 
MonitorKeyboardPowerCase
Samsung 27SA850D Filco Ninja Brown Seasonic Platinum 1000W Silverstone TJ11 
MouseMouse PadAudio
Logitech G700 Razer Destructor Bowers & Wilkins MM-1 
  hide details  
Reply
post #2 of 14
From what i have read its some sort of a memory error. Try testing your memory one stick at a time and if no errors both at once.
Worse than crack.
(14 items)
 
  
CPUMotherboardGraphicsRAM
Intel 3570k Asrock z77 extreme4 Saphire R9 290 Samsung green 
Hard DriveHard DriveOSMonitor
Samsung 840 ssd Samsung f3 spinpoint Win8 pro X-star 2560x1440 27in 
KeyboardCaseMouseMouse Pad
Microsoft x4 Sidewinder Haf 922 Razor Naga Fragmat 
  hide details  
Reply
Worse than crack.
(14 items)
 
  
CPUMotherboardGraphicsRAM
Intel 3570k Asrock z77 extreme4 Saphire R9 290 Samsung green 
Hard DriveHard DriveOSMonitor
Samsung 840 ssd Samsung f3 spinpoint Win8 pro X-star 2560x1440 27in 
KeyboardCaseMouseMouse Pad
Microsoft x4 Sidewinder Haf 922 Razor Naga Fragmat 
  hide details  
Reply
post #3 of 14
Hi smile.gif

**Before we begin, if your system is overclocked in any way, please bring it back to stock values while we diagnose your issues. You're welcome to overclock after we solve your issues.

I've taken a look at your dump, it's a common *F4 bugcheck with the probable cause pointed to csrss.exe. csrss.exe is a core Microsoft file, so it's very unlikely that this is the actual case as Microsoft files are protected by the SFC (System File Checker).

Nothing really out of date in your drivers list or suspicious at this time, so I'm going to recommend enabling Driver Verifier:
Quote:
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.

Dump for reference:
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\040912-11887-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0300c000 PsLoadedModuleList = 0xfffff800`03250650
Debug session time: Mon Apr  9 09:51:16.735 2012 (UTC - 4:00)
System Uptime: 0 days 0:48:25.967
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800e42bb30, fffffa800e42be10, fffff8000338b5f0}

Probably caused by : csrss.exe

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa800e42bb30, Terminating object
Arg3: fffffa800e42be10, Process image file name
Arg4: fffff8000338b5f0, Explanatory message (ascii)

Debugging Details:
------------------


PROCESS_OBJECT: fffffa800e42bb30

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

BUGCHECK_STR:  0xF4_IOERR

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02bd73f8 fffff800`034127b2 : 00000000`000000f4 00000000`00000003 fffffa80`0e42bb30 fffffa80`0e42be10 : nt!KeBugCheckEx
fffff880`02bd7400 fffff800`033bfc9b : ffffffff`ffffffff fffffa80`0ed14970 fffffa80`0e42bb30 fffffa80`0e42bb30 : nt!PspCatchCriticalBreak+0x92
fffff880`02bd7440 fffff800`0333f094 : ffffffff`ffffffff 00000000`00000001 fffffa80`0e42bb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`02bd7490 fffff800`03087fd3 : fffffa80`0e42bb30 fffff800`c0000006 fffffa80`0ed14970 00000000`04200dc0 : nt!NtTerminateProcess+0xf4
fffff880`02bd7510 fffff800`03084570 : fffff800`030d3aff fffff880`02bd7ff8 fffff880`02bd7d50 fffff880`02bd80a0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`02bd76a8 fffff800`030d3aff : fffff880`02bd7ff8 fffff880`02bd7d50 fffff880`02bd80a0 00000000`04201ad0 : nt!KiServiceLinkage
fffff880`02bd76b0 fffff800`030883c2 : fffff880`02bd7ff8 00000000`0003f19f fffff880`02bd80a0 00000000`042015a8 : nt! ?? ::FNODOBFM::`string'+0x48e24
fffff880`02bd7ec0 fffff800`03086f3a : 00000000`00000000 00000000`76ab8af4 00000000`00000001 00000000`0003f19f : nt!KiExceptionDispatch+0xc2
fffff880`02bd80a0 00000000`76fd9c12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`042014f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76fd9c12


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

Followup: MachineOwner
---------

post #4 of 14
Thread Starter 
Hi conzilla, I will consider reseating the rams if all else fails, cuz Noctua D14 is a pain to remove biggrin.gif

Thanks E-Peen for your valuable input! I will monitor again after installing Driver Verifier! Also, what are the chances that this might be a hardware failure?
The system uptime is 48 minutes before the BSOD..so I'm just wondering if it's a faulty component. I tried running memtest and found no errors though but I just want to be sure since this is a new rig smile.gif
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-3960X Asus Rampage IV Extreme MSI GTX 560Ti OC G.Skill Ripjaws Z DDR3-2133  
Hard DriveHard DriveOptical DriveOS
Samsung F3 Spinpoint 1TB OCZ Vertex 3 Max IOPS 120GB Sony DRU-880S DVDRW Windows 7 Ultimate 
MonitorKeyboardPowerCase
Samsung 27SA850D Filco Ninja Brown Seasonic Platinum 1000W Silverstone TJ11 
MouseMouse PadAudio
Logitech G700 Razer Destructor Bowers & Wilkins MM-1 
  hide details  
Reply
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-3960X Asus Rampage IV Extreme MSI GTX 560Ti OC G.Skill Ripjaws Z DDR3-2133  
Hard DriveHard DriveOptical DriveOS
Samsung F3 Spinpoint 1TB OCZ Vertex 3 Max IOPS 120GB Sony DRU-880S DVDRW Windows 7 Ultimate 
MonitorKeyboardPowerCase
Samsung 27SA850D Filco Ninja Brown Seasonic Platinum 1000W Silverstone TJ11 
MouseMouse PadAudio
Logitech G700 Razer Destructor Bowers & Wilkins MM-1 
  hide details  
Reply
post #5 of 14
Quote:
Originally Posted by Microstar View Post

Also, what are the chances that this might be a hardware

We'll know whether or not this is the case once Driver Verifier gives us something to work with smile.gif
post #6 of 14
Thread Starter 
Quote:
Originally Posted by E-Peen View Post

We'll know whether or not this is the case once Driver Verifier gives us something to work with smile.gif

Ok, will keep you posted again. Thank you! smile.gif
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-3960X Asus Rampage IV Extreme MSI GTX 560Ti OC G.Skill Ripjaws Z DDR3-2133  
Hard DriveHard DriveOptical DriveOS
Samsung F3 Spinpoint 1TB OCZ Vertex 3 Max IOPS 120GB Sony DRU-880S DVDRW Windows 7 Ultimate 
MonitorKeyboardPowerCase
Samsung 27SA850D Filco Ninja Brown Seasonic Platinum 1000W Silverstone TJ11 
MouseMouse PadAudio
Logitech G700 Razer Destructor Bowers & Wilkins MM-1 
  hide details  
Reply
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-3960X Asus Rampage IV Extreme MSI GTX 560Ti OC G.Skill Ripjaws Z DDR3-2133  
Hard DriveHard DriveOptical DriveOS
Samsung F3 Spinpoint 1TB OCZ Vertex 3 Max IOPS 120GB Sony DRU-880S DVDRW Windows 7 Ultimate 
MonitorKeyboardPowerCase
Samsung 27SA850D Filco Ninja Brown Seasonic Platinum 1000W Silverstone TJ11 
MouseMouse PadAudio
Logitech G700 Razer Destructor Bowers & Wilkins MM-1 
  hide details  
Reply
post #7 of 14
Thread Starter 
Been running driver verifier for almost a week with all the drivers except those from Microsoft checked..but I haven't had a BSOD yet..what does this mean?
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-3960X Asus Rampage IV Extreme MSI GTX 560Ti OC G.Skill Ripjaws Z DDR3-2133  
Hard DriveHard DriveOptical DriveOS
Samsung F3 Spinpoint 1TB OCZ Vertex 3 Max IOPS 120GB Sony DRU-880S DVDRW Windows 7 Ultimate 
MonitorKeyboardPowerCase
Samsung 27SA850D Filco Ninja Brown Seasonic Platinum 1000W Silverstone TJ11 
MouseMouse PadAudio
Logitech G700 Razer Destructor Bowers & Wilkins MM-1 
  hide details  
Reply
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-3960X Asus Rampage IV Extreme MSI GTX 560Ti OC G.Skill Ripjaws Z DDR3-2133  
Hard DriveHard DriveOptical DriveOS
Samsung F3 Spinpoint 1TB OCZ Vertex 3 Max IOPS 120GB Sony DRU-880S DVDRW Windows 7 Ultimate 
MonitorKeyboardPowerCase
Samsung 27SA850D Filco Ninja Brown Seasonic Platinum 1000W Silverstone TJ11 
MouseMouse PadAudio
Logitech G700 Razer Destructor Bowers & Wilkins MM-1 
  hide details  
Reply
post #8 of 14
Running Driver Verifier for a week was not necessary as Driver Verifier snags culprits within ~24 hours. Usually, the norm for Driver Verifier catching a culprit driver is minutes within bootup, if not, it takes a bit longer.

Since we got no BSODs with DV, it's very unlikely this is a software issue, and we have a hardware issue here. First off, before we begin hardware diagnostics, I would recommend updating to the latest BIOS for your board if you have not done this already. If updating the BIOS doesn't help, we'll move onto hardware diagnostics:

1. Memtest. Read the following on how to test your memory for errors.

2. Chkdsk. Run a chkdsk /r in elevated command prompt (run cmd as admin) to see if it finds any bad sectors on your drive.

3. If the above two find nothing, start running stress tests on your video card(s) to ensure this is not a GPU related issue.

4. Try running a "Blend" of Prime95 at full stock settings. If you're at stock, there should be no issue passing a Blend test.
post #9 of 14
Thread Starter 
Quote:
Originally Posted by E-Peen View Post

Running Driver Verifier for a week was not necessary as Driver Verifier snags culprits within ~24 hours. Usually, the norm for Driver Verifier catching a culprit driver is minutes within bootup, if not, it takes a bit longer.
Since we got no BSODs with DV, it's very unlikely this is a software issue, and we have a hardware issue here. First off, before we begin hardware diagnostics, I would recommend updating to the latest BIOS for your board if you have not done this already. If updating the BIOS doesn't help, we'll move onto hardware diagnostics:
1. Memtest. Read the following on how to test your memory for errors.
2. Chkdsk. Run a chkdsk /r in elevated command prompt (run cmd as admin) to see if it finds any bad sectors on your drive.
3. If the above two find nothing, start running stress tests on your video card(s) to ensure this is not a GPU related issue.
4. Try running a "Blend" of Prime95 at full stock settings. If you're at stock, there should be no issue passing a Blend test.

Thanks E-Peen for your valuable advice. I'll test those steps over the weekend. But just curious, if it's a hardware issue, shouldn't the computer crash and show up BSOD regardless whether DV is running or not? I was totally baffled when the BSOD stopped after DV was running. blinksmiley.gif

Also, should I be using Chkdsk for my SSD? It might be the culprit, given OCZ Vertex 3 prevalent BSOD problems. But then again, prior to using it on this rig, it was working fine on my LGA1155 rig. I had secure erased it before transferring it though.
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-3960X Asus Rampage IV Extreme MSI GTX 560Ti OC G.Skill Ripjaws Z DDR3-2133  
Hard DriveHard DriveOptical DriveOS
Samsung F3 Spinpoint 1TB OCZ Vertex 3 Max IOPS 120GB Sony DRU-880S DVDRW Windows 7 Ultimate 
MonitorKeyboardPowerCase
Samsung 27SA850D Filco Ninja Brown Seasonic Platinum 1000W Silverstone TJ11 
MouseMouse PadAudio
Logitech G700 Razer Destructor Bowers & Wilkins MM-1 
  hide details  
Reply
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-3960X Asus Rampage IV Extreme MSI GTX 560Ti OC G.Skill Ripjaws Z DDR3-2133  
Hard DriveHard DriveOptical DriveOS
Samsung F3 Spinpoint 1TB OCZ Vertex 3 Max IOPS 120GB Sony DRU-880S DVDRW Windows 7 Ultimate 
MonitorKeyboardPowerCase
Samsung 27SA850D Filco Ninja Brown Seasonic Platinum 1000W Silverstone TJ11 
MouseMouse PadAudio
Logitech G700 Razer Destructor Bowers & Wilkins MM-1 
  hide details  
Reply
post #10 of 14
Hardware issues are very random, and depending on what piece of hardware is the culprit, and the severity of it, that all effects how random the crashes will be. Say for example your RAM is the culprit. If the RAM is still relatively healthy and not completely bad RAM, it will be idle to handle idle tasks with very little or no crashes at all, but it will croak under heavy load.

Driver Verifier also only stresses 3rd party drivers, not hardware, as drivers should never crash under any instance of stress.

As far as running chkdsk on an SSD goes, yes, it's 100% safe. The thing that you may be thinking of is defragging, you do NOT want to defrag an SSD.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Operating Systems