People have a misconception that if they have a high wattage power supply that it should run everything. This isn't always true. If you have a poor quality power supply that has high wattage, you might still have problems with it. I've never heard of that power supply manufacturer before. I would purchase a quality PSU like corsair and see if that fixes the problem.
PC Power & Cooling is actually one of the top of the line PSU makers. That PSU cost me $450 when I bought it (2009) and it has functioned well until now (don't know if the PSU is at fault here).
However, I do have an update.
I returned one of the cards and got a new one yesterday and installed it along with removing and reinstalling new drivers (275.50 Beta).
I reset the CPU OC to default (no OC) and BOTH Crysis 2 and Battlefield Bad Company 2 CRASHED. Crysis 2 just froze while Bad Company 2 had a BSOD (black screen)!
I have attached the dump file as well as the PerfMon Report so can you tell me if it points to something specific here?
Also, when I installed the BETA NVidia driver, I completely removed the NVIDIA folder from the C-drive and installed it (after running CC-Cleaner).
It definitely looks like the PSU may be the culprit here but what I find weird is that there is no overclock at all (CPU is at the stock 3.47GHz) and the GPUs are not overclocked either. So the PSU isn't really being stressed is it?
I will be getting a new PSU anyway and I am thinking of getting the Antec HCP-1200. How does it compare to the Corsair AX1200 in your opinion? The Antec is a multi-rail PSU while the Corsair is a single-rail one.
Please help!
I enabled Driver Verifier again and was not able to boot into Windows.
However, this time, I got a BSOD with BC Code: 0xC9 and wrote down the driver that seems to have caused it: dtsoftbus01.sys
I have also attached the crash dump associated with this 0XC9 BSOD so please look at it and let me know what it says/means.
Thanks.
*I am writing this from Safe Mode since I was not able to boot into Windows. Should I disable Driver Verifier now or should it keep running? I have to use my PC so how long should the Driver Verifier run?
dtsoftbus01.sys belongs to Daemon Tools Lite. Go ahead and remove that software. You can use MagicISO as a replacement.
BSOD BUGCHECK SUMMARY
Code:Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Debug session time: Sat Jul 2 15:48:07.079 2011 (UTC - 4:00) System Uptime: 0 days 0:01:48.451 *** WARNING: Unable to verify timestamp for PxHlpa64.sys *** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys *** WARNING: Unable to verify timestamp for dtsoftbus01.sys *** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1308 ) BUGCHECK_STR: 0xc9_23e PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0xc9_23e_dtsoftbus01+1308 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Debug session time: Sat Jul 2 14:54:22.650 2011 (UTC - 4:00) System Uptime: 0 days 1:00:03.006 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+1eb65d ) EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. PROCESS_NAME: System ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. BUGCHECK_STR: 0x7E FAILURE_BUCKET_ID: X64_0x7E_nvlddmkm+1eb65d ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Hi,
I just got another BSOD today. I have attached the crash dump so please let me know what's going on.
I was able to play both Crysis 2 and Bad Company 2 for several hours each yesterday without any problems. However, when I played Crysis 2 for about 20 minutes today, I got this BSOD.
After looking at the crash in 'bluescreenview', it points to a driver called SCDEmu.sys. This, it says, belongs to PowerISO which I have installed. How can this be causing problems when I've had this program for several months without any BSODs at all? Do you recommend I uninstall this one also? PowerISO is very useful for me and I need it so what should I do?
Please look at the dump file and let me know.
I got another two BSODs after the one I posted above. They were also after I completely removed PowerISO from my system.
The first BSOD was when during Crysis 2 and it said the driver that caused it was mrxsmb.sys and the second one was during Bad Company 2 and that was caused by HIDCLASS.sys.
Both BSODs were again 0x1000007e.
Please help me diagnose this problem.
I've attached the BSOD dumps here.
nvidia kernel crashed.
Scrub the nvidia drivers with this
Phyxion.net - Driver Sweeper
this should be run in safe mode.
And then reinstall the latest from here.
NVIDIA DRIVERS 275.33 WHQL
Don't ever get graphics drivers from anywhere but the chip makers, only exception is with specific laptop graphics.
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88010a8665d, The address that the exception occurred at
Arg3: fffff88004e4b5d8, Exception Record Address
Arg4: fffff88004e4ae30, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nvlddmkm+1eb65d
fffff880`10a8665d ff5020 call qword ptr [rax+20h]
EXCEPTION_RECORD: fffff88004e4b5d8 -- (.exr 0xfffff88004e4b5d8)
ExceptionAddress: fffff88010a8665d (nvlddmkm+0x00000000001eb65d)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000020
Attempt to read from address 0000000000000020
CONTEXT: fffff88004e4ae30 -- (.cxr 0xfffff88004e4ae30)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=000000000000000e rsi=0000000000000000 rdi=0000000000000000
rip=fffff88010a8665d rsp=fffff88004e4b810 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=0000000000000001
r11=0000000000000004 r12=0000000000000000 r13=0000000000000001
r14=fffffa8011c7ccd8 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
nvlddmkm+0x1eb65d:
fffff880`10a8665d ff5020 call qword ptr [rax+20h] ds:002b:00000000`00000020=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000020
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80004f16100
0000000000000020
FOLLOWUP_IP:
nvlddmkm+1eb65d
fffff880`10a8665d ff5020 call qword ptr [rax+20h]
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88010a8665d
STACK_TEXT:
fffff880`04e4b810 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nvlddmkm+0x1eb65d
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvlddmkm+1eb65d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4df87081
STACK_COMMAND: .cxr 0xfffff88004e4ae30 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nvlddmkm+1eb65d
BUCKET_ID: X64_0x7E_nvlddmkm+1eb65d
Followup: MachineOwner
---------
I uninstalled the BETA drivers and ran Driver Sweeper and then installed the WHQL 275.33 drivers from NVidia.
I started Crysis 2 and within 10 minutes, I got another BSOD (attached dump file) with BC Code 0x116. This is really concerning because I believe the 116 STOP code has to do with the graphics card(s) themselves (hardware). I just got these EVGA GTX-580 3GB cards BRAND NEW from Fry's about 4 weeks ago.
In BlueScreenView, the driver that caused this BSOD seems to be: dxgkrnl.sys
Please look at the dump file and let me know what I should do.
I have already tested my RAM btw with MemTest for 8 passes and it passed with no errors. I've already run sfc /scannow AND chkdsk as well as uninstalling Daemon Tools Lite and PowerISO completely (with Your Uninstaller! 2010)
Thanks.
Yeah the crashes are still related to the graphics.
You may want to try it one card at a time and hope only one is bad..
RMA with EVGA isn't too painful if I remember correctly you just need to box up the bad card and start the process.
I'm still not 100% convinced it's the cards themselves but ... as I said the crashes are graphics related.
That power supply should be adequate.
btw since the new patch a lot of people are getting black screens and crashes from crysis.
I haven't seen their system files though only know what I read on the crytek forums.
Could you elaborate on what you mean by that? I mean, what is in the crash dumps that makes you think the crashes have to do with something other than the GPUs?
I'm just curious to know because the BSODs started happening soon after I got these cards and NEVER happened before. I had two GTX-590s in Quad-SLI and my CPU was overclocked to 4.41GHz and I never ran into any of these issues before. I even had Daemon Tools, PowerISO etc. start on boot every time. It really points to the card(s) or the graphics drivers but hopefully it can be figured out.
Like you said, I too think the PSU is enough for Tri-SLI so I highly doubt its giving up on load.
Quote