Somewhat random BSoDs

Kirby · Dec 1, 2008

Overview of the problem
BSoD while doing anything from gaming to browsing the web.
Full description of the problem and symptoms
DRIVER_IRQL_NOT_LESS_OR_EQUAL is the most common error, but latest one is just a STOP with hex 7F. I've also have gotten atapi.sys and ati3duag.dll with the errors.
Did it work normally at one time, or has the problem always existed?
On and off for a while, I'm been too lazy/busy to fix it.
Is the problem consistent and repeatable, or entirely random, or semi-random?
Gaming for a while will definately do it, sometimes extracting from a rar or web browsing. Random as far as I can tell.
I already tried these steps:
MemTest
Swapped video card
New motherboard
Reinstalled XP and latest drivers
My software:
- Operating System: XP Home, Version 5.1 (Build 2600.xpsp_sp3_gdr.080814-1236: Service Pack 3)
My hardware
- System brand & model, if it?s a pre-built system such as a Dell, HP, Gateway, etc. If it?s not, fill in as much of the information below as you can.
- MSI P35 Neo2
- Intel E6750 (not OC, stock fan/heatsink)
- ATI X1900GT
- 4 x 1 GB Ocz Gold
- Antec 430W
- Chaintech AV710
Kernel Dump from WinDbg

Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Documents and Settings\Kirby\Local Settings\Temp\WER9197.dir00\Mini113008-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Wed Nov 26 12:13:25.093 2008 (GMT-6)
System Uptime: 0 days 13:11:56.666
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
..............................................................
Loading User Symbols
Loading unloaded module list
.................
Unable to load image afd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for afd.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
Unable to load image tcpip.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {d, 0, 0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for NDIS.sys
*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys
*** WARNING: Unable to verify timestamp for psched.sys
*** ERROR: Module load completed but symbols could not be loaded for psched.sys
*** WARNING: Unable to verify timestamp for Rtenicxp.sys
*** ERROR: Module load completed but symbols could not be loaded for Rtenicxp.sys
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for rdbss.sys
*** ERROR: Module load completed but symbols could not be loaded for rdbss.sys
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : Rtenicxp.sys ( Rtenicxp+7d29 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4869a430

BUGCHECK_STR: 0x7f_d

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

LAST_CONTROL_TRANSFER: from ad674942 to ad60d13d

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f78b2aac ad674942 f78b2b1c 8a109c80 f78b2b1c afd+0xd13d
f78b2ac4 ad677be6 88f66650 00000000 0000007c tcpip+0x4942
f78b2ae4 ad67445f f78b2b1c 8ac3c864 8a7d670e tcpip+0x7be6
f78b2b60 ad671ef5 8ad29608 f616c518 891a10ad tcpip+0x445f
f78b2bc0 ad671b19 00000020 8ad29608 ad6740b6 tcpip+0x1ef5
f78b2c3c ad671836 ad6b18f0 8ad29608 8a7d670e tcpip+0x1b19
f78b2cf4 ad670928 8ad29608 8a7d6722 0000001a tcpip+0x1836
f78b2d34 ad670853 00000000 8a7dd9b8 8a7d6700 tcpip+0x928
f78b2d70 f7a44b9f 8abdccb0 00000000 b9935b40 tcpip+0x853
f78b2dc4 b993001d 00c7c670 8ac45e58 00000001 NDIS+0x22b9f
f78b2dd8 b99301b4 8ac12938 8ac45e58 00000001 psched+0x801d
f78b2dfc b99305f9 8abd6b50 00000000 8ac12938 psched+0x81b4
f78b2e14 f7a44c40 8abd6b48 00000000 8a878114 psched+0x85f9
f78b2e64 b9b10d29 00c7c670 f78b2f04 00000001 NDIS+0x22c40
f78b2f9c b9b12ec2 8ac3afb8 8aba3378 8a878220 Rtenicxp+0x7d29
f78b2fb4 f7a3ae99 8a878000 8abc1e18 f77179c0 Rtenicxp+0x9ec2
f78b2fcc 804dcd22 8a878234 8a878220 00000000 NDIS+0x18e99
f78b2fd0 8a878234 8a878220 00000000 00000000 nt+0x5d22
f78b2fd4 8a878220 00000000 00000000 ffffdfbf 0x8a878234
f78b2fd8 00000000 00000000 ffffdfbf 40034ab1 0x8a878220

STACK_COMMAND: kb

FOLLOWUP_IP:
Rtenicxp+7d29
b9b10d29 ?? ???

SYMBOL_STACK_INDEX: e

SYMBOL_NAME: Rtenicxp+7d29

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Rtenicxp

IMAGE_NAME: Rtenicxp.sys

BUCKET_ID: WRONG_SYMBOLS

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

Click to expand...

[/quote]

Any help would be greatly appreciated!

Kirby · Dec 2, 2008

Latest:

Playing Far Cry 2
STOP: 0x0000008E (0xC00000005, 0xBF067F83, 0xAA6DA3AC, 0x00000000) with ati2cqag.dll

Blended test in Orthos
BUGCODE_USB_DRIVER
STOP: 0x000000FE (0x00000005, 0x8A3C80E0, 0x80862935, 0x89C44180)

I wish they were at least consistent.

Ausm · Dec 2, 2008

First of all it looks like a possible driver problem to me. I would do a clean install of the OS with the latest device and mobo drivers downloaded off the web. oh make sure you have the drivers on a partition where the O.S. will not reside, if that is not possible burn them to a CD so you can easily reinstall them during the clean O.S. installation.

Vidda · Dec 9, 2008

Update from nkgreen:

Reformatted with a clean install of Vista Ultimate, installed on the drivers, and working on updating and installing FL Studio when it died.

Another Stop: 0x00000024 (0x001904AA, 0x956B29DC, 0x956B26D8, 0x8187620E)

After it rebooted, it scanned through a bunch of files (exes, dlls, registry, etc). I'm not sure if that's a Vista thing or not.

So can I safely assume that it's not a driver problem?

Kirby · Dec 10, 2008

I got tcpip.sys with a stop message last night. This is so frustrating. :|

KGB · Dec 10, 2008

Originally posted by: nkgreen
I got tcpip.sys with a stop message last night. This is so frustrating. :|

Try stripping the rig down to just the basics: 1HDD, 1 DIMM etc.

What do yout temps look like?

Kirby, dat you?

Kirby · Dec 10, 2008

Originally posted by: KGBMAN

Originally posted by: nkgreen
I got tcpip.sys with a stop message last night. This is so frustrating. :|

Click to expand...

Try stripping the rig down to just the basics: 1HDD, 1 DIMM etc.

What do yout temps look like?

Kirby, dat you?

Yah, it's me.

I've only got one hard drive (2 NTFS and 1 FAT32 partitions) and I've Memtested the RAM individually. But I guess I'll pull my sound and serial port card and try it anyway.

At this point, if someone told me to stick my tongue in the cpu fan while it was running I'd do it.

KGB · Dec 10, 2008

Originally posted by: nkgreen

Originally posted by: KGBMAN

Originally posted by: nkgreen
I got tcpip.sys with a stop message last night. This is so frustrating. :|

Click to expand...

Try stripping the rig down to just the basics: 1HDD, 1 DIMM etc.

What do yout temps look like?

Kirby, dat you?

Click to expand...

Yah, it's me.

I've only got one hard drive (2 NTFS and 1 FAT32 partitions) and I've Memtested the RAM individually. But I guess I'll pull my sound and serial port card and try it anyway.

At this point, if someone told me to stick my tongue in the cpu fan while it was running I'd do it.

That's EXACTLY what I was going to suggest. Is the heatsink getting warm?

Have you Memtested the DIMMs together?
While Memtest is a good tool, it is not the end-all-be-all for RAM issues. Granted, if Memtest is throwing errors, you've got a problem. But, I've seen dodgy RAM pass Memtest.

Kirby · Dec 10, 2008

I've tested the hell out of the ram with Memtest, every config possible: all together, separate, 1 -> 4 sticks.

Temp wise, I don't remember specifics, but I don't remember having anything outrageous in SpeedFan (I know it's not very accurate). I'll check again tonight though. I just can't imagine a heating problem giving so many different unrelated errors. Don't most motherboards just restart the computer and give an error in the BIOS if it overheats?

KGB · Dec 10, 2008

Originally posted by: nkgreen
I've tested the hell out of the ram with Memtest, every config possible: all together, separate, 1 -> 4 sticks.

Temp wise, I don't remember specifics, but I don't remember having anything outrageous in SpeedFan (I know it's not very accurate). I'll check again tonight though. I just can't imagine a heating problem giving so many different unrelated errors. Don't most motherboards just restart the computer and give an error in the BIOS if it overheats?

Heat problems, along with RAM problems will get you random errors.
It may not be your CPU that's overheating. Could be the northbridge.

Kirby · Dec 10, 2008

Originally posted by: KGBMAN

Originally posted by: nkgreen
I've tested the hell out of the ram with Memtest, every config possible: all together, separate, 1 -> 4 sticks.

Temp wise, I don't remember specifics, but I don't remember having anything outrageous in SpeedFan (I know it's not very accurate). I'll check again tonight though. I just can't imagine a heating problem giving so many different unrelated errors. Don't most motherboards just restart the computer and give an error in the BIOS if it overheats?

Click to expand...

Heat problems, along with RAM problems will get you random errors.
It may not be your CPU that's overheating. Could be the northbridge.

I have a hard time believing it's the northbridge since this is my second motherboard. I'm unlucky, but I hope I'm not that unlucky or I'm going to buy a bubble to live in.

KGB · Dec 10, 2008

Originally posted by: nkgreen

Originally posted by: KGBMAN

Originally posted by: nkgreen
I've tested the hell out of the ram with Memtest, every config possible: all together, separate, 1 -> 4 sticks.

Temp wise, I don't remember specifics, but I don't remember having anything outrageous in SpeedFan (I know it's not very accurate). I'll check again tonight though. I just can't imagine a heating problem giving so many different unrelated errors. Don't most motherboards just restart the computer and give an error in the BIOS if it overheats?

Click to expand...

Heat problems, along with RAM problems will get you random errors.
It may not be your CPU that's overheating. Could be the northbridge.

Click to expand...

I have a hard time believing it's the northbridge since this is my second motherboard. I'm unlucky, but I hope I'm not that unlucky or I'm going to buy a bubble to live in.

Yeah, but if you're getting this on XP and a clean Vista install, it's definitely hardware related.

On an outside chance, do you have another PSU to try in there?

Kirby · Dec 10, 2008

Originally posted by: KGBMAN
Yeah, but if you're getting this on XP and a clean Vista install, it's definitely hardware related.

On an outside chance, do you have another PSU to try in there?

No, but I'll see if I can borrow one to try out. Mines about 4 or 5 years old, so I guess it's worth looking at.

Kirby · Dec 11, 2008

Volts from SpeedFan seem whacked up, but I think it may be overheating.

VCC3V: 3.28 V
Vcore: 1.28 V
VRAM: 2.13 V
VChipset: 1.19 V
+5V: 4.71 V
+12V: 12.06 V
VCC1.5V: 0.9 V
VSB3V: 3.26 V
Vbat: 3.15V

I ran Orthos, and my core temps got up to 78C.

KGB · Dec 11, 2008

Originally posted by: nkgreen
Volts from SpeedFan seem whacked up, but I think it may be overheating.

VCC3V: 3.28 V
Vcore: 1.28 V
VRAM: 2.13 V
VChipset: 1.19 V
+5V: 4.71 V
+12V: 12.06 V
VCC1.5V: 0.9 V
VSB3V: 3.26 V
Vbat: 3.15V

I ran Orthos, and my core temps got up to 78C.

Yeah... some of those numbers are pretty screwed. Try a different PSU.

Oh, and make sure your HSF is getting good contact with your processor and apply a fresh dolse of thermal paste. Does your HSF even get warm to the touch? Try checking it with your tongue.

KGB · Dec 13, 2008

nkgreen???

Bump for an update!

Kirby · Dec 13, 2008

hey, the weekends are for drinking.

i'm going to get some thermal paste this weekend, and my boss is going to lend me a psu on monday (if he remembers).

KGB · Dec 13, 2008

Originally posted by: nkgreen
hey, the weekends are for drinking.

i'm going to get some thermal paste this weekend, and my boss is going to lend me a psu on monday (if he remembers).

Kewl. Now get back to drinking!!! :beer:

Kirby · Dec 16, 2008

New PSU in, volts are pretty much the same, couple tenths higher on +5V and +12V. I guess the weird VCC1.5V is an incorrect reading or something.

About to do some torture tests. :/

*crosses fingers*

KGB · Dec 17, 2008

Originally posted by: nkgreen
New PSU in, volts are pretty much the same, couple tenths higher on +5V and +12V. I guess the weird VCC1.5V is an incorrect reading or something.

About to do some torture tests. :/

*crosses fingers*

Hit the deck! Incoming!!

Kirby · Dec 17, 2008

Ran Orthos cpu test, ran 4.5 hours, no problem.

Blended test crashed it though.

KGB · Dec 17, 2008

What are your new SpeedFan voltages?

Kirby · Dec 17, 2008

Originally posted by: KGBMAN
What are your new SpeedFan voltages?

I don't think they changed when I was running Orthos. Between the different PSUs, a couple tenths of a volt on +5 and +12.

KGB · Dec 17, 2008

Originally posted by: nkgreen

Originally posted by: KGBMAN
What are your new SpeedFan voltages?

Click to expand...

I don't think they changed when I was running Orthos. Between the different PSUs, a couple tenths of a volt on +5 and +12.

Actually, one of my concerns with the voltages on your old PSU was the +5V line. It seemed a little low. Is your new number even lower?

I'm not trying to split hairs here just curious.

Are you still running a stripped down hardware configuration? 1 DIMM etc. ?

Kirby · Dec 17, 2008

Originally posted by: KGBMAN

Originally posted by: nkgreen

Originally posted by: KGBMAN
What are your new SpeedFan voltages?

Click to expand...

I don't think they changed when I was running Orthos. Between the different PSUs, a couple tenths of a volt on +5 and +12.

Click to expand...

Actually, one of my concerns with the voltages on your old PSU was the +5V line. It seemed a little low. Is your new number even lower?

I'm not trying to split hairs here just curious.

Are you still running a stripped down hardware configuration? 1 DIMM etc. ?

Oh ok. I'll try that when I get home. This run was with all my stuff in. I'll pull out all my cards and other sticks and try it again when I get home.

Somewhat random BSoDs

Lifer

Lifer

Lifer

Senior member

Lifer

Diamond Member

Lifer

Diamond Member

Lifer

Diamond Member

Lifer

Diamond Member

Lifer

Lifer

Diamond Member

Diamond Member

Lifer

Diamond Member

Lifer

Diamond Member

Lifer

Diamond Member

Lifer

Diamond Member

Lifer