BSOD ntoskrnl.exe

Ill have a look at em, but for now .. The dmp(s) point to ntkrpamp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause. To pin the problem down, enable driver verifier..

- 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).

I sopke too soon... DISABLE Driver Verifer for the time being.. You have too many issues here, and until they are cleared up, driver verifer is just going to crash your system for the same issues.. Lets address them one by one...

usb.sys ... This is your USB driver ... go to Asuss' home page and make sure that you have the latest version...

nvlddmkm.sys ... Driver for your nVidia Geforce 6600 card .. Update to the latest version...

I8042prt.sys This is a system function driver found in Microsoft Windows 2000 and later versions for PS/2-style keyboard and mouse devices. Check for updates for your keyboard/mouse

tcpip.sys.... Update your network adapter to the latest version...

kl1.sys ... Kaspersly Antivirus.... A known cause for BSOD crashes in some systems.. Uninstall Kaspersky and install Microsoft Security Essentials...

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ffffffff, 2, 1, fffff88003eceec0}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+2fc )

Followup: MachineOwner
---------
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {200, 2, 1, fffff88004b8b203}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : hardware ( dxgmms1!VidSchiProcessCompletedQueuePacketInternal+2db )

Followup: MachineOwner
---------


.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff50006593a38, 2, 1, fffff880048082bd}

Probably caused by : i8042prt.sys ( i8042prt!I8042MouseIsrDpc+261 )

Followup: MachineOwner
---------

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1, {7710ff8a, 0, ffff0000, fffff88002618c60}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

Followup: MachineOwner
---------


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F7, {fffff88002215bc8, f88001966020, ffff077ffe699fdf, 0}

Probably caused by : tcpip.sys ( tcpip!_report_gsfailure+26 )

Followup: MachineOwner
---------


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff880040f5a30, 1, 0}

Unable to load image \SystemRoot\system32\DRIVERS\kl1.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for kl1.sys
*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
Probably caused by : kl1.sys ( kl1+7aa30 )

Followup: MachineOwner
---------

The following drivers are out of date.. They may or may not be contributing to your problem, but should be updated ..

Code:

ffff880`02cac000 fffff880`02cb4000   ASACPI   ASACPI.sys   Wed May 13 21:25:17 2009 (4A0B72FD) ..This file is used by Asus utilites and various others. Yours is old and needs to be updated. That should resolve this issue..
fffff880`02c7a000 fffff880`02cac000   Rt64win7 Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D) ... This driver is a component of the Realtek network driver available here: Realtek

Once you have replaced/updated all of these drivers, see if you continue to get BSOD crashes...

Disable driver verifier until you have updated the drivers that I pointed out...


How to Enable or Disable Driver Verifier in Windows 7

Let us know how it goes...

Fingers crossed!! Thanks for letting us know..