Maybe in need of an RMA?

[Rookie1986]

Hey,

I made a thread earlier in the main Hexus forums because I've been having a few problems with my new system and I've been pointed in the direction of a RAM fault and that I should contact yourselves about it, the other thread is located here

Hope you can help me
Rookie

[Mick@SCAN]

Hey,

I made a thread earlier in the main Hexus forums because I've been having a few problems with my new system and I've been pointed in the direction of a RAM fault and that I should contact yourselves about it, the other thread is located here

Hope you can help me
Rookie

Rookie1986,

Please submit a query via our website https://secure.scan.co.uk/aspnet/sup...px?QueryType=R and we will raise a return for the faulty component.

Kind regards,

[Rookie1986]

Rookie1986,

Please submit a query via our website https://secure.scan.co.uk/aspnet/sup...px?QueryType=R and we will raise a return for the faulty component.

Kind regards,

I'm still "testing" the two sticks to try and decide which one it is, or should I return both plus the pring out of crash information to you??

[Lee H]

If the RAM was part of a kit, i.e supplied as 2 modules in the packaging together then these will need to be returned as a pair so they can be tested and then replaced.

Best Regards,

[Mick@SCAN]

I'm still "testing" the two sticks to try and decide which one it is, or should I return both plus the pring out of crash information to you??

Hi, please download a program called memtest from www.memtest.org, this program is a free download and will help determine if your memory is faulty.

You can run this program with one or both sticks of memory installed and it should pin point the faulty module.

Please be aware that as the memory is probably a matched pair both sticks would need to come back anyway.

Kind regards,

[Rookie1986]

Ok, I've ran the memtest and it came back 100% Pass no Errors found....

Maybe building my own PC was a bad idea

[Mick@SCAN]

Rookie1986,

Could you please PM me your invoice number or reply to the email that we have sent you via our OLQ system, I will take a look at the parts and see if I can come up with some suggestions for you to try.

Kind regards,

[Rookie1986]

Ok, I have replied to your email

Rookie

[Rookie1986]

Things seem more stable now that the OC has been turned off and we are just running at default BIOS settings, I will keep testing over the weekend but where do we go for here if the problem lies with the OC??

Regards
/Rookie

[Rookie1986]

Well I guess crashes are like busses, you wait all day for one and then two come along at once. I have loaded the OC profile again in the BIOS so its possible that it could be the cause of the problem because I didn't have any BSOD when running without the OC profile loaded:

On Sun 20/05/2012 13:28:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-16333-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCB545)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000EB545, 0xFFFFF8800C2F2B70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

&

On Sun 20/05/2012 13:10:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-16239-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009C0180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

&

On Sun 20/05/2012 18:05:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-16270-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009C0180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

&

On Sun 20/05/2012 21:14:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-16380-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x0, 0xB, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

I know no one is at the Scan office on a Sunday but if someone can get back to me about this sometime early next week it would be much appreciated - Also I have had several other crashes that do not should up in WhoCrashed, is this normal??

Regards,
Rookie

[Rookie1986]

One more for good luck

On Mon 21/05/2012 21:47:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052112-16348-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88003342180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

[Phage]

because I didn't have any BSOD when running without the OC profile loaded

Sounds like a clue !

[Rookie1986]

Sounds like a clue !

Possibly, or it just means I didn't test the system enough when the OC was turned off. I will reload things in to the default settings and go from there. I'm off all day today so should be able to put the hours in to make 100% sure that the crashes are only while the OC profile is loaded.

Rookie

[Rookie1986]

Voltage up to 1.32 now as advised and still having some problems:

On Wed 23/05/2012 02:57:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052312-17066-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF88005E3638C, 0x0, 0xFFFFF880049C85D8, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

[Rookie1986]

Just a further update:

After setting the Line Load to Lv.1 and upping the voltage to 1.34 these were the results in Core Temp while running Prime95



I'm also still getting a combination of BSOD errors ranging from the ones already listed above in this thread and also in this thread

I have now loaded the default BIOS settings like advised and await further instruction.

Regards,
Rookie

[Rookie1986]

Looks like an error with Core Temp because CPU-z doesn't have the "ES" suffix.

Rookie