SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Pastimes : Computer Learning -- Ignore unavailable to you. Want to Upgrade?


To: SIer formerly known as Joe B. who wrote (76771)9/14/2011 11:29:31 PM
From: Gottfried  Read Replies (1) | Respond to of 110655
 
you must have been taking notes to remember all you did :) Congrats to the fix



To: SIer formerly known as Joe B. who wrote (76771)9/29/2011 7:41:48 PM
From: SIer formerly known as Joe B.1 Recommendation  Read Replies (1) | Respond to of 110655
 
Turns out my IE scroll issue wasn't caused by leaving a tab with Drudgereport open. It contributed to the problem but it wasn't the cause the cause was a Nvidia driver update. I rolled back the drivers to the previous version and now IE scrolls fine.

Kind of along the same lines I worked on a Vista HP desktop computer last week that was blue screening intermittenly. The BSOD error messages kept changing which usually means bad memory but even after swapping the memory with known good memory the blue screens continued so I left in the known good memory and did a clean install, no BSOD, installed Sp1, Sp 2 and ~100 high priority updates still no BSOD. Then I ran HP's update software, shortly after the BSOD returned so I did a system restore to b4 the HP updates were installed and the blue screens stopped. The funny part is whenever I Googled any of the BSOD error messages the solutions were always updating drivers but that was actually the culprit not the solution. After getting the PC up to date I put the old memory back in and guess what the BSOD returned. The PC had 3 GBs of memory so I rebooted with just 2 1 GB RAM sticks, it booted fine no BSOD. Then I added the 2 1/2 GB sticks of RAM and the BSOD returned so the original BSOD were being caused by bad memory AND bad drivers. Lucky for the PC's owner the RAM was cheap, 2 1GB sticks was only $30 and that upped their PC to 4 GB. Also they were lucky I figured it out, I was very close to blaming the BSOD on the motherboard going bad.