Jump to content
NotebookTalk

All Activity

This stream auto-updates

  1. Today
  2. TM5 is primarily Memory and some CPU. Windows Memory Diagnostics. I just toss it on top of the pile with MemTest when I'm just hitting it different ways but less intense than Karhu. If I can make it past TN5 extreme I'm usually good but many times toss Absolut on it for that extra lock down for at least 90 minutes on either.
  3. 1.3.2 was only popular to keep the higher 200W on the 2080. I personally do not care since I run the AGA. I ran my M15x from 2009 (I forget, I think two sticks banged together) -> 680M (2014) -> 980M(2018) and even got Occulus Rift running on it (such great memories Xmas work week VR stuff w coworkers). So that's 17 years on only two Alienware laptops....not bad. Area 51m "upgradability" was a total knife in the back. Zero drop-in....not even 2080 Super but the 2080 worked for me through Cyperpunk, BG3 & Alyx so I didn't suffer. Only recently with 2025+ titles did I dust off the AGA and throw in a 5080 to continue being fine. I heard from Amir that 1.7.3 has more forgiving RAM speed settings vs. 1.9.3
  4. from Neowin - Microsoft shares Windows 10 LTSC end of support date, and extended security update details
  5. actually there was a 1.10.12 version available around middle or late July but the 1.10.13 version followed few days after v1.10.12 was released; I use this site to obtain different versions of the Nahimic app
  6. Posting this here because there does not appear to be a dedicated AA18250/2025+ Area-51 notebook subforum yet. I came up with the following help from good bud ChatGPT. $6k machine - you bet I am going to do what I can to keep this thing until the solder joints break. I ran into something tonight that may be useful to other AA18250 owners, especially anyone who prefers to control BIOS/firmware updates manually. My machine is an Alienware 18 Area-51, currently running BIOS 2.4.1. I noticed Windows Update had suddenly installed/staged the following and was asking for a reboot: Intel SoftwareComponent Driver Update 3.4.1007.0 — several instances Dell, Inc. Firmware Driver Update 2.5.0.0 Intel System Driver Update 2.3.20304.7 Intel Platform Monitoring Technology 3.2.0.22 several other Intel components The Dell firmware entry was the one that caught my attention because I intentionally do not want Windows Update deciding when my BIOS gets flashed. I had previously configured Windows not to include drivers with Windows Update, but checking the registry showed: HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate ExcludeWUDriversInQualityUpdate REG_DWORD 0x0 So somewhere along the way that protection had been reset to 0. I restored it with elevated PowerShell: reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v ExcludeWUDriversInQualityUpdate /t REG_DWORD /d 1 /f and verified: reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v ExcludeWUDriversInQualityUpdate which then showed: ExcludeWUDriversInQualityUpdate REG_DWORD 0x1 The more interesting part was checking what Windows had actually staged. Running: pnputil /enum-devices /class Firmware /drivers showed: Device Description: System Firmware 2.5.0 Manufacturer Name: Dell, Inc. Status: Problem Problem Code: 14 (0x0E) [CM_PROB_NEED_RESTART] Driver Name: oem79.inf and: Driver Version: 06/09/2026 2.5.0.0 Driver Status: Best Ranked / Installed So this was not just some harmless Windows Update listing. The 2.5.0 firmware package had been bound to the System Firmware device and was waiting for a reboot. Since I did not want Windows flashing the BIOS automatically, I removed the staged package before rebooting: pnputil /delete-driver oem79.inf /uninstall After that, running: pnputil /enum-devices /class Firmware /drivers showed: Device Description: System Firmware 2.4.1 Status: Started Driver Name: oem43.inf and the 2.5.0 firmware package was no longer the active firmware driver. I then rebooted directly into BIOS and confirmed the actual installed BIOS was still: BIOS Version: 2.4.1 So the 2.5.0 flash had not occurred. While I was in BIOS I also checked for some kind of UEFI Capsule Firmware Updates toggle. On my BIOS I could not find one. Searching for “UEFI,” “firmware,” etc. only returned things like Secure Boot, BIOS downgrade, BIOS recovery, firmware tamper detection, and related settings. BIOSConnect was already OFF on my machine. After exiting BIOS and returning to Windows, Windows Update showed “You’re up to date” with no pending restart. The only offered update was the optional July preview cumulative update, which I left alone. A few takeaways: Windows Update can absolutely stage a Dell BIOS update as a firmware driver. If you rely on ExcludeWUDriversInQualityUpdate, periodically verify that it is still set to 1. The relevant check is: pnputil /enum-devices /class Firmware /drivers If you see a newer System Firmware version with: CM_PROB_NEED_RESTART then Windows has likely staged the firmware for the next reboot. If you want to remove a staged firmware package, identify the exact oemXX.inf first and only then remove that specific package. In my case it was: pnputil /delete-driver oem79.inf /uninstall Do not blindly copy that oem79.inf number from my machine; yours may be different. The Windows firmware-driver label is not necessarily the same thing as the BIOS physically installed in the machine. The BIOS setup screen is the authoritative check. I still do not know what caused ExcludeWUDriversInQualityUpdate to revert from 1 to 0. I am not claiming Dell changed that policy. It could have been Windows servicing, a configuration change, an updater, or something else. For anyone who likes to manually vet BIOS releases before installing them, this is probably worth keeping an eye on. In my case, the machine remained on BIOS 2.4.1, and the staged 2.5.0 package was removed before Windows got a chance to flash it. If anyone else with an AA18250 sees BIOS 2.5.0 being offered through Windows Update, I’d be interested to know whether Dell has also posted it publicly for manual download yet, and what the release notes say.
  7. Yesterday
  8. Time Spy with 150W power limit (effectively no limit). Also, the power slider does work. Only Nvidia Inspector (NOT Nvidia Profile Inspector, you need Nvidia Inspector from ~2017) can control it, but it works.
  9. If no one cares about anything older than 1.5.0 we don't need to do it. I am fine with 1.50+ whatever newer versions you guys use
  10. Yep, I'm working on the copper plate at the moment, trying to dig some slots for R22 composants (they are higher than the GPU die), so everything fit well and the plate can sit on the die. And when done, i will solder some high performance heatpipes on it (minimum 2)to keep the card cool. Will share some pics later.
  11. Raising the TDP does work though. This is 125w vs 110w in firestrike: systeminfo doesn't work, but this is on a P150EM with a 3920xm at 4.3ghz that is modded for direct dGPU display output.
  12. I had 1.3.2 on my system but updated to 1.7.3 and then 1.9.3 I think I can recovery flash back to 1.3.2 without bricking the system. When i tried from way later BIOS (you can only go back to 1.12.X) I had to swap out the CPU due to eFuses being blown by the security updates
  13. Multimeter. The card runs memory at 1.35V, except for the max speed bin (7.2GHz) runs at 1.5V. The P4000 runs 6GHz at 1.5V since that is its max memory speed. The OC bios had the same issue. No core overclock. RAM would only run 6GHz. The card cannot run an Nvidia driver with the MSI vBIOS.
  14. Well that's odd, I compared both files and all the data is correctly written. I didn't know the vram had speed bins associated with voltage, where do you read the voltage of VRAM ? Here's a 1960Mhz core and 4504Mhz vram bios that should work (if the ram can overclock well) p5200_dell_OC.bin And here is an MSI "max-P" version of the P5200 that can boost up to 1911Mhz @160w P5200_max_P.bin
  15. Ideally stable enough so it does not crash in wow with up to 80F ambient temps without any supplemental cooling or having to use max fan speed. This goes for balanced or performance mode as both have a different fan profile. Does TM5 load the GPU? I thought it was CPU+RAM only. I have not heard of WMD.
  16. 500 DOLLARS ???????? YIIIIIIIKES
  17. custom resolution utity . mine is okay at 120hz . most top out at 100 i used CVT reduced blanking
  18. Yes I saw that. It's a LVDS display since the 120Hz requires a 50 pins cable.
  19. A P570WM is currently listed on eBay. Although details about the display aren't provided, given that it is Full HD at 60Hz, it is likely an LVDS type.
  20. TLDR New AI "accidently" hacks website Looks like I'm gonna need a new hobby...................Hack the Planet! https://www.abc.net.au/news/2026-08-10/ai-assistant-hacks-gym-website-aus-cyber-attack/107007986
  21. Hello, I am planning to purchase a Dell Pro Max 16 for work. I use CAD, Visio, and Blender, and I have always used my dad’s Dell workstation at home for school and work. However, I will be assigned to work overseas, so I am not sure which configuration would be best. I have a few questions and would appreciate your advice. CPU: 265HX or 285HX (Not decided yet, but 285HX will not be able to run at sustainable speed for long rendering hours from what I read on reddit - have you experienced any issues with heat?) Memory: DDR5 64GB CSO DIMM at 6400 Mhz (I am debating on whether to go for a single DRAM Module and upgrade later to 128GB or go with dual 32GB x 2). May I confirm whether this laptop can run 128GB at 6400 Mhz? SSD: I will keep the 1TB factory SSD for now GPU: RTX 2000 or RTX 3000 (I have concerns about heat and also seems like the GPU is locked at 115W) Display: Going for 1920 x 1200 (To save battery life on the road/working on construction site) Thanks
  22. Here's a crazy odd problem for ya courtesy of Asrock.... So remember that Asrock board that refused to boot with the $237.50 combo with the 7500X3D from MC? On the last return day to MC, I decided to roll the dice and keep it and see if it or even potentially the 7500X3D was truly defective or some other issue. I considered it a sub $250 fun project plus I didn't want to have to burn another $15-20 in gas.... I had ordered the B850i Phantom ITX from Asrock (<== major clue) and it wouldn't boot either. Swapped three different CPUs (9800X3D, 8400f, 7500X3D) and four different kits of memory. Same no post issues. Odds of two faulty motherboards is slim to none. Common denominator was Asrock. Had that HP Omen 35L HP sent me a few months back on the shelf (8400f, 5060, 16GB Rage memory, 500w PSU....such power) so I decided to open it up to use as a test bed in this "why won't Asrock work?" fiasco and of course everything works in there. 9800X3D? Sure. 8400f? Yep. 7500X3D? You betcha. KingBank memory? Boots right up no problem right along with all my other sticks. Did some googlin' and..... Issue turned out to be my KingBank 2x24GB sticks which I found out are known to have timing issues with Asrock boards even at Jedec. But wait, there's more. Testing those sticks first every time would load in the problematic timings and basically somehow wreck all the subsequent sticks I would test to the point I couldn't even blind flash the bios update on the B850i. Everything had to be completely reset/reseat and you could not start with the KingBank sticks or the same vicious "doesn't matter what sticks you put in here now, I'm not working" cycle would start again....even a single stick wouldn't boot. If I start with a known, working stick of memory and boot but then power down and install the KingBank sticks it won't work but I can at least go back to another set of sticks and they will eventually boot. It is only when I install a new/different CPU and start first with the KingBank sticks that everything goes to poo. This is with both boards running the newest 4.43 bios from Asrock.... Here is one chap with the problem, others who knew about it and Asrock offering a beta bios to fix the issue at least for his Nova board: I'm still testing and retesting to lock it down but either way, I won't be using the KingBank sticks in the Asrock boards. I'm going to swap out my TG 2x24GB 8200 sticks in my main rig and put the KingBanks in there even if they are overall inferior. If I can really lock this down and have total confidence in the MC combo for my C26 portable build, I'll send back the B850i, but we'll see as testing continues.....
  23. Editing the attached P5200 vBIOS with v1.34 of your tool isn't getting me an overclock. If I overclock vram, the 1.5V speed bin gets ignored and it runs at the 6ghz 1.35V speed bin. Raising the core limit over 1708 is also ignored. Currently I'm trying to set 8GHz on the ram. I am using the #2 memory strap setting on the card instead of #0 like every other P5200 in existence. idk if that matters for vbios vram overclocks. p5200_dell.rom p5200_8000_2.bin
  24. Last week
  25. No one helps where I live. They say they only repair certified brands, like what the heck. I hope it's a CPU issue. An "ebay" repair job is like 300-400€ lol and we aren't sure if they can repair. I'll try and see if one of my connections knows someone for repairs
  26. I think you should have it checked by a specialist who can repair motherboards; you might not need to replace the motherboard after all.
  1. Load more activity
×
×
  • Create New...

Important Information

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. Terms of Use