BSOD win32k

theres no real clues i can see in your .dmp file at the moment but there are some drivers that need researching and updating

GVTDrv64.sys fffff880`08971000 fffff880`0897b000 0x0000a000 0x44fd22ca 05/09/2006 07:10:02
jraid.sys fffff880`011c7000 fffff880`011e2000 0x0001b000 0x48855b12 22/07/2008 03:59:14
RTKVHD64.sys fffff880`05a42000 fffff880`05babf80 0x00169f80 0x488853f3 24/07/2008 10:05:39
000.fcl fffff880`06dcb000 fffff880`06df6000 0x0002b000 0x48dcdf7a 26/09/2008 13:11:22
AODDriver.sys fffff880`0897b000 fffff880`08982000 0x00007000 0x48f2d0df 13/10/2008 04:38:55
purendis.sys fffff880`05a00000 fffff880`05a0c000 0x0000c000 0x490695a0 28/10/2008 04:31:28
pnarp.sys fffff880`05bf1000 fffff880`05bfd000 0x0000c000 0x4906a9ac 28/10/2008 05:57:00

also what antivirus and or third party firewall are you using ?

Sorry, I was composing this as ickymay was posting above :)
No specifics from the dump file - but there are a couple of hints:

Please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:

Code:

000.fcl      Fri Sep 26 09:11:22 2008 - CyberLink FCL Driver - http://www.carrona.org/dvrref.html#000.fcl
AODDriver.sys Mon Oct 13 00:38:55 2008 - AMD Overdrive; also in EasyTune6 for Gigabyte motherboard - http://www.carrona.org/dvrref.html#AODDriver.sys
GVTDrv64.sys Tue Sep 05 03:10:02 2006 - Gigabyte EasyTune6 driver - http://www.carrona.org/dvrref.html#GVTDrv64.sys
jraid.sys    Mon Jul 21 23:59:14 2008 -    JMicron RAID Driver - http://www.carrona.org/dvrref.html#jraid.sys
pnarp.sys    Tue Oct 28 01:57:00 2008 - Pure Networks, Inc. Network Magic Address Resolution Protocol Driver - http://www.carrona.org/dvrref.html#pnarp.sys
purendis.sys Tue Oct 28 00:31:28 2008 - Pure Networks, Inc. Network Magic NDIS Relay Driver - http://www.carrona.org/dvrref.html#purendis.sys
RTKVHD64.sys Thu Jul 24 06:05:39 2008 - Realtek High Definition Audio Function Driver - http://www.carrona.org/dvrref.html#RTKVHD64.sys

After these are updated (and if the BSOD's still occur), please run Driver Verifier according to these directions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Summary of the BSOD:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Mar 25 13:02:45.233 2010 (GMT-4)
System Uptime: 0 days 11:06:51.028
BugCheck 3B, {c0000005, fffff960002841d9, fffff88009517010, 0}
Probably caused by : win32k.sys ( win32k!DestroyUMPDHeap+d )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  iTunes.exe

justjohnny86 said:

Thanks to both of you for your assistance! I am working on the apparently older drivers. How were you able to find the year of the drivers from the report? I looked at it and couldn't find anything like that...lol call me a nub. Anyway, I figured I would post this because I decided after some dabbling to just run the verifier to check my status. Turns out the driver that crashed consistently after following the instructions was ElbyCDIO.sys, which, from my research is just some file associated with anydvd. Should this be of real interest or simply worthy of passing glance?

Thanks again!
Johnny B.

well if driver verifier identified anydvd I would update the program for a newer version of ElbyCDIO.sys or unninstall the program completely and monitor for crashes and system stability