Welcome to PCHF

Click on the BSOD link below in my signature and follow the procedure.

Ok, moved to the BSOD section.

Hello Waloower, welcome to PCHF.

I couldn't find any evidence that this was a graphics card problem in these logs. There were aspects that suggested hardware might be the cause, but my suspicions lie heavily on your Razer Copperhead mouse driver. Well known for causing stop errors, and the version your currently running is not Windows 7 compatible. Can you install the lastest driver from here: Razer Support

As for the graphics card, since the 9600gt would have to have been installed in the PCI Express graphics slot, so the "Primary Graphics Adapter" in BIOS would need to be set to PCI Express. This is the scanning order in which the motherboard searches for a graphics card - so PCI Express would be top of the list. The item above it "Share Memory" should be set to Auto. The combination of Auto and PCI Express will disable the onboard chipset whilst the card is installed.

See also: http://download.asrock.com/manual/N68C-GS UCC.pdf

Any time .. no problems

No problems. I won't rely on these logs too heavily.. they are all over the place and as they only show the final moments of death, I believe that whatever caused the problem has long since done it's damage some time before the stop errors occurred. One log that did interest me though suggested a bad IP (Instruction Pointer) by an nVidia driver trying to access an invalid address in memory. An Instruction Pointer (if your not already aware) simply tells the CPU where in memory it can find it's next instruction. A bad IP indicates that it did not find the start of the instruction where it was supposed to be. Just to make sure, it would be worth updating these also, either from the AsRock website, or directly from nVidia, even though I'm not personally aware of any known problems with these particular drivers.

If problems persist.. not to worry - we will need to perform further diagnostics to track the problem further. In the meantime, I would also recommend making sure your up to date with the latest Microsoft updates/patches (as your out of date at the moment) from Control Panel > System and Security > Windows update.

No prob's.. they should be different versions so even if it's an older version, it would be worth trying the other just to be sure. Also, can you confirm one of those updates was Service Pack 1? if not, you'll probably find further updates after you restart. . keep us updated budd

Renaming win32k.sys - awful idea for many many different reasons.

1) you probably noticed that all of your stop errors have suggested many different drivers, nvmf6264, hdaudbus, ntkrnlmp, nvstor64, nvlddmkm, win32k are some that have all been named in these logs. Chances of all these drivers causing problems - none.

2) win32k.sys can't simply be renamed because it would be in use by Windows. It would have to be done at the recovery console and you would need to guarantee that it was the same version as it comes as part of many windows updates. Otherwise Windows doesn't tend to react well when it's Kernel drivers are running mismatched versions.

3) win32k.sys comes part of Windows - so if there was a problem with this driver, we should all be experiencing problems. I can tell from the logs that win32k.sys hasn't been replaced by anything malcious, and are often wrongly blamed as the probable cause in stop errors in any case.

TBH, I was a bit skeptical about this still being a driver issue since investigating the bad IP, but we do need to rule out software to be sure. One thing we can do just to be sure is use verifier, which will catch any misbahaving process and report it in another minidump.

To use driver verifier:
- First make sure you can access Safe Mode (with Networking preferably), by tapping [F8] during startup. If verifier detects a problem, you may not be able to start in normal mode.
- Go to Start and in the search bar type in verifier
- At the start of wizard, click Next.
- Click Automatically select all drivers installed on this computer followed by Finish, and then restart the PC.

If you receive any BSOD's during the course of using verifier, please upload the logs, as they will contain the results of any driver problems. To turn off driver verifier, simply go back to the verifier wizard again in Safe Mode, and select Delete existing settings.

In the meantime, it would be good to start ruling out hardware components too. A bad instruction pointer could be caused by CPU, motherboard or RAM issues. RAM is fairly easy to rule out using memtest86. The instructions of how to use it can be found here: http://www.pchelpforum.com/memory/58877-memtest86-how-download-run.html