Help with Blue Screen

[Rydis]

Trying to determine what is causing me crash occasionally. It happens a few times a week a most, rarely more than once a day. This is the mini dump. I have ran memtest before, and got 0 errors for about 9 hours.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8007E0B038
BCP3: 0000000000000000
BCP4: 0000000000000000

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


Loading Dump File [Z:\Windows\Minidump\082814-11668-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 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`03057000 PsLoadedModuleList = 0xfffff800`03294e50
Debug session time: Thu Aug 28 20:02:31.116 2014 (UTC - 4:00)
System Uptime: 0 days 0:00:07.505
*********************************************************************
* 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
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007e0b038, 0, 0}

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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!_WHEA_ERROR_RECORD_HEADER                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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!_WHEA_ERROR_RECORD_HEADER                  ***
***                                                                   ***
*************************************************************************
Unable to load image PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************

 

[ATMINSIDE]

124 is typically not enough vCore

 

[Rydis]

so I need to up the vcore of my memory some more? I think im at 2.1 atm.

 

[ATMINSIDE]

so I need to up the vcore of my memory some more? I think im at 2.1 atm.

No, vCore is the CPU voltage.

 

[Rydis]

No, vCore is the CPU voltage.

ill try it and see what happens, thanks.

 

[Rydis]

changing the vcore to anything from auto prevents me from booting.

 

[RJARRRPCGP]

Please check the event log for WHEA errors. Does it say "bus/interconnect error"?

If it does, increase the bus termination voltage!

(I know that this appears to be a common problem for socket 775 quad core processors) (Not as likely with a dual core)

 

[Rydis]

Please check the event log for WHEA errors. Does it say "bus/interconnect error"?

If it does, increase the bus termination voltage!

(I know that this appears to be a common problem for socket 775 quad core processors) (Not as likely with a dual core)

looking under system events I do see any. All I have are:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa8007d38038, 0x0000000000000000, 0x0000000000000000). A dump was saved in: Z:\Windows\Minidump\082914-11278-01.dmp. Report Id: 082914-11278-01.

..oh I just found one:

A fatal hardware error has occurred.

Component: AMD Northbridge
Error Source: Machine Check Exception
Error Type: HyperTransport Watchdog Timeout Error
Processor ID: 0

The details view of this entry contains further information

and

The following boot-start or system-start driver(s) failed to load:
lsnfd.

Just had another restart typing this (thanks chrome for saving even what I typed) and another WHEA error

 

[ATMINSIDE]

What voltages did you try on the CPU?

 

[Rydis]

What voltages did you try on the CPU?

anything other than auto fails to get past post messages. I had it at 1.1 (next setup from auto) and goes up in .0625 increments, but anything other than auto as I said..it failed.

I just spent last 1.5 hours trying to even get it to turn on after turning off all my overclocks. Occastionally when it blue screen restarted me, was telling me to plug the extra PCIe cables into my video card..which they were...

and a few new errors

The following boot-start or system-start driver(s) failed to load:
lsnfd

wasn't accompanied by a WHEA error this time, just

previous system shutdown at 6:32:27 PM on ‎8/‎29/‎2014 was unexpected.

 

[Robert17]

Page 2-10 of the manual says:
The following item only appears when you set CPU Overclocking to [Manual].
CPU/HT Reference Clock (MHz) [200]
Sets the CPU/HT Reference Clock. Configuration options: [Min.=200] [Max.=550]
The following item only appears when you set CPU Overclocking to [Overclock Profile].
Overclock Options [Auto]
Selects the overclocking profile. Configuration options: [Auto] [Overclock 2%] [Overclock 5%] [Overclock 8%] [Overclock 10%]
PCIE Overclocking [Auto]
Sets the PCIE overclocking. Configuration options: [Auto] [Manual]
The following item only appears when you set PCIE Overclocking to [Manual].
PCIE Clock [100]
Sets the PCIE Clock. Configuration options: [Min.=100] [Max.=150]
Processor Frequency Multiplier [Auto]
Sets the processor frequency multiplier. Configuration options: � � � � [Auto] [x8.0 1600MHz]
[x8.5 1700MHz] ~ [x34.5 6900MHz] [x35.0 7000MHz]
CPU/NB Frequency [Auto]
Sets the CPU/NorthBridge frequency. Configuration options: [Auto] [x4.0 800MHz]
[x5.0 1000MHz] [x6.0 1200MHz] ~ [x18.0 3600MHz] [x19.0 3800MHz] [x20.0 4000MHz]
CPU Over Voltage [Auto]
Sets the CPU over voltage. The valid value ranges vary depending on your CPU model. Use <+> / <-> keys to adjust the value. Configuration options: [Auto]
VDDNB Over Voltage [Auto]
Sets the VDDNB over voltage. The valid value ranges vary depending on your CPU model. Use <+> / <-> keys to adjust the value. Configuration options: [Auto]
CPU VDDA Voltage [Auto]
Sets the CPU VDDA voltage. Use <+> / <-> keys to adjust the value. Configuration options: [Auto] [Min.=2.5V] [Max.=2.8V]
LoadLine Calibration [Auto]
Sets the LoadLine. The values range from 0% to 100% with a 3.225% increment. Use the <+> / <-> keys to adjust the value. Configuration options: [Auto] [Max. = 100%] [Min. = 0%]
HT Link Frequency [Auto]
Sets the HyperTransport link speed. Configuration options: [Auto] [200MHz] [400MHz] [600MHz] [800MHZ] [1000MHz] [1200MHz] [1400MHz] [1600MHz] [1800MHz] [2000MHz] [2200MHz] [2400MHz] [2600MHz

 

[Rydis]

Page 2-10 of the manual says:
The following item only appears when you set CPU Overclocking to [Manual].
CPU/HT Reference Clock (MHz) [200]
Sets the CPU/HT Reference Clock. Configuration options: [Min.=200] [Max.=550]
The following item only appears when you set CPU Overclocking to [Overclock Profile].
Overclock Options [Auto]
Selects the overclocking profile. Configuration options: [Auto] [Overclock 2%] [Overclock 5%] [Overclock 8%] [Overclock 10%]
PCIE Overclocking [Auto]
Sets the PCIE overclocking. Configuration options: [Auto] [Manual]
The following item only appears when you set PCIE Overclocking to [Manual].
PCIE Clock [100]
Sets the PCIE Clock. Configuration options: [Min.=100] [Max.=150]
Processor Frequency Multiplier [Auto]
Sets the processor frequency multiplier. Configuration options: � � � � [Auto] [x8.0 1600MHz]
[x8.5 1700MHz] ~ [x34.5 6900MHz] [x35.0 7000MHz]
CPU/NB Frequency [Auto]
Sets the CPU/NorthBridge frequency. Configuration options: [Auto] [x4.0 800MHz]
[x5.0 1000MHz] [x6.0 1200MHz] ~ [x18.0 3600MHz] [x19.0 3800MHz] [x20.0 4000MHz]
CPU Over Voltage [Auto]
Sets the CPU over voltage. The valid value ranges vary depending on your CPU model. Use <+> / <-> keys to adjust the value. Configuration options: [Auto]
VDDNB Over Voltage [Auto]
Sets the VDDNB over voltage. The valid value ranges vary depending on your CPU model. Use <+> / <-> keys to adjust the value. Configuration options: [Auto]
CPU VDDA Voltage [Auto]
Sets the CPU VDDA voltage. Use <+> / <-> keys to adjust the value. Configuration options: [Auto] [Min.=2.5V] [Max.=2.8V]
LoadLine Calibration [Auto]
Sets the LoadLine. The values range from 0% to 100% with a 3.225% increment. Use the <+> / <-> keys to adjust the value. Configuration options: [Auto] [Max. = 100%] [Min. = 0%]
HT Link Frequency [Auto]
Sets the HyperTransport link speed. Configuration options: [Auto] [200MHz] [400MHz] [600MHz] [800MHZ] [1000MHz] [1200MHz] [1400MHz] [1600MHz] [1800MHz] [2000MHz] [2200MHz] [2400MHz] [2600MHz

I didn't have issues finding the options, just changing the options was failing to past post.

 

[ATMINSIDE]

You're probably going to take 1.4V or a bit more to get that CPU stable, did you go that high?

 

[Rydis]

You're probably going to take 1.4V or a bit more to get that CPU stable, did you go that high?

I didn't because if it was failing past auto, then why would going higher work..but maybe 1.1 is lower than auto.

Other than that..my CPU already gets to 55 under load..I think more voltage would just overheat it no?

 

[ATMINSIDE]

Because a CPU needs a certain level of voltage to operate...

Also, unlocking cores can cause instability like this.
Have you tried cutting those extra two cores back off?

 

[Rydis]

Because a CPU needs a certain level of voltage to operate...

Also, unlocking cores can cause instability like this.
Have you tried cutting those extra two cores back off?

ive went to complete default on this, and thats why then PC wouldn't post at all for a good 1.5 hours..and occasionally was giving me the plug in power to pcie slot for some reason.

Now if I ran this setup for a few years with out any issues, could there be a possibility of a faulty Mobo going on here?

 

[ATMINSIDE]

What spare parts do you have to test with?

 

[Rydis]

What spare parts do you have to test with?

none. I know memory is good, video card is new, and I also had a other video card in it before and occasionally had issue, I thought it was related to wildstar because it was only time my PC reset on me.

as far as processor/mobo..I have nothing.

 

[ATMINSIDE]

What kind of reset were you getting with your old GPU?

 

[Rydis]

What kind of reset were you getting with your old GPU?

It would just crash out to blue screen and reset. Load back into windows. It happened only every few days and only playing wildtar (which had memory issues which is why I thought it was wildstar related).

So I ran memtest, and talked with the person who sold me the ram, and I had upped the ram voltage as needed and ran memtest for 9 hours..0 errors.

But I since stopped playing and its still occurring, and more often. Today was the worst though.