BSOD on shutdown

Hello everyone. It seems that my computer is another victim of this "kernel-power 41" thing. This system (details in profile) was perfectly stable for over a year. Not a single BSOD on Vista.
Now I'm using Win 7 Ultimate x64 and about a month ago kernel-power happened while just brousing with firefox. Payed no attention to it (you see, I had a paging file disabled due to my 8Gb of RAM and a presence of an SSD, system was set to reboot instead of showing BSOD). My monitor just flashed with multicolor horisontal stripes and next moment I was staring into BIOS. Unpleasant, but it was a single outbreak.
But now I got goddamn thing almost every single time I'm trying to shutdown. Same stripes (updated video drivers already). Sometimes during reboot. My sysfiles seems to be unaffected (checked with cmd)... yet. Boots are successfull.
Now, I tried updating my outdated drivers. No help. My personal guess would be my EMU USBaudio driver (antique thing from 2008, Creative abandoned support of it, so no updates). But i switched it off (no cable disconnecting), no help.
Nothing is overheating.
Latest hardware addition - 2 tb drive. BSOD started... 2 weeks after? Drive SMART ok.
Sorry for my English.
Here comes the minidump. Thanks for your help in advance!

Well, an update. And another BSOD. During shutdown, again. After playing around with debuggers I got this:

On Sun 02.05.2010 14:16:44 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x226, 0x2, 0x1, 0xFFFFF80002AC3275)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\050210-13525-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 02.05.2010 7:58:53 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xF011D0220, 0x2, 0x1, 0xFFFFF80002ADF275)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\050210-13275-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

So, basically - bad news. ntoskrnl is like a core of a system, and detecting it as a cause of a crash is pointing pretty... everywhere. I mean, it's not an easy "bad driver" solution I was hoping for. So help still much appreciated.

Oh, and I'm using KIS2010. Worked fine before. Should I uninstall it?