So i just set my main monitor here on the dual-PIII to 1400x1050. Like so.
I shut down the computer and went to the beach, had a few with my friends, then back to the hood, had a few more , and finally back home. I turn the computer on to find a blue screen, PAGE_FAULT_IN_NONPAGED_AREA. I restart it only to find another one, IRQL_NOT_LESS_OR_EQUAL. Now, i know those screens are usually caused by overclocking, and i am overclocking, but it's been perfectly stable so far. So wondered if the problem was caused by my recent resolution change.
I rebooted in VGA mode, and sure enough, no BSOD. However i couldn't enable the second screen after the VGA mode reboot, so i set the resolution to 1280x1024 on the main and rebooted again. Sure 'nuff, worked fine. I've set the main monitor to 1400x1050 again and disabled the second screen. I wonder if it'll boot fine tomorrow...
So i propose a new designator for bluescreens: MAXIMUM_RESOLUTION_REACHED
I shut down the computer and went to the beach, had a few with my friends, then back to the hood, had a few more , and finally back home. I turn the computer on to find a blue screen, PAGE_FAULT_IN_NONPAGED_AREA. I restart it only to find another one, IRQL_NOT_LESS_OR_EQUAL. Now, i know those screens are usually caused by overclocking, and i am overclocking, but it's been perfectly stable so far. So wondered if the problem was caused by my recent resolution change.
I rebooted in VGA mode, and sure enough, no BSOD. However i couldn't enable the second screen after the VGA mode reboot, so i set the resolution to 1280x1024 on the main and rebooted again. Sure 'nuff, worked fine. I've set the main monitor to 1400x1050 again and disabled the second screen. I wonder if it'll boot fine tomorrow...
So i propose a new designator for bluescreens: MAXIMUM_RESOLUTION_REACHED
Comment