Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › blue screen showing up
New Posts  All Forums:Forum Nav:

blue screen showing up - Page 2

post #11 of 26
Thread Starter 
i dont have MEMORY.DMP file because ccleaner erased every temp files of my pc

is this it ?

418

can it be lack of power from psu
phantom
(11 items)
 
  
Reply
phantom
(11 items)
 
  
Reply
post #12 of 26
Event Viewer won't help, it will only give the bugcheck (1e bugcheck it states there), which can be anything. We need the dump files. Stop your CCleaner from deleting DMP files for now.

So, for now, just wait to BSOD again, and then attach the dump file.
post #13 of 26
Thread Starter 
ok im going to do that and when it fails again ill post it.

thanks you very much wink.gif
phantom
(11 items)
 
  
Reply
phantom
(11 items)
 
  
Reply
post #14 of 26
Quote:
Originally Posted by phileps View Post

ok im going to do that and when it fails again ill post it.
thanks you very much wink.gif

My pleasure, I'll be awaiting any dumps you post thumb.gif
post #15 of 26
Thread Starter 
i just get another blue screen but this time on my working laptop
i'm going to send you dump files
phantom
(11 items)
 
  
Reply
phantom
(11 items)
 
  
Reply
post #16 of 26
Thread Starter 
phantom
(11 items)
 
  
Reply
phantom
(11 items)
 
  
Reply
post #17 of 26
My sincere apologies for the delayed reply.

4 dumps, 3 dumps say 116 TDR video failure, one points to SbFw.sys (Sunbelt Personal Firewall driver).

First off, uninstall the Sunbelt Personal Firewall to rule this out, I believe it is conflicting with your Avast anti virus and causing crashes. If the company provides an uninstall tool be sure to use it. You may want to uninstall unsing revno, to insure complete removal.

Driver(s) in need of update:

NETw2v32.sys - Tue Mar 06 21:08:44 2007 (Intel Wireless LAN Driver). Update if available here.

Rtnicxp.sys - Fri May 30 11:12:11 2008 (Realtek 10/100/1000 NDIS 5.1 Driver). Update here if available.

AGRSM.sys - Mon Nov 10 09:56:37 2008 (TOSHIBA V92 Software Modem/Agere Systems Soft/Creatix V.92 Data Fax Modem). Part of SLI Logic. Update if available here.

Next, there are a multitude of things that can cause a 116 TDR bugcheck. Before going into that, I should mention this:

NOTE: If overclocking, please reset the system to default values while troubleshooting it. This includes CPU, RAM, GPU overclocking. You're more than welcome to put your stocks back to clock after we've diagnosed your issues!!!!!

The first thing I recommend doing if overclocks aren't the issue is fully uninstalling and reinstalling your AMD video card drivers, as a bad driver installation can cause 116 bugchecks, especially since the culprit is being pointed to atikmpag.sys (ati video card drivers). If these issues started happening after a driver update, rollback the video card drivers you installed to an earlier version that worked previously without issue.

If drivers do not help, your issue may be heat related, inadequate cooling, dust buildup in the fans or pci-e slot, so make sure your rig is being cooled adequately.

Run Furmark to test your video card to ensure that the card(s) itself is running as intended:
Quote:
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

The following hardware issues can cause a TDR event:
Quote:
- Failing overclock on CPU or GPU (stop overclocking)
- Bad sector in memory resulting in corrupt data being communicated between GPU and the system (either video or system memory) ( MemTest and a video memory stress test: |MG| Video Memory Stress Test 1.7.116 Download )
- Corrupt hard drive/windows install resulting in corruption to the system registry or the page file (Hard drive diagnostics ( HD Diagnostic ), reset your pagefile

Memtest download to test your RAM: http://www.memtest86.com/

To "reset" the pagefile, follow these instructions:
Quote:
Use this technique to "reset" your pagefile:
a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
-Then click on the Advanced tab,
-then on the Performance Settings Button,
-then on the next Advanced tab,
-then on the Virtual Memory Change button.
b ) In this window, note down the current settings for your pagefile (so you can restore them later on).
-Then click on the "No paging file" radio button, and
- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.
-Click OK to exit the dialogs.
c ) Reboot (this will remove the pagefile from your system)
d ) Then go back in following the directions in step a ) and re-enter the settings that you wrote down in step b ). Follow the steps all the way through (and including) the reboot.
e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.

Run System File Checker:
Quote:
SFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.

- Over heating of GPU or CPU again resulting in corrupt data being communicated. (Point a house fan at the video card, take temperature readings from the card with an IR detector (or your finger - but be very, very careful!!!)

- GPU failure due to any sort of issue from insufficient power(VERY common) to heat. (check the power leads, use a multimeter to check the power output, try another, more powerful PSU)

The following software issues can cause a TDR event:
Quote:
-Incompatible drivers of any sort (either GPU, sound, etc) ( http://www.microsoft.com/windows/com...s/default.aspx )
-Messy registry (I doubt this and don't approve of registry cleaners)
-Known vista issues resounding around multiple displays, aero, dreamscape, and various display drivers. (none known for this OS)
-Known vista issues that sometimes cause corrupt information to be sent to the video card from system memory (will be addressed completely in SP2, has had various fixes applied since vista's release) (none known for this OS)
-Bad direct x files (uninstall, then reinstall DirectX)
-bad system files (System File Checker - was run above)
-Bad driver (some drivers will cause an event due to internal bugs, however these are not nearly as common as many think due to all of the previous things causing the same symptom) - (remove all 3rd party programs and check to be sure drivers aren't loading. Then install only the necessary 3rd party stuff, and ensure it's the latest version and that it's compatible with Windows 7)


Dump(s) 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\Cardbox\Downloads\110811-99000-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0x82839000 PsLoadedModuleList = 0x829824f0
Debug session time: Tue Nov  8 18:20:49.906 2011 (UTC - 4:00)
System Uptime: 0 days 6:40:38.578
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
..........
kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 86440938, Pointer to a stuck thread object.  Do .thread then kb on it to find
        the hung location.
Arg2: 00000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 00000000, Pointer to offending driver name.
Arg4: 00000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

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

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

FAULTING_THREAD:  86440938

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8f08c1f7 to 82917eb4

STACK_TEXT:  
8c4fe4f8 8f08c1f7 000000ea 86440938 00000000 nt!KeBugCheckEx+0x1e
8c4fe53c 8f084bc0 8c4fe584 858643d0 85864190 dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x2c
8c4fe564 8f05348a 8c4fe584 00000000 00000000 dxgkrnl!TdrTimedOperationDelay+0xc9
WARNING: Stack unwind information not available. Following frames may be wrong.
8c4fe5b8 8f053902 50210000 00000001 00000001 atikmdag+0x42c48a
8c4fe5d8 8ecffafe 00000000 00000001 00000001 atikmdag+0x42c902
8c4fe63c 8ec37b84 8c4fe698 00000000 8c4fe698 atikmdag+0xd8afe
8c4fe658 8f07d57f 848b86c0 8c4fe698 86451000 atikmdag+0x10b84
8c4fe680 8f0bedf6 8c4fe698 a7bc0094 8de711b0 dxgkrnl!DXGADAPTER::DdiSetVidPnSourceAddress+0xc7
8c4fe804 8f0c14c9 a19c09d8 00000000 8c4fea01 dxgkrnl!DXGADAPTER::CommitVidPn+0x49f
8c4fe858 8f0bd89c 86451000 93c1da20 a19c09d8 dxgkrnl!CommitVidPn+0x27
8c4fea54 93bb262d 00000004 00000000 8c4fed28 dxgkrnl!DxgkCddEnable+0xe24
8c4fea9c 93bb2912 ffb89010 8c4fecd0 8c4fed28 cdd!CreateAndEnableDevice+0x171
8c4feac0 93bb534e ffb89010 8c4fecd0 8c4fed28 cdd!TryCreateDevice+0xac
8c4fed50 82a41fda ffb89010 af4f6ffe 00000000 cdd!PresentWorkerThread+0xa06
8c4fed90 828ea1d9 93bb4948 ffb89010 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .thread 0xffffffff86440938 ; kb

FOLLOWUP_IP: 
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+2c
8f08c1f7 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+2c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce78ffe

FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

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



Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Cardbox\Downloads\050412-34757-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02c5f000 PsLoadedModuleList = 0xfffff800`02ea3650
Debug session time: Fri May  4 17:23:01.862 2012 (UTC - 4:00)
System Uptime: 0 days 0:04:50.360
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8003d9a4e0, fffff880065488c8, ffffffffc00000b5, a}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+78c8 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8003d9a4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880065488c8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc00000b5, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000a, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+78c8
fffff880`065488c8 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0375aa58 fffff880`07d5e000 : 00000000`00000116 fffffa80`03d9a4e0 fffff880`065488c8 ffffffff`c00000b5 : nt!KeBugCheckEx
fffff880`0375aa60 fffff880`07d5dddb : fffff880`065488c8 fffffa80`03d9a4e0 fffffa80`0559a6d0 fffffa80`06426010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0375aaa0 fffff880`0720ff07 : fffffa80`03d9a4e0 00000000`c00000b5 fffffa80`0559a6d0 fffffa80`06426010 : dxgkrnl!TdrIsRecoveryRequired+0x273
fffff880`0375aad0 fffff880`0723dd5a : fffffa80`ffffffff 00000000`0000443b fffff880`0375ac30 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0375abb0 fffff880`0720b29e : fffffa80`06426010 ffffffff`feced300 fffffa80`0559a6d0 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`0375abf0 fffff880`07237e7a : 00000000`00000000 fffffa80`0559a6d0 00000000`00000080 fffffa80`06426010 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`0375ad00 fffff800`02f75fda : 00000000`067f668c fffffa80`061d6b60 fffffa80`03cd2990 fffffa80`061d6b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0375ad40 fffff800`02ccc9c6 : fffff800`02e50e80 fffffa80`061d6b60 fffff800`02e5ecc0 fffff880`02ff42b0 : nt!PspSystemThreadStartup+0x5a
fffff880`0375ad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+78c8
fffff880`065488c8 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+78c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ebb331c

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Cardbox\Downloads\050312-62640-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.x86fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0x82805000 PsLoadedModuleList = 0x8294e4d0
Debug session time: Thu May  3 08:37:35.952 2012 (UTC - 4:00)
System Uptime: 0 days 0:08:21.795
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.....
kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

NO_MORE_IRP_STACK_LOCATIONS (35)
A higher level driver has attempted to call a lower level driver through
the IoCallDriver() interface, but there are no more stack locations in the
packet, hence, the lower level driver would not be able to access its
parameters, as there are no parameters for it.  This is a disasterous
situation, since the higher level driver "thinks" it has filled in the
parameters for the lower level driver (something it MUST do before it calls
it), but since there is no stack location for the latter driver, the former
has written off of the end of the packet.  This means that some other memory
has probably been trashed at this point.
Arguments:
Arg1: 84459df8, Address of the IRP
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

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

*** WARNING: Unable to verify timestamp for SbFw.sys
*** ERROR: Module load completed but symbols could not be loaded for SbFw.sys
*** WARNING: Unable to verify timestamp for sbtis.sys
*** ERROR: Module load completed but symbols could not be loaded for sbtis.sys
*** WARNING: Unable to verify timestamp for aswTdi.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswTdi.SYS

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x35

PROCESS_NAME:  AvastSvc.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8283c55a to 828e3f1c

STACK_TEXT:  
849e38f8 8283c55a 00000035 84459df8 00000000 nt!KeBugCheckEx+0x1e
849e391c 8bd2c898 84732a68 84459df8 849e3950 nt!IofCallDriver+0x30
WARNING: Stack unwind information not available. Following frames may be wrong.
849e392c 8bd2cc3b 8509d448 84459df8 8bd2ca46 SbFw+0xa898
849e3950 8bd2d50e 8509d448 00000000 8509ee60 SbFw+0xac3b
849e3968 8bd2d673 8509ee60 8509d448 84459df8 SbFw+0xb50e
849e3988 8bd258c2 8509ee60 84459df8 849e39b0 SbFw+0xb673
849e3998 8283c58e 8509ee60 84459df8 84459ea8 SbFw+0x38c2
849e39b0 8bd7ea14 84732a68 8bd84000 849e39e4 nt!IofCallDriver+0x63
849e39c0 8bd7ee8b 8509ee60 84459df8 8bd7edb6 sbtis+0x9a14
849e39e4 8bd7fbb1 8509ee60 84459df8 8516f0e8 sbtis+0x9e8b
849e3a00 8bd7ffec 8516f0e8 8509ee60 84459e8c sbtis+0xabb1
849e3a24 8bd795b6 8516f0e8 84459df8 84459df8 sbtis+0xafec
849e3a40 8283c58e 8516f0e8 84459df8 846a55b0 sbtis+0x45b6
849e3a58 9a764c7b 1ee8c316 00000000 84459eb0 nt!IofCallDriver+0x63
849e3ab4 9a7618fd 846a5580 84459df8 84459eb0 aswTdi+0x3c7b
849e3afc 8283c58e 8516f0e8 84459df8 84668868 aswTdi+0x8fd
849e3b14 8b448815 0fdd186c 00012007 8b447ea4 nt!IofCallDriver+0x63
849e3bec 8b4422bc 846e4e78 850a3788 849e3c14 afd!AfdConnect+0x971
849e3bfc 8283c58e 850a3788 84459df8 84459df8 afd!AfdDispatchDeviceControl+0x3b
849e3c14 82a2fb09 846e4e78 84459df8 84459ed4 nt!IofCallDriver+0x63
849e3c34 82a32cdb 850a3788 846e4e78 00000000 nt!IopSynchronousServiceTail+0x1f8
849e3cd0 82a79614 850a3788 84459df8 00000000 nt!IopXxxControlFile+0x6aa
849e3d04 8284320a 000009e4 000009e8 00000000 nt!NtDeviceIoControlFile+0x2a
849e3d04 772e7094 000009e4 000009e8 00000000 nt!KiFastCallEntry+0x12a
0946d93c 00000000 00000000 00000000 00000000 0x772e7094


STACK_COMMAND:  kb

FOLLOWUP_IP: 
SbFw+a898
8bd2c898 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  SbFw+a898

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SbFw

IMAGE_NAME:  SbFw.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9b5a88

FAILURE_BUCKET_ID:  0x35_SbFw+a898

BUCKET_ID:  0x35_SbFw+a898

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




post #18 of 26
Thread Starter 
thank you very very much man, you are the best guy of the forum no doubt.... thank you for the time you spend on my issue, i really apriciate it.

one thing i think you wold like to know:
my gaming rig (the first i complaint at this thread) didn't have more blue screens but now its being fixed because one ram slot and one ram bar stopped working so i guess my blue screens on that pc were related with that
phantom
(11 items)
 
  
Reply
phantom
(11 items)
 
  
Reply
post #19 of 26
For future reference, BSOD (Blue Screen Of Death) Viewer is a handy utility that displays lots of information about the last few seizures (read: BSODs) of your PC. smile.gif
 
BloodFury Build
(30 items)
 
 
CPUMotherboardGraphicsGraphics
i7 3930K @ 4.7GHz ASUS Rampage IV Extreme ASUS Radeon HD7970 ASUS Radeon HD7970 
RAMHard DriveHard DriveHard Drive
Corsair 32GB 2133MHz DDR3 RAM WD Caviar Green 3TB x4 - 12TB WD My Book 3TB WD My Book 2TB x2 - 4TB 
Hard DriveOptical DriveCoolingCooling
Crucial M4 512GB External optical drive Swiftech MCR420-QP 480 Radiator Yate Loon D12SL-12 1350RPM x15 
CoolingCoolingCoolingCooling
Alphacool VPP655 -T12 x2 Alphacool Repack - Dual Laing D5 - Dual 5,25 Ba... DangerDen Delrin 90° G1/4 connector EK-FB KIT RE4 - Acetal+Nickel EN 
CoolingCoolingCoolingCooling
EK-FC Bridge DUAL Parallel EK-FC7970 - Nickel EN Acetal x2 EK-FC7970 Backplate - Black x2 EK-VGA I/O bracket HD7970 x2 
CoolingCoolingOSMonitor
Feser Tube UV - HighFlow - 3/8 ID - 1/2 OD - BLACK Lamptron FC9 Fan Controller 4-channel 50W FC-9-... Windows 7 Ultimate x64 Samsung Syncmaster S27A750D x2 
MonitorMonitorKeyboardPower
IIYAMA G2773HDS-GB1 LG 37LF2500 Razer Blackwidow Ultimate Corsair AX1200W 
CaseMouseMouse PadAudio
Mountain Mods Ascension Razer Mamba Razer Goliathus Extended Control Edition ASUS ROG Phoebus 9.1 Soundcard 
AudioAudioOther
CM Storm Sirus 5.1 Headset Teufel Concept E 400 Digital Media 5.1 Surround... Canon MG6250 MultiFunctional Printer 
CPUMotherboardGraphicsRAM
i7 3930K C2 @4.7GHz ASUS Rampage IV Extreme/BF3 ASUS Radeon HD 7970 12GB Corsair Dominator 1600MHz memory 
Hard DriveHard DriveHard DriveCooling
Crucial M4 128GB 7 TB External HDDs 2.2 TB HDDs in Raid0 Black Ice GT Stealth 360 
CoolingCoolingCoolingCooling
Swiftech Apogee HD 7x Yate Loon D12SL-12 XSPC X2O 750 Dual Bay Reservoir+Pump Phobya Nano-G 14 Silent Waterproof 140mm - 1000rpm 
CoolingCoolingOSMonitor
10MM (3/8) Compression Fitting Gripz Style - G1... PVC Tube 3/8 ID (10mm ID -13 mm OD ) - 2 meter ... Windows 7 Ultimate LG 37LF2500 
KeyboardPowerCaseMouse
Logitech G15 Corsair HW 750W Cooler Master Cosmos II Razer Naga 
Mouse PadAudioOtherOther
Steelseries SK Gaming Mouse Pad Creative HS 1200 NZXT 12x Red LED Sleeve - 1M NZXT 12x Red LED Sleeve - 1M 
OtherOtherOtherOther
BitFenix PCIe 6-Pin to 6-Pin Cable - 45 cm - Pr... BitFenix USB 2.0 internal extension - 30 cm - P... BitFenix PCIe 8-Pin to 8-Pin Cable - 45 cm - Pr... Sweex US011 4-poorts USB Hub 
OtherOther
3-Pin Splitter naar 4x 3-Pin Fan - Sleeved UVRe... BitFenix Molex to 3x Molex 55cm - Premium Sleev... 
  hide details  
Reply
 
BloodFury Build
(30 items)
 
 
CPUMotherboardGraphicsGraphics
i7 3930K @ 4.7GHz ASUS Rampage IV Extreme ASUS Radeon HD7970 ASUS Radeon HD7970 
RAMHard DriveHard DriveHard Drive
Corsair 32GB 2133MHz DDR3 RAM WD Caviar Green 3TB x4 - 12TB WD My Book 3TB WD My Book 2TB x2 - 4TB 
Hard DriveOptical DriveCoolingCooling
Crucial M4 512GB External optical drive Swiftech MCR420-QP 480 Radiator Yate Loon D12SL-12 1350RPM x15 
CoolingCoolingCoolingCooling
Alphacool VPP655 -T12 x2 Alphacool Repack - Dual Laing D5 - Dual 5,25 Ba... DangerDen Delrin 90° G1/4 connector EK-FB KIT RE4 - Acetal+Nickel EN 
CoolingCoolingCoolingCooling
EK-FC Bridge DUAL Parallel EK-FC7970 - Nickel EN Acetal x2 EK-FC7970 Backplate - Black x2 EK-VGA I/O bracket HD7970 x2 
CoolingCoolingOSMonitor
Feser Tube UV - HighFlow - 3/8 ID - 1/2 OD - BLACK Lamptron FC9 Fan Controller 4-channel 50W FC-9-... Windows 7 Ultimate x64 Samsung Syncmaster S27A750D x2 
MonitorMonitorKeyboardPower
IIYAMA G2773HDS-GB1 LG 37LF2500 Razer Blackwidow Ultimate Corsair AX1200W 
CaseMouseMouse PadAudio
Mountain Mods Ascension Razer Mamba Razer Goliathus Extended Control Edition ASUS ROG Phoebus 9.1 Soundcard 
AudioAudioOther
CM Storm Sirus 5.1 Headset Teufel Concept E 400 Digital Media 5.1 Surround... Canon MG6250 MultiFunctional Printer 
CPUMotherboardGraphicsRAM
i7 3930K C2 @4.7GHz ASUS Rampage IV Extreme/BF3 ASUS Radeon HD 7970 12GB Corsair Dominator 1600MHz memory 
Hard DriveHard DriveHard DriveCooling
Crucial M4 128GB 7 TB External HDDs 2.2 TB HDDs in Raid0 Black Ice GT Stealth 360 
CoolingCoolingCoolingCooling
Swiftech Apogee HD 7x Yate Loon D12SL-12 XSPC X2O 750 Dual Bay Reservoir+Pump Phobya Nano-G 14 Silent Waterproof 140mm - 1000rpm 
CoolingCoolingOSMonitor
10MM (3/8) Compression Fitting Gripz Style - G1... PVC Tube 3/8 ID (10mm ID -13 mm OD ) - 2 meter ... Windows 7 Ultimate LG 37LF2500 
KeyboardPowerCaseMouse
Logitech G15 Corsair HW 750W Cooler Master Cosmos II Razer Naga 
Mouse PadAudioOtherOther
Steelseries SK Gaming Mouse Pad Creative HS 1200 NZXT 12x Red LED Sleeve - 1M NZXT 12x Red LED Sleeve - 1M 
OtherOtherOtherOther
BitFenix PCIe 6-Pin to 6-Pin Cable - 45 cm - Pr... BitFenix USB 2.0 internal extension - 30 cm - P... BitFenix PCIe 8-Pin to 8-Pin Cable - 45 cm - Pr... Sweex US011 4-poorts USB Hub 
OtherOther
3-Pin Splitter naar 4x 3-Pin Fan - Sleeved UVRe... BitFenix Molex to 3x Molex 55cm - Premium Sleev... 
  hide details  
Reply
post #20 of 26
Thread Starter 
thank you thumb.gif
phantom
(11 items)
 
  
Reply
phantom
(11 items)
 
  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Windows
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › blue screen showing up