My apologies, I was here earlier while you were in-forum but I was called away before I could formulate a reply.
IE9 should run flawlessly on Win7 as it was built for Win7. Because of peer pressure Microsoft (MS) has created versions of IE originally meant for Win8; 10 and 11, for Win7, and users of Win7 have found these versions to be problematic when trying to upgrade.
On my machine I started with IE9 and had no problems until I upgraded to IE10, but I've since resolved those problems. I would rather bite the bullet and go to Win8.1 if I'd want to try and upgrade to IE11.
Then, afterwards, I got a blue screen after reverting to IE9. I believe it's the same error. I'll put the zip into the downloads. It occurred shortly after I opened IE and started typing in a web adress.
Now that you have IE9 we will stay with that. You may have missed adding that error because all I saw was a new Windbg dmp file but we won't worry about that now. More on the new dmp file in a bit.
Thank you for covering all my questions, and If and when you have a new BSOD run the SF diagnostic tool and make sure you click on the "Grab All" button then upload that as a zip file.
The newest dmp points to a csrss.exe problem which involves:
CSRSS runs as a user-mode
system service. When a user-mode process calls a function involving console windows, process/thread creation, or
side-by-side support, instead of issuing a
system call, the Win32 libraries (kernel32.dll, user32.dll, gdi32.dll) send an
inter-process call to the CSRSS process which does most of the actual work without compromising the kernel.
[1] Window manager and
GDI services are handled by a kernel mode driver (win32k.sys) instead.
Source:
Client/Server Runtime Subsystem
I remembered something in the beginning of your thread that
Arc tried to point you to in post #4 and what is important here is the gdi32.dll that involves the Graphics Device Interface (
GDI) services.
Cause
This error has been linked to
excessive paged pool usage and may occur due to
user-mode graphics drivers crossing over and passing bad data to the kernel code.
Source:
My previous post #62
Concentrate on the part of Arc's post about trying a different driver for your graphics card. In the time since you tried a different driver there have been two new ones added to GeForce List.
I realize this will be painful, but I would start at the top and try each one until you find the one that will work with your build. Remember, make sure you do a
clean install of each driver and test stability after each new install.
You could try Auto-Detect to see if GeForce can try to pick one that may work with your build. The link I offer points to a list that you can do that, plus a list that I picked from information that you supplied in your System Specs.
Drivers | GeForce
If you do have new BSOD's with any of the new driver tries, run the SF diagnostic tool and save them and continue on to the next newest driver pack,
remember, do a clean install, hopefully one of those will work, if not upload all of the SF diagnostic tool reports when you are done trying.
If this doesn't help then the only thing I can think of is there is incompatibility between your motherboard, ram, and the graphic card. You may have to change one or the other.