Monitor Tests Forum

Full Version: Custom Resolution Utility (CRU)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441
(06-12-2019 05:01 PM)ToastyX Wrote: [ -> ]The driver is not handling EDID overrides correctly. Export a file from CRU and post it here. I will see if I can create an alternative method that works with Intel.

I believe the problem is solved.

I had previously been using the most recent Intel GPU drivers (at the time, ~6 months old atm). I reverted back to the manufacturer default drivers, which would not allow ANY CRU overrides to be applied. I browsed through the original post looking to see if I was missing something - I was. Downloaded the [15.40] Intel GPU drivers and manually installed them to override the "Driver being installed is not validated for this computer" error. Now it appears everything is working properly. I retain HDMI audio and the settings persist after losing signal to the TV. Restarted the computer, went to display settings, it properly continues to show 1080 as my (Recommended) resolution and games are properly output to 1080 without having to use restart64.exe.

So yes, I thought as long as I had the most recent drivers it would be fine. But it seems necessary to use those specific [15.40] drivers if you have an Intel GPU. Appreciate your help and your work on this awesome program, otherwise this TV would be a huge PITA.
I deleted all of the resolutions and just kept the extension block. So should I just reset CRU back to default to get the first detailed resolution back?

There were I think 4 other extension blocks when I initially had CRU installed.

As to the Hz change, for whatever reason the regular refresh rate of 239.759 exhibited a picture with heavy stuttering. This was confirmed by other owners of the monitor and LG is currently investigating the issue. As soon as you bring the Hz to 239.760, there's no more stuttering. I had to manual adjust the vertical lines to get to 1304 which would give me that Hz refresh rate of 239.760.

So it sounds like I shouldn't have deleted all of those resolution profiles that originally came when I started CRU. Would you suggest I reset it back to default somehow?

Thanks for your reply.
(06-12-2019 10:31 PM)witega Wrote: [ -> ]So it sounds like I shouldn't have deleted all of those resolution profiles that originally came when I started CRU. Would you suggest I reset it back to default somehow?
You don't need to, but you should have something as the first detailed resolution. You can move 239.760 Hz there. It's more likely adjusting the vertical total removed the stuttering, not the very slight difference in refresh rate.
I added that as a first detailed resolution:

[Image: jU6NtMb.png]

Now I'm running into an issue where after restarting the driver (and not going into Recovery Mode) my monitor turns off and back on again after every 5 seconds or so. So I basically go back into my monitor's OSD, while the screen is still on, power it off, wait a few minutes then turn it on again. Then I restart the drivers until it's stable where I'm not encountering this issue.

Should I remove the extension block from the CRU application since it's identical to my first detailed, or does that not matter?
(06-13-2019 04:10 AM)witega Wrote: [ -> ]Should I remove the extension block from the CRU application since it's identical to my first detailed, or does that not matter?
It's redundant so it doesn't need to be there, but it doesn't matter. Blinking on and off would indicate the monitor or cable can't handle the resolution or timing parameters you gave it. I would try the "LCD standard" and "LCD native" timing options to see if that improves anything.
ToastyX, thanks for your replies.

When you said "Recovery Mode" applies the default settings until the next graphics driver restart, what do you mean by "default settings" here? The first detailed resolution I have or something else?

So now every time I do the restart.exe, run a benchmark, I keep getting these black line artifacts as I posted earlier in my videos. Yet, if I do restart.exe and then go into Recovery Mode, these artifacts are no longer present in the benchmark. They also are gone from games like PUBG.

This is kind of a head scratcher to me.
(06-14-2019 03:07 PM)witega Wrote: [ -> ]When you said "Recovery Mode" applies the default settings until the next graphics driver restart, what do you mean by "default settings" here? The first detailed resolution I have or something else?
Default as in no override, as if you didn't change anything with CRU.
(06-12-2019 05:01 PM)ToastyX Wrote: [ -> ]The driver is not handling EDID overrides correctly. Export a file from CRU and post it here. I will see if I can create an alternative method that works with Intel.

Just FYI I finally found a solution for the current Intel DCH drivers (tested with 26.20.100.6912 on my Surface Go). Under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY\SHP14A6 there were two keys that referred to the same display, one with the EDID_OVERRIDE key (presumably added by CRU) and one without. So I copied everything in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY\SHP14A6\4&3291bf54&0&UID265988\Device Parameters\EDID_OVERRIDE to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY\SHP14A6\1&8713bca&0&UID0\Device Parameters\EDID_OVERRIDE and rebooted, and afterwards my custom resolutions were again shown and usable in Windows display settings.

This is a relief as it looks like the DCH drivers are required for Windows 10 1903, the legacy drivers no longer have a control panel on this version.
(06-23-2019 03:40 PM)xtcrefugee Wrote: [ -> ]Just FYI I finally found a solution for the current Intel DCH drivers (tested with 26.20.100.6912 on my Surface Go). Under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY\SHP14A6 there were two keys that referred to the same display, one with the EDID_OVERRIDE key (presumably added by CRU) and one without. So I copied everything in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY\SHP14A6\4&3291bf54&0&UID265988\Device Parameters\EDID_OVERRIDE to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY\SHP14A6\1&8713bca&0&UID0\Device Parameters\EDID_OVERRIDE and rebooted, and afterwards my custom resolutions were again shown and usable in Windows display settings.
CRU should list both entries in the monitor list, so you should be able to use the "Copy" and "Paste" buttons at the top instead of editing the registry directly. The solution doesn't make sense though. The second entry is added by the Microsoft Basic Display Adapter driver and shouldn't apply to Intel's driver. That seems like a bug in Intel's driver.
I currently have a Samsung Q900RA 8K set, i can enable 8K 30HZ @ 4.2.0 Chroma in CRU but I've been unable to add 3840x2160 @ 120HZ @ 4.2.0

The TV does have a 120HZ panel and enough bandwidth for 4K 120 @ 4.2.0 but i cant add the resolution.

My GPU is a 1080TI

Regards
Scott
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441
Reference URL's