Sign in with
Sign up | Sign in
Your question
Solved

Games keep freezing and/or creating bsods. getting device errors

Last response: in Storage
Share
October 14, 2012 2:41:53 AM

So for the past 2 weeks or so my games have been freezing and an occasional BSOD. Recently it's been getting worse where 5 minutes into any game it freezes instead of freezing every 3-4 hours. I have tried a ton of things including:
-driver verifier
-uninstall recent programs/updates
-chkdsk
-disk defrag and cleanup
-running a game from a different hdd (although I have not re-installed windows on a different hdd)
-swapping sata cables and ports
-memtest (no errors after 4 hours or so)
-western digitals hdd checker thing (forgot name)
-tons of virus scans (bitdefender, malwarebytes, spybot search & destroy)
-rootkit scans
-unplugging things from my psu (bluray, cd/dvd, card reader)
-sfc scan
-prime95
-monitored temps of gpu and cpu (all good)

Here is my system:
graphics card- http://www.amazon.com/gp/product/B004UE1Q7S/ref=oh_deta...
ram- http://www.amazon.com/gp/product/B0037TO5C0/ref=oh_deta...
primary hdd- http://www.amazon.com/gp/product/B004CSIFFS/ref=oh_deta...
monitor- http://www.amazon.com/gp/product/B003Y3BJ7S/ref=oh_deta...
mouse- http://www.amazon.com/gp/product/B003L62T7W/ref=oh_deta...
keyboard- http://www.amazon.com/gp/product/B003ELVLKU/ref=oh_deta...
case- http://www.amazon.com/gp/product/B003WOL4W4/ref=oh_deta...
secondary hdd- http://www.amazon.com/gp/product/B002ZCXK0I/ref=oh_deta...
mobo- http://www.amazon.com/gp/product/B003A764XM/ref=oh_deta...
cpu- http://www.amazon.com/gp/product/B003FVI2KQ/ref=oh_deta...
psu- Ultra LSP 750Pro ATX PSU

Here is data from 2 recent minidumps.
If anyone has suggestions that would be awesome. I think I may need to replace my mobo but I'm not sure yet.
When I ran the wd hdd scanner it came up all clear and everything was fine.
When I ran chkdsk it came up with a ton of corrupt files, so I tried running a game from a different hard drive and still the same problem. (drive has no OS, I ran it from the same hdd with all game files installed on other hdd)

anyways here are the minidumps:
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc400060f0, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 0000000114119860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88000c1e93c, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000000e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: fffff88003199620 -- (.trap 0xfffff88003199620)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88000c16500 rbx=0000000000000000 rcx=fffffa80074f2050
rdx=fffffa80071feb10 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000c1e93c rsp=fffff880031997b8 rbp=fffffa800a37b6f0
r8=0000000000000007 r9=fffffa80074f21a0 r10=0000000000000000
r11=fffffa80071fecb8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
ataport!ChannelQueryDeviceRelations:
fffff880`00c1e93c 4053 push rbx
Resetting default scope

LOCK_ADDRESS: fffff800038d5b80 -- (!locks fffff800038d5b80)

Resource @ nt!PiEngineLock (0xfffff800038d5b80) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0xfffff800038d5b80
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from fffff80003747552 to fffff800036d9fc0

STACK_TEXT:
fffff880`03199308 fffff800`03747552 : 00000000`0000007a fffff6fc`400060f0 ffffffff`c000000e 00000001`14119860 : nt!KeBugCheckEx
fffff880`03199310 fffff800`03700cbf : fffffa80`06d7e580 fffff880`03199480 fffff800`0390c540 fffffa80`06d7e580 : nt! ?? ::FNODOBFM::`string'+0x36bea
fffff880`031993f0 fffff800`036e7589 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffffa80`0e41bf68 : nt!MiIssueHardFault+0x28b
fffff880`031994c0 fffff800`036d80ee : 00000000`00000008 fffff880`00c1e93c fffffa80`00000000 fffffa80`071feb10 : nt!MmAccessFault+0x1399
fffff880`03199620 fffff880`00c1e93c : fffff880`00c1c4ce 00000000`00000000 fffff880`03199880 fffff800`037d15a0 : nt!KiPageFault+0x16e
fffff880`031997b8 fffff880`00c1c4ce : 00000000`00000000 fffff880`03199880 fffff800`037d15a0 fffffa80`06b12ba0 : ataport!ChannelQueryDeviceRelations
fffff880`031997c0 fffff800`03a8ffde : 00000000`00000000 00000000`00000000 fffffa80`0a37b6f0 fffff880`030a4180 : ataport!IdePortDispatchPnp+0x22
fffff880`031997f0 fffff800`03a9034a : 00000000`00000000 fffffa80`0a37b6f0 fffff800`037d15a0 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`03199830 fffff800`03a92697 : fffff800`038d5940 fffffa80`06b16890 00000000`00000002 00000000`00000600 : nt!PnpQueryDeviceRelations+0xfa
fffff880`031998f0 fffff800`03ac2c7c : fffffa80`06b16890 fffffa80`06b10020 fffffa80`06b16890 00000000`00000002 : nt!PipEnumerateDevice+0x117
fffff880`03199950 fffff800`03ac3288 : fffff800`038d3500 00000000`00000000 00000000`00000001 fffff800`0393f5e8 : nt!PipProcessDevNodeTree+0x21c
fffff880`03199bc0 fffff800`037d3ee7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`03199c10 fffff800`036e3641 : fffff800`037d3bc0 fffff800`039cc501 fffffa80`06a29000 fffffa80`06a29040 : nt!PnpDeviceActionWorker+0x327
fffff880`03199cb0 fffff800`03970e5a : 00000000`00000000 fffffa80`06a29040 00000000`00000080 fffffa80`06a0cb30 : nt!ExpWorkerThread+0x111
fffff880`03199d40 fffff800`036cad26 : fffff880`030a4180 fffffa80`06a29040 fffff880`030af040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03199d80 00000000`00000000 : fffff880`0319a000 fffff880`03194000 fffff880`03199060 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
ataport!IdePortDispatchPnp+22
fffff880`00c1c4ce eb04 jmp ataport!IdePortDispatchPnp+0x28 (fffff880`00c1c4d4)

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: ataport!IdePortDispatchPnp+22

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ataport

IMAGE_NAME: ataport.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79293

FAILURE_BUCKET_ID: X64_0x7a_c000000e_ataport!IdePortDispatchPnp+22

BUCKET_ID: X64_0x7a_c000000e_ataport!IdePortDispatchPnp+22

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

2: kd> .trap 0xfffff88003199620
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88000c16500 rbx=0000000000000000 rcx=fffffa80074f2050
rdx=fffffa80071feb10 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000c1e93c rsp=fffff880031997b8 rbp=fffffa800a37b6f0
r8=0000000000000007 r9=fffffa80074f21a0 r10=0000000000000000
r11=fffffa80071fecb8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
ataport!ChannelQueryDeviceRelations:
fffff880`00c1e93c 4053 push rbx



and the second one:
5: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* 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: fffffa8007d2eb30, Terminating object
Arg3: fffffa8007d2ee10, Process image file name
Arg4: fffff80003998460, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa8007d2eb30

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`07b1c0e8 fffff800`03a20822 : 00000000`000000f4 00000000`00000003 fffffa80`07d2eb30 fffffa80`07d2ee10 : nt!KeBugCheckEx
fffff880`07b1c0f0 fffff800`039cce0b : ffffffff`ffffffff fffffa80`08f11060 fffffa80`07d2eb30 fffffa80`07d2eb30 : nt!PspCatchCriticalBreak+0x92
fffff880`07b1c130 fffff800`0394bf04 : ffffffff`ffffffff 00000000`00000001 fffffa80`07d2eb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176e6
fffff880`07b1c180 fffff800`03698253 : fffffa80`07d2eb30 fffff800`c0000006 fffffa80`08f11060 00000000`00ec0e70 : nt!NtTerminateProcess+0xf4
fffff880`07b1c200 fffff800`03694810 : fffff800`036e3b7f fffff880`07b1cb78 fffff880`07b1c8d0 fffff880`07b1cc20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`07b1c398 fffff800`036e3b7f : fffff880`07b1cb78 fffff880`07b1c8d0 fffff880`07b1cc20 00000000`00ec1a10 : nt!KiServiceLinkage
fffff880`07b1c3a0 fffff800`03698642 : fffff880`07b1cb78 00000000`00011b1c fffff880`07b1cc20 00000000`00ec14e8 : nt! ?? ::FNODOBFM::`string'+0x488a4
fffff880`07b1ca40 fffff800`036971ba : 00000000`00000000 000007fe`fd60d8c0 00000000`00000001 00000000`00011b1c : nt!KiExceptionDispatch+0xc2
fffff880`07b1cc20 00000000`77199c12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00ec1430 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77199c12


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



I'm pretty knowledgeable with computers/components/command line/etc, but I'm still newish to troubleshooting and have only done a few things with reading minidump files.

Thank you in advance for anyone that can help.
October 14, 2012 4:04:30 PM

Update, nothing freezes while I'm on my mobo graphics, here is another chkdsk I ran last night. I am going to try reinstalling windows on a new hdd today and see if that works.

The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
371456 file records processed. File verification completed.
331 large file records processed. 0 bad file records processed. 2 EA records processed. 90 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
494014 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
371456 file SDs/SIDs processed. Cleaning up 123 unused index entries from index $SII of file 0x9.
Cleaning up 123 unused index entries from index $SDH of file 0x9.
Cleaning up 123 unused security descriptors.
Security descriptor verification completed.
61280 data files processed. CHKDSK is verifying Usn Journal...
34549936 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
371440 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
117565764 free clusters processed. Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Write failure with status 0xc0000015 at offset 0xaea23d5e00 for 0x200 bytes.
The second NTFS boot sector is unwriteable.

Internal Info:
00 ab 05 00 b0 9a 05 00 4a f1 09 00 00 00 00 00 ........J.......
72 03 00 00 5a 00 00 00 00 00 00 00 00 00 00 00 r...Z...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
m
0
l
a c 152 G Storage
October 14, 2012 4:13:28 PM

It sure looks like a bad drive. More likely then a bad controller/driver issue. It never hurts to try a different SATA power/data cable.

Have you run the drives diagnostic tools?

You can even use the surface scan option in HD tune(non Pro) as a generic test for hard drives. It works well and shows you bad sectors as soon as they are found.

Scroll down to the free one if you wish or you can use the PRO for 30 days
http://www.hdtune.com/download.html
m
0
l
Related resources
October 14, 2012 7:18:03 PM

Yeah that's what I was thinking. I'm reinstalling windows now on a different hdd and am going to just download a graphic extensive game to check it. I also had a thought.
Do you think it's possible that my power supply is starting to go?
If it's not sending a continuous current would that explain the freezing and the hard drive not appearing occasionally in my computer and disk defrag?
m
0
l
a c 152 G Storage
October 14, 2012 8:12:56 PM

Its highly unlikely, but anything can happen. That power supply is much more of a 550 watt power supply from its 12 volt rail perspective(It has 540 watts @ 12 volts, the test is on the lower rails.).

You want to stress it good, use OCCT(power supply stress).

It places systems under more stress then any game will.

http://www.ocbase.com/

You can also get a multimeter to check the voltage under stressful situations(black to yellow is 12 and black to red is 5 black to orange is 3.3).

12 is the big one and you can check it from a molex LP4(old style hard drive connector) connector on most power supplies.

Most meters can not show your voltage ripple however, but can still give you an idea of if the power supply is dropping or raising out of spec at load.
m
0
l
October 15, 2012 5:01:43 AM







Join Date: Oct 2012
Windows 7 Ultimate x64
5 posts





--------------------------------------------------------------------------------

No luck with the Windows install on different HDD. Here is the dump file from the BSOD I received after 5 minutes of gaming. I'm thinking I may need a new MOBO, not sure though.
Any ideas???



3: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* 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: fffffa8008ea6b30, Terminating object
Arg3: fffffa8008ea6e10, Process image file name
Arg4: fffff80002dce460, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa8008ea6b30

IMAGE_NAME: wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: wininit.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`0a49bb08 fffff800`02e56822 : 00000000`000000f4 00000000`00000003 fffffa80`08ea6b30 fffffa80`08ea6e10 : nt!KeBugCheckEx
fffff880`0a49bb10 fffff800`02e02e0b : ffffffff`ffffffff fffffa80`070d8b50 fffffa80`08ea6b30 fffffa80`08ea6b30 : nt!PspCatchCriticalBreak+0x92
fffff880`0a49bb50 fffff800`02d81f04 : ffffffff`ffffffff 00000000`00000001 fffffa80`08ea6b30 0000007f`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176e6
fffff880`0a49bba0 fffff800`02ace253 : fffffa80`08ea6b30 00000000`c0000006 fffffa80`070d8b50 00000000`00000026 : nt!NtTerminateProcess+0xf4
fffff880`0a49bc20 00000000`772615da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`026cf9d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772615da


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0xF4_IOERR_IMAGE_wininit.exe

BUCKET_ID: X64_0xF4_IOERR_IMAGE_wininit.exe

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




and some more info that someone asked for on another forum.
I have 2 HDD's. I tried playing with graphics at 1600x900 but it still BSoD'd. I will lower them more and take a look as well. I used to get BSOD's after a new graphics driver install, so I kept an old one that worked and then after about 5 more revisions I finally decided to give the new graphics driver a go. It started BSOD'ing a lot. So then I tried a bunch of things and it still BSOD'd. So I finally installed the old driver again and the BSOD's stopped for about 2 days. And then they came back and are very bad again. I just tried updating my graphics driver again today and no luck. I also ran Memtest tonight for 2 passes and nothing still. My MOBO is fairly new, I will try updating the BIOS tomorrow.
I bought the MOBO about 1 and a half years ago. I bought the graphics card a year ago.
I don't have another graphics card, but the on board graphics don't cause BSOD's. I think it's a MOBO compatibility thing with my card, but I'm really not sure. I will see if I can borrow a card tomorrow and see if that fixes anything.
I have 2 HDDs.
Tomorrows goals (if I have any time) are to run games at low settings, install a very old graphics driver and try it, and Possibly try flashing BIOS to the beta version (would you recommend this?)
m
0
l
a c 152 G Storage
October 15, 2012 7:39:36 PM

Bios flashing is a last case hing, you are kind of last case here.

Maybe the card or power supply is an issue. Unfortunately, you are at a point of parts swap testing.

Does it crash out with OCCT? If you do not want to push it with that, I understand.

Maybe you can use GPU-Z to log video card temps to see if it gets too hot when gaming before the crash.
http://www.techpowerup.com/gpuz/
m
0
l
October 16, 2012 12:28:27 AM

I've already checked the card temps. everything is fine. But is OCCT overclocking? I just posted this in the other forum I'm getting help in so I'll just copy and paste it. What do you think. I don't want to buy a new psu and graphics card if I don't have to. I'm in college so I don't have much money lol

Ok well it looks like I found the problem. Plugged my buddies graphics card in and it worked perfectly. Played a game where with my card wouldn't last over 3 minutes max for 30 minutes with no problem all max graphics. I'm disappointed because his power supply can't support my card so I could not check if the card was bad or if it is just a compatibility thing. Or again do you guys think it's possible that my power supply just can't take it. I checked the BIOS and I'm not sure what it means but under power it said this:
VCORE 1.472V
DDR3 1.5V
1.520V
+3.3V 3.264V
+12V 10.336V

Does that mean that of the 12V I should be getting I'm only getting 10.336V? I know very little about power.

Before I go ahead and buy a new graphics card I want to make sure you guys would recommend doing so. What do you think?

Oh and just so you guys know his graphics card is much worse than mine. It's a 1GB older version. I can't remember exactly what it is, but I believe it's a hd radeon 6550 and mine is a 2gb hd radeon 6950. So it would be taking up less power with his, which wouldn't prove the power supply concern wrong. How do I go about checking my PSU?
m
0
l
a c 152 G Storage
October 16, 2012 1:15:29 AM

If you have 10.3, You would be about 14% below 12 volts. This falls out of the spec for sure.

In general, you should be within 5%(used to be 10% many years back when 12 volt was not the most used rail). Many higher end power supplies strive for 1% tolerance.

If you have a multimeter(set to DC volts or =V and not ~v) or can get your hands on one, you should test black to yellow on a molex connector to confirm or deny this reading.

If you confirm it(11.4-12.6 is considered to be "safe" closer to 12 the better). You should replace the power supply.

EDIT.

Ohh and OCCT is not an overclocking tool as such it is a stress test that overclockers use to test an overclocked system to make sure it is stable(The power supply tests gets my system all they way upto 356 watts :)  vs the 170-250 of most games. Interesting how efficient today's hardware is :)  ). If your power supply is going, lets not run that after all.

If you need images of the power supply testing, let me know.
m
0
l
October 16, 2012 2:03:07 AM

I do have a multimeter. Could you supply images of how to do that to test the supply. I have only used it in outlets and on wires.
m
0
l
October 17, 2012 12:26:02 AM

Looks to be a power issue. Kept crossing my mind, but always neglected it. At least glad I probably won't need a new graphics card or mobo. I ordered this one. Do you think it is a good future proof one if I wanted to crossfire my card?
Amazon.com: XFX 850w XXX Edition Semi-Modular Power Supply: Computers & Accessories

I researched psu's more for about 2 hours today and chose this one over the ocz 700w thats on amazon and has a rebate to get it for $50 lol. It better be worth it.
m
0
l

Best solution

a c 152 G Storage
October 17, 2012 3:06:46 AM

The power supply you picked is a good unit and should last a long time.

850 watts(840 of it can be pushed out as 12 volts if needed[provided the load on the 3.3 and 5 is low. either way LOTS of power]) is LOTS of power for all but the most extreme systems.

To test it is just this easy.
Set DC volts(if you have range, use something over 12 volts)
Black(either black are the same thing) to black and red to what you need to test.

As long as you do not short anything out this test is safe to do on a running system

I used a hard drive power supply as a stand-in.
Share
October 27, 2012 3:44:52 AM

Best answer selected by hcshadow.
m
0
l
October 27, 2012 3:45:04 AM

Thanks for all your help. Sorry I didn't post sooner but it was the power supply.
m
0
l
!