Billions of BSOD's My sorry story

AlexHaden · 17 Oct 2010

Hi All,

Just to put my experience into context, I have been building PC's for years and years, since the heady days of my first ever 486dx and buying 4mb ram!

Anyway, i have either been very lucky with my builds, as i have never had any problem, until i come to build a stable "homework/gaming" pc for the offspring.

I purchased an Over clocked bundle from Scan Computers which basically consists of

Intel Core i5 760 - Quad Core CPU
4Gb Corsair Dominator 1600Mhz
Asus P7P55D-E
Akasa Venom Performance Cooler

All professionally overclocked to 4.0GHZ. Got the bundle, installed it and was hit with probably the most BSOD's i have ever seen in my entirfe life

I had multiple of the following:-
PAGE_FAULT_IN_NONPAGED_AREA
KMODE_EXCEPTION_NOT_HANDLED
SYSTEM_SERVICE_EXCEPTION
MEMORY_MANAGEMENT
IRQL_NOT_LESS_OR_EQUAL

Temps under load seemed on the high side with CPU getting to 70, and the mobo getting to 60, so i thought that its probably an unstable overclock and dropped to stock speeds. Again, i had multiple BSOD's.

Temps at stock were fine at 33 for CPU and never more than 40 for the Mobo.

Out came my Trusty Memcheck CD and i ran that for ages and it came up with around 20 errors. So the first thing i did was remove, clean the contacts and reseat the Ram.

Now memcheck passess all tests, can run for days without a problem.

So thought, 100's of BSOD's and crashes, time for a full, clean install.

Did that - everything seemed to be fine, installed and offspring was playing LFD2 and Settlers 7 for ages without a problem.

Today - back to BSOD city.

Just today, all in the space of a 30 mins, i have had
PFN_LIST_CORRUPT
IRQL_NOT_LESS_OR_EQUAL
MEMORY_MANAGEMENT
PAGE_FAULT_IN_NONPAGED_AREA

So after some searching around i found a possible driver issue with ATK0110 being out of date, i have installed that, but still get BSOD's

I have updated all of the drivers, (that i can see need doing) - and made sure that i have the latest MOBO Bios.

Its driving me mad that seems stable for ages, and then i get multiple BSOD's. Just cannot figure it out. Before i do the last thing and RMA the bundle, can anyone offer any help by revewing the minidumps for me, and see if there is anything im missing, or if you really consider it to be a hardware issue rather than a driver?

Thanks

AlexHaden · 17 Oct 2010

Me again,

Just running driver Verifyer and the PC seems to be "stuck" at the windows logo.....is that normal? I guess i'll leave it for a short while and see what happens.....

AlexHaden · 17 Oct 2010

Hi All,

Still in trouble shooting mode

Ok then, Driver Verifier crashed the Pc, and windows 7 wouldnt boot untuil i did a system restore.

Once thats been done, windows booted up and came up with a "windows has detected a critical error" and rebooted itself.

Then it had managed to drop the drivers for my Nvidia gtx260......

Ack, im never going to build again!

CarlTR6 · 17 Oct 2010

Alex, welcome to the forum. I am sorry you are having problems. Please read this tutorial, follow the instructions, and upload the files. We need to take a look at your system along with the dumps.

https://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

AlexHaden · 17 Oct 2010

Hiya,

Apologies for not reading the posting instructions, im so stressed with this thing, im ready to throw it away and buy a PC from PC World or Best Buy!

Anyway - Attached is file

CarlTR6 · 17 Oct 2010

Thanks much. Good job. I looked at your five most recent dumps. All of them indicate memory problems/memory corruption.

[quote]
Error code A, IRQL_NOT_LESS_OR_EQUAL (2X). Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.

Error code 50, PAGE_FAULT_IN_NONPAGED_AREA. Defective hardware (particularly memory - Usual causes: but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

Error code 1A, MEMORY_MANAGEMENT. Usual causes: Device driver, memory, kernel.

Error code 4E, PFN_LIST_CORRUPT. Usual causes: Device driver, ?memory.

Code:

Kernel base = 0xfffff800`02a01000 PsLoadedModuleList = 0xfffff800`02c3ee50
Debug session time: Sun Oct 17 08:44:58.569 2010 (GMT-4)
System Uptime: 0 days 0:07:02.006
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff68000130188, 0, 0, fffff80002a852e2}

Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1c2 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff68000130188, memory referenced
Arg2: 0000000000000000, IRQL
Arg3: 0000000000000000, 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: fffff80002a852e2, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ca90e0
 fffff68000130188 

CURRENT_IRQL:  0

FAULTING_IP: 
nt!MiAgeWorkingSet+1c2
fffff800`02a852e2 488b19          mov     rbx,qword ptr [rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  explorer.exe

TRAP_FRAME:  fffff880033167a0 -- (.trap 0xfffff880033167a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000007ffffffff8 rbx=0000000000000000 rcx=fffff68000130188
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a852e2 rsp=fffff88003316930 rbp=000000000013018e
 r8=0000000000000001  r9=fffffa8007cc1ec8 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!MiAgeWorkingSet+0x1c2:
fffff800`02a852e2 488b19          mov     rbx,qword ptr [rcx] ds:fffff680`00130188=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a70ca9 to fffff80002a71740

STACK_TEXT:  
fffff880`03316658 fffff800`02a70ca9 : 00000000`0000000a fffff680`00130188 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`03316660 fffff800`02a6f920 : 00000000`00000000 00000980`00000000 00000000`00040000 00000000`0000000b : nt!KiBugCheckDispatch+0x69
fffff880`033167a0 fffff800`02a852e2 : 00000003`00000000 2b300000`a152f867 00000000`00000000 00000000`00001ab3 : nt!KiPageFault+0x260
fffff880`03316930 fffff800`02af3a5e : fffffa80`07cc1ec8 fffff880`00000001 00000000`00000001 fffff880`03316bb0 : nt!MiAgeWorkingSet+0x1c2
fffff880`03316ae0 fffff800`02a85ee2 : 00000000`000001a7 00000000`00000000 fffffa80`00000000 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x496d6
fffff880`03316b80 fffff800`02a86173 : 00000000`00000008 fffff880`03316c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03316bd0 fffff800`02d15c06 : fffffa80`03702680 00000000`00000080 fffffa80`036d8040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03316d40 fffff800`02a4fc26 : fffff880`02f63180 fffffa80`03702680 fffff880`02f6dfc0 98fc18fc`17da15db : nt!PspSystemThreadStartup+0x5a
fffff880`03316d80 00000000`00000000 : fffff880`03317000 fffff880`03311000 fffff880`03316710 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiAgeWorkingSet+1c2
fffff800`02a852e2 488b19          mov     rbx,qword ptr [rcx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiAgeWorkingSet+1c2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiAgeWorkingSet+1c2

BUCKET_ID:  X64_0xA_nt!MiAgeWorkingSet+1c2

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

Kernel base = 0xfffff800`02a5f000 PsLoadedModuleList = 0xfffff800`02c9ce50
Debug session time: Sun Oct 17 08:34:29.915 2010 (GMT-4)
System Uptime: 0 days 0:53:08.779
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a02f8fe420, 0, fffff80002c02f8c, 2}

Unable to load image \SystemRoot\System32\Drivers\N360x64\0403000.005\SRTSP64.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SRTSP64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS

Could not read faulting driver name
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )

Followup: Pool_corruption
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a02f8fe420, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002c02f8c, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d070e0
 fffff8a02f8fe420 

FAULTING_IP: 
nt!ExDeferredFreePool+100
fffff800`02c02f8c 4c8b02          mov     r8,qword ptr [rdx]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  mcbuilder.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88006634ef0 -- (.trap 0xfffff88006634ef0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800365fb10 rbx=0000000000000000 rcx=fffffa800365fb10
rdx=fffff8a02f8fe420 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c02f8c rsp=fffff88006635080 rbp=0000000000000000
 r8=fffff8a02f8fe420  r9=0000000000000000 r10=fffff8a00b571850
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!ExDeferredFreePool+0x100:
fffff800`02c02f8c 4c8b02          mov     r8,qword ptr [rdx] ds:07ff:fffff8a0`2f8fe420=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b4e8f2 to fffff80002acf740

STACK_TEXT:  
fffff880`06634d88 fffff800`02b4e8f2 : 00000000`00000050 fffff8a0`2f8fe420 00000000`00000000 fffff880`06634ef0 : nt!KeBugCheckEx
fffff880`06634d90 fffff800`02acd82e : 00000000`00000000 00000000`00000004 fffff880`01150000 fffff880`011451b1 : nt! ?? ::FNODOBFM::`string'+0x40ec0
fffff880`06634ef0 fffff800`02c02f8c : 00000000`00000000 fffff880`06635150 00000000`74414153 fffff880`0116ec41 : nt!KiPageFault+0x16e
fffff880`06635080 fffff800`02c044c1 : fffff8a0`0b79dcc0 fffff8a0`089923f0 fffff8a0`0778ccc0 fffff8a0`00000000 : nt!ExDeferredFreePool+0x100
fffff880`06635110 fffff880`058ff121 : 00000000`00000000 fffff8a0`01665628 00000000`65456153 00000000`00000002 : nt!ExFreePoolWithTag+0x411
fffff880`066351c0 00000000`00000000 : fffff8a0`01665628 00000000`65456153 00000000`00000002 fffff8a0`01665628 : SRTSP64+0x4f121


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+100
fffff800`02c02f8c 4c8b02          mov     r8,qword ptr [rdx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!ExDeferredFreePool+100

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!ExDeferredFreePool+100

BUCKET_ID:  X64_0x50_nt!ExDeferredFreePool+100

Followup: Pool_corruption
---------

Kernel base = 0xfffff800`02a1c000 PsLoadedModuleList = 0xfffff800`02c59e50
Debug session time: Sun Oct 17 08:36:38.889 2010 (GMT-4)
System Uptime: 0 days 0:00:50.325
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, 42df001, 14d7, fffff70001080000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 00000000042df001
Arg3: 00000000000014d7
Arg4: fffff70001080000

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_41284

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ae13b3 to fffff80002a8c740

STACK_TEXT:  
fffff880`067a3218 fffff800`02ae13b3 : 00000000`0000001a 00000000`00041284 00000000`042df001 00000000`000014d7 : nt!KeBugCheckEx
fffff880`067a3220 fffff800`02abf379 : fffffa80`07aa0ec8 ffffffff`ffffffff fffffa80`07fd5060 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x4a83
fffff880`067a3260 fffff800`02ad2b2b : cd700000`9f6c7867 fffff680`000216f8 ffffffff`ffffffff 000fffff`ffffffff : nt!MiTerminateWsle+0x29
fffff880`067a32a0 fffff800`02acddee : 00000000`00000002 fffff880`00000000 fffffa80`07aa0b30 fffffa80`07aa0ec8 : nt!MiDecommitPages+0x20b
fffff880`067a3b30 fffff800`02a8b993 : ffffffff`ffffffff 00000000`02d6bfe8 00000000`02d6bfe0 00000000`00000001 : nt!NtFreeVirtualMemory+0x2de
fffff880`067a3c20 00000000`76ddff3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02d6bf38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ddff3a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4a83
fffff800`02ae13b3 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4a83

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4a83

BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4a83

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

Kernel base = 0xfffff800`02a61000 PsLoadedModuleList = 0xfffff800`02c9ee50
Debug session time: Sun Oct 17 09:25:29.030 2010 (GMT-4)
System Uptime: 0 days 0:10:09.467
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, b129e, 0, b131e}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000000b129e, page frame number
Arg3: 0000000000000000, current page state
Arg4: 00000000000b131e, 0

Debugging Details:
------------------


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002b6138c to fffff80002ad1740

STACK_TEXT:  
fffff880`085c2f98 fffff800`02b6138c : 00000000`0000004e 00000000`00000099 00000000`000b129e 00000000`00000000 : nt!KeBugCheckEx
fffff880`085c2fa0 fffff800`02b439f7 : 00000000`00000000 fffff680`0003fb48 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`085c2fe0 fffff800`02aa5c23 : fffffa80`07feeb30 fffff700`00002fd7 0000007f`fffffff8 fffff8a0`0101bcd8 : nt! ?? ::FNODOBFM::`string'+0x3223e
fffff880`085c3070 fffff800`02aa468a : fffffa80`07feeb30 fffffa80`00000000 fffff8a0`00001083 fffff880`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`085c3920 fffff800`02db6dcf : fffff8a0`01c0da90 fffff880`085c3c20 00000000`00000000 fffffa80`080fd950 : nt!MmCleanProcessAddressSpace+0x96
fffff880`085c3970 fffff800`02d8f635 : 00000000`000000ff 00000000`00000001 000007ff`fff9e000 fffffa80`0859b7a0 : nt!PspExitThread+0x92f
fffff880`085c3a30 fffff800`02aae1db : 00000000`085c3ca0 fffffa80`0804d770 00000000`00000000 00000000`00000000 : nt!PsExitSpecialApc+0x1d
fffff880`085c3a60 fffff800`02aae620 : 00000000`77734298 fffff880`085c3ae0 fffff800`02d8f74c 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`085c3ae0 fffff800`02ad0a37 : fffffa80`080fd950 00000000`77734270 fffff880`000000c0 00000000`00000000 : nt!KiInitiateUserApc+0x70
fffff880`085c3c20 00000000`7768165a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`0762f4b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7768165a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02b6138c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

2: kd> lmtsmn
start             end                 module name
fffff880`00f96000 fffff880`00fed000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02d5a000 fffff880`02de4000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`10b82000 fffff880`10b98000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`01e13000 fffff880`01e1ff00   Alpham164 Alpham164.sys Mon Jul 23 03:57:03 2007 (46A45F4F)
fffff880`01e20000 fffff880`01e25500   Alpham264 Alpham264.sys Tue Mar 20 05:51:03 2007 (45FFAE87)
fffff880`01078000 fffff880`01083000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`045ea000 fffff880`045f2000   ASACPI   ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)
fffff880`043b5000 fffff880`043bb000   AsIO     AsIO.sys     Mon Aug 03 03:03:16 2009 (4A768BB4)
fffff880`043af000 fffff880`043b5000   AsUpIO   AsUpIO.sys   Sun Jul 05 22:21:38 2009 (4A515FB2)
fffff880`08620000 fffff880`0862b000   asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5)
fffff880`00c1a000 fffff880`00c23000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00c23000 fffff880`00c4d000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff960`00870000 fffff960`008d1000   ATMFD    ATMFD.DLL    Thu May 27 00:11:31 2010 (4BFDF0F3)
fffff880`014b6000 fffff880`014bd000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`042c2000 fffff880`043af000   BHDrvx64 BHDrvx64.sys Fri Aug 27 18:11:09 2010 (4C7837FD)
fffff880`041a4000 fffff880`041b5000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`059b9000 fffff880`059d7000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff880`04108000 fffff880`041a4000   ccHPx64  ccHPx64.sys  Fri Feb 05 16:05:45 2010 (4B6C8829)
fffff960`00730000 fffff960`00757000   cdd      cdd.dll      Wed May 19 15:48:26 2010 (4BF4408A)
fffff880`01fbe000 fffff880`01fdb000   cdfs     cdfs.sys     Mon Jul 13 19:19:46 2009 (4A5BC112)
fffff880`01200000 fffff880`0122a000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00ed6000 fffff880`00f96000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01450000 fffff880`01480000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00ce6000 fffff880`00d44000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`014d2000 fffff880`01545000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`04400000 fffff880`04410000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`01fdb000 fffff880`01fe9000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`041e3000 fffff880`041f5000   dc3d     dc3d.sys     Thu Jul 01 06:07:45 2010 (4C2C68F1)
fffff880`040ea000 fffff880`04108000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`040db000 fffff880`040ea000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`0143a000 fffff880`01450000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`04299000 fffff880`042bb000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`01ff5000 fffff880`01ffe000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01fe9000 fffff880`01ff5000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01e00000 fffff880`01e13000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`04de7000 fffff880`04df3000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`04416000 fffff880`0450a000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`0450a000 fffff880`04550000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`03f7d000 fffff880`03ff3000   eeCtrl64 eeCtrl64.sys Fri May 21 17:44:45 2010 (4BF6FECD)
fffff880`08600000 fffff880`08620000   ENG64    ENG64.SYS    Wed Sep 15 06:25:35 2010 (4C909F1F)
fffff880`040b6000 fffff880`040db000   EraserUtilRebootDrv EraserUtilRebootDrv.sys Fri May 21 17:44:45 2010 (4BF6FECD)
fffff880`08639000 fffff880`087f7000   EX64     EX64.SYS     Wed Sep 15 06:33:41 2010 (4C90A105)
fffff880`0113d000 fffff880`01151000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01083000 fffff880`010cf000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`01556000 fffff880`01560000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01400000 fffff880`0143a000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`017a9000 fffff880`017f3000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`045dd000 fffff880`045ea000   GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
fffff800`02a18000 fffff800`02a61000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`045b7000 fffff880`045db000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`0400e000 fffff880`04027000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`10bf7000 fffff880`10bff080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`04000000 fffff880`0400e000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`058f1000 fffff880`059b9000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`01619000 fffff880`01622000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`03f02000 fffff880`03f7d000   IDSvia64 IDSvia64.sys Fri Sep 10 17:54:50 2010 (4C8AA92A)
fffff880`043e1000 fffff880`043f7000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`03e5f000 fffff880`03e86000   Ironx64  Ironx64.SYS  Tue Apr 27 20:48:23 2010 (4BD785D7)
fffff880`00c4d000 fffff880`00c6b000   jraid    jraid.sys    Thu Aug 13 04:10:27 2009 (4A83CA73)
fffff880`0fe56000 fffff880`0fe65000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`04027000 fffff880`04035000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00bc4000 fffff800`00bce000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`0fe74000 fffff880`0feb7000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`013d3000 fffff880`013ed000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`0177e000 fffff880`017a9000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`04de1000 fffff880`04de6200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`01e57000 fffff880`01e6c000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`01e34000 fffff880`01e57000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00c8e000 fffff880`00cd2000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`01e26000 fffff880`01e34000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`0fe65000 fffff880`0fe74000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`04035000 fffff880`04042000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00c00000 fffff880`00c1a000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`05800000 fffff880`0582d000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`0582d000 fffff880`0587b000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`0587b000 fffff880`0589e000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`01025000 fffff880`01030000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00ff6000 fffff880`01000000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`0118c000 fffff880`011ea000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`03ef7000 fffff880`03f02000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`01607000 fffff880`01619000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`0162c000 fffff880`0171e000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`10bbc000 fffff880`10bc8000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`01ebf000 fffff880`01ed2000   ndisuio  ndisuio.sys  Mon Jul 13 20:09:25 2009 (4A5BCCB5)
fffff880`10bc8000 fffff880`10bf7000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`04284000 fffff880`04299000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`02c8a000 fffff880`02c99000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02c00000 fffff880`02c45000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`0171e000 fffff880`0177e000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`01ed5000 fffff880`01fb1000   netr28ux netr28ux.sys Wed Feb 25 21:49:17 2009 (49A6032D)
fffff880`01030000 fffff880`01041000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`03eeb000 fffff880`03ef7000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02a61000 fffff800`0303d000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`01230000 fffff880`013d3000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`014ad000 fffff880`014b6000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`0426c000 fffff880`04284000   nusb3hub nusb3hub.sys Thu Jan 21 22:22:18 2010 (4B5919EA)
fffff880`10b52000 fffff880`10b82000   nusb3xhc nusb3xhc.sys Thu Jan 21 22:22:21 2010 (4B5919ED)
fffff880`10b50000 fffff880`10b51180   nvBridge nvBridge.kmd Fri Jul 09 17:07:54 2010 (4C378FAA)
fffff880`0febe000 fffff880`10b4fe00   nvlddmkm nvlddmkm.sys Fri Jul 09 17:15:58 2010 (4C37918E)
fffff880`01e6c000 fffff880`01ebf000   nwifi    nwifi.sys    Mon Jul 13 20:07:23 2009 (4A5BCC3B)
fffff880`02c4e000 fffff880`02c74000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`00ec0000 fffff880`00ed5000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00d44000 fffff880`00d77000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00de8000 fffff880`00def000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00def000 fffff880`00dff000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`01545000 fffff880`01556000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`05e15000 fffff880`05ebb000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`04042000 fffff880`04052000   point64  point64.sys  Tue Jun 29 04:54:31 2010 (4C29B4C7)
fffff880`04c00000 fffff880`04c3d000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00cd2000 fffff880`00ce6000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`10b98000 fffff880`10bbc000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0fe00000 fffff880`0fe1b000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`0fe1b000 fffff880`0fe3c000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`0fe3c000 fffff880`0fe56000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`03e9a000 fffff880`03eeb000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`015f6000 fffff880`015ff000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`013ed000 fffff880`013f6000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`013f6000 fffff880`013ff000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`015ac000 fffff880`015e6000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`04052000 fffff880`0406a000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`01049000 fffff880`01078000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`05ebb000 fffff880`05ec6000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`045f2000 fffff880`045fe000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`03e13000 fffff880`03e30000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`01600000 fffff880`01607000   speedfan speedfan.sys Sun Sep 24 09:26:48 2006 (45168798)
fffff880`017f3000 fffff880`017fb000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`06116000 fffff880`0619c000   SRTSP64  SRTSP64.SYS  Wed Feb 24 18:59:29 2010 (4B85BD61)
fffff880`03e86000 fffff880`03e9a000   SRTSPX64 SRTSPX64.SYS Wed Feb 24 18:59:48 2010 (4B85BD74)
fffff880`06080000 fffff880`06116000   srv      srv.sys      Thu Aug 26 23:38:00 2010 (4C773318)
fffff880`05f05000 fffff880`05f6c000   srv2     srv2.sys     Thu Aug 26 23:37:46 2010 (4C77330A)
fffff880`05ec6000 fffff880`05ef3000   srvnet   srvnet.sys   Thu Aug 26 23:37:24 2010 (4C7732F4)
fffff880`04410000 fffff880`04411480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`010cf000 fffff880`0113d000   SYMDS64  SYMDS64.SYS  Mon Aug 17 19:35:30 2009 (4A89E942)
fffff880`01151000 fffff880`0118c000   SYMEFA64 SYMEFA64.SYS Wed Apr 21 17:47:39 2010 (4BCF727B)
fffff880`02d24000 fffff880`02d5a000   SYMEVENT64x86 SYMEVENT64x86.SYS Wed Apr 28 04:24:20 2010 (4BD7F0B4)
fffff880`02cae000 fffff880`02d24000   SYMTDIV  SYMTDIV.SYS  Tue May 04 00:38:27 2010 (4BDFA4C3)
fffff880`01802000 fffff880`019ff000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`05ef3000 fffff880`05f05000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`011ea000 fffff880`011f7000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`00c6b000 fffff880`00c89000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`03e4b000 fffff880`03e5f000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00510000 fffff960`0051a000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`043bb000 fffff880`043e1000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`04200000 fffff880`04212000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`041b5000 fffff880`041d2000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`045db000 fffff880`045dcf00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`04550000 fffff880`04561000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`04212000 fffff880`0426c000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`04561000 fffff880`045b7000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`04df3000 fffff880`04dff000   usbprint usbprint.sys Mon Jul 13 20:38:18 2009 (4A5BD37A)
fffff880`041d2000 fffff880`041e3000   usbscan  usbscan.sys  Mon Jul 13 20:35:32 2009 (4A5BD2D4)
fffff880`00eb3000 fffff880`00ec0000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`014bd000 fffff880`014cb000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`04c42000 fffff880`04de1000   viahduaa viahduaa.sys Thu Sep 17 07:04:15 2009 (4AB217AF)
fffff880`01000000 fffff880`01025000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`00d77000 fffff880`00d8c000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00d8c000 fffff880`00de8000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01560000 fffff880`015ac000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`01fb1000 fffff880`01fbe000   vwifibus vwifibus.sys Mon Jul 13 20:07:21 2009 (4A5BCC39)
fffff880`02c74000 fffff880`02c8a000   vwififlt vwififlt.sys Mon Jul 13 20:07:22 2009 (4A5BCC3A)
fffff880`03e30000 fffff880`03e4b000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`015e6000 fffff880`015f6000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00e00000 fffff880`00ea4000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00ea4000 fffff880`00eb3000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02c45000 fffff880`02c4e000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`00020000 fffff960`0032f000   win32k   win32k.sys   Tue Aug 31 22:58:04 2010 (4C7DC13C)
fffff880`00fed000 fffff880`00ff6000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)

Unloaded modules:
fffff880`06000000 fffff880`06071000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01480000 fffff880`0148e000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0148e000 fffff880`0149a000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01622000 fffff880`0162b000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0149a000 fffff880`014ad000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

This driver is almost guaranteed to cause crashes:

ASACPI.sys Sun Mar 27 22:30:36 2005

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

Next, please uninstall all Norton/Symantec programs using this uninstall tool: Tool. Download and install Microsoft Security Essentials and make sure Windows Firewall is turned on. Norton is known to cause BSOD's on some Win 7 systems. Once you get your system stable, you can try Norton again; but I do not recommend it.

You have some other obsolete drivers on your system. Old drivers can and do cause memory corruption and crashes. Update these drivers.

Alpham164.sys Mon Jul 23 03:57:03 2007- Ideazon ZBoard http://www.steelseries.com/download. This is obsolete. If you cannot update the drivere, uninstall it.

Alpham264.sys Tue Mar 20 05:51:03 2007 - Ideazon ZBoard http://www.steelseries.com/download. See above.

AsUpIO.sys Sun Jul 05 22:21:38 2009 - AsUpIO.sys – Asus utility driver. ASUSTeK Computer Inc.-Support-

netr28ux.sys Wed Feb 25 21:49:17 2009 - Ralink RT2860 series Wireless LAN Card (you may have a different manufacturer)Ralink corp.

Uninstall Norton/Symantec and update your drivers. Reboot and lets see how your system does. If you get another BSOD, upload it. Let us know.

AlexHaden · 17 Oct 2010

Hi there,

Thanks very much for the analysis. I wish i could learn how to do that

I have just removed the ideazon drivers, and i'll remove norton tomorrow. Updated the ASACPI driver also.

Interestingly enough, the asus update program isnt there anymore, so is it safe to just remove the AsUpIO.sys driver manually from the drivers folder? i cannot see any other way to get rid.

Just been looking around some other forums, and there has been info about the p755d undervolting the memory. So i have checked that and in the bios it was set to auto and was reading at 1.5v. Corsair's website shows it should be 1.65v so i have upped that and am leaving memtest running all night to see if it shows any errors.

Tomorrow morning when i get up, i'll power on the pc and leave it running prime 95 all day to see how i go with any bsod's. I'll report back accordingly.

Do you think it could be a hardware issue, or is it more likley due to some software problem? Its only 5 weeks old, so i can RMA the kit if needs be. The weird thing is, that its an intermittent problem, so if it was hardware, you would think it would be happening all the time, which is leading me to think its a driver somewhere.

Yesterday the offspring was on it all day, today repeated BSOD's.....oh well, gives us all something to do on a sunday evening!

Anyway, thanks for the help

its much appreciated!

CarlTR6 · 17 Oct 2010

Alex, I think that driver is part of PCProbe. You might look for the latest update to PCProbe. Rather than delete the driver, try renaming it from .sys to .bak. This will break the program it is associated with.

It could be a RAM issue and that was my next step. I suspect the ASACPI driver was causing your crashes.

AlexHaden · 18 Oct 2010

Hia,

Just a morning update for you all

i know you all must be eager to see whats happened?

Last night memtest ran for 10+ hours without a single error.

Pc has been booted and running for the past 5 hours without a BSOD, its just idle at the moment, and im going to leave it running for the next few days to see what happens.

removed all of the old drivers, but left Norton/norton family on it for the time being as its for the offspring and i want to keep him safe from all us weirdo's on the internet. If it BSOD's again, i'll remove it and see what happens then.

By the way, have i said thank you very, very much?

CarlTR6 · 18 Oct 2010

You are very welcome, Alex; I am glad we were able to help. I hope your problems are behind you. Do let us know.

Regarding Norton. When troubleshooting, the idea is to remove any possible causes of BSOD's. Once your system is stable, you start adding things back. Norton does not cause problems on all Win 7 systems; but it definitely crashes some. There are valid reasons why this happens. It has to do with Win 7's new security levels. Microsoft Security Essentials and Windows Firewall will gave you the same adequate protection as does Norton/Symantec. Nothing out there gives 100% protection. Norton may run fine on your system and I hope it will. The suggestion to uninstall it was for troubleshooting purposes.