Announcement

**solar** · 02-12-2011, 02:23 AM

"Low RAM score problem solved...actually the concept is that if your usable Ram is less than
4GB...then win 7 64 bit limits score to 5.9 irrespective of the any ram you use(ddr3 or ddr2
etc)...

I disabled my onboard graphics from "BIOS and not from Device manager" which solved the problem....now my usable ram is 4094 MB as shown in task manager and i have regained my original rating ... as it was in win 7 32 bit..."

From win7 forums.. okidokie.. .so that explains it.

2. things stand out: A. as I say, you can't trust M$ for anything regarding accuracy... neitehr WEI, and this is a clasisc exmaple of instead of accumulating points, one actually gets pre-defined values based on some arbitrary parameter (eg. hard disks , most spindle will rate 5.9) even raptors haha.

B. It must be a very inaccurate program then since WEI reports my bbandwidth as 19GB/s when throughput should be measured up towards 25.

But ok, I guess I now have to go back and explain to those not impressed.. sigh. I hate that people are so thick and allow lobbying to keep games on windows mainly.. and drivers.. as if MS didn't do the lobbying, windows would of been a sunken ship ages ago and computers would generally be way more stable and all that

Let Mac do the fancy HCI.. and linux the real stuff.

Windows...? erm get them a gucci bag or something ;p

**solar** · 02-12-2011, 02:23 AM

Ooops.. wrong thread.

**solar** · 02-12-2011, 02:35 AM

hmm, on a sidenote.. as long as your cpu temps are fine, then the grease application is ok.. but it does sound awfully lot when the grease goes on the side.

I only now am seeing some of your details.. you really shouldn't bve overclocking is all I can say.

You run 6 cores on 62 degrees C???? and you have fluctuating cpu voltage / NB and wonder why you get bsods..and on top of it all you are running 255-260 ref. clock sheesh.. now it could work but there is something called a 'sweet spot' which just exists or does not exist for a reason. You keep meddling in a configuration which gives you NO stability and you say ' I give up' yes, you obviously are configuring your system entirely non-sequitur; you should go back to the 101 of OC or just leave it alone.

On my system when I do a multi ONLY OC, I could hit 4.2 for 'relative' stability (not production, testing only)... on HT ref. ONLY I could not go above 240 no matter what I did almost on this comp.. it just is a sweet spot.. 243, 241, 250, all failed no matter what I did with my volates, and dram timings.. hint hint? do you see a PATTERN I had to realise? YES.. I was capped on 240.. SO I did 240 x 17 and have a 4.08 GHz OC but in return has had OEN blue scrren of death in its young life.. namely the known ARI CCC bug with sleep/hiber and so I uninstalled CCC and she purrs like a cheetah.

Looking at the classic case of gamers and the like, OC'ing => BSODING, then RMAing probably often perfectly good HW due to absolute unrealistic engineering methods.

**Tradesman** · 02-12-2011, 07:39 AM

Well put. In other words start at all stock settings, get it stable, then work your way up

**animaluc** · 02-12-2011, 02:19 PM

just turned on my pc and checked amd-od just to see how everything was. the nb voltage changed on its own. if you move up the thread you can see what my last tweaks were. it dropped down to stock settings.

not really interested in being belittled here. I was only looking for some help. thanks I think I will find anther place to sort through this issue. I bumped it back up too 1.2

BugCheck 101, {21, 0, fffff880009b1180, 4}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000021, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b1180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.

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

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_6_PROC

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: AMD OverDrive.

CURRENT_IRQL: d

STACK_TEXT:
fffff880`0aaf7a58 fffff800`02e81453 : 00000000`00000101 00000000`00000021 00000000`00000000 fffff880`009b1180 : nt!KeBugCheckEx
fffff880`0aaf7a60 fffff800`02edbde7 : 00000000`00000000 fffff800`00000004 00000000`00026160 43380000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4dfe
fffff880`0aaf7af0 fffff800`02e24895 : fffff800`02e49460 fffff880`0aaf7ca0 fffff800`02e49460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0aaf7bf0 fffff800`02ecfc33 : fffffa80`072a3790 fffff880`0aaf7ca0 00000000`003a57e9 00000000`7ef9b000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0aaf7c20 00000000`0086f2db : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
00000000`02fdfed0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x86f2db

STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCL USIVE

BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCL USIVE

**Tradesman** · 02-12-2011, 07:48 PM

Not belittling you, just not sure what you are doing, you put in a brand new motherboard and immediately started OCing, reading through the threads there have been big jumps all over, and the ZAP you heard right after the new mobo went in wasn't promising. Try putting it all to defaults and working your way up. This AMD OD software sounds like it has problems, you've reported a few times it not reading things right, so I doubt if it sets them right (to interface w/ the system BIOS the software basically needs to be updated for the changes in the BIOS when updated, yet near as I can tell the OD is a across the board generic program for their mobos. It's always best to make changes through the BIOS itself

**animaluc** · 02-12-2011, 08:37 PM

the popping of high voltage happened after windows told me it was an unauthorized copy of windows then froze. I took your advise. bought some CRC QD Contact Cleaner. took out my cpu looked it over with a magnifying glass with a another glass embedded for more magnification. seen some pins had pits.

anyways I took a toothbrush isopropyl alcohol and worked over the cpu pins. looked it over with mag glass till I thought it was clean of whatever then sprayed the hell out of it with CRC QD Contact Cleaner. let it evaporate then looked it over again the installed it then reapplied arctic silver just enough to cover the entire cpu. it will pass an hour long amd-od stability test at bus speed 260mhz. fast enough for me. no need in anymore pain in the *** pc problems. did download a hotfix from microsoft too. Fix302249 dealing with irql_not_less_or_equal bsod's.

http://www.tomshardware.com/news/Win...x-OS,9637.html

**animaluc** · 02-13-2011, 02:54 PM

everything is running smooth with exception of windows media center. it will not show hd channels only analog. i dont care everything else works fine.

**Tradesman** · 02-13-2011, 06:31 PM

Glad you got it going, the problem w/ the high def channels may be your tuner card or driver for it. I know one of my systems has a similar problem using Direct TV as the feed

**animaluc** · 02-13-2011, 06:42 PM

yeah I updated the driver 1/14/2010 but still will not tune any of the hd channels analog are sketchy. ASUS MyCinema-EHC3150 Combo
uninstalled wmc and recreated the drm values but no luck after changing out the mobo. just have to live with it. I rma'd the old mobo hope to get a response from asus soon. funny the whole purpose of this build was so I could do video editing and record tv.

**Tradesman** · 02-13-2011, 07:02 PM

I know how that goes, have the ASUS PE9400 in my main system, which works OK, normally send the signal and do editing on a 28' Hanns-G which is nice and keep the other LCd up for a few Windows like GSkill, and a couple other sites I work with.

**animaluc** · 02-28-2011, 03:58 PM

system was idle 45 minutes and this happen. had no problems in a while.

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

Loading Dump File [C:\Windows\Minidump\022811-26629-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\WinDDK\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e1c000 PsLoadedModuleList = 0xfffff800`03061e90
Debug session time: Mon Feb 28 17:50:05.570 2011 (UTC - 6:00)
System Uptime: 0 days 2:05:48.616
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
........................................
Loading User Symbols
Loading unloaded module list
.....
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a0296b3558, 0, fffff80002ebded8, 2}

Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!FsRtlLookupBaseMcbEntry+48 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a0296b3558, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002ebded8, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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

Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030cd0e8
fffff8a0296b3558

FAULTING_IP:
nt!FsRtlLookupBaseMcbEntry+48
fffff800`02ebded8 443b4cd1f8 cmp r9d,dword ptr [rcx+rdx*8-8]

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 1

TRAP_FRAME: fffff8800a062320 -- (.trap 0xfffff8800a062320)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000004000000 rbx=0000000000000000 rcx=fffff8a0096b3560
rdx=0000000004000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ebded8 rsp=fffff8800a0624b8 rbp=0000000000000000
r8=0000000004000000 r9=0000000000000000 r10=0000000000000000
r11=0000000008000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po nc
nt!FsRtlLookupBaseMcbEntry+0x48:
fffff800`02ebded8 443b4cd1f8 cmp r9d,dword ptr [rcx+rdx*8-8] ds:3540:fffff8a0`296b3558=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002e46ca0 to fffff80002e9c640

STACK_TEXT:
fffff880`0a0621b8 fffff800`02e46ca0 : 00000000`00000050 fffff8a0`296b3558 00000000`00000000 fffff880`0a062320 : nt!KeBugCheckEx
fffff880`0a0621c0 fffff800`02e9a76e : 00000000`00000000 fffff8a0`296b3558 00000000`03d46000 fffff8a0`0bf3e250 : nt! ?? ::FNODOBFM::`string'+0x448c6
fffff880`0a062320 fffff800`02ebded8 : fffff880`0121040e fffff8a0`0bf3e230 fffff880`0a062960 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0a0624b8 fffff880`0121040e : fffff8a0`0bf3e230 fffff880`0a062960 00000000`00000000 fffff8a0`0bf3e140 : nt!FsRtlLookupBaseMcbEntry+0x48
fffff880`0a0624c0 fffff880`012b8c01 : fffffa80`06559e40 fffff8a0`0bf3e140 00000000`00000000 fffff880`0a062690 : Ntfs!NtfsLookupAllocation+0x12e
fffff880`0a062630 fffff880`01338767 : fffffa80`06559e40 fffff8a0`0bf3e140 fffffa80`060038e0 00000000`00000000 : Ntfs!NtfsPreloadAllocation+0x91
fffff880`0a0626f0 fffff880`01302cc6 : fffffa80`06559e40 00000000`00000008 fffffa80`06003800 fffff880`00010000 : Ntfs!NtfsGetRetrievalPointers+0x4d3
fffff880`0a062840 fffff880`012bb53d : fffffa80`06559e40 00000000`00000000 fffff880`0a062960 00000000`00000000 : Ntfs! ?? ::NNGAKEGL::`string'+0x1d04d
fffff880`0a062880 fffff880`01029bcf : fffff880`0a0629d0 fffffa80`03ec9810 fffff880`0a062900 fffffa80`06559e40 : Ntfs!NtfsFsdFileSystemControl+0x13d
fffff880`0a062920 fffff880`0104995e : fffffa80`060038e0 fffffa80`073da920 fffffa80`06003800 fffffa80`03ec9810 : fltmgr!FltpLegacyProcessingAfterPreCallbacksComple ted+0x24f
fffff880`0a0629b0 fffff800`031b6f97 : fffffa80`073da920 fffff880`0a062ca0 fffffa80`03ec9bf8 fffffa80`03ec9810 : fltmgr!FltpFsControl+0xee
fffff880`0a062a10 fffff800`031768c6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`0a062b40 fffff800`02e9b8d3 : 00000000`00000198 00000000`0120e910 00000000`014b1cc0 fffff800`00001000 : nt!NtFsControlFile+0x56
fffff880`0a062bb0 00000000`76f516aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0120e788 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f516aa

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!FsRtlLookupBaseMcbEntry+48
fffff800`02ebded8 443b4cd1f8 cmp r9d,dword ptr [rcx+rdx*8-8]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!FsRtlLookupBaseMcbEntry+48

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a

FAILURE_BUCKET_ID: X64_0x50_nt!FsRtlLookupBaseMcbEntry+48

BUCKET_ID: X64_0x50_nt!FsRtlLookupBaseMcbEntry+48

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

**animaluc** · 08-28-2011, 02:47 PM

Finally stable while OCing 1800mhz.

In bios the adjustments for HT and NB volts do not function properly. I finally found the right combination to OC the ram to 1800 mhz. Pretty muck everything is auto. I never had my voltage above recommend by g.skill which was 1.65 v

Hope this will help anyone else that may build with these components. Never got any reliable help from many websites.

F3-14400CL9D-4GBFLS 1800mhz + ASUS M4A78T-E Deluxe BIOS settings
BIOS
vendor American Megatrends Inc.
version 3406
date 08/20/2010
AI Overclock Tuner - Manual
CPU Ratio x15
Turbo Core disabled

CPU Bus (225)3375
Pcie 100
DRAM Frequency - using the 1600 step OC'd to 1800mhz in bios. I was told by everyone the cpu could only read 1333 step. wrong!

HT Link speed 2025
CPU/NB speed 2250

DRAM Frequency - 900mhz
9-9-9-24
2t

cpu Voltages- 1.35 on auto(1.0-1.475V) cpu Max Temps 62(C) Max Frequency 3500 MHz
CPU/NB Voltage-vid-1.2750
cpu vdda auto
DRAM Voltage - 1.70V
HT Voltage-1.2v on auto these do not represent the same values in overdrive when changed from bios
NB Voltage -1.1v on auto these do not represent the same values in overdrive when changed from bios
SB Voltage-1.35 on auto

cpu spread spectrum auto
pcie spread spectrum auto

enable cpu q-fan
pwr- 4-pin cpu fan
performance

enable cpu q-fan
performance

c1e disabled
cool&quiet disabled-

power options in windows-system cooling policy- active

disabled Advanced Clock Calibration
disabled unleashing mode "No cores to unlock"

**animaluc** · 02-18-2012, 07:07 PM

had to come back and tell everyone that I bought for my first build this.
G.SKILL Ripjaws Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-12800CL9D-4GBRL - Retail
Item #:*N82E16820231277
for $93.99
Even at defaults it would not run. I fought with it for a long time then I gave gskill the benefit of the doubt and bought a new pair after I sold the others for less than half the price I paid.

I got these.
G.SKILL Flare 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1800 (PC3 14400) Desktop Memory Model F3-14400CL9D-4GBFLS for $89.99

And I dialed in all the right numbers and it would not run right. I rma'd them got a new pair and they worked well enough at a low over clock just above default. still had radom crash's and everything pointed to memory so I got these and they were flawless from the moment I started my new amd build.

($74.99) Crucial Ballistix 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model BLE2KIT4G3D1608DE1TX0

I will sell the flares on ebay and hope I get at least half my money back.

My -PC | Sun, 19 Feb 2012 03:49:04 +0100 | Validated by CPU-Z 1.58
http://valid.canardpc.com/show_oc.php?id=2256465

**RamJam** · 02-19-2012, 09:36 PM

Well they have finally updated the BIOS for that mobo, which should have been done months ago, I ran into problems with this mobo and fast RAM on two different occasions, 1600 was about the limit it would run, and the BIOS you have, which is what, about 16months old just wasn't very good. Might give the Flares another try and make gradual adjustments, from what I saw here, were jumping all around

Announcement

AMD Phenom II X6 1075T Thuban 3.0GHz F3-14400CL9D-4GBFLS 1800mhz + ASUS M4A78T-E

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment