Jump to content

Adam Noble

Registered User
  • Posts

    63
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Adam Noble

  1. Right after spending all night creating a Driver map and seeing "who talks to who" in the whole driver universe I came to the conclusion that nothing should be messing around with the way OSD reads and writes its scripts. I did a little digging before systematically uninstalling everything one by one when all of a sudden I noticed somethings strange, I use TeamViewer to interconnect all my machines at home for monitoring purposes and for access away from home, its just a fancy Remote access tool but with a good looking GUI.....ANYWAY when I started playing with the Dell display driver I noticed that Teamviewer had installed its own display driver and called it a "Secondary Display Monitor" Now I thought it may have had something to do with my Crossfire setup first but when I tried to uninstall it I received a BSOD. Only starting in safemode with Team Viewer disabled allowed me to uninstall it and wouldn't you believe....the following boot my OSD is now working fine and touch controls are back (well they all worked except the brightness controls) So it was this Team Viewer driver that was doing something to OSD, I have not seen any changes in Either of them for months and their update logs show this too, so why they have decided to fight now is a mystery, maybe that crash I had that took my cards out of Crossfire had something to do with it, unless that is another symptom :/ Anyway thanks for the help guys, It would appear that I have wasted your time with this but at least we know this problem can happen in the older R2's with Team Viewer
  2. Welcome to the fun guys Right I have tried every single combination and I still come up with this error, I have tried removing OSD, Command Centre and my GPU software + Drivers then cleaned up with Driver Sweeper then installing them in different patterns, even previous versions of OSD. I have tried in both safe mode and normal mode. As I type this I do not have OSD or Command Centre installed, I would leave it this way but My touch controls are now dead as I believe either OSD or Command Centre deals with them. Everything is up to date, BIOS, GPU although I have never flashed the VBios, didn't know you could on the 4870's and to top it off............My Restore settings are being uncooperative and only showing today's restore points () I am stumped for now, everything is working fine except OSD, but apparently any OSD problems are caused by GPU failed writes :/
  3. Trying your suggestions now, like you said its a strange one :/ I have been looking over the logs and the only thing that I have done different was that after a failed shutdown my GPU's came out of corssfire, I noticed this during some GW2 so I closed down, re-enabled and and played some more. That is the only thing I have done different in almost 2 months. I will report back once I have done ALL of the above.
  4. I am now getting this error at startup for no reason, it seems to be a problem with OSD and from what I gather from Google, caused by some sort of bad GPU driver install? I have tried reinstalling OSD from fresh.......I have tried reinstalling my GPU drivers from fresh but no change? Has anyone had any experience with this, with OSD down I am getting a truck load of problems ranging from touch controls to RAM leaks :/ Machine is.. M17x R2 Windows 7 64bit ATI Xfire 4870's - Catalyst version 12.6 - Driver version 9.97 OSD version 2.5.54.0
  5. That sound like exactly what I need I'm not bothered about paying, I have the trial activated now for Diskeeper and seeing a noticeable difference immediately and its not even finished Thanks again mw86
  6. Hi, I have been running my Alienware M17x R2 with the Twin drives for almost a year now and it has been great. I have a 120GB SSD containing only the OS and a secondary 1TB HDD Partitioned into 3 x 300GB partitions. One contains only Games, One contains all Media (Music, Pictures and Videos) and the third contains Windows 8 at the minute for testing. Since instillation I have had all the recommended system settings disabled such as superfetch and Defrag but I have only now realised that these keep the SSD healthy but not the HDD. Now I know I have not made things easy in partitioning the HDD into three but I was thinking is there any way if restoring superfetch and defrag but only on the HDD? It is being bogged down by fragmented data and killing performance in some cases. What do you suggest?
  7. Well i don't understand them sometimes but the job gets done, once their 24 hours was up i called and got the "we have no record of that conversation sir" so i calmly explained that was going to happen and that they would be reported for this, im not asking for free parts or a new system just the disks that SHOULD have come with my system. I explained that had previously happened and when she asked if i would like her to look into the problem i said no thanks and ended the call. The next day i went to my friends to grab a copy of his reinstall media and when i got back.......BAM i had a delivery and wouldn't you know it was my recovery disks, a mouse mat AND a money off voucher for the alienware suite (0_0) must have really spooked someone high up to have been sent a goody bad for a problem that apparently "doesn't exist" Looks like i can finally start rebuilding my baby's brain in all honesty she was due a fresh install anyway Thanks for all you help in this guys especially the tips on how to handle it all mw86, you guys should be on the alienware payroll
  8. Right an update, i followed your advice and everything was going fine for about 2 hours, they took my details and confirmed that my system shipped with 64bit ultimate and that the disks must be faulty if they do not run or complete any actions, they even took my address confirming from the shipping address from the initial purchase but just before anything was finished they said they ask their manager for a confirmation and then they said they would get back to me within 24 hours :S ......... What just happened?
  9. Sounds good, i have to admit once they started saying i was not going to get anything i got a little agitated, tomorrow i am going to settle down and hold my ground for as long as it takes, thanks for the tactic mw86 i will report back when i have things settled. Thanks again.
  10. Oh well it does......Was on the phone for like 2 hours today to dell asking if i could have replacement disks for both OS and Drivers, they asked for my service tag before saying that they do not ship systems with those disks......then after an argument they said they would ship them but i would need to pay.......then after yet another argument they are claiming that my system shipped with a 32bit version of ultimate even though Alien command centre, the program that controls one of the key features of the alienware line...THE ALIENFX...requires a 64bit platform :S Does anyone have an alienware with a 32bit OS installed?
  11. You would not believe it....The recovery disks that came with my R2 are both wrecked 0_0 the drivers CD was a failed write and contains nothing and the OS recovery DVD contains a 32bit version of ultimate not the 64bit needed, this means i am now stuck on a 32bit OS and cant install most of the Alienware suite :(could things get any worse ()
  12. Awesome, i am just about to finish my secondary backup before trying to restore to an external drive and if it works i will need to implement this ASAP because that dimming issue was becoming a real PITA () Thanks guys
  13. bad luck indeed :/ lucky for me my secondary HDD had a 150Gb backup partition that now houses a copy of a working....yet naked OS so i am now able to backup the defective drive before testing to see if it is a hardware or software fault :/ Either way i was due a fresh install of windows anyway AND this wraps up the screen brightness problem
  14. Thanks for the help StamatisX, you would not believe but seconds after writing my last post i came out of Safe Mode to try the driver uninstall and my God Damn SSD failed on me it has taken me this long to get my baby back to a some what "working" state :/ tried everything to get the SSD working but from what i can see it has a Boot Config corruption that i cannot seem to fix :/ looks like its back to the drawing board
  15. Now that is strange, when i boot into safe mode the brightness is as it should be Very bright and vibrant. So this means the problem lies with some sort of software error? only activated in a normal boot.
  16. When I use Fn+F5 to reduce the brightness it decreases in very small increments, then when I use Fn+F4 to increase it again it increases in small increments back to Max on the brightness icon but the screen is still quite dull. I have tried restarting and everything but no luck and whats even stranger is just 10 minutes ago i woke it from a Screen off standby and for a split second the brightness was maxed out like it should be and very bright but then it dropped again to the normal dull level it is now
  17. Just when i thought i had sweet talked my R2 into a very sweet and harmonious relationship it would appear that i have something wrong with the brightness on Rig. Turned it on this morning for some updates and blogging and everything was great but then it went into sleep while went for a walk (not with the R2 of course) and upon waking it up it would appear that it will not achieve max brightness? everything shows as on max brightness, i am om max performance and everything everywhere shows as the screen brightness is maxed out I tried some gaming later in the morning but the screen brightness was so poor i had to increase the Gamma and brightness just to see anything in the sun Anyone got any ideas?
  18. I am compiling a list of benching records to put on my blog as we speak, running a few of the old classics such as Crysis and Supcom ect with some of the newer beauties available such as Skyrim, Crysis 2, ANNO's 14xx & 2070, Battlefields & COD's so plenty of screenshots and data to present once done
  19. Followed the instructions.............AND GOT IT RUNNING () Thanks guys My problem was caused by TRIXX not properly disabling ULPS and so causing other OC'ing software to crash. Now everything is great and i can now look forward to benching my way to new hardware
  20. Wow thanks mw86 () Specs as follows; Xfired ATI Mobility Radeon HD 4870's (ATI M98) Driver - Catalyst 11.11 (on both cards) according to TRIXX OR atiumdag 8.911.0.0 (on both cards) according to GPU-Z. The reason for wanting to run Afterburner is exactly what you said, i want in-game and in-app stats for recording my findings especially when i move to newer specs and want to see if the old motherboard keeps up
  21. I already have TRIXX Just been told good things about Afterburner :/
  22. I have the exact same problem, have been looking around the net and cant find a solution so have been forced to avoid it
  23. Makes sense, i am making some slight changes here and there but not seeing anymore drastic performance increases anymore so might just stop for a while lol
  24. At the stated OC I saw GPU temps of around 61°C-68°C from 43°C Idle and CPU Temps going from 40°C Idle to around 70°C GPU Clock - 650MHz Memory Clock - 950MHz VDDC - 1111 This is with the Above overclock and it seems very stable so tonight when i have finished my long due uni work i am going to bump it up again by another 0.50MHz on each and see how it handles EDIT: Right moving the GPU clock to 700MHz causes problems, in short it BSOD just after a GPU failure "Pink Checkered" screen lol going to move up in 0.10MHz now and find a sweet spot
  25. Well i think it has finally allowed it to work everything is holding strong at; GPU Clock - 650MHz Memory Clock - 950MHz VDDC - 1111 I have been benching using ANNO 2070 since it stresses the entire system when i play it and its going great going to move up another 0.50MHz tomorrow and bench again and see if it still works ok i can already see a big difference within ANNO so it should be noticeable in my other "Favorites" Oh and thanks for the Regedit tip, at least i know it is disabled
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.