My Dlink DWA140 arrived today and is working fine on Win7 64bit with this board. Plugged it in and Windows automatically recognised it.
Nice to know
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
My Dlink DWA140 arrived today and is working fine on Win7 64bit with this board. Plugged it in and Windows automatically recognised it.
Possible causes for that behavior are:why is my 4 gb of corsair pc1333 cas 7 in this dfi board only seeing 3084mb in bios? [snip] perhaps its a bios setting i am missing?
My D-Link has stopped working completely now. It worked for about 10 min after a fresh install of my new Win7 64bit system but won't work anymore despite trying different drivers and reinstalling windows again. It worked perfectly on my old GA-G33M-DS2R Win7 build so I'm stumped. The Zotac board is looking more and more attractive
If the D-link is plugged in while Windows is installing it freezes everything until I unplug it. Once I've logged on and plugged it back in Windows recognises it but says there is no connection. If I try installing drivers they freeze until I unplug the D-link. Safe mode installation didn't help either :-(
Possible causes for that behavior are:
1) Faulty RAM (not likely, but still...) - Run something like CPU-Z or SANDRA, and see if it recognizes the two memory sticks with the correct sizes (that software accesses hardware directly, so it can sniff out the correct info).
2) Check the BIOS for a way to activate "Memory Remap". Asus's BIOS usually have that option, but I never worked with DFI BIOSes, so I don't know how that works, and if the name of the option is even the same.
So, this is what you're experiencing, if your memory is not faulty: the BIOS needs some memory space to store information about what hardware is available, and how hardware can access itself directly (DMA and such); 32bit versions of non-Server Windows also stick with this approach for some OS-related stuff. That can take quite a lot of space, especially if you have a large video framebuffer (a.k.a. GPU RAM), more exactly up to ~1GB of memory space.
In 32bit OSes, that memory mapping MUST be kept within the maximum 4GB confine of the addressable space, often shaving up to 1GB of available RAM space for 32bit OSes, which is why everyone says you only really need 3GB of RAM if you're running a 32bit OS.
In 64bit OSes, addressable memory grew quite a lot, and it's possible to relocate that memory mapping of hardware info to other areas far way from (current) physical limits on addressable RAM, since it's only virtual memory space we're talking about, a technique also known as PAE. However, that breaks 32bit OS support unless both CPU and OS supports it.
Funny thing is, CPU support for PAE is available since the Pentium Pro era, and Windows is PAE-aware at least XP SP2; Linux is also compatible with PAE; MacOS for Intel also handles it; and even FreeBSD.
So, what happens when PAE is not enabled in BIOS and you have a 64bit OS (who are PAE-aware by nature) and 4GB+ of RAM installed? Simply put, you end up with a memory "hole" between the 3GB and 4GB marks. If you only have 4GB of RAM installed, the thing looks just like a 32bit OS: it reports only ~3GB of available RAM, instead of the full 4GB.
I believe I've covered the basics on this. If I made any mistakes, please, guys, do point it out.
Cheers.
Miguel
have tested with other memory here that i know does work its same thing reports 3064mb in system bios and remap is enabled in bios.
i guess a call to dfi is needed at this point since nobody else is seeing this
Jen
If the D-link is plugged in while Windows is installing it freezes everything until I unplug it. Once I've logged on and plugged it back in Windows recognises it but says there is no connection. If I try installing drivers they freeze until I unplug the D-link. Safe mode installation didn't help either :-(
have tested with other memory here that i know does work its same thing reports 3064mb in system bios and remap is enabled in bios.
i guess a call to dfi is needed at this point since nobody else is seeing this
Jen
Yes it's just the original BIOS, newer versions have addressed the issue
Jen, try setting your timings by hand and do a run of memtest.
Or a faulty memory controller, which would mean ditching the CPU (downside of integration, I guess...). Auch.most likely its a bad motherboard
Or a faulty memory controller, which would mean ditching the CPU (downside of integration, I guess...). Auch.
Can you try another CPU (or that CPU on another motherboard), or those are the only ones available right now?
Also, for the sake of completeness, try looking at the PCB traces going from the CPU socket to the memory slots, preferably with a magnifier glass, on both sides of the board. If there's a nicked trace, then it's definitely the mobo.
Good luck.
Miguel
Please read if you are interested in H50 with DFI mini itx board.
http://sffclub.com/index.php?option...corsairproblem&catid=36:sffarticles&Itemid=56
Please read if you are interested in H50 with DFI mini itx board.
http://sffclub.com/index.php?option...corsairproblem&catid=36:sffarticles&Itemid=56
well chances are you won't be handling the board as much as I do to mess it up but for the people that replace heatsinks often or are a little less than careful it does matter. The supplied foam make it so you will have a harder time getting the backplate off. I think a lot of people opt not to have it. I If you do use the foam you still end up hitting the same piece but it's like having an airbag making it possible it doesn't rub as much depending on how much you tighten the screws. The foam on the other side will cover some mosfets which I think is not a wise move since you are basically insulating them if you do that. However it most likely won't hurt.Did you put in the foam supplied on the backplate? That's what I did, there are no problems using H50 on the DFI
The backplate doesnt need to be necessarily in contact with the board, it is the reason why there is a foam supplied for the backplate
Yeah, I probably should have stressed more that it is only a potential problem. I mean I have been using a lot of heatsinks on this board for my tests and some of the others knocked it loose before this one just ripped it off. Most everyone else will just be putting it on there, tighten a little bit and move on. It will just sit on the little black piece (still not sure what you call it) awkwardly.Not having any issues either and I have built 3 of these so far.
Still I'll now use the dual sided tape for sure
I learned NOT to peel backplates off after I had to take a motherboard with one attached to the store after I discovered a very strange behavior... It was sent to the manufacturer, and replaced, the backplate nowhere to be seen. Add to that replacement backplates where not sold in my country at the time, and the end result was about 1.5 YEARS without a decent heatsink on my CPU...I dont peel off the side that will touch the motherboard, never had problems doing that for the last couple of years with other heatsinks
Yeah, the foam doesn't do much but keep it in place. If you are using the sticky part there is no need for it other than to cushion a little.@ Steeeeve : Thanks for the concern, hopefully others dont experience it on their systems
By the way, regarding the foam, I dont peel off the side that will touch the motherboard, never had problems doing that for the last couple of years with other heatsinks
Has anyone updated the BIOS on win7 64? I attempted it with EZ flash as per DFIs advice and now the boards bricked.