If you attach any minidumps back, I'll take it a look at them when I can. ;)
If you attach any minidumps back, I'll take it a look at them when I can. ;)
I renamed it to .txt, couldnt upload it otherwise. So rename it to .dmp when you get it. This is just one of today.
Thx in advance
K, I found a site where all those error codes are listed.
As far as I remember I get these, some multiple times: 0x1e, 0x1d, 0xc4.
Looks like it's bad driver stuff although Ive no clue what driver really. And still I dont understand why a higher clocked CPU might cause this sooner than a lower clocked CPU:shrug:
i think drivers crash first because they are very closely related to hardware..
So due to higher OC'd CPU drivers error sooner or something? If they're bugged of course.Quote:
Originally Posted by Oese
In the past four months I've managed to Build 4 790FX MOBOs. The ASUS, Gigabyte and two DFI Models. The DFI models have died, having memory issues (GSKILL) in all built systems. DFI seems to only have a problem with it, then it would not boot on the first cold start, had to reboot, just to run it. The LED works if you have the Phoenix codes manual that lists the meaning of '88'. The other ASUS and Gigabyte 790FX boards are still running very might I add. Sorry DFI just stating the Facts.:down:Quote:
Originally Posted by Brother Esau
If it means anything AMDkid1 my DFI was defective on arrival. Not dead since it sorta worked, but certainly not right :rolleyes:
Hopefully the replacement works fine.
@ rammsteiner: no i think not bugged drivers will error at first if overclocked too high because of their hardware relation.. otherwise you would get errors even at stock speed.. thats what i can think of not sure really..
@ amdkit: mine runs fine with gskill..
260~262 with CPU=x11; HTT/NB=8/8.Quote:
Great, yeah, you have one of the better Phenoms around. What was max HT on the DFI with low NB/CPU Multi?
I wonder whats happening with the 3GPU setup and the lower oc
Me too lol..., 3-GPU's CFX are reported to work well performance wise in Intel X38 chipsets, not with AMD 790FX chipset, I tested in both MSI/DFI boards, and with MSI I had more troubles for Cat 8.3 recognise the 3-GPU's for enabling CF, it have 4 PCIE slots, bridge connections order depends on PCIE slots used, eg. PCIe1-PCIe3-PCIe2 or PCIe4.
The lower OC, I hope that's BIOS NB/HT 2250MHz limitation, need some feedback from regular Phemons users with this board, or my board is defective in some way. :(
ATM I'm playing with an 5000+ BE, found some Mem divider change at some CPU multi's.
In this case I only manualy changed CPUFID from Default (13) to 15, and Memory timingns to EPP values (CL4 4-3-5 2T) all the other settings are default.
Well I bought this Phenom for Bios Testing so I will do my part to see whats going on with all of this but its going to take some time to get up to speed so I will contribute when its available on my end anyways;)
I to have noticed that some versions of Prime95 just don't seem to agree with this chipset :rolleyes: I use version 25.5 and set to Custom 1700mb for Ram Use instead of 1750mb:up:Quote:
Originally Posted by Oese
24.14 (64bit) seems to work.. will test further with your chip be :D
I checked it out, it's almost certainly a software driver but I couldn't get details on it since the actual file was corrupt (incomplete details). :(Quote:
Originally Posted by Rammsteiner
Some notes on stress testing to keep in mind:-
*In XP/Vista 32b, 2GB installed, nothing in background, not even AV, I can never run plus 1450MB with any stress test, it'll fail at stock or just not run.
*If you start stress testing reserving an area of memory and then you open applications which try to access that reserved space, you will very likely start getting errors in that stress test, even though nothing hardware wise is wrong (even BSoDs). ;)
OK ...Need some advice for my First Vista 32 Bit install on this Board Please:)
Whats the Story with Installing NET Framework on a Fresh Vista 32 Bit Install so that I can Install CATALYST 8.3 ????? Does Vista have NET included into the O.S or is it a separate Installation required like Windows XP????
Vista has .net 2 and .net 3 already installed. Nothing you need to do there, just install the drivers and go.
Wow thats cool:D Hows about some advice on Vista in general? Is there still the Issue with it consuming a large portion of HDD space for what ever reason?
Not sure about the issue, wasn't even aware of it actually :shrug: I have 250GB so I don't care much :D
I am using about 38GB, that is running vista ultimate 64 bit (which I'm sure ultimate takes more), office 2000 installed, 3.5GB game installed, a couple gig or so of other programs installed, some downloaded files...
Yeah vista takes more than xp by quite a bit, but it IS a bigger OS. Also, someone here reported getting some more HD space available after installing SP1, maybe there is a glitch in pre-SP1 vista in space reporting? I don't know for sure :shrug:
Shoot I am referring to something that was a issue quite a while ago like last year when it first became Public Market
Honestly Brother,
To me its about the same as Xp in as far as installation.
Runs some games like crap. Besides that it works fine, does like 4g though. Seems to run allot smoother with more memory. Not sure if Vista 32 will see 4g though. I have Vista 64.
You have done a great job thus far and look forward to your Phenom posts.
I'll have a phenom as soon as the B3 show up or the tri-core with my DK M2RS :)
Thx a lot for checking KTE.Quote:
Originally Posted by KTE
I did a complete fresh install on my 2nd Raptor (had it only plugged in comepletely new, didnt even format lol). Right after I installed .NET 2.0, SB600 drivers from DFI site, went to MS page and did all updates (except for IE7, I hate that. Also deselected Outlook updates, dont use that). Then installed GPU and sound drivers.
After that, Prime95 25.5. OC'd CPU to 16x219 and ran Prime95. And it's still running:shocked: . So most likely it was indeed faulty software stuff then. It's running 2.5 hours now, not super long so Ill keep it going over night. But it didnt last Prime95 so long in days so looks fine untill now.
To examine the issue... D9's not dieing, CPU looks to be fine. Same with mobo then, BIOS 1/30 most likely didnt corrupt the BIOS chip then. I start to think more and more it's due my RAM OC attempts. I had to repair Windows like three times a day due to corrupted/missing files (like NTLDR etc) after attempts. One time just as I pressed enter to log in I received a warning about corrupted registry. But didnt notice anything from that at that moment, but that could be a good candidate too for all the crap. But Ill see tomorrow morning if it's still going.
After that move a few files from old HDD to new HDD, install some games, OC to 14x251 RAM 1:1 4-4-4 again and have some fun. Ill just forget about running ram 1:1 293 then:rolleyes:
...
Still I think it's the friggin Drive Strengths:p:
Found this over at OCW. 9600 BE to 3.25ghz on air. Wonder what the secret sauce was.
http://my.ocworkbench.com/bbs/showth...threadid=72267
That Dude so stole my Phenom 9600 BE:slapass: :slap: ....Bastage!:D
z0mfg, I got a BSOD on the Frsh install after 4 hours of Priming:confused: ... When I was asleep:shakes:
Debug said this:
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\WINDOWS\Minidump\Mini032608-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
*** WARNING: Unable to verify checksum for ntkrnlmp.exe
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.070321-2337
Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140
Debug session time: Wed Mar 26 00:03:21.421 2008 (GMT+1)
System Uptime: 0 days 3:53:28.259
*** WARNING: Unable to verify checksum for ntkrnlmp.exe
Loading Kernel Symbols
.................................................. .................................................. .....................
Loading User Symbols
Loading unloaded module list
..................................................
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffadb9040f938, 0, fffff97fff0d9508, 2}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!xxxReadPostMessage+2da )
Followup: MachineOwner
---------
1: 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: fffffadb9040f938, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff97fff0d9508, 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: fffffadb9040f938
FAULTING_IP:
win32k!xxxReadPostMessage+2da
fffff97f`ff0d9508 8b4708 mov eax,dword ptr [rdi+8]
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffffadf9040f5d0 -- (.trap 0xfffffadf9040f5d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8002acf560 rbx=fffffadf9040f720 rcx=fffffadf9c5b7110
rdx=fffffa80013546a0 rsi=0000000000000001 rdi=0000000000000000
rip=fffff97fff0d9508 rsp=fffffadf9040f760 rbp=fffffadf9be34ed0
r8=fffffa8002acf560 r9=500026a8d4000000 r10=500026a8d57e0004
r11=fffff97ff7ba0280 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
win32k!xxxReadPostMessage+0x2da:
fffff97f`ff0d9508 8b4708 mov eax,dword ptr [rdi+8] ds:0010:00000000`00000008=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800010a5c1c to fffff8000102e890
STACK_TEXT:
fffffadf`9040f4f8 fffff800`010a5c1c : 00000000`00000050 fffffadb`9040f938 00000000`00000000 fffffadf`9040f5d0 : nt!KeBugCheckEx
fffffadf`9040f500 fffff800`0102d459 : 00000000`000007ff fffffadf`9b94cbf0 fffff800`011b4f00 00000020`9d92f628 : nt!MmAccessFault+0x435
fffffadf`9040f5d0 fffff97f`ff0d9508 : fffffa80`01406d80 00000000`00000000 fffffa80`01406d80 fffffadf`9040f930 : nt!KiPageFault+0x119
fffffadf`9040f760 fffff97f`ff0d6c86 : fffffa80`01406d80 fffffadf`9040f930 00000000`00000000 00000000`00000000 : win32k!xxxReadPostMessage+0x2da
fffffadf`9040f7e0 fffff97f`ff05c22c : fffffadf`00000001 fffffadf`00000001 fffffa80`00000000 00000000`ffffffff : win32k!xxxRealInternalGetMessage+0x439
fffffadf`9040f8a0 fffff97f`ff0161df : 00000000`00000000 00000000`00000000 fffffadf`9040fcf0 00000000`00000004 : win32k!xxxDesktopThread+0x4e0
fffffadf`9040fc10 fffff97f`ff0a3800 : 00000000`00000004 fffffadf`9b94cbf0 00000000`00000000 00000000`00000022 : win32k!xxxCreateSystemThreads+0xba
fffffadf`9040fc40 fffff800`0102e33d : 00000000`00000002 00000000`00000000 fffffadf`9b94cbf0 00000000`00000020 : win32k!NtUserCallOneParam+0x3c
fffffadf`9040fc70 000007ff`7c7d802a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
00000000`0085ffa8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ff`7c7d802a
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!xxxReadPostMessage+2da
fffff97f`ff0d9508 8b4708 mov eax,dword ptr [rdi+8]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: win32k!xxxReadPostMessage+2da
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45e6f310
FAILURE_BUCKET_ID: X64_0x50_win32k!xxxReadPostMessage+2da
BUCKET_ID: X64_0x50_win32k!xxxReadPostMessage+2da
Followup: MachineOwner
---------
1: 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: fffffadb9040f938, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff97fff0d9508, 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: fffffadb9040f938
FAULTING_IP:
win32k!xxxReadPostMessage+2da
fffff97f`ff0d9508 8b4708 mov eax,dword ptr [rdi+8]
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffffadf9040f5d0 -- (.trap 0xfffffadf9040f5d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8002acf560 rbx=fffffadf9040f720 rcx=fffffadf9c5b7110
rdx=fffffa80013546a0 rsi=0000000000000001 rdi=0000000000000000
rip=fffff97fff0d9508 rsp=fffffadf9040f760 rbp=fffffadf9be34ed0
r8=fffffa8002acf560 r9=500026a8d4000000 r10=500026a8d57e0004
r11=fffff97ff7ba0280 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
win32k!xxxReadPostMessage+0x2da:
fffff97f`ff0d9508 8b4708 mov eax,dword ptr [rdi+8] ds:0010:00000000`00000008=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800010a5c1c to fffff8000102e890
STACK_TEXT:
fffffadf`9040f4f8 fffff800`010a5c1c : 00000000`00000050 fffffadb`9040f938 00000000`00000000 fffffadf`9040f5d0 : nt!KeBugCheckEx
fffffadf`9040f500 fffff800`0102d459 : 00000000`000007ff fffffadf`9b94cbf0 fffff800`011b4f00 00000020`9d92f628 : nt!MmAccessFault+0x435
fffffadf`9040f5d0 fffff97f`ff0d9508 : fffffa80`01406d80 00000000`00000000 fffffa80`01406d80 fffffadf`9040f930 : nt!KiPageFault+0x119
fffffadf`9040f760 fffff97f`ff0d6c86 : fffffa80`01406d80 fffffadf`9040f930 00000000`00000000 00000000`00000000 : win32k!xxxReadPostMessage+0x2da
fffffadf`9040f7e0 fffff97f`ff05c22c : fffffadf`00000001 fffffadf`00000001 fffffa80`00000000 00000000`ffffffff : win32k!xxxRealInternalGetMessage+0x439
fffffadf`9040f8a0 fffff97f`ff0161df : 00000000`00000000 00000000`00000000 fffffadf`9040fcf0 00000000`00000004 : win32k!xxxDesktopThread+0x4e0
fffffadf`9040fc10 fffff97f`ff0a3800 : 00000000`00000004 fffffadf`9b94cbf0 00000000`00000000 00000000`00000022 : win32k!xxxCreateSystemThreads+0xba
fffffadf`9040fc40 fffff800`0102e33d : 00000000`00000002 00000000`00000000 fffffadf`9b94cbf0 00000000`00000020 : win32k!NtUserCallOneParam+0x3c
fffffadf`9040fc70 000007ff`7c7d802a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
00000000`0085ffa8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ff`7c7d802a
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!xxxReadPostMessage+2da
fffff97f`ff0d9508 8b4708 mov eax,dword ptr [rdi+8]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: win32k!xxxReadPostMessage+2da
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45e6f310
FAILURE_BUCKET_ID: X64_0x50_win32k!xxxReadPostMessage+2da
BUCKET_ID: X64_0x50_win32k!xxxReadPostMessage+2da
Followup: MachineOwner
---------
Does this mean it's win32k.sys this time? And how to fix it? What does it do? Or is it csrss.exe?:confused:
After two weeks of qx6850 i'm back on my phenom system now. And as other reported earlier it feels snappier at 2.3GHz than an qx6850 at 3.0GHz even if it looses all benchmarks.
Anyway, I tried to optimize the memory. Had 4-4-4-12@1066@2,3V working on the intel system. Now on the DFI/Sapphire the minimum i can set in the bios is 4-5-5-16. With memset I can optimize that to 4-5-5-15 that's it.
I ran hdtach and hdtune on winxp32 sp2 and sp3rc2 with two WD 500GB RE2 HD's in Raid0 . Both get better results that the same hd's as raid0 in the p5k-e with an qx6850, well the burst max is better on the Intel system but the average is higher on the AMD machine.
I'll have this setup running for this week and I can do further raid testings if needed.
AMD
http://www.abload.de/img/hdtunez7n.jpg
Intel
http://www.abload.de/img/hdtuneerz.jpg
AMD
http://www.abload.de/img/hdtachj06.jpg
Intel
http://www.abload.de/img/hdtachbu2.jpg
CrystalMark HDD:
AMD
24020 Pts.
Intel
16995 Pts.
Next thing is the RightMark MT test, check those screenies, cores 1 performs more then twice as fast as the other cores.
Ganged - Unganged
http://www.abload.de/thumb/rightmark-gangedwyp.jpghttp://www.abload.de/thumb/rightmark-ungangedo80.jpg
Also I tried to run the HT at 2 GHz (10x) with CPU multi 13 and NB multi 11. But CPU-Z reports it is running at 1.8GHz and Memset calculates the NB speed wrong in that case. If I set it to 1.8 GHz memset still calculates a wrong NB speed (should be 2.2GHz).
http://www.abload.de/thumb/setup-ht2xly.jpg
EDIT: Above testings where done with the latest stable dfi bios from jan 08. Will do some 3850 testings today and try the beta tomorrow to see if some of my issues are gone.
Quote:
Originally Posted by flippin_waffles
After seeing that 4800MhZ+ on 5000+ BE from (Kris?) CPUz certified, I need more evidence.:)
Not to say it's impossible or anything.