Jump to content

Low resolution BSOD

Go to solution Solved by BULLYBEEF,
5 hours ago, SpookyCitrus said:

If it still doesn't work after a fresh install, I hate to say it. But if that new card you bought was used it could just be a bad card. 

I think I may have solved it. I had the card plugged into a PCIE power Extension cable so I removed it and Plugged the card directly into the power supply and It seemed to have resolved the issue. I’ve been playing cyberpunk for almost 2 hours with no issues. Thank you for the response. 
 

Hey guys, could yall help me out? I just got a new RTX 3060 to replace my old 1060. 

I installed it in my system, used DDU to uninstall my old drivers completely, and Installed the latest drivers from 3Dguru. Every time I load into a game it blue screens but the kicker is: before it blue screens the screen goes black and when the blue screen appears it’s in a lower resolution. I Hope someone can help me get to the bottom of this. Thanks

My specs

 

My specs:
Processor: AMD Ryzen 5 4500 6-Core Processor 3.60 GHz
RAM: 32.0 GB 3200MHz Corsair Vengeance  LPX
GPU: ASUS DUAL RTX 3070 SI (8 GB)
Power Supply: EVGA 600-watt 
Stage: Wester Digital M.2 NVME EVME SSD / 3X Crucial BX500 Sata SSD


 

Link to comment
https://linustechtips.com/topic/1593342-low-resolution-bsod/
Share on other sites

Link to post
Share on other sites

Run DDU again, use the clean and restart option. Then install the Nvidia App to get the drivers, don't get the drivers from GURU3D or Windows Updates. Only get the GPU drivers from the Nvidia Apps automatic driver updater.

Main Desktop: CPU - i9-14900k | Mobo - Gigabyte Z790 Aorus Elite AX | GPU - PNY Gaming OC RTX 5080 16GB RAM - Corsair Vengeance Pro RGB 64GB 6400mhz | AIO - Arctic Liquid Freezer III 360mm | PSU - Corsair RM1000X | Case - Hyte Y40 - White | Storage - Samsung 980 Pro 1TB Nvme /  Sabrent Rocket 4 Plus 4TB Nvme / Samsung 970 EVO Plus 2TB Nvme / Samsung 870 EVO 4TB SSD / Samsung 870 QVO 2TB SSD/ Samsung 860 EVO 500GB SSD|

 

TV Streaming PC: Intel Nuc CPU - i7 13th Gen | RAM - 16GB DDR4 3200mhz | Storage - Crucial P3 Plus 1TB Nvme |

 

Phone: Samsung Galaxy S26 Ultra - Black 256GB |

 

Link to comment
https://linustechtips.com/topic/1593342-low-resolution-bsod/#findComment-16603631
Share on other sites

Link to post
Share on other sites

1 hour ago, SpookyCitrus said:

Run DDU again, use the clean and restart option. Then install the Nvidia App to get the drivers, don't get the drivers from GURU3D or Windows Updates. Only get the GPU drivers from the Nvidia Apps automatic driver updater.

Okay, I'll give it a try and back get with the results. 

Link to comment
https://linustechtips.com/topic/1593342-low-resolution-bsod/#findComment-16603684
Share on other sites

Link to post
Share on other sites

5 hours ago, SpookyCitrus said:

Run DDU again, use the clean and restart option. Then install the Nvidia App to get the drivers, don't get the drivers from GURU3D or Windows Updates. Only get the GPU drivers from the Nvidia Apps automatic driver updater.

Okay, I'll give it a try and back get with the results. 

Link to comment
https://linustechtips.com/topic/1593342-low-resolution-bsod/#findComment-16603898
Share on other sites

Link to post
Share on other sites

1 hour ago, BULLYBEEF said:

No luck, same result I have a pretty cooked Windows install, I'm gonna try reinstalling. It probably won't help I needed to do it anyway. 

If it still doesn't work after a fresh install, I hate to say it. But if that new card you bought was used it could just be a bad card. 

Main Desktop: CPU - i9-14900k | Mobo - Gigabyte Z790 Aorus Elite AX | GPU - PNY Gaming OC RTX 5080 16GB RAM - Corsair Vengeance Pro RGB 64GB 6400mhz | AIO - Arctic Liquid Freezer III 360mm | PSU - Corsair RM1000X | Case - Hyte Y40 - White | Storage - Samsung 980 Pro 1TB Nvme /  Sabrent Rocket 4 Plus 4TB Nvme / Samsung 970 EVO Plus 2TB Nvme / Samsung 870 EVO 4TB SSD / Samsung 870 QVO 2TB SSD/ Samsung 860 EVO 500GB SSD|

 

TV Streaming PC: Intel Nuc CPU - i7 13th Gen | RAM - 16GB DDR4 3200mhz | Storage - Crucial P3 Plus 1TB Nvme |

 

Phone: Samsung Galaxy S26 Ultra - Black 256GB |

 

Link to comment
https://linustechtips.com/topic/1593342-low-resolution-bsod/#findComment-16603972
Share on other sites

Link to post
Share on other sites

5 hours ago, SpookyCitrus said:

If it still doesn't work after a fresh install, I hate to say it. But if that new card you bought was used it could just be a bad card. 

I think I may have solved it. I had the card plugged into a PCIE power Extension cable so I removed it and Plugged the card directly into the power supply and It seemed to have resolved the issue. I’ve been playing cyberpunk for almost 2 hours with no issues. Thank you for the response. 
 

Link to comment
https://linustechtips.com/topic/1593342-low-resolution-bsod/#findComment-16604110
Share on other sites

Link to post
Share on other sites

WHEA means a hardware error with the CPU or a PCIe device. Go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.

 

If you don't have any dump files from these crashes it makes storage the main suspect (The drive is taken offline if it gets an error this severe so it can't write dump files to it), but there are other things we can do/check to see what the issue was. There are other things that can prevent dump file creation so we still want to check the error properly.

 

Method 1: Go into Event Viewer and find the critical (Red X icon) Kernel-Power Event ID 41 from the BSOD (Scroll down to the timestamp of the crash and you should see it). This just means unexpected shutdown, but when you have a BSOD it will save the parameters for the BSOD in the event. So select it and change to the Details tab. Screenshot or copy paste the info here.

 

Method 2:  If it already hangs on the BSOD screen (As you can't get dump files) then this step is not necessary, but if it reboots normally after a few seconds then go to this guide and on this screen remove the check for automatically restart. To restart manually, just use the power button.

 

To make the BSOD screen display the additional info on the BSOD screen we need to add a field to the registry. If you are not comfortable editing the registry then do not do this step. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl, right click on the empty area on the right section and select New → DWORD value with the name "DisplayParameters". Right click on it, modify and set the value data to 1 (Does not matter if you use Hexadecimal or Decimal). It should look like this once done. Reboot to apply the registry change.

 

The next time you BSOD, you should have these extra numbers in the top left corner. I want a picture of this.

 

EDIT: 

Quote

 before it blue screens the screen goes black and when the blue screen appears it’s in a lower resolution.

On this note, there is currently a bug in Windows where if you get a BSOD and use a monitor that is higher resolution than 1080p it can look like this. Maybe this is something new Microsoft is testing to prevent this bug. It would be the first time I see it doing something like this so it's purely speculation.

Link to comment
https://linustechtips.com/topic/1593342-low-resolution-bsod/#findComment-16604161
Share on other sites

Link to post
Share on other sites

7 hours ago, BULLYBEEF said:

I think I may have solved it. I had the card plugged into a PCIE power Extension cable so I removed it and Plugged the card directly into the power supply and It seemed to have resolved the issue. I’ve been playing cyberpunk for almost 2 hours with no issues. Thank you for the response. 

That'll do it. Glad it's sorted and wasn't the actual card.

Main Desktop: CPU - i9-14900k | Mobo - Gigabyte Z790 Aorus Elite AX | GPU - PNY Gaming OC RTX 5080 16GB RAM - Corsair Vengeance Pro RGB 64GB 6400mhz | AIO - Arctic Liquid Freezer III 360mm | PSU - Corsair RM1000X | Case - Hyte Y40 - White | Storage - Samsung 980 Pro 1TB Nvme /  Sabrent Rocket 4 Plus 4TB Nvme / Samsung 970 EVO Plus 2TB Nvme / Samsung 870 EVO 4TB SSD / Samsung 870 QVO 2TB SSD/ Samsung 860 EVO 500GB SSD|

 

TV Streaming PC: Intel Nuc CPU - i7 13th Gen | RAM - 16GB DDR4 3200mhz | Storage - Crucial P3 Plus 1TB Nvme |

 

Phone: Samsung Galaxy S26 Ultra - Black 256GB |

 

Link to comment
https://linustechtips.com/topic/1593342-low-resolution-bsod/#findComment-16604343
Share on other sites

Link to post
Share on other sites

13 hours ago, Bjoolz said:

WHEA means a hardware error with the CPU or a PCIe device. Go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.

 

If you don't have any dump files from these crashes it makes storage the main suspect (The drive is taken offline if it gets an error this severe so it can't write dump files to it), but there are other things we can do/check to see what the issue was. There are other things that can prevent dump file creation so we still want to check the error properly.

 

Method 1: Go into Event Viewer and find the critical (Red X icon) Kernel-Power Event ID 41 from the BSOD (Scroll down to the timestamp of the crash and you should see it). This just means unexpected shutdown, but when you have a BSOD it will save the parameters for the BSOD in the event. So select it and change to the Details tab. Screenshot or copy paste the info here.

 

Method 2:  If it already hangs on the BSOD screen (As you can't get dump files) then this step is not necessary, but if it reboots normally after a few seconds then go to this guide and on this screen remove the check for automatically restart. To restart manually, just use the power button.

 

To make the BSOD screen display the additional info on the BSOD screen we need to add a field to the registry. If you are not comfortable editing the registry then do not do this step. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl, right click on the empty area on the right section and select New → DWORD value with the name "DisplayParameters". Right click on it, modify and set the value data to 1 (Does not matter if you use Hexadecimal or Decimal). It should look like this once done. Reboot to apply the registry change.

 

The next time you BSOD, you should have these extra numbers in the top left corner. I want a picture of this.

 

EDIT: 

On this note, there is currently a bug in Windows where if you get a BSOD and use a monitor that is higher resolution than 1080p it can look like this. Maybe this is something new Microsoft is testing to prevent this bug. It would be the first time it doing something like this so it's purely speculation.

I think it was just a voltage issue because I tested the same PCIE power cable on my brother's rig with a 2070 ti and it did the same thing. 

Link to comment
https://linustechtips.com/topic/1593342-low-resolution-bsod/#findComment-16604698
Share on other sites

Link to post
Share on other sites

1 hour ago, BULLYBEEF said:

I think it was just a voltage issue because I tested the same PCIE power cable on my brother's rig with a 2070 ti and it did the same thing. 

Unless it's the EXACT same model PSU, do NOT swap PSU cables. The pinout on the PSU side isn't standardized. 

 

EDIT: Read the other post and saw that it's an extension. That would be standardized on that end of the cable. So it should be fine.

Link to comment
https://linustechtips.com/topic/1593342-low-resolution-bsod/#findComment-16604742
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×