BUG 219 FIX!

There really is NO 219 BUG!!! I thought there was. First, I was blaming my CBBID CPU, then the 219 BUG after getting a Venice.
But after receiving my Corsair TCCD memory, I am now able to run to 290 x 9 or 2610 mhz with my 3000+ Venice or 286 x 9 2574 mhz old 3000+ CBBID Cpu.
I was using a Kingston Value Ram before.
So, again there is NO 219 BUG!!! Stop blaming it and get a GOOD set of memory.

Quote from: Ratt on 07-July-05, 10:45:22
I think the 219 issue is now very confusing. Many of us thought we have the bug when they have other issues. We really have to clarify what is the 219 bug and more importantly, what is not.
When you can't get pass 219 at all from the BIOS, but you can go all the way with Clockgen.
When you overclock your CPU fine, but can't clock your PC 5000 RAM pass 219 at all.
You can overclock your CPU and RAM fine, but have to drop to 2T command rate.
What is and what is not? Feel free to add more "what is or what is not the 219 bug".
Remember, if the clockgen can't do, then it's not the BIOS bug.
This is why the "219 cold boot hypertransport bug" is so hard to spot.  It really has to do with cpu initialization, overclocking and the hypertransport bus speed.  We know its a bios problem because those using bios version 1.3 and venice core chips dont have it but as soon as they flash bios version 1.4, the bug appears.
Here is my email back to MSI:
Hi Xxxx, I just want to report back after I and many others on the MSI Forum board have tested this beta bios.  Well, for all of us that have 90nm winchester cores, the 219 cold boot hypertransport bug is still there.  For venice core users, I cannot get a good answer if its there or not.  Aicjofs did get the same beta bios from a MSI engineer and he emailed me and said that the bug is still there with his sli setup (he has both winchester and venice 90nm chips).
Basically, here are my stats and this is what I did.
Stats:
psu - tagan u22 with 12v@30a - power supply is fine
memory - crucial ballistix tracer pc4000 - stable at least up to 255fsb so I could test all your test scenarios (new memory purchase so I dont know the limits yet)
cpu - winchester 3000+ cbbid0509
video card - msi 6600gt
mobo - msi neo4 platinum sli
Settings:
Memclock: 200 (or in tech lingo 1:1)
Timings: 2.5,3,3,7 1T, stable at 255fsb (prime95 & memtest 8 hours plus)
Tests:
FSB:                      219     220     250     255
HT Multiplier:           x4       x4       x4       x4
Cold boot post:       yes      no       no       no
Warm reset post:    yes     yes      yes      yes
Whats really interesting is that after a few warm resets (sometimes 10 or more), I can get the SLI motherboard to post to windows but never on a cold boot with the hypertransport multiplier set at either x4 or even x3 at 250fsb.  I have to lower the ht multy to x2 at 250fsb to get a cold boot post.
So Xxxx, this is the problem because I can get to 250fsb through either warm resets or using clockgen.  If I use clockgen, I cold boot post to 219fsb with the ht multy set at x4, then increase the fsb to 250fsb and its stable.
All we users are saying is why cant this cold boot post if we can get it to post either by warm resets or clockgen?
As a side note, using the enclosed D-bracket, the cold boot post always stops at "cpu initialization" so it is my belief that it has to do with the bios programming and cpu initialization...but I am not a technical engineer.
If you have any new beta bioses, I would like to test them.  If you would like to see the results that users have had, here is the thread on the MSI forum boards.  Thank you again for your support on this issue.

Similar Messages

  • Bug CSCun42967 fixed: ISE 1.2 : SNMP process stops randomly

    As of June 9th, the status of this bug is "Fixed" with "Known Affected Releases" being 1.2(0.899), which is the one we are running.
    Known Fixed Releases is (0) and then there is a link to the download area where I can download an update to 1.2.1. The release notes does not mention bug "CSCun42967"
    Does anyone know if this bug has been fixed?

    Hi,
    I just ran into the same issue.
    I would assume that if it was fixed in 1.3 it would be mentioned in the release notes as resolved caveats. Can anyone confirm the problem is fixed in 1.3?
    Soren, have you upgraded and is the issue resolved?
    Thank you :)

  • FF has become useless and nothing but bugs and fixes

    Comment, <br /> See also similar question with some answers
    * '' 'save as' redownloads the data '' [/questions/986667] ~J99
    you cannot right click save as on an image, after the image has been dl already to save it FF re-downloads the image again. Noone can produce a config setting that corrects that. so if your paying for data FF is causing you to pay double.
    while something is DL most of the time the dl stalls. You now cannot pause and resume a dl to get it going again, the old Dl dialogue box had a pause function, the new one 'right-click' shows a pause but its grayed out and does not function
    FF cannot handle multiple tabs anymore, if you open multiple tabs it freezes FF and you get a slow script error. But the same tabs can be opened in an old version of IE 7,
    the repeated crashes are well known without a fix,
    the new version seems to have numerous bugs without fixes, or explanations that you need some add-on instead of a FF function.
    the mere fact that FF cause double data usage without a fix or explanation is beyond inexcusable. Payinf for double data because of a code error is unbelievable. test i opened IE went to a pg open 3 tabs saved the images, and did the same in FF and it used 3.23 times more data.
    Every since that Tor / FF debacle when the old versions were declared no good every version of FF since then has had to many errors without fixes that it has became an industry joke. The fact that chrome and IE or better browsers now speaks volumes. I am no code writer, but since that time, every version is so slow and bug prone, that what ever attempt to say face or redemption has been a disaster.

    To answer your questions here:
    <blockquote>you cannot right click save as on an image, after the image has been dl already to save it FF re-downloads the image again. Noone can produce a config setting that corrects that. so if your paying for data FF is causing you to pay double. </blockquote>
    I'm not sure I understand this. When I click save image as then try again it works fine for me. Can you clarify what you are trying to achieve?
    <blockquote>while something is DL most of the time the dl stalls. You now cannot pause and resume a dl to get it going again, the old Dl dialogue box had a pause function, the new one 'right-click' shows a pause but its grayed out and does not function </blockquote>
    It is better to use an external Download Manager (DM) if you are on dialup or have an unreliable connection.
    An external Download Manager offers better support for resuming interrupted downloads than the built-in Firefox DM.
    You can use the FlashGot extension to integrate an external Download Manager in Firefox.
    FlashGot: https://addons.mozilla.org/firefox/addon/flashgot/
    <blockquote>FF cannot handle multiple tabs anymore, if you open multiple tabs it freezes FF and you get a slow script error. But the same tabs can be opened in an old version of IE 7, </blockquote>
    This is most likely the way Firefox is set up on your end. What add-ons are you running since I don't see any listed. I need some more non-personal information from you. Please do the following:
    *Click the Firefox button at the top left, then click the ''Help'' menu and select ''Troubleshooting Information'' from the submenu. If you don't have a Firefox button, click the Help menu at the top and select ''Troubleshooting Information'' from the menu.
    Now, a new tab containing your troubleshooting information should open.
    *At the top of the page, you should see a button that says "Copy text to clipboard". Click it.
    *Now, go back to your forum post and click inside the reply box. Press Ctrl+V to paste all the information you copied into the forum post.
    If you need further information about the Troubleshooting information page, please read the article [[Use the Troubleshooting Information page to help fix Firefox issues]].
    <blockquote>the repeated crashes are well known without a fix, </blockquote>
    Again this is specific in your case. Follow the steps below to provide us crash IDs to help us learn more about your crash.
    #Enter ''about:crashes'' in the Firefox address bar and press Enter. A Submitted Crash Reports list will appear, similar to the one shown below.
    #Copy the '''5''' most recent Report IDs that start with '''bp-''' and paste them into your response here.
    [[Image:SubmittedCrashReports-Win7|width=520]]
    <br><br>
    <blockquote>the new version seems to have numerous bugs without fixes, or explanations that you need some add-on instead of a FF function. </blockquote>
    I see you have Fx 26 installed and not the latest 27.0.1. See what's new with Firefox in version 27.0.1 http://www.mozilla.org/en-US/firefox/27.0.1/releasenotes/
    <blockquote>the mere fact that FF cause double data usage without a fix or explanation is beyond inexcusable. Payinf for double data because of a code error is unbelievable. test i opened IE went to a pg open 3 tabs saved the images, and did the same in FF and it used 3.23 times more data. </blockquote> Double data usage? Are you talking about a smart phone data limit or your RAM usage?
    <blockquote>Every since that Tor / FF debacle when the old versions were declared no good every version of FF since then has had to many errors without fixes that it has became an industry joke. The fact that chrome and IE or better browsers now speaks volumes. I am no code writer, but since that time, every version is so slow and bug prone, that what ever attempt to say face or redemption has been a disaster. </blockquote> Tor and Firefox? What are you talking about?

  • ACR 7.x known bugs and fixes

    Since Adobe stopped supplying Camera Raw downloads, I've noticed that it's become harder to track bugs and fixes. Hopefully, someone here can put me straight on the current state of play.
    Can anyone summarise the well-known problems with version 7, and when they were fixed (or are still ongoing)? Is there a 'changelog' somewhere? What is/are the main outstanding issues at the moment?
    Unfortunately, I'm getting to that age where my short–medium term memory isn't very good at retaining this sort of information, so it's good to have it written down!

    Jeff,
    I have been dealing with this since November. Steve G knows about it but hasn't had time to do anything. Here's the deal...I am on Windows 7 and Photoshop CS6. I shoot with a Canon 7D and G11.  I do all my initial work in the metadata template...my own info, description, keywords, location, etc. etc.  This creates an .xmp file. When the update from RAW 7.2 to 7.3 came through in November, I downloaded it, as I have all other updates. Then, suddenly, all images in folders with RAW files that had ANY metadata applied, would regenerate endlessly. This only happens with RAW files, not with folders containing jpegs or tifs.
    I tried resetting preferences. I tried creating new folders. I have asked if this problem is seen with Nikon RAW files and I'm not sure there has been an answer. I think people have recreated this even with DNG files tho I am not sure. I do know that someone in Adobe has recreated it.
    I then discovered that previous .8bi folders were no longer readily available. Getting to one is way, way, way above my ability and involved all kinds of ridiculous backflips but I finally got one. Then followed a solid week of me trying replace the 7.3 .8bi file with the 7.2. Of course, with no instructions, I was putting the wrong file in the wrong folder (32 bit and 64 bit). When I finally got THAT straightened out, it still didn't work. It took someone at Adobe taking over my computer to successfully revert to 7.2.
    I lost hours and days of work time trying to deal with this. Meanwhile, should I buy a new camera, I won't be able to see my own RAW CR2 files and will, instead, have to convert to DNG, which, frankly, I find to be a royal pain. Am I peeved. You bet I am. I've been asking, pleading, begging for something to be done since November. Some thoughtful soul suggested I try updating to 7.4 to see if it fixed the problem (the 'fixed problems' listed for 7.4 does NOT mention the recalibration). You can understand, after the problems I had in November, why I will NOT do this until I am absolutely sure the current, latest update has fixed my problem. And I will NOT spend another two hours on the phone with adobe alleged tech help to finally get someone in India who doesn't know what I am talking about. This forum has been far more helpful but please underestand, I am an old school film photographer who has had my share of problems understanding this digital stuff and mucking around with the basic technology of my computer only leads to horrifying outcomes for me.
    Jeff, are you with Adobe? Can you look into this?

  • [svn:fx-trunk] 5114: Fix FxRadioButton doc bug and fix the bug fix I messed up yesterday.

    Revision: 5114
    Author: [email protected]
    Date: 2009-02-27 12:50:47 -0800 (Fri, 27 Feb 2009)
    Log Message:
    Fix FxRadioButton doc bug and fix the bug fix I messed up yesterday.
    QE Notes: mustella gumbo/RadioButtons passed
    Doc Notes:
    Bugs: SDK-19475, SDK-19531
    Reviewers:
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-19475
    http://bugs.adobe.com/jira/browse/SDK-19531
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/FxRadioButton.as

  • Hi i need to send bug to fix it  from /opt/SUNWexplo/bin/explorer

    Hi i need to send bug to fix it from /opt/SUNWexplo/bin/explorer ...simply executing the command will generate any files anywhere in the server..or it will give the output in the screen only ..i need to send the output of the command ..help me plz

    Public InfoDoc 203335 is the README for Sun's Explorer.
    [http://sunsolve.sun.com/search/document.do?assetkey=1-9-82329-1|http://sunsolve.sun.com/search/document.do?assetkey=1-9-82329-1]
    That document clearly states that any communication about that software tool needs to go to the email alias that is provided in that InfoDoc.
    All other communications to anywhere else (such as to this forum) will be ignored.
    Though if you had read the Explorer FAQ or its User Guide, you would have your answer as to where the output files might be. The FAQ and the U.G. are also linked in the README InfoDoc.

  • Subscriptions for fimware/software new releases, bugs and fixes

    Hi,
    Where can I subscibe for MDS 9000 Firmware/Software releases, bugs and fixes?
    Thanks,

    You have the "Cisco Notification Service" tool where you can setup a profile:
    http://www.cisco.com/en/US/customer/support/tsd_most_requested_tools.html
    - Filiph

  • What bugs are fixed?

    Is it possible to find out which bugs apple thinks they have fixed with a release of their software? I also have this issue with front row: http://discussions.apple.com/thread.jspa?threadID=485117&tstart=15
    and from what I have been told, QuickTime is really the 'engine' behind playing music and videos and the ITunes (for example) is just a "skin" over this engine. Perhaps this is not true. Anyway, I would like to find out if the recent release of QuickTime fixes this bug. Also, is there anyway to find out from Apple if they plan to ever fix a particular bug? The only thing I use my mini for is as the head of my home theater, and the only reason I would upgrade is because they plan to fix this bug.
    BTW, up until 3 months ago, I was a lifelong PC user. I thought that those PC/Mac commercials were really funny. Then I got a mac. All those people who had somehow convinced themselves that macs are more stable/secure/easier to use/etc. than a PC are just fooling themselves. I can't believe how much trouble I have had trying to do simple things and how much obfuscation I have gotten from people at the apple store, tech support. Just for grins, anyone here who thinks that mac is so great, try to play a song encoded as .flac in ITunes. Even better, try to get it to play two in a row without a gap between them. Then, go to an apple store and ask one of the 'geniuses' how easy that is to do.
    Sorry for the rant... I feel better now.

    Apple does not announce what bugs they fix. They almost never do for any of their computers either.
    The current update was a security and minor bug fix, no major new additions or substractions.
    The only way you can find out what updates do is to read through other websites where people "autopsy" the upgrade software and post what they find different in the code. Those are not highly reliable because Apple often includes things in their software that are not activated, just idle code.
    If you click on the Apple links, all you will get are a direct link to the Update page from the users manual, to explain how updates are done, and a general message stating this is a "security and stability update."

  • Anyone aware if the battery life (in ML) "bug"is fixed ?

    Is anyone aware if the battery life (in ML) "bug"is fixed  yet, Or is it something that happens toa ll all instalaions and we have to live we it?

    It's not a problem here. I'm not sure that it's a bug. I helped someone in this forum on an issue like this and the problem was linked to the use of a 3rd party software using too many processing cycles.
    Activity Monitor is a good tool to identify such misbehavior.

  • Text-inset cross-reference PDF bug ever fixed?

    We're using FrameMaker 8.0 and Acrobat 8.1.
    Has Adobe ever fixed the bug where cross-references in text insets aren't converted to valid links in PDFs? In other words, do we still need to work around that bug by using newlink / gotolink hypertext markers in text insets?

    Robert:
    As far as I can tell, FM8 still exhibits the undesirable behavior...
    Cheers & hope this helps,
    Riley

  • ICal Alarm Editing Bug, not fixed yet in 10.5.3?

    Hi All Mac users,
    I have noticed this bug for quite a long while, which I cannot remember from when, but I think it was from around 10.3 or 10.4. I am used to it, and can deal with this since I know it. But, it still seems to persist even after updating to 10.5.3, and I have finally wanted to raise the issue up to this forum, in order to get it fixed, or obtain knowledge on how to fix this in my Mac.
    When you double-click or Command+I an event in iCal, the detail of the event shows up, and you click "Edit" button at the bottom to edit it. Most of my events' "Alarm" are set as "Alarm with Sound". To edit this, you click right next to "Alarm" to bring out the pull-down menu. You can change "Alarm with Sound" to "No Alarm", etc. Also, you will see a list of the latest settings you used at the bottom of this pull-down menu, with date, time and sound, etc. to choose from.
    *My Bug Phenotype:*
    ALL of the listed settings in this pull-down menu are EXACTLY *4 hours* (FOUR HOURS) later of what that actually sets and do. For instance, I set a new event at "2008/6/1 10:00, playing Susumi sound". This setting will newly show up in the for-mentioned pull-down menu. But, because of a bug or by an unknown reason, within the list it shows "2008/6/1 14:00, playing Susumi sound", showing the time 4 hours later. Continuously, if you edit another event's alarm setting, and choose the previous setting of erroneous "2008/6/1 14:00, playing Susumi sound" that shows up from the pull-down menu, the event you're editing will actually be set to "2008/6/1 10:00, playing Susumi sound", which is correct with the very original setting I first used, but then again it is 4 hours ahead of what you see in the pull-down list. Once set, all event will show the proper Alarm time set, and work at the correct timing. It seems that there's a bug just in this pull-down menu showing the previous settings, adding and showing 4 hours later to what it should be, but also correctly stores and set the original time.
    Does everybody understand what I tried to explain?
    Does anyone else have the same experience?
    Is this just me?
    Is it always 4 hours?
    Any way to fix this?
    Is this an iCal Bug, to be fixed?
    Thanks for your help in advance!
    Dr.MORO
    PS: Is there a way to directly (Online) way to tell (email, post, etc) this problem to Apple?
    PPS: I have used many different disk maintenance tool of most kinds, both free and commercial, but nothing has helped.

    Dr.MORO,
    1. Try refreshing the iCal plist file. Navigate to your Macintosh HD/Users/yourusername/Library/Preferences Folder, and find the com.apple.iCal.plist file. Drag that file to your desktop, log out/in or restart.
    2. What time do you have set in your iCal Time Zone Window?
    3. Have you tried to change your settings in System Preferences...>International>Formats>(Region:) (Dates) (Times)? Customize... Quit iCal before changing these settings, and repeat #1 above before opening iCal.
    4. Do you have a default time checked in iCal>Preferences...>General>Add a default alarm to all new events and invitations?
    5. Do you have "Turn on time zone support" checked in iCal>Preferences>Advanced?
    6. Do you have the proper "Time Zone" selected in System Preferences...>Date & Time?
    7. Are you syncing any of your computers?
    PS: Is there a way to directly (Online) way to tell (email, post, etc) this problem to Apple?
    Only through AppleCare, but your equipment is probably no longer covered. As far as I know you could still use AppleCare but it would cost an arm and a leg for phone support since you no longer have a contract. Do you have an Apple Store or Authorized Apple Provider nearby?
    PPPS?: This is my second post on this iCal issue this year, last time on May 30, 2008, but no one seems to care...
    Since Apple Discussions participation relies entirely upon other users for possible solutions, it is my guess that no one had the same problem or could offer a reasonable solution. Sorry to hear that you did not get a response to your previous post, but I care.
    ;~)

  • Master Slide Builds Bug? Fix?

    USing Keynote 3.0.1 on 10.4.5
    When I create a new Theme by creating new master slides with builds built into them I encounter a problem.
    On one of my Master Slides (Title & Bullets) I have a title box, an object (Line) and a bullet text box.
    I have set the Title to build automatically after transition, then I have set the Object (Line) to build automatically after the first build (Title).
    I have then set the bullet box to build the first bnullet automatically after the Object and each bullet on click after that.
    This has all been set at the Master Slide level.
    When I apply that master slide to a slide within my presentation, the build order changes. The Object builds first instead of the Title. To get the correct order I have to re-apply the master to the particular slide.
    This causes much confusion when I distribute the theme to my colleagues who are not as computer litererate as myself.
    Is this a known bug? Is there a fix for it?
    Thanks in advance

    it won't keep the new format when pasting the text box on other slides.
    Why are are you pasting the page number on to other slides when the master slide will place the slide number on all slides correctly formatted? There is no reason to do that.

  • Captivate 8 vs yosemite. Audio speech doesn't work neither on Captivate 7 nor Captivate 8. Is there any bug to fix this problem?

    I'm having problems when using Captivate 7 and 8 - specially audio speech management.
    As I use OSX Yosemite, I don't know why but it doesn't work properly.
    Any bug or way to fix this problem?
    Thanks in advance.

    Captivate for yosemite is all around really buggy. I also cant get text to speech to work, but I am experiencing issues with what I call "windowing". When I attempted to maximize captivate 8 to my cinema display, menus and modal windows spawned by captivate often appear behind other windows. In addition, Captivate can't seem to figure out how to maximize to the available screen real estate.
    These two things happen to be the most annoying bugs, but I have experienced many more:
    1.Timeline is really wonky. I can't select multiple timeline items and move them without the timeline completely falling apart.
    2. Selecting objects that are overlapping on the stage is terrrible
    3. Altering the duration that an item should appear in the timeline often creates an extremely annoying bug where other timeline items will jump to an arbitrary spot. This creates a ton of re-work.
    Adobe - Cap 8 is not ready for use in OSX Yosemite- please fix it!

  • PDF in Safari: Fonts not displaying correctly: Has this bug been fixed?

    Last year I was trying to view a PDF on the iPad with Safari, and there was a font corruption problem: On zooming in, the type would become garbled. Now granted, I was using a non-standard font (Univers Type 1). I also noticed this problem with certain magazines in the MagCloud app. I decided to work around the problem by converting my type to outlines; while this worked, it made the PDFs much larger in file size.
    I checked this bug again under iOS 4.3 and could not replicate it. I've found anecdotal evidence out there that as of iOS 4.2.1 this may have been fixed, but I can't find confirmation. Any help in this regard is much appreciated. I need to present my project managers with discrete evidence that this bug has been fixed before they'll allow me to go ahead with "live" type -- and as we all know, the plural of anecdote is not data. Thanks.

    Apologies, I should also make clear another key point...where it's blowing out (multiple places), I'm using apex_item within the SQL to render the form. So that's where the problem lies

  • How can we tell when the Aperture+TM bug is fixed?

    I'm wondering how I will know when Apple has fixed the time machine bug with Aperture, here:
    http://support.apple.com/kb/TS1228

    Since this appears to be a core OS issue, watch for updates in that area. Most likely, watch for 10.5.3 being released. Nobody outside of Apple knows which this will be, though I speculate that it will be in the next few weeks. Rumour sites have been talking about changes which developers are seeing in their pre-release copies for a couple of months now. When it's released, the Mac-oriented part of the interweb will talk about little else for days. Watch for discussions which begin by listing what's addressed in the new release. In particular, keep an eye on the various Aperture forums/sites, as they should quickly identify changes which affect or relate to Aperture.
    Also, Apple should also have at least one tech page which lists all the changes (at least, all the changes they're prepared to list).
    Final thought - when any updates are released, keep an eye on the web page you've cited. It could well be updated to reflect any changes, but give them a few days....

Maybe you are looking for