Windows 7 ntoskrnl.exe,... problems

[jonesx]

I m having bsof for a couple of months now, and there nrs are increasing in time.
I tried googling it, but no real (specific) solution was found..

Thats why i joined this forum for professional assistance, so please help. I attached all the info as explained.

Thnx in advance,

Jones

Link Removed

 

[usasma]

Late for work, this is my canned speech.....
Will look back after work today!
Good luck!

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

This one MUST BE UPDATED!!!:
ASACPI.sys Sun Mar 27 22:30:36 2005 (42476C4C)
Asus ATK0110 ACPI Utility (a known BSOD maker in Win7). Also a part of the Asus PCProbe and AISuite Utilities
Link Removed - Invalid URL

System32LdriversLvga.sys Mon Jul 13 19:38:47 2009 (4A5BC587)

System32LdriversLvga.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

driversLrdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)

driversLrdprefmp.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.



Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Thu Nov  1 09:00:44.092 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\110112-17284-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:02:24.700[/B]
BugCheck Code: [B]BugCheck 1A, {5003, fffff70001080000, d87, d8900001b1e}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2983f )[/B]
BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
Arguments: 
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 0000000000000d87
Arg4: 00000d8900001b1e
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]dwm.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+2983f[/B]
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: [B]2405[/B]
  BIOS Version                  0604   
  BIOS Release Date             07/16/2008
  Manufacturer                  System manufacturer
  Product Name                  P5E-VM HDMI
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Oct  8 15:44:37.211 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\100812-16083-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 1:10:21.649[/B]
BugCheck Code: [B]BugCheck 1A, {5003, fffff70001080000, 5308, c9a0000a600}[/B]
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29dcf )[/B]
BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
Arguments: 
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 0000000000005308
Arg4: 00000c9a0000a600
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]FlashPlayerPlu[/B]
FAILURE_BUCKET_ID: [B]X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+29dcf[/B]
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: [B]2405[/B]
  BIOS Version                  0604   
  BIOS Release Date             07/16/2008
  Manufacturer                  System manufacturer
  Product Name                  P5E-VM HDMI
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Sep 22 08:12:48.782 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092212-18595-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:02:39.779[/B]
BugCheck Code: [B]BugCheck 1E, {ffffffffc0000005, fffff960001a6079, 0, c0214018}[/B]
Probably caused by :[B]win32k.sys ( win32k!HANDLELOCK::vLockHandle+51 )[/B]
BugCheck Info: [B]KMODE_EXCEPTION_NOT_HANDLED (1e)[/B]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff960001a6079, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 00000000c0214018, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]firefox.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x1E_c0000005_R_win32k!HANDLELOCK::vLockHandle+51[/B]
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: [B]2405[/B]
  BIOS Version                  0604   
  BIOS Release Date             07/16/2008
  Manufacturer                  System manufacturer
  Product Name                  P5E-VM HDMI
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Sep 16 15:41:41.797 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\091612-15116-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:03:25.794[/B]
BugCheck Code: [B]BugCheck 24, {1904fb, fffff88002183e08, fffff88002183660, fffff880012373cb}[/B]
Probably caused by :[B]Ntfs.sys ( Ntfs!NtfsLookupAllocation+eb )[/B]
BugCheck Info: [B]NTFS_FILE_SYSTEM (24)[/B]
Arguments: 
Arg1: 00000000001904fb
Arg2: fffff88002183e08
Arg3: fffff88002183660
Arg4: fffff880012373cb
PROCESS_NAME: [B]csrss.exe[/B]
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
FAILURE_BUCKET_ID: [B]X64_0x24_Ntfs!NtfsLookupAllocation+eb[/B]
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: [B]2405[/B]
  BIOS Version                  0604   
  BIOS Release Date             07/16/2008
  Manufacturer                  System manufacturer
  Product Name                  P5E-VM HDMI
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Sep 12 16:08:07.147 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\091212-15709-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:02:35.129[/B]
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
BugCheck Code: [B]BugCheck 1A, {5003, fffff70001080000, 68b, 4be00000d06}[/B]
Probably caused by :[B]intelppm.sys ( intelppm+39c2 )[/B]
BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
Arguments: 
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 000000000000068b
Arg4: 000004be00000d06
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x1a_5003_intelppm+39c2[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Sep  9 17:43:42.974 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\090912-16380-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:01:06.582[/B]
BugCheck Code: [B]BugCheck 1A, {5003, fffff70001080000, 1f4a, 2e3900003e84}[/B]
Probably caused by :[B]hardware ( nt! ?? ::FNODOBFM::`string'+22274 )[/B]
BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
Arguments: 
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 0000000000001f4a
Arg4: 00002e3900003e84
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]AvastSvc.exe[/B]
FAILURE_BUCKET_ID: [B]X64_IP_MISALIGNED[/B]
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: [B]2405[/B]
  BIOS Version                  0604   
  BIOS Release Date             07/16/2008
  Manufacturer                  System manufacturer
  Product Name                  P5E-VM HDMI
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Sep  9 17:41:53.369 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\090912-16894-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 5:30:34.485[/B]
BugCheck Code: [B]BugCheck A, {18, 2, 1, fffff80002cbb868}[/B]
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]ntkrnlmp.exe ( nt!ExpWorkerFactoryCheckCreate+1b0 )[/B]
BugCheck Info: [B]IRQL_NOT_LESS_OR_EQUAL (a)[/B]
Arguments: 
Arg1: 0000000000000018, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002cbb868, address which referenced memory
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME: [B]FlashPlayerPlu[/B]
FAILURE_BUCKET_ID: [B]X64_0xA_nt!ExpWorkerFactoryCheckCreate+1b0[/B]
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: [B]2405[/B]
  BIOS Version                  0604   
  BIOS Release Date             07/16/2008
  Manufacturer                  System manufacturer
  Product Name                  P5E-VM HDMI
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Sep  7 12:07:25.238 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\090712-22713-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:03:05.220[/B]
BugCheck Code: [B]BugCheck 1E, {ffffffffc0000005, fffff8800537f251, 0, 0}[/B]
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]hardware ( dxgmms1!VIDMM_GLOBAL::EndPreparation+29 )[/B]
BugCheck Info: [B]KMODE_EXCEPTION_NOT_HANDLED (1e)[/B]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800537f251, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_IP_MISALIGNED_dxgmms1.sys[/B]
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: [B]2405[/B]
  BIOS Version                  0604   
  BIOS Release Date             07/16/2008
  Manufacturer                  System manufacturer
  Product Name                  P5E-VM HDMI
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Aug 27 17:53:54.128 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\082712-15974-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:10:24.110[/B]
BugCheck Code: [B]BugCheck 50, {fffff88009809150, 0, fffff8800525c01a, 0}[/B]
Probably caused by :[B]dxgkrnl.sys ( dxgkrnl!DXGADAPTER::AcquireDdiSync+12 )[/B]
BugCheck Info: [B]PAGE_FAULT_IN_NONPAGED_AREA (50)[/B]
Arguments: 
Arg1: fffff88009809150, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800525c01a, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME: [B]FlashPlayerPlu[/B]
FAILURE_BUCKET_ID: [B]X64_0x50_dxgkrnl!DXGADAPTER::AcquireDdiSync+12[/B]
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: [B]2405[/B]
  BIOS Version                  0604   
  BIOS Release Date             07/16/2008
  Manufacturer                  System manufacturer
  Product Name                  P5E-VM HDMI
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Thu Nov  1 09:00:44.092 2012 (UTC - 4:00)**************************
[B]ASACPI.sys                  Sun Mar 27 22:30:36 2005 (42476C4C)[/B]
GEARAspiWDM.sys             Mon May 18 08:17:04 2009 (4A1151C0)
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
l160x64.sys                 Mon Oct 12 22:08:28 2009 (4AD3E11C)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
atikmpag.sys                Tue Apr 19 21:22:32 2011 (4DAE3558)
atikmdag.sys                Tue Apr 19 21:53:29 2011 (4DAE3C99)
SASKUTIL64.SYS              Tue Jul 12 17:00:01 2011 (4E1CB5D1)
SASDIFSV64.SYS              Thu Jul 21 19:03:00 2011 (4E28B024)
aswFsBlk.SYS                Tue Jul  3 12:13:12 2012 (4FF31A18)
aswMonFlt.sys               Tue Jul  3 12:13:24 2012 (4FF31A24)
aswTdi.SYS                  Tue Jul  3 12:13:33 2012 (4FF31A2D)
aswrdr2.sys                 Tue Jul  3 12:13:43 2012 (4FF31A37)
aswSP.SYS                   Tue Jul  3 12:14:23 2012 (4FF31A5F)
aswSnx.SYS                  Tue Jul  3 12:14:27 2012 (4FF31A63)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Aug 27 17:53:54.128 2012 (UTC - 4:00)**************************
[B]System32LdriversLvga.sys    Mon Jul 13 19:38:47 2009 (4A5BC587)[/B]
[B]driversLrdprefmp.sys        Mon Jul 13 20:16:35 2009 (4A5BCE63)[/B]
driversLHTTP.sys            Sat Nov 20 04:24:30 2010 (4CE793CE)
System32Lcdd.dll            Sat Nov 20 07:55:34 2010 (4CE7C546)
driversLUSBD.SYS            Thu Mar 24 23:28:59 2011 (4D8C0BFB)
SACDIFSV64.SYS              Thu Jul 21 19:03:00 2011 (4E28B024)
driversLafd.sys             Tue Dec 27 22:59:20 2011 (4EFA9418)
[/font]

Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
System32LdriversLvga.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
driversLrdprefmp.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
driversLHTTP.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
System32Lcdd.dll - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
driversLUSBD.SYS - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
SACDIFSV64.SYS - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
driversLafd.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

 

[jonesx]

Thnx for the advice.
Now, I think I updated the first driver from your red list (how/where can i see the new driver status, date?).

I tried googling the other 2, but i couldn't find any results. How do i find the program they are related to?

 

[jonesx]

Seems the problem isn't solved. Just had another BSOD (see minidumpfile attached).
Things are getting serious, windows failed a few times starting up..

Link Removed

 

[usasma]

It's looking like hardware to me.
Follow the instructions about memory below.
Then, if it still BSOD's, try these free, bootable diagnostics: Link Removed - Invalid URL
If they pass, then try these: Link Removed

FWIW - I've seen a lot of issues with the Asus P5 series of boards. I usually recommend this:
- DO NOT use the AUTO setting for memory. Go to the RAM manufacturer's website and get the recommended settings for the RAM. Then set those settings manually in the BIOS
- one person with a 2009 BIOS has experienced success by updating the BIOS. This is dangerous and one simple mistake can easily damage your motherboard so it won't work. Be VERY, VERY CAREFUL!!!
- one person reports bad caps ( Link Removed due to 404 Error ) in this post: [SOLVED] Bad overclock and now can't load windows 7 - Tech Support Forum

As of late June 2012 - I haven't seen many issues with these boards over the last several months.

Analysis:
The following is for informational purposes only.

[FONT=lucida console]**************************Sat Nov  3 18:34:52.299 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\110412-14976-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 3:55:56.297[/B]
BugCheck Code: [B]BugCheck 1, {49f001af, 0, 1, fffff880046e2ca0}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )[/B]
BugCheck Info: [B]APC_INDEX_MISMATCH (1)[/B]
Arguments: 
Arg1: 0000000049f001af, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 0000000000000001, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffff880046e2ca0, Call type (0 - system call, 1 - worker routine)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1
PROCESS_NAME: [B]csrss.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x1_SysCallNum_82_nt!KiSystemServiceExit+245[/B]
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: [B]2405[/B]
  BIOS Version                  0604   
  BIOS Release Date             07/16/2008
  Manufacturer                  System manufacturer
  Product Name                  P5E-VM HDMI
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[FONT=lucida console]**************************Sat Nov  3 18:34:52.299 2012 (UTC - 5:00)**************************
ASACPI.sys                  Wed May 13 21:25:17 2009 (4A0B72FD)
GEARAspiWDM.sys             Mon May 18 08:17:04 2009 (4A1151C0)
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
l160x64.sys                 Mon Oct 12 22:08:28 2009 (4AD3E11C)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
tcpiprew.sys                Sat Nov 20 05:51:48 2010 (4CE7A844)
atikmpag.sys                Tue Apr 19 21:22:32 2011 (4DAE3558)
atikmdag.sys                Tue Apr 19 21:53:29 2011 (4DAE3C99)
SASKUTIL64.SYS              Tue Jul 12 17:00:01 2011 (4E1CB5D1)
SASDIFSV64.SYS              Thu Jul 21 19:03:00 2011 (4E28B024)
aswrdr2.sys                 Mon Oct  8 04:23:43 2012 (50728D8F)
aswFsBlk.SYS                Tue Oct 30 18:43:04 2012 (509057F8)
aswMonFlt.sys               Tue Oct 30 18:43:09 2012 (509057FD)
aswTdi.SYS                  Tue Oct 30 18:43:16 2012 (50905804)
aswSP.SYS                   Tue Oct 30 18:44:06 2012 (50905836)
DriversLaswSnx.SYS          Tue Oct 30 18:44:08 2012 (50905838)
[/FONT]

Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
Link Removed
tcpiprew.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed
DriversLaswSnx.SYS - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

 

[jonesx]

Bad news:

I had 2 new BSOD during my next start up (I wanted to start the init diag tests..).
Now my pc won't start the OS anymore (my pc runs but the screen remains black).

HELP!

 

[usasma]

The initdiag tests are bootable. This means that you don't need Windows to run them.
Make the CD's for the tests on another computer - and boot from them on your system.

If you can't even see the Asus screen when the system boots up, then the problem is more severe than that. Please post back if that's the case and we'll see what else we can suggest.

 

[jonesx]

If you can't even see the Asus screen when the system boots up, then the problem is more severe than that. Please post back if that's the case and we'll see what else we can suggest.

Nothing appears on the screen..
I wanted to change my boot seq (hd -> usb) but i even didn't get the chance (the memory test is on my usb).

I also opened up my pc, but I couldn't see any clear (visual) problems. I removed my 4 RAM plates and re-installed them back because nothing strange was seen.

I really hope this problem can be solved. I bought this pc second handed in may this year. The BSOD issues began in august. So the seller didn't sell me a corrupted pc, right?

 

[usasma]

I don't know enough about the situation to tell. IMO this is most likely a failure of the graphics sub-system - although that's just a guess now because we can't run any further tests. I can't tell if it was having problems when you bought it or not.

That being said, the next thing to try is another graphics card. If you don't have a spare one laying around, you can purchase one from a store that will allow returns (and will refund your money) if the part isn't needed.

Be sure to use anti-static precautions when messing around inside of the case. Unplug the system from the wall and, at a minimum, hold onto the metal of the case while messing around inside of it!

Good luck!

 

[jonesx]

I don't understand why you are suggesting the graphicscard now..
I m using my old (self-build) pc right now. So I think I can handle the hardwaresteps.
This one got a graph card (nvidia geforce 6600 GT PCI version).

So how do I start? Do I still need to follow the steps you mentioned one post earlier (making booting disk)?
Even I have a bootable DVD, how can I acces my BIOS (black screen) to change the boot seq?

Or do I just remove the current graph card by the Geforce version and try starting up?


PS: how do I prevent damaging/losing the data on my HD?

 

[usasma]

If you can't see anything, but the system seems to run - it's most likely a graphics card problem.
Even if that's not correct - it's the first place to start troublehshooting.

If you can't see anything on the screen, then the booting disks won't do you any good. You have to be able to see the screen in order to run the tests.

Using appropriate anti-static precautions, you remove the current video card and replace it with one that's known to be good.
If you don't have one that's known to be good, you purchase on (and presume that it's good). You purchase it from a store that will allow returns - so you can get your money back if it doesn't fix the problem.

You prevent data loss/damage to your hard drive by following anti-static precautions.
Leave the hard drive alone and don't touch it.

 

[jonesx]

I vent got the time to try this yet.
More updates/news tonight,
positive i hope.

 

[jonesx]

No good news:
I tried my old graph card, which fits, but i still don't get any signal - no image it seems..

HELP

 

[usasma]

If you can't see anything at all, then it's most likely a mobo problem (this presumes that the other video card is good).
To verify, place the old video card in another system to see if it works.

Remove as much as you can from the motherboard to see if it'll let you see if there's any video.

 

[jonesx]

As I am using my old computer with the old graph still functioning, I assume the cards themselves are not causing the problem. I hope its not the PCI slot itself..

What do you suggest removing from the MOBO?
I read on another website that corrupted RAM also can cause the black screen/no booting issue.
I ll start removing some RAM (6Gb -> 4 sticks). Win 7 demands 2 Gb RAM, so I ll keep that in mind.
Any suggestions on this testingprocedure (1 out, 2 out, 3 out..)?

 

[jonesx]

As planned, I removed one RAM stick.
Now the image is back and I got the message "overclock failed". Press F1 set up or F2 default settings.

I chose F1, changed the boot order (usb first) and saved. So next time I can do the memorytest from my usb.
Now Win is running and when I open Speccy, it says there only 2 memory slots used.. weird.. What does that mean?

So I don't know what to do next. Am I lucky -> removed the problem RAM?
Or shall I start copying files from HD in case of total crash?

 

[usasma]

I'm going to suggest that you post over in the Graphics forum for more expert assistance: Link Removed - Invalid URL

 

[jonesx]

I'm going to suggest that you post over in the Graphics forum for more expert assistance: Link Removed - Invalid URL

Why?
I don't think it is a graph problem.

 

[usasma]

Because I'm out of ideas as to what could be causing this. You can always try the Hardware forums: Link Removed - Invalid URL

 

[jonesx]

Ok,

but if I get more BSOD's (propably yes), I'll post them in this thread.