Nvidia system tools forceware 186.51 upon windows start display corruption

[chris89]

Ok, so I have an hp dv2615nr and its running a tl-68 turion x2 from 2.4Ghz to 2.6Ghz but is unstable at 2.6Ghz so I'll dial back to 2.5Ghz. Anyway, I have a modded driver which allows the 7150M nvidia chip to be overclocked in windows 7 x64. It's 186.51 x64 and it works fine. However once it crashes it corrupts something and the screen artifacts on windows start. If I setup msconfig to diagnostic mode it'll start up and not go corrupted. Can you tell me how to view a log on what service is causing the issues I'm having from a log? I think there's some registry corruption upon the crash.

THANKS

[3dfxrain]

Event viewer I suppose in admin tools or whatever, I wouldn't overclock laptop, haven't done that before.

[chris89]

Okay ill check it out. I'm 100% sure heat is not causing the instability. I bought a new 18.5V 6.5A charger for more power from the 3.5A one. Anyway my temps are like 29*C at idle on the cpu and gpu and under load I see 60-65*C. The fan is modded to 5v with copper shims and new thermal paste and arctic silver ceramique 2 none electrically conductive. This laptop plays games at 2.6Ghz from 2.4Ghz, just won't pass intelburntest but I'm guessing the power supply is insufficient.

I'll look into the event viewer and find out what's going on. I made a full windows backup of when its running perfectly and it'll run amazing for weeks then after 1 crash it'll corrupt the registry or some system service and cause the display corruption. Very odd. The laptop runs very very cool with all the mods. I also cut a hole under the laptop intake cooling fan to suck in lots of cool air to exhaust out all the heat.

[chris89]

I did another fresh windows install and randomly after installing the nvidia smbus driver when it booted it was messed up. So, I guess it is in fact the smbus driver im installing possibly? I need SMBus access to change my memory speed in SPDTool.

I know that a service is causing is since if i mimic safe modes services it'll boot right up into normal windows no issues. So it is a service that is causing this but it occured after installing the SMBus driver from Chipset_MCP67M_1313_vista_x64_x86 which I downloaded. Since I'm running windows 7 x64 it's hard to find the right drivers but i have them all.