Noone want to help me try to replace the win32k.sys before attempting new install of win 7?
In this present issue under discussion, win32k.sys is not a problem, it was never, and it cannot be.
And trustedinstaller will not allow to replace you to win32k.sys. Why? Because there is enough reason to prevent you from doing it.
If win32k.sys is corrupted, SFC scannow should fix it. If SFC failed, that means there are errors beyond recovery in normal course; and the wise decision is to go for a repair install.
In your situation, the real problem is the storage controller driver. That is failing, that is unstable. But the crash dump initially failing to determine it as the failing module, so it blaming win32k.sys wrongly. I suggested you all the possible ways to stop the storage controller driver; but it is so vulnerable that it is not letting you to go upto that place too, failing even before that.
In such a situation, it is the best for you to go for a clean reinstall. Saying again, win32k.sys is not the problem, and it never was.
Here is the link to the stop 0x3B hotfix:
"0x0000003B" Stop error when you run certain applications in Windows 7 or in Windows Server 2008 R2
There is a description that what files it contains. There is no win32k.sys. Verify it. And, this fix will be a part of the service pack 2. That means, win32k.sys is not anything that reported bad or failing till now.
Then why you are getting this result on the Blue Screen? It is a misunderstanding from the Crash Dump's part. We interpret it, we can come to know that it is iaStor.sys that is behind the prima facie win32k.sys.
I hope you can understand now, why nobody is helping you replace win32k.sys?