NIGHTMARE intel gma 3650

marsay001

Distinguished
Apr 21, 2009
184
0
18,710
I recently bought a netbook with an atom n2600, I upgraded the ram to 2GB and upgraded to windows 7 64 bit (from starter) however I decided after a couple of days that a 32 bit would be more sensible due to lesser system requirements.

However now when I go to install my display driver, the process goes fine but on reboot, af ter the green loading bar, the screen goes black then appears all pix-elated with lines/artifacts all over.

I can just make out the mouse pointer, however it doesn't move when I move the mouse (asin the pc is frozen ) I've used every different driver I can, Including the one that came with the net book. The funny thing is when I was using 64 bit 7 I was using a beta driver which worked flawlessly! .. .

Please help. these netbook screens aren't exactly large, and using it in 800x600 makes it ten times worse!

thanks !
 
Solution
The device could have come with custom drivers installed, which may not be available from Intel. You would need to use the drivers supplied by your device's manufacturer if the Intel drivers are not working.

RAM usage at idle is not a preferable indication of inefficiency. RAM usage in Windows Vista or later is usually higher due to caching and other methods designed to actually improve performance of the machine. It's more efficient to use your RAM for caching than to leave it sitting idle. :)

The build of Windows is not going to affect driver support, because the core framework of Windows 7 is not going to change from one version to another, but only the feature set that has been hung upon the framework that is the Windows 7...

marsay001

Distinguished
Apr 21, 2009
184
0
18,710
There was a difference in ram usage at idle of just under 500mb with 32 opposed to 64. Intel don't seem too be giving any support for this chip tbh. Loads of complaints, but if there not making newer drivers I guess that the only way.

However when I bought the laptop it worked fine so why not now, could it be because I'm using a diffrent build of windows starter to the one that came originally ? I'd heard people where saying certain builds had issues with drivers, but some didn't
 
The device could have come with custom drivers installed, which may not be available from Intel. You would need to use the drivers supplied by your device's manufacturer if the Intel drivers are not working.

RAM usage at idle is not a preferable indication of inefficiency. RAM usage in Windows Vista or later is usually higher due to caching and other methods designed to actually improve performance of the machine. It's more efficient to use your RAM for caching than to leave it sitting idle. :)

The build of Windows is not going to affect driver support, because the core framework of Windows 7 is not going to change from one version to another, but only the feature set that has been hung upon the framework that is the Windows 7 kernel and supporting code. Starter has essentially the same kernel as Ultimate, with the exception that, it's had a lot of features omitted from it, which I'm sure you are quite familiar with.
 
Solution
Well, in a nutshell, any RAM that is not in use is practically going to waste. Since the release of Vista, Microsoft has chosen to use a much greater amount of RAM for caching when possible. All this means is that program code and data is loaded into RAM in a sort of predictive manner, and then left there, based on your usage patterns, and the system's current need for RAM. Cache is cleared to make room for anything else as more RAM is needed, so it isn't that all your RAM is used up, it's simply, pre-loaded, and often with the same information you would have asked for. When you choose to launch one of the cached programs, instead of reading everything from the computer's hard drive, which is usually the slowest form of memory, the cached information is read from RAM instead, greatly improving performance.

Further still, as you close programs, the RAM contents aren't exactly wiped back to nothingness by the act of closing the program. Instead, the RAM contents are left intact as much as possible, in case you reopen the same application, at which point, your program loads faster, as the entirety of it does not need to be loaded from disk.