785GTM-E45 vcore reset when resume

I currently have the vcore set to 1.34x in the bios since auto puts it over 1.45. When I resume from S3 the vcore resets itself to auto.
Nothing is overclocked, it is all at default speeds except my memory which is running at 800mhz.
I read about the high auto vcore, but it shouldn't be resetting to auto on resume.
BIOS is version 8.8, that latest I was able to find.

Quote from: wlahdone on 02-March-11, 08:42:05
If your intention is to keep the CPU with low voltages ,you could do the opposite and Enable CnQ ONLY ,to keep the CPU at low voltages dinamically.
And the real measurement is made with a multimeter at the VRM coil outputs on the back of the mobo.
The voltages you see are software reads.
I plan to use CnQ, but CnQ is used to lower power usage while you are using the computer. When not in use I'd prefer it to sleep to save even more energy. I would just shut it down but it is a media PC and I would to be able to turn it on with my remote.
I'm aware the software voltages are not accurate. In the BIOS the "safe settings" for vcore are between 1.447 and 1.456 with Auto being between 1.453 and 1.456. So it isn't just software readings. I considered that the sensor could be doing something weird on resume and reading wrong, but running prime95 for 5-10 mins after a resume shows temps several degrees higher than before the sleep/resume.

Similar Messages

785GTM-E45 VCORE ADJ.?

Hi Everybody,
I update new bios (g10) my 785gtm-e45, IGP overclok is on but there is no vcore adjusment. Will MSI enable vcore adjusment or should we mod our bios to enable or selectable vcore?

See this thread, same topic.
https://forum-en.msi.com/index.php?topic=130185.msg979795#msg979795

P35 - CPU fan reset when resumed from sleep

Hi,
I just got S3 sleep to work where it turns off all fans. The problem is that when it resumes from sleep, the CPU fan spins a lot faster than from boot. I've set it to run at 12,5 % as long as temps are under 65c. I'm guessing it runs at about 50 % when resuming from sleep. It does this until I restart the computer.
Tips?
/Edit; Just checked with SpeedFan, CPU fan normally runs at 1100 RPM, but after resume it runs at 1800 RPM. Any utility I can use that resets this to 1100 after resume?

I ended up disabling fan control in BIOS, so that SpeedFan would work in OS. This means that CPU fan runs at 100 % until OS and SpeedFan har loaded up. Tips to fix this through BIOS or whatever are welcome.

Vcore resets when restarting : AMD XP 3000+ - NEO2

Hi, I'm going to first of all give a brief about my
Computer specs :
AMD 64 "Winchester" 3000+
MSI K8N Neo2
Crucial 3200 Value 512 DDR
etc.
My current config is this:
Core Speed : 2340 Mhz
Multiplier : 9x
HTT : 260 MHz
Current Voltage : 1,360 v
HT: 3x
My Problem
I use CoreCenter to raise my Voltage to 1,6 v
I "save" , or press OK and close down CoreCenter...
CPU-Z tells me that the Core still is 1,6 v
But!
When i restart my computer, the Vcore is back to 1,360 v
Why is it that this happens? It's quite stabile, but i want to raise the Vcore to 1,6 to have the opporunity to raise my HTT even more...
Thanks =)
w0lla

Quote
Originally posted by w0lla
allright, thanks for the tip problem solved.
No prob... just make sure that you don't exceed the 1000mhz HT limit by very much (if at all). There's a very real possibility that you could zorch the CPU's memory controller & other things associated with it.
One poster here exceeded it by a 100mhz or so & got a damaged board and CPU for his trouble.

MOVED: 785GTM-E45 VCORE ADJ.?

This topic has been moved to Overclockers & Modding Corner.
https://forum-en.msi.com/index.php?topic=132121.0

See this thread, same topic.
https://forum-en.msi.com/index.php?topic=130185.msg979795#msg979795

785GTM-E45 and the disappearing video controller

Noticed an odd behavior on my 785GTM-E45 motherboard. When there is no video card installed on the motherboard, the onboard video works.
I have since installed an ATI Radeon HD 4350 board, and I can no longer use the video ports on the motherboard. Hardware info only shows one adapter.
I was hoping to use three or four monitors with this setup, but as of yet no dice.
I have tried both Internal and PCI-E for the primary video setting in the BIOS, but that doesn't seem to change anything.
Anyone know why this is? Thanks!

+1.
I have a G45 Asus mobo, and the only thing I can do when a videcard is installed is choosing between internal (and the videocard doesn't work) or pcie (and the internal doesn't work). Before, I had an old G31 Gigabyte motherboard, and I was able to use both internal and pcie at the same time. Maybe some nvidia 9300/9400 boards too. I never tried a pcie card with my 890GXM-G65, don't think it will work.
What you can do, since you only have an HD4350, is to plug it in the pcie 1x port...you'll have to cut it at the end (quite easy with a cutter, but be careful !), but normally you should be able to use both HD4350 and Internal (not too sure how the driver will react ?). You could also buy a special pcie 1x videocard (or pci).
http://forums.whirlpool.net.au/archive/1380104

785GTM-E45 MOBO BIOS V 8.80 RANDOMLY RESETS BOOT SEQUENCE

785GTM-E45 MOBO W/ PHENOM 9750 QUAD CORE CPU/4 GB WINTEC DDR2 PC6400 (2 x 2 GB) / WINDOWS XP SP3
PROBLEM: BIOS V 8.80 RANDOMLY RESETS BOOT SEQUENCE
I HAVE 4 HARD DRIVES (2 SATA II - 1 USB 2.0 1 USB 3.0) ALL OF WHICH HAVE MULTIPLE PARTITIONS WITH 1 ACTIVE ON EACH DRIVE
SATA II DRIVES / DEVICES:
ON SATA 1: HITACHI 1TB SATA II DRIVE
ON SATA 2: MSI DVD-CW RW
ON SATA 3: MAXTOR 320GB SATA II DRIVE
USB DRIVES:
1. SEAGATE FREE AGENT EXTERNAL USB 2.0 1TB HD
2. FANTOM EXTERNAL USB 3.0 2TB HD (VIA DIABLOTEK USB 3.0 PCI-E CARD)
EXPLANATION OF PROBLEM AND FIXES ATTEMPTED TO DATE
IN BIOS BOOT SEQUENCE I SELECT THE HITACHI HD AS 1ST DEVICE AND ALSO SET IT 2ND 3RD AND 4TH AND BOOT OTHER DEVICE DISABLED. SAVE/EXIT BIOS AND WHEN SYSTEM REBOOTS IT RANDOMLY SELECTS ANY OF THE 4 DRIVES TO BOOT FROM. WHEN I ENTER BIOS AGAIN IT SHOWS WHATEVER DRIVE IT HAD SELECTED TO BOOT FROM AS 1ST, 2ND, 3RD AND 4TH DEVICE. ENABLING OR DISABLING BOOT FROM OTHER DEVICE MAKES NO DIFFERENCE.
ORIGINALLY MY HITACHI WAS ON SATA 3 AND THE MAXTOR ON SATA 1 - I SWITCHED THESE AND NO DIFFERENCE. BIOS SWITCHES BOOT DEVICE NOT ONLY TO THE MAXTOR SATA DRIVE BUT ALSO TO THE USB DRIVES. USUALLY WHEN I REENTER BIOS AND CHANGE THE BOOT SEQUENCE BACK FROM WHATEVER HD IT SHOWS TO THE HITACHI IT WILL USUALLY THEN BOOT FROM THE HITACHI SOMETIMES THOUGH IT TAKES 2 OR 3 TRIES TO GET IT TO BOOT FROM THE DRIVE I HAVE SELECTED AS 1ST BOOT DEVICE.
I HAVE TESTED ALL DRIVES EXTENSIVELY USING ONTRACK EASY RECOVERY PROFESSIONAL SOFTWARE AND ALL DRIVES SHOW NO PROBLEM.
MSI LIVE UPDATE 5 REPORTS THAT THE BIOS IS 8.80 HOWEVER IT ALSO SHOWS MY OS AS WINDOWS 2000 WHICH IS INCORRECT. MY CURRENT OS IS WINDOWS XP SP3. MY XP INSTALLATION WAS AN UPGRADE FROM WINDOWS 2000.
PROBLEM IS NOT DEVASTATING JUST ANNOYING IF ANYONE KNOWS OF A FIX I'D LOVE TO HEAR ABOUT IT. IF THIS IS A BUG IN THIS VERSION OF THE MOBO BIOS I SURE HOPE THEY EXTERMINATE IT AND RELEASE AN UPDATED VERSION IN THE NEAR FUTURE.

Quote from: Bas on 26-August-11, 18:07:03
How do you know it's randomly booting a different drive?
What are the messages you get?
As this:
That looks like a broken drive to me, where it can't find the bootsector/mbr in time to boot from, so the BIOS moves to the next drive and tries again.
I built this box about 2 months ago or so and this is the version of BIOS that came with the MOBO. I have not flashed the bios in this board.
As for knowing that it is randomly booting from a different drive as I stated each of my 4 drives has at a minimum 1 active partition. The Hitachi has a dual boot setup in Windows and if it is booting from the Hitachi drive I will get the Window giving me a choice of booting from either the Hitachi or the Seagate. If I select the Hitachi I also have it setup for two hardware profiles so it then gives me that screen to select profile 1 or 2. If I get these screens no problem - I select the Hitachi and profile 1 and it boots without any further problem.
If it has switched lets say to the maxtor (remember I have selected the Hitachi as 1st, 2nd, 3rd and 4th for boot sequence and the boot from other device is NO) I get no multi boot option it just automatically starts Windows from the active partition on the MAXTOR (I can tell because the last time I used the Maxtor didn't shut down Windows properly so I get the option screen to boot normally or use safe mode etc). The active partition on the Maxtor is a duplicate of the Hitachi but about 2 months old - basically a backup of the Hitachi active partition but out of date and without the multi boot option.
In addition if it has switched boot drives and I hit my reset button and del to open up bios again and go to the boot sequence menu it will no longer show my hitachi as all 4 choices but sometimes it will show all 4 drives in varying order (including the hitachi but not as first device), sometimes 1 drive in all 4 (as in the seagate or the maxtor or the fantom drive in all 4 of the boot sequences) this seems to occur randomly and each time the list of boot sequence is different.
Keeping in mind that I had initially selected the Hitachi drive in all 4 of the boot sequences and selected NO to boot from other device - If the Hitachi drive was not ready or had a bad bootsector/mbr should I not get a message similar to "cannot boot from selected device so and so is missing etc?? I was under the impression that when one disabled the boot from other device as in NO then the bios should not attempt to go any further then attempting to boot from the selected device(s)????
As for the broken drive and bios moving to the next drive and trying again I could understand that 1. If I had not supposedly disabled its ability to do that 2. I could perhaps understand this going to the next drive if I had selected the Seagate USB drive as my initial drive because of it's so called sleep mode which I have now turned off as it was causing errors in windows. In addition I have run numerous and rigorous tests on the drives and they all passed with flying colors.
Yesterday after a couple of tries I booted from the Hitachi drive (it was listed as 1,2,3,and 4 in bios and the boot from other device was NO) and was using that all day and was on it when I posted my help request here. Shortly thereafter I properly shut down my computer. Now I would think that when I turned it on again this morning the BIOS would have maintained its previous settings of the Hitachi in all 4 of the boot sequences and the No on enabling it to boot from other device? However when I booted up again this morning it tried to boot from the Maxtor (I can tell because I get the option screen to boot normally or use safe mode etc) so I hit the reset button and then entered bios and boot sequence and now it showed the Seagate as 1 (it had just tried to boot from the Maxtor when I hit the reset button), the Fantom as 2, the Maxtor as 3 and the Hitachi as 4 and boot from other device still said NO - changed them once again to show the Hitachi in all 4 positions and exited bios and it did then boot from the Hitachi and here I am writing this message using Windows XP located in the active partition of my Hitachi drive.
I'm not exactly a novice as my computer experience goes all the way back to mainframe days of the IBM 360 series computers. I have built so many boxes I have lost count including numerous one using MSI mobos and I have never encountered a problem similar to this. As I said it is not devastating just annoying - the only thing I can think of to totally eliminate the possibility of it being the mbr/bootsector of the Hitachi drive is to back up the drive and rewrite those sectors even though no errors have been reported.
I could be wrong but after messing with this for sometime it really seems to be a bios bug or perhaps just my bios is defective - I was able to dl a copy of v8.8 from another post in the forums - and have not used it yet. Sent all of this info in a Tech support request and posted it here to see if there were any solutions I may have overlooked before flashing the bios with a dl copy of the same version I have installed.
As for downloading the current v of bios from the forums here it was apparently the only way I could get a copy as Liveupdate 5 shows that I have the current version installed and only gives me a message that my mobo bios is current and no download is needed or something like that and the MSI site no longer gives one the ability to download the mobo bios without using liveupdate 5 or at least I couldn't find one. Guess they got tired of people killing their boards with bad flashes.

785GTM-E45 RAM problem

I've bought the board last February and paired it with dual channel 2GB (1GB x 2) Team Xtreem Dark DDR2-1066 CL 5 rams. Everything worked flawlessy.
Yesterday, I purchased a 4GB (2GB x 2) G.Skill DDR2-1000 CL5 rams to replace the Team Xtreem. I inserted the modules, turned the power on, but the system wouldn't post. I made a bios reset and and still the system won't post. I tried to troubleshoot the problem and found out that Slot 1 won't accept either of the 2GB modules. I used Slot 2 and stress tested both rams (one at a time) and both worked fine.
Currently I'm back with the Team Xtreem setup.
Are there any compatibility issues on the G.SKill RAMS? Do I have to update the board's BIOS to make Slot 1 accept the 2GB RAM? Any advice is greatly appreciated.
My system's spec by the way is:
Processor: AMD Phenom II x4 910e (stock)
Motherboard: MSI 785GTM-E45 (BIOS version 8.6)
RAMS: 2GB (1GB x 2) Team Xtreem Dark DDR2-1066 CL 5 (hope to replace it with 4GB (2GB x 2) G.Skill DDR2-1000 CL5)
PSU: Corsair HX450w PSU
Video: Sapphire ATI Radeon HD 5770 1GB

Quote from: Bas on 30-August-10, 15:22:44
So if you put the old memory back everything is fine again?
If so return the Gskill and get some other brand memory, we have seen many problems with Gskill.
Yup. I can't return it though coz it performed perfectly fine on another AMD setup so the culprit might be in my system. Will do a system cleanup later and see what happens.
:edit:
Also can anyone direct me to the latest 8.7 bios for my board? Live Update 4 says there's a latest one (8.7) and says that it has improved memory compatibility.
The problem is when i start downloading it, Live Update says Download fail. URL Invalid.

10.6.4 complete system freeze when resuming from screensaver-VMWare Fusion

I have a Macbook Pro, 3,1. I just upgraded to 10.6.4 and noticed the following symptoms:
Shortly after launching VMWare Fusion 3.1 running a Windows XP VM (from a Bootcamp partition), a series of pop up messages were complaining about a bad OpenGL driver. The message popped up repeatedly and wouldn't let me out, even though I kept pressing "Ok". I had to force quit Fusion, which caused a chkdsk on relaunch of the XP VM.
After a complete reboot, I started VMWare again. The Fusion complaints haven't shown up again, but when resuming from the screensaver, the system either completely freezes up, or the screen login window starts to flash rapidly and seize up. I'm running Spaces with 6 virtual screens. Whether I'm in the Fusion Spaces screen or any other Spaces screen, the system freaks out when resuming from a screensaver.
I use this system at work, so I have to be able to lock my screen when I leave my cube. The only way I've been able to ensure the system doesn't freeze up and cause a hard reset of the XP VM is to completely disable the screensaver and power saver features, such as Start Screen Saver = Never, Computer Sleep = Never, Display Sleep = Never and launch the login window by clicking on my user name in the upper right corner of the screen on the menu bar. Even that causes a sluggish screen and I'm not confident it will keep working. I also made sure (from day one) that the Windows XP screensaver functions were all completely disabled. I prefer to use the OS X screensaver for everything, if for no other reason than having a single screen locking/unlocking point for when I step away.
This was all working properly in 10.6.3. The only nit-nat I noticed about Fusion in 10.6.3 was that it had to be launched in the "Primary Window", which seems to be the upper leftmost Spaces desktop. If I ever moved it to, or started in any other Spaces desktop, it would also exhibit the same random lockups. Keeping it in the "primary" space seems to have stopped the lockups.
I noticed that there seemed to be significant updates to the OpenGL drivers in 10.6.4. I am experiencing an unfortunate side effect of these updates and hope I'm not alone and that a fix is coming soon. Looking at the other posts, there seem to be a lot of similar problems. I wanted to describe my configuration in case the Apple dev team reads these posts. Thanks.

I ended up doing an erase and fresh install of Snow Leopard (10.6.0), upgraded to 10.6.4 with the combo update, then a fresh install of all my apps, including VMware 3.1. Everything has been solid for 2 days now. I'm guessing that my system had a magic combination of issues that weren't visible in 10.6.3 but became obvious only after upgrading to 10.6.4. I had been upgrading my OS since 10.5.0 over the last 2 years and needed to do a clean re-install for some time now.
I'm guessing that others who are noticing problems with the 10.6.4 update have a similar situation with their installations. Think back on all the times a software installation failed, or the system required a hard boot. Plus, I had a lot of 3rd party apps on my box that never posted updates for later Snow Leopard releases, so who knows? Anyway, it's good to have a clean and snappy system again. A lot of my apps launch a lot faster now and survive the screen saver and power saver modes just fine.
Message was edited by: mausoleum

X220 very slow reconnecting to WiFi when resuming from sleep

So my X220 with the Intel 6205 card is having issues reconnecting to WiFi when resuming from sleep or hibernation. It takes about a minute for it to do so, though occasionally it will reconnect right away. Maybe 1 out of 20. When doing a cold boot or restart, it connects immediately upon the desktop showing up.
This was not always the case, in fact when I first got my X220 in June, I have not had this issue.... In fact, I don't know when it started happening, but it was maybe a couple months ago. I just thought it was my old router going bad. Well I got a new router, and it still happens. I have the latest Intel WiFi drivers from Lenovo, and I even tried downgrading to the previous driver from Intel's site. Still the same problem. I tried setting a default profile in access connections, and that does not help. In fact, it behaves the same way if I totally uninstall access connections as well. In fact I tried this on three different brand routers, and I can reproduce it on all of them (Asus, Netgear & TP-Link) so I think this is not a router issue. Other devices in the house reconnect right away with no issues (iPhone 4, PS3, Mac desktop, Dell laptop).
I currently have BIOS 1.24, but this was happening with 1.21 and 1.23 as well. My X220 originally came with 1.16, and I haven't updated it until 1.21. Unfortunately I don't remember that far back, if the problem started occuring then.
There was a brief discussion about this in another thread, but it went nowhere so perhaps this will get more attention. At least one other user reported the same issue.
Here's a clip of exactly what happens. When i press the button or open the lid from sleep, the windows wifi icon will start spinning for a few seconds, then turn into an X. then only about a minute later, does it quickly connect to the wifi and I have full signal. Manually clicking on the icon and selecting the access point does not speed up the process. It will only connect when it wants to, about a minute after resuming from sleep/hibernation.
http://youtu.be/dmboeA7HBgg
| X220 i7-2620M | 12.5" IPS | Intel 520 Series 180GB Main SSD | Mushkin 120GB mSATA SSD | 8GB RAM | Intel 6205 WiFi | BT | Win7 Pro 64 SP1 |
Solved!
Go to Solution.

Normally when a laptop running windows tries to connect to a network, it may also seek to identify certain components on the network, for example, asking the router "Who are you?". In your case, maybe the config are corrupted because the network address entries are messed up. Queries send out to the network come back with no replies, and the computer waited for the default time till timeout and it gives up.
Try this one at a time, reboot, or try all at once and reboot
TCP/IP stack repair options for use with Vista or 7.
Start, Programs\Accessories and right click on Command Prompt, select "Run as Administrator" to open a command prompt.
Reset WINSOCK entries to installation defaults: netsh winsock reset catalog
Reset IPv4 TCP/IP stack to installation defaults. netsh int ipv4 reset reset.log
Reset IPv6 TCP/IP stack to installation defaults. netsh int ipv6 reset reset.log
Reboot the machine.

Access Violation in aapltp.sys when resuming from sleep.

Hello,
*I have diagnosed an issue in the aapltp.sys (touch pad) driver included with the MacOS 10.6.2 DVD. This issue causes a illegal access to be performed by this driver when the computer resumes from sleep (I have never reproduced it when resuming from hibernate or during normal operation). This issue occurs about once in every 10 resume operations, with both Windows 7 and Windows Vista. I have not experimented other versions of the OS.*
*The version of this driver included with 10.5.x DVD does not have this issue - this is a new regression.*
*In summary, KeyMagic (another apple driver) running on a system thread calls the OS for a dispatch (FxDevice::Dispatch). This ends up being routed to aapltp. While executing, aapltp dereferences a memory position offseted from a register that contains NULL. This causes an Access Violation which escalates into a BugCheck.*
*AFAIK Apple does not distribute driver symbols so I was unable to dig into the cause for the fault in this driver. I am appending some additional crashdump information that might be useful. If you require additional information, let me know. I can either provide you with the full crashdump of perform further analysis if you make the symbols available.*
* Bugcheck Analysis *
SYSTEMTHREAD_EXCEPTION_NOTHANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88004a7ea74, The address that the exception occurred at
Arg3: fffff88005134718, Exception Record Address
Arg4: fffff88005133f70, Context Record Address
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
aapltp+ca74
fffff880`04a7ea74 807e5b01 cmp byte ptr [rsi+5Bh],1
EXCEPTION_RECORD: fffff88005134718 -- (.exr 0xfffff88005134718)
ExceptionAddress: fffff88004a7ea74 (aapltp+0x000000000000ca74)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000000000000005b
Attempt to read from address 000000000000005b
CONTEXT: fffff88005133f70 -- (.cxr 0xfffff88005133f70)
rax=0000000000000000 rbx=0000000000000004 rcx=fffffa80057899e0
rdx=0000057ffa876618 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004a7ea74 rsp=fffff88005134950 rbp=fffffa8005789d50
r8=fffff88004a7b140 r9=0000000000000000 r10=fffffa80056809e0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000057ffa99e188 r15=0000057ffa99e188
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
aapltp+0xca74:
fffff880`04a7ea74 807e5b01 cmp byte ptr [rsi+5Bh],1 ds:002b:00000000`0000005b=??
Resetting default scope
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 000000000000005b
READ_ADDRESS: 000000000000005b
FOLLOWUP_IP:
aapltp+ca74
fffff880`04a7ea74 807e5b01 cmp byte ptr [rsi+5Bh],1
BUGCHECK_STR: 0x7E
DEFAULTBUCKETID: NULLCLASS_PTRDEREFERENCE
LASTCONTROLTRANSFER: from fffff88000e52f90 to fffff88004a7ea74
STACK_TEXT:
fffff880`05134950 fffff880`00e52f90 : fffffa80`05661e70 0000057f`fa9443a8 fffffa80`056809e0 fffffa80`056bbc50 : aapltp+0xca74
fffff880`051349b0 fffff880`00e5299f : 00000000`00000000 fffffa80`05661e70 fffffa80`056bbc50 fffffa80`056bbc50 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x4b8
fffff880`05134a30 fffff880`00e51f98 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`05661fc2 : Wdf01000!FxIoQueue::DispatchEvents+0x4df
fffff880`05134aa0 fffff880`00e57558 : fffffa80`04e2fb00 fffffa80`05661e70 fffffa80`04e2fb00 fffffa80`05661e70 : Wdf01000!FxIoQueue::QueueRequest+0x2bc
fffff880`05134b10 fffff880`00e41245 : fffffa80`05661e70 fffffa80`04160c30 fffffa80`04e8ea58 00000000`000f2008 : Wdf01000!FxPkgIo::Dispatch+0x37c
fffff880`05134b90 fffff880`04a672f6 : fffffa80`04160c30 fffffa80`056bcc90 00000000`00000000 00000000`000007ff : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`05134bc0 fffff880`04a6660b : fffffa80`056bcc90 fffffa80`04e8c010 fffffa80`08897640 fffffa80`04e8ec20 : KeyMagic+0x32f6
fffff880`05134c30 fffff800`03334166 : fffffa80`04e00040 00000000`00000080 fffffa80`03cd1740 fffffa80`04e00040 : KeyMagic+0x260b
fffff880`05134d40 fffff800`0306f486 : fffff800`03209e80 fffffa80`04e00040 fffffa80`03ce6680 fffff880`0122ca90 : nt!PspSystemThreadStartup+0x5a
fffff880`05134d80 00000000`00000000 : fffff880`05135000 fffff880`0512f000 fffff880`05134770 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_NAME: aapltp+ca74
MODULE_NAME: aapltp
IMAGE_NAME: aapltp.sys
DEBUGFLR_IMAGETIMESTAMP: 49c7fb1c

Thanks for posting this information in this forum. You just saved me a couple thousand dollars!
Based on my experience if you want to get this problem fixed as soon as possible you need to do the following:
1. www.apple.com/feedback
2. Post a video of the problem on www.youtube.com
3. Send www.apple.com/feedback a link to the video on youtube.
4. Encourage others to visit your youtube video and to post their own.
Good luck!

UVD-power summary of MSI 5770 Hawk, 5570, & 785GTM-E45; Hawk min voltage

MSI R5770 Hawk
MSI R5570-MD1G
MSI 785GTM-E45
GPU PWR SYS f_GPU f_VRAM V_GPU set V_GPU meas Note 1: freq & voltage Note 2: system state
DCW Mhz Mhz V V
785 35 197 400 idle stock idle, light (5 min max)
785 46 498 400 UVD stock 1x 720p sharpen complex 2
5570 43 157 200 0.9 idle stock idle, light (5 min max)
5570 54 400 800 1 UVD stock 1x 720p sharpen complex 2
5570 52 400 800 0.9 0.8987 UVD undervolt/underclock 1 1x 720p sharpen complex 2
5570 55 400 800 0.9 0.9001 UVD undervolt/underclock 1 1x 1080p sharpen complex 2
5770 53 157 300 0.95 0.956 idle stock idle, light (5 min max)
5770 58 157 600 0.95 0.957 idle 2x f_VRAM idle, light (5 min max)
5770 65 157 1200 0.95 0.957 idle 4x f_VRAM (nom. max) idle, light (5 min max)
5770 61 400 900 0.95 0.958 idle @ UVD stock idle, light (5 min max)
5770 72 400 900 0.95 0.9499 UVD stock 1x 720p sharpen complex 2
5770 75 400 900 0.95 0.9508 UVD stock 1x 1080p sharpen complex 2
5770 60 157 300 0.95 0.9498 UVD undervolt/underclock 1 1x 720p sharpen complex 2
5770 63 157 300 0.95 0.9503 UVD undervolt/underclock 1 1x 1080p sharpen complex 2
5770 61 157 200 0.95 0.9497 UVD undervolt/underclock 2 1x 720p sharpen complex 2
5770 61 157 200 0.95 0.9497 UVD undervolt/underclock 2 1x 1080p sharpen complex 2
AMD Power Play states are glitchy, and not all videos detect and run with DirectX Video Acceleration. So max power during playback can end up on the highest power state which is not shown above.
MSI R5770 Hawk minimum power
The uP6204 power controller used on the MSI R5770 Hawk design nominally supports 0.5625 to 1.3500V in 0.0125V steps.
With a stock video BIOS, MSI Afterburner 1.50/1.51 allows the MSI R5770 Hawk to be soft-modded from 1.000 to 1.350V in the roughly 0.0125V steps.
The video BIOS can be set as low as 0.950V but with no steps between 0.950 and 1.000V.
MSI Afterburner 1.60 beta 4 or earlier adds the AllowCaptureVoltageDefaults profile setting. Acquiring, then changing the default GPU voltage allows "resetting" the Hawk to 0.950V in Afterburner for the highest frequency state. This allows maintaining Power Play transitions and running the max frequency at 0.950V, where Afterburner by itself is limited to 1.000V.
The max frequency state of the Hawk is 875 MHz 1200 MHz 1.200V. To have the most flexibilty on control the Hawk, lowest power in the Desktop/HTPC/light gaming, and the ability to manually overvolt/overclock for specific games: run the Hawk at 0.950V in the max frequency state.
How-to work around Afterburner and the Hawk design to run 1.000V in the max frequency state. *
1) in the video BIOS, leave the voltage as 1.200V in the BIOS--which is required for Afterburner to change the Hawk voltages in Windows
2) in the video BIOS, change the GPU frequency of that state to something less than or equal to the maximum stable frequency at 1.000V
3) in Afterburner, Reset to default settings **
4) in Afterburner, change "Core Voltage" to 1.000V
5) in Afterburner, Apply
6) in Afterburner, Save to Profile 1
7) in Afterburner, \Settings\Profiles\2D Profile\ & "3D Profile" choose "Profile 1" ***
8) on each Windows startup, run Afterburner
How-to work around Afterburner and the Hawk design to run 0.950V in the max frequency state.*
1) in the video BIOS, leave the voltage as 1.200V in the BIOS--which is required for Afterburner to change the Hawk voltages in Windows
2) in the video BIOS, change the GPU frequency of that state to something less than or equal to the maximum stable frequency at 0.950V
3) in Afterburner, confirm the voltage default setting for 0.950V--capture voltage defaults as needed using AllowCaptureVoltageDefaults mentioned above
4) in notepad as an Administrator (Win 6.x), change the Hawk's profile configuration file to 0.950V
example:
[Settings]
uP6204_Defaults=D7 20
5) in Afterburner, Reset to default settings **
6) in Afterburner, change "Core Voltage" to 1.000V--changing the profile setting to 0950/950 is not useful as of 1.60 beta 4.
7) in Afterburner, Apply
8) in Afterburner, Save to Profile 1
9) in Afterburner, \Settings\Profiles\2D Profile\ & "3D Profile" choose "Profile 1" ***
10) on each Windows startup, run Afterburner
11) in Afterburner, "Reset" to re-enable 0.950V.
* UnlockVoltageControl in the primary Afterburner profile's [Settings] will likely be needed.
** Only default profiles support Power Play states correctly.
*** Having a non-"default" profile in 3D results in the "3D Profile" activating instead of the UVD in the BIOS.
MSI Afterburner, default voltages
Profile Idle V_GPU @ V_CORE (V)
D7 12 1.125
D7 14 1.100
D7 16 1.047
D7 18 1.049
D7 19 1.037
D7 20 0.949
D7 21 0.937
D7 22 0.925
D7 23 0.912
D7 24 0.899
Power Play states in RBE 1.25
0 Boot 00 -> 00 -> 00
1 Power saving 01 -> 02 -> 00
2 UVD 03 -> 03 -> 03
3 Power saving 04 -> 02 -> 00
4 ACPI 01 -> 01 -> 01
Stock clocks & V_GPU
Clock info 00 01 02 03 04
f_GPU 875 157 600 400 400
f_RAM 1200 300 1200 900 1200
V_GPU 1.20 0.95 1.00 0.95 0.95
My current and likely final settings for MSI R5770 Hawk:
MOD clocks & V_GPU
Clock info 00 01 02 03 04
f_GPU 714 157 600 157 400
f_RAM 1200 300 600 300 600
V_GPU 1.20 0.95 0.95 0.95 0.95
Afterburner Profiles
# CoreVoltage CoreClk MemClk
1 0950 714000 1200000
2 1000 785000 1200000
3 1125 902000 1200000
5 1200 951000 1200000
More data & full system config:
http://forums.techpowerup.com/showpost.php?p=1858205&postcount=1

Msi 785gtm-e45 Video issues

Hello everyone, hope you can help.
I have just changed from a Lanparty Jr series (due to a bios failure) to a Msi 785gtm-e45 motherboard. Everything is okay apart from running the graphics card which does not output any video. I first thought this was a bios setting so I tried setting the video default to pci-e, no change. I'm currently running on the on-board graphics (HD4200) with the 9600gt also inserted, the odd thing is that windows sees the card so I installed the latest drivers and tried again but still no change. The card is functional as I had it running not long ago in my previous machine. I have also tried resetting bios settings to default. I have searched for similar threads and found a couple although none come to conclusion to the problem. My PC specs are as follows:
- Athlon 64 X2 5600+ 2.9Ghz
- Msi 785gtm-e45 v1.4 running bios ver 8.8
- Corsair Ballistix Sport 4gb (2 x 2gb) DDR2 6400
- XFX Geforce 9600gt 512mb
- Hitachi HDP725050GLA360 500Gb SATA
- Windows 7 Home Premium 64bit
- Corsair VX550W 550w (41A @ 12v / 30A @ 5v / 28A @ 3.5v)
Any help or advice is welcome.
Cheers.

Did you unplug your PSU from A/C power to properly >>Clear CMOS<< at any point after inserting the video card? If not, please give that a shot.

MSI 785GTM-E45 BIOS CPU fan voltage control

Hello MSI gurus,
I've replaced the MB in an older HP media center with the MSI 785GTM-E45 running BIOS V8.8 out of the box.
CPU = Athlon 64 X2 4200+
My problem is the stock CPU fan has a 3 pin connection (voltage controlled) and is running at 100% speed all the time. From what I've read on the forums there are a number of people that have this issue (with other MBs with 4 pin cpu fan headers) and don't want to switch to a 4 pin CPU fan (PWM controlled). I am in the same situation.
I am hoping that there is a BIOS for this board that has an option to switch to or enable voltage control on the CPU fan header.
I have tried enabling the CPU smart fan target but no matter what settings I chose the fan remains at 100%. The H/W monitor of the MB indicates a CPU temperature (33C) well below the target (tried all options from 40C to 60C in 5C increments).
I have tried MSI's dual core center and it had no effect on the fan speed.
I have tried the 3rd party freeware SpeedFan and if had no effect on the fan speed.
I am not able to check if I have the latest BIOS or even find changelogs for existing BIOS verions because MSI seems to only direct BIOS downloads for this product to the Live update application. I have installed the live update program and it indicated V8.8 was the most recent veriosn of the BIOS for this board, although I have seen posts indicating the Live Update application is not to be trusted.
Dual core center, SpeedFan, and Live Update have all now been uninstalled.
I know the fan I'm using will change speed because I can connect a 3 pin fan controller and manually dial down the speed.
I know the BIOS can read the fan speed becase it correctly shows the RPM changes when I use the hardware fan controller.
Can anyone direct me to a BIOS version for this board (or some secret keystroke) that enables automated 3 pin voltage control on the CPU fan header?
Thanks in advance for your time.

For those who are interested I received the following answer from MSI technical support. Personally I find this to be a flaw in this board's design. I chose this MB to replace a dead MB in a HP media center for a friend. If I was buying this board for myself I likely would be using it as a HTPC because of the mATX form factor, HDMI on board, and backward compatibility for CPUs. However, due to the added cost of purchasing a new heat sink and fan I would be RMAing if I had bought it for myself. Considering many of the top performing after market coolers still come with a 3 pin fan it was a poor decision for MSI to not include support for automatic speed control of a 3 pin voltage controlled fan.
Quote
Dear Sir/Madam,
Thanks for contacting msi technical support team!
We are sorry that because of the circuit designs,we could not add cpu smart function for 3 pin's connector fan in the BIOS. The difference between 3pins and 4pins is that the second has a temperature controller but the first does not.We would suggest you utilize a 4-pin CPU Fan in order to control the CPU Fan speed.
Sorry for any inconvenience caused you!
Best regards,
MSI Technical Support Team

MSI 785GTM-E45 wont post with 4 GB ram just about at witts end help please

I have a MSI 785GTM-E45 with a AMD Athlon 7750 Black Edition Dual Core 2.7 (all overclocking was restored to normal for install of new ram) that ive been putting together its just about done except vid card and memory.. K heres my problem I"ve been using a 1 X 1gb single channel ddr2 800 pc2 -5300 1.8v 240 pin to set stuff up untill i got my new ram. well i got my new ram today its 2 sticks 2 GB each PC2-8500 DDR2-1066Mhz ..CL 5-7-7-25 dimm when I install it on my board the machine wont post. seems like it boots theres no beeps or anything so i cleared the CMOS Flashed and upgraded the bios set bios to defaults still wont post. I tried one stick then other tried one slot then other nothing took it out put in my old ram fires right up. HELP what am i doing wrong. PC2-8500 DDR2-1066Mhz owners manual and everything i read online says this should work they are a new maching pair.

hey mark thanks i took it to a shop today guy said it was 100% compatible so i asked him to test it came back bout 5 min later said it was completely dead worthless so in sendin it back bout some from the guy at the store machine runs awsome now i just need a good inexpensinve graphics pci-e pretty sad when you spend good Money and a few days looking for excactly what you want / need and when you get it its trash im just glad it wasnt my main board

785GTM-E45 vcore reset when resume

Similar Messages

Maybe you are looking for