Any help determining cause of crashes / instability ?

[JimmyBoy1]

Hi,

The SSD is a recent addition - I did have a 320GB Western Digital hard drive in there before - with the same crashing results, so I am reasonablly confident its not the SSD.

I have in the past loaded the fail safe defaults, but always set a few things after (like disabling the onboard graphics, as I use a GTX 460, and set things like "Full Sreen Boot Logo" to Disabled)

This is going to sound a bit daft, but m not too sure what the capacitors look like! lol I got a few things on my mobo labelled 1R2 (or are these the "chokes" ?), I also have a lot of silver round things! I think these may be the caps! lol

Here is a pic of my mobo

[Ferral]

You see all those silver circular things with the black bit on the right of the top. Those are the capacitors, just check them over, easy enough one to check out.

[JimmyBoy1]

This doesn't sound to me like a disk read blue screen. Sounds like a stability issue with the Ram.

As the Ram controller is on the processor this can only be one of 4 bits of kit

PSU
CPU
Ram
Mobo

Have you tried running memtestx86?

Also, have a look at http://forums.hexus.net/distributed-...ml#post2045958 - It's Intel Biassed, but you can see that the code that Windows reports pertains to which part of the sub-system has failed. The codes will exist somewhere for AMD's so have a google around.

I've usually found stability problems like this are caused by the RAM or PSU. If the RAM is seated correctly (have you tried different slots, or one at a time?), and validates ok, then test the PSU.

What are the reported voltages in Windows? Use CPU-Z...
Is it the same BSOD error number?
Have you connected the ATX 12V connector?
Are there any of the ATX connectors that are loose in their pin?
Have you got all the power points to the motherboard securely in?

Queelis is one of many AMD over/under clockers - it may be worth while dropping him a PM if he hasn't already cast his eyes over this issue....?

I've usually found stability problems like this are caused by the RAM or PSU. If the RAM is seated correctly (have you tried different slots, or one at a time?), and validates ok, then test the PSU.
Yes, I have tried Single/Dual channel config and also swapping modules to try all possibilities. Im not really sure how to "test the PSU"

Have you connected the ATX 12V connector?
Yes.

Are there any of the ATX connectors that are loose in their pin?
All appear to be tight

Have you got all the power points to the motherboard securely in?
Everything appears to be seated correctly, everything that can "clip" in, has.

What are the reported voltages in Windows?


Is it the same BSOD error number?
Ive not always had a chance to make a note. I have been using BlueScreenView to look at BSOD results, but for some reason BlueScreenView was not detecting any new BSOD's after 28/02/2011, I dont understand as to why? So this morning, I went to Control Panel\System and Maintenance\System > Advanced System Settings > Advanced > Startup & Recovery > Settings... and noticed the "Write debugging information" was set to "Kernel Memory Dump", so I changed this to "Small memory dump" (This is what BlueScreenView says it uses), and since ive done this, the two BSOD's that have happened to me today have appeared in BlueScreenView.

Here is a screenshot of the latest BSOD in BlueScreenView, followed by a report of ALL the BSOD's.


==================================================
Dump File : 031311-20155-01.dmp
Crash Time : 13/03/2011 11:10:00
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0x00000004
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x82eba9c9
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+819c9
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\031311-20155-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 164,112
==================================================

==================================================
Dump File : 031311-8299-01.dmp
Crash Time : 13/03/2011 09:24:41
Bug Check String :
Bug Check Code : 0x0000010e
Parameter 1 : 0x0000001f
Parameter 2 : 0xa3219008
Parameter 3 : 0x00000000
Parameter 4 : 0x00000231
Caused By Driver : watchdog.sys
Caused By Address : watchdog.sys+51f0
File Description : Watchdog Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\031311-8299-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 164,144
==================================================

==================================================
Dump File : 022811-8330-01.dmp
Crash Time : 28/02/2011 20:21:48
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0x00000035
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x82ea1148
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+4681b
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\022811-8330-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 155,232
==================================================

==================================================
Dump File : 022811-8502-01.dmp
Crash Time : 28/02/2011 00:38:23
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0x00000000
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x82ef8e9f
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+4681b
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\022811-8502-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 160,912
==================================================

==================================================
Dump File : 022711-8517-01.dmp
Crash Time : 27/02/2011 18:13:07
Bug Check String : REFERENCE_BY_POINTER
Bug Check Code : 0x00000018
Parameter 1 : 0x00000000
Parameter 2 : 0x87f1c148
Parameter 3 : 0x00000002
Parameter 4 : 0xffffffff
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+dcdfc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\022711-8517-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 160,920
==================================================

[JimmyBoy1]

I want too sure about the VCore in CPU-Z as it appears to be diiferent to what the BIOS reports, so I also run HWMonitor



Which reports the same as CPU-Z, but the BIOS has a different VCore


Also, a little confused by the 803 Mhz Core Speed reported by cpu-z as this is a 3.2 GHz CPU (Although 803 x 4 (Multiplier) = 3.2 GHz)

[JimmyBoy1]

Well, after my previous post, I decide to double check my BIOS settings, Exit (without saving), load cpu-z again, and get different results to last time?????



Compared to 1st run :



Im assuming that the first run may of been done after a little while of inactivity and the CPU may of gone into some sort of powersave mode, but this is only a guess?

[Domestic_Ginger]

Cool n Quiet will drop your multiplier; it is the power saving feature.

[JimmyBoy1]

Cool n Quiet will drop your multiplier; it is the power saving feature.

So that is normal then, and nothing to worry about, or should I be considering disabling Cool'n'Quiet ?

[Domestic_Ginger]

keep it imo.

do you know wht those 2 files in your dump do?

[JimmyBoy1]

keep it imo.

do you know wht those 2 files in your dump do?

Are you referring to ntoskrnl.exe and watchdog.sys ?

[Ferral]

That blue screen could possibly be a shared IRQ conflict, check your device manager for any little yellow exclamation marks.

Few links that may help you out here with this one :

http://technet.microsoft.com/en-us/l.../cc957609.aspx

http://www.sevenforums.com/crashes-d...skrnl-exe.html

Looks like that blue screen is quite a common thing since the days of XP.

I still think there could well be a fault on your motherboard.

[JimmyBoy1]

No conflicts or problems in device manager.

with this IRQL_NOT_LESS_OR_EQUAL error, it did make me just wonder if it had anything to do with 4GB installed, and windows only seeing 3.25GB of it.

Im currently running a memtest on my system, and so far no errors. If I leave it run for a few hours and still 0 errors, the I will be reasonablly happy that the memory is fine. If the BSOD issues continue afterwards then I think im going to have to try something which ive been putting off.

I have another AM3 machine here which works flawlessly, so am considering doing a motherboard swap and seeing how things pan out, although I am a bit reluctant to dismantle a perfectly fine PC and then inserting new hardware (motherboard) and possibly getting a new Machine ID which may cause some programs to want to be registered etc... its just a real pain. I may use Acronis True Image to first make an image of the system disk before I do the motherboard swap, so when I put the original motherboard back in, I can restore the image and thus its original Machine ID.

This is something I really want to do as a last resort though, so any other tips / info would be greatly appreciate.

PS: The capacitors appear (visually) to be fine.

[Ferral]

Instead of ripping everything out of 1 machine, just try things like the processor, GPU, ram and PSU out of the faulty machine in your working machine (provided the socket and ram is the stuff your other board takes). Do this one by one and see if the error pops up. If not then it will most likely be your board.

Windows Vista & 7 reserves ram for Aero and a few other things. I have 4 Gb in mine and it shows as 3 available, its perfectly normal so nothing to worry about there.

[JimmyBoy1]

The thing thats really annoying and also puts me off from swaping components is the fact that I cannot find anyway to replicate these BSOD's. Sometimes the machine seems to work fine for a week, maybe even two weeks, then... it all goes pear shaped, so sometimes you think "its working ok now", only for it to randomly happen when your least expecting it. So, I could find myself in the situation of swapping an item, and it appearing to be ok, when in fact it may just be going through a good phase! lol

I hope you understand what im trying to say.

[Ferral]

Yeah, when things like this happen it is frustrating as you cant put a finger on it, there are so many different components in a PC it can end up being any number of things. What makes it worse is the fact that you cant replicate the problem, it is intermittent.

[Tattysnuc]

I'd start by disabling everything, and unplugging all devices onboard, removing the GPGPU card and then enabling items that you want to use one by one. Leave it for a reasonable length of time to see if it's stable, and if it is, then go back in and enable each item you want until you find instability.

Did you uninstall the onboard GFX before you installed the GTX 460?

IRQ complaints are usually modems or audio related, but old drivers have been a big cause of this. My bet would be on the GPUBooster or something related to the onboard GFX. Is this showing in the device manager as working?

IT looks like you PSU is giving a steady voltage judging by the settings you see in Harware manager, and to be fair, 600W is more than enough for what you have...

[kalniel]

I'm not an expert, but this smells of software to me, not hardware. Drivers are the usual suspects, but anti-virus installs/remnants can cause the same symptoms.

edit: oops, didn't see the one post with your problems booting up - that is hardware/BIOS. I would still try a fresh windows install and stable drivers (ones that came with the GPU CD are usually best).