ntoskrnl.exe BSoDs

Good evening,

I was wondering if anyone could help me diagnose some .dmp file data please?

When I first bought my computer, I would occasionally experience bluescreens/restarts upon my computer going into sleep mode. Error message: DRIVER_POWER_STATE_FAILURE

I updated my BIOS to try to help the issue, and haven't had the same type since (although this may be due to me only putting the computer to sleep manually now). However, I have started getting more frequent BSoDs, error message: UNEXPECTED_KERNEL_MODE_TRAP. These happen randomly... during internet browsing, watching DVDs, or when idle. Firefox seems to be a bit unstable on my system. Could this be related?

Using bluescreenview and whocrashed to view my minidumps, it is clear that ntoskrnl.exe is implicated in all of these crashes. My memory and system files seem to be ok from the tests that I have done, and dskchk reported no problems either. I have attached my .dmp files to this post, and included the bugcheck codes below.

My system specs can be found in my profile if they are important (ASUS P7P55D Pro, Core i5 processor, 4gb corsair RAM, ATI HD4850).

Thank you in advance for any help.

On Tue 1/19/2010 6:06:45 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002A4E40F)
Error: UNEXPECTED_KERNEL_MODE_TRAP

On Tue 1/19/2010 9:02:10 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002AA540F)
Error: UNEXPECTED_KERNEL_MODE_TRAP

On Sat 1/16/2010 12:45:05 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002A5740F)
Error: UNEXPECTED_KERNEL_MODE_TRAP

On Mon 1/11/2010 6:45:29 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x9F (0x3, 0xFFFFFA8004B03A20, 0xFFFFF80004027748, 0xFFFFFA8004E1A8D0)
Error: DRIVER_POWER_STATE_FAILURE

On Mon 12/14/2009 7:17:47 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x9F (0x3, 0xFFFFFA8004A82060, 0xFFFFF80000B9C518, 0xFFFFFA8004F0FD30)
Error: DRIVER_POWER_STATE_FAILURE

On Wed 12/9/2009 10:35:04 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x9F (0x3, 0xFFFFFA8004A62A20, 0xFFFFF8000401B518, 0xFFFFFA80040F3850)
Error: DRIVER_POWER_STATE_FAILURE

On Mon 11/23/2009 11:08:54 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x9F (0x3, 0xFFFFFA8004AFDA20, 0xFFFFF80004021518, 0xFFFFFA8007D30440)
Error: DRIVER_POWER_STATE_FAILURE

You'll probably be unsurprised to hear I'm using ZoneAlarm. There seem to be quite a few posts on the internet from users experiencing BSoDs with it... but to be fair, people using ZoneAlarm have every problem going.

I updated a RealTek driver earlier actually, but this was using windows update, and as you say, this might not be the latest. It crashed again 3 hours later too. I'll try and find some newer ones.

Thanks a lot for your speedy reply!

Alright mate,

I downloaded an autoinstall thing from the website (about 5mb) rather than just the Rt64win7.sys driver, even though both drivers seemed to be an older date than the one I had. However, after installation, my connection seems to be superfast?! Maybe there was some sort of conflict going on before? If I get any more BSoDs, I'll get rid of ZoneAlarm. I've been loath to ditch it, as they charged me for another year's subscription (despite cancelling it). If MSE is good though, I'll try that next.

Thanks a lot for your help. You might have just saved my PhD thesis!

If anyone else can help, here are all 8 dump files together. I think the other 2 uploads in this thread will have missed one of them. Thanks in advance to anyone that can help

Cheers. I've already done the BIOS and driver options, and checked pretty much every aspect of my computer (memory tests, disk checks, system file checks etc.), so I've now cleansed myself of zonealarm. I think you're right... if this doesn't sort it, time for a new network card