Jump to content
Sign in to follow this  
xen

DFI Lanparty S939 NF3 Ultra -TWEAKS

Recommended Posts

turning ON fastwrites seemed to have fixed my pausing problem and give me faster gaming performance overall. so much for that theory... i'll be using fastwrites from now on!

Share this post


Link to post
Share on other sites
turning ON fastwrites seemed to have fixed my pausing problem and give me faster gaming performance overall. so much for that theory... i'll be using fastwrites from now on!

 

Fastwrites should never be turned off, period. If someone said the cure to cancer was to disable fastwrites, I would leave it on because that is too drastic a performance hit to go without.

Share this post


Link to post
Share on other sites

yea man, i can now enable AA in games without my pc shtting a brick. i can run really high settings before but whenever i enabled any kind of aa my system takes a sht. Now its possible...

 

I am going to test 1t setting for my ram, as i assumed it wouldnt work because its cheapo ram. I am typing now at 1t and will test with 3dmark 01/05 and cs:source later..

Share this post


Link to post
Share on other sites
Guest Tim

My fan died yesterday, so I took it off....and it didn't spin at all anymore when I pushed it with my finger...

 

It's very easy to fix this guys... (if you don't want to buy another one)

 

What you need:

 

Screwdriver,

Teflon or WD40

 

(Turn off the PC ofcourse)

 

Take the fan off the HS, peel the sticker off the back, and put a drop of Teflon (or WD40, I prefer Teflon) straight into the little hole, spin the fan around by blowing it, and repeat it once more... see if you can also drop alittle between the spacing between the fan and motor (didn't harm mine, I thought why not.)

 

Look carefully that you didn't spill anything over the fan blades, hook it back up and turn the PC back on.

 

Voila...6000rpm again, purring like a happy kitten :cat: (sort of :nod: )

Share this post


Link to post
Share on other sites
My fan died yesterday, so I took it off....and it didn't spin at all anymore when I pushed it with my finger...

 

It's very easy to fix this guys... (if you don't want to buy another one)

 

What you need:

 

Screwdriver,

Teflon or WD40

 

(Turn off the PC ofcourse)

 

Take the fan off the HS, peel the sticker off the back, and put a drop of Teflon (or WD40, I prefer Teflon) straight into the little hole, spin the fan around by blowing it, and repeat it once more... see if you can also drop alittle between the spacing between the fan and motor (didn't harm mine, I thought why not.)

 

Look carefully that you didn't spill anything over the fan blades, hook it back up and turn the PC back on.

 

Voila...6000rpm again, purring like a happy kitten :cat: (sort of :nod: )

 

Tim:: I'm going to look at this tommorow, you saying theres a hole on the bottom

of the fan after its off the heat sink?

Share this post


Link to post
Share on other sites
Guest Tim
Tim:: I'm going to look at this tommorow, you saying theres a hole on the bottom

of the fan after its off the heat sink?

 

When you remove the little sticker yes...but I'm gonna remove it...because it's sort of dying again....it doesn't start up..once it runs (push it with your finger) it's ok...

 

This fan is just 100% crap...I'm gonna take it off...temps are ok. :)

Share this post


Link to post
Share on other sites

SATA Ports 1&2 are not locked, so avoid the use of these ports when Overclocking.

 

This is clearly not true for the s754 verision. I'll definately keep it in mind for the Ultra D, thanks.

Share this post


Link to post
Share on other sites
Guest Tim

Chipset fan = off and chipset temp is 36c....AS5 on it...I repeat...NO FAN.

 

Even under load it stays cool....

Share this post


Link to post
Share on other sites
Chipset fan = off and chipset temp is 36c....AS5 on it...I repeat...NO FAN.

 

Even under load it stays cool....

Mine also runs way cool but I have like 6 fans moving air through my case, so yeah, even if the chipset fan dies in the night it wouldn't be a problem for me. :drool:

 

You must have good air flow in your case also.

Share this post


Link to post
Share on other sites
Encase anyone has this problem,

 

An app, particularly Counter Strike Source for me, was BSODing for an unkown reason giving a

 

DRIVER_IRQL_NOT_LESS_OR_EQUAL_THAN

 

BSOD halt.

 

Turned out after I pretty much tried everything else, to be a Sound Driver incompatibility with a newer verson od the ac97 driver from Realteks website.

 

Uninstalled and used the one from the CD completely fixed the issue.

I get this on the NF3 250gb. I've thought it was the video driver or something...so will a different sound driver fix it for me?

 

Found this though:

Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL

The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A. This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

 

Parameters

The following parameters are displayed on the blue screen.

 

Parameter Description

1 Memory referenced

2 IRQL at time of reference

3 0: Read

 

1: Write

 

 

4 Address which referenced memory

 

 

Cause

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.

 

The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

 

If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

 

Resolving the Problem

If a kernel debugger is available, obtain a stack trace.

 

To resolve an error caused by a faulty device driver, system service, or BIOS

Restart your computer.

Press F8 at the character-based menu that displays the operating system choices.

Select the Last Known Good Configuration option from the Windows Advanced Options menu. This option is most effective when only one driver or service is added at a time.

 

To resolve an error caused by an incompatible device driver, system service, virus scanner, or backup tool

Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.

Try disabling memory caching of the BIOS.

Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer.

Make sure the latest Service Pack is installed.

If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming proper termination.

For integrated device electronics (IDE) devices, define the onboard IDE port as Primary only. Also, check each IDE device for the proper master/slave/stand-alone setting. Try removing all IDE devices except for hard disks.

 

If the message appears during an installation of Windows, make sure that the computer and all installed peripherals are listed on the Microsoft Windows Hardware Compatibility List (HCL).

 

Here is a debugging example:

 

kd> .bugcheck [Lists bug check data.]

Bugcheck code 0000000a

Arguments 00000000 0000001c 00000000 00000000

 

kd> kb [Lists the stack trace.]

ChildEBP RetAddr Args to Child

8013ed5c 801263ba 00000000 00000000 e12ab000 NT!_DbgBreakPoint

8013eecc 801389ee 0000000a 00000000 0000001c NT!_KeBugCheckEx+0x194

8013eecc 00000000 0000000a 00000000 0000001c NT!_KiTrap0E+0x256

8013ed5c 801263ba 00000000 00000000 e12ab000

8013ef64 00000246 fe551aa1 ff690268 00000002 NT!_KeBugCheckEx+0x194

 

kd> kv [Lists the trap frames.]

ChildEBP RetAddr Args to Child

8013ed5c 801263ba 00000000 00000000 e12ab000 NT!_DbgBreakPoint (FPO: [0,0,0])

8013eecc 801389ee 0000000a 00000000 0000001c NT!_KeBugCheckEx+0x194

8013eecc 00000000 0000000a 00000000 0000001c NT!_KiTrap0E+0x256 (FPO: [0,0] TrapFrame @ 8013eee8)

8013ed5c 801263ba 00000000 00000000 e12ab000

8013ef64 00000246 fe551aa1 ff690268 00000002 NT!_KeBugCheckEx+0x194

 

kd> .trap 8013eee8 [Gets the registers for the trap frame at the time of the fault.]

eax=dec80201 ebx=ffdff420 ecx=8013c71c edx=000003f8 esi=00000000 edi=87038e10

eip=00000000 esp=8013ef5c ebp=8013ef64 iopl=0 nv up ei pl nz na pe nc

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202

ErrCode = 00000000

00000000 ??????????????? [The current instruction pointer is NULL.]

 

kd> kb [Gives the stack trace before the fault.]

ChildEBP RetAddr Args to Child

8013ef68 fe551aa1 ff690268 00000002 fe5620d2 NT!_DbgBreakPoint

8013ef74 fe5620d2 fe5620da ff690268 80404690

NDIS!_EthFilterIndicateReceiveComplete+0x31

8013ef64 00000246 fe551aa1 ff690268 00000002 elnkii!_ElnkiiRcvInterruptDpc+0x1d0

 

 

 

Comments

Before upgrading to a new version of Windows, remove all third-party device drivers and system services, and disable any virus scanners. Contact the software manufacturers to obtain updates of these third-party tools.

 

http://msdn.microsoft.com/library/default....0cb07a6.xml.asp

Share this post


Link to post
Share on other sites
Guest Tim
Mine also runs way cool but I have like 6 fans moving air through my case, so yeah, even if the chipset fan dies in the night it wouldn't be a problem for me. :drool:

 

You must have good air flow in your case also.

 

Yep...good airflow :nod:

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...