BSOD crashing my computer..

Hello everyone.. I keep having a BSOD occur and crash my work computer.. unfortunately the clinic I work at does not provide IT support so while I fiddle with this, my patients wait.. if anyone could suggest a cause based on the debug report I would greatly appreciate it. Here is the info I have..


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Alex\Desktop\091910-66253-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:/symbols*http://msdl.microsoft.com/download/symbols;sympath SRV*C:\localsymbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a4f000 PsLoadedModuleList = 0xfffff800`02c8ce50
Debug session time: Sun Sep 19 18:36:03.152 2010 (UTC - 4:00)
System Uptime: 0 days 0:07:05.009
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, 5b6c001, 2c87, 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: 0000000005b6c001
Arg3: 0000000000002c87
Arg4: fffff70001080000

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


BUGCHECK_STR: 0x1a_41284

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: dllhost.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002b143b3 to fffff80002abf740

STACK_TEXT:
fffff880`08672218 fffff800`02b143b3 : 00000000`0000001a 00000000`00041284 00000000`05b6c001 00000000`00002c87 : nt!KeBugCheckEx
fffff880`08672220 fffff800`02af2379 : fffffa80`03d8eec8 ffffffff`ffffffff fffffa80`06425060 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x4a83
fffff880`08672260 fffff800`02b05b2b : c8700000`c66fa867 fffff680`0002db60 ffffffff`ffffffff 000fffff`ffffffff : nt!MiTerminateWsle+0x29
fffff880`086722a0 fffff800`02b00dee : 00000000`00000002 fffff880`00000000 fffffa80`03d8eb30 fffffa80`03d8eec8 : nt!MiDecommitPages+0x20b
fffff880`08672b30 fffff800`02abe993 : ffffffff`ffffffff 00000000`01dbdf18 00000000`01dbdf10 00000000`00000001 : nt!NtFreeVirtualMemory+0x2de
fffff880`08672c20 00000000`77cbff3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01dbde68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77cbff3a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4a83
fffff800`02b143b3 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
---------

0: kd> lmvm nt
start end module name
fffff800`02a4f000 fffff800`0302b000 nt (pdb symbols) c:\symbols\ntkrnlmp.pdb\30092BE745B24FE2A311A936E7B7486F2\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: c:\symbols\ntoskrnl.exe\4C1C44A95dc000\ntoskrnl.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Timestamp: Sat Jun 19 00:16:41 2010 (4C1C44A9)
CheckSum: 005489D7
ImageSize: 005DC000
File version: 6.1.7600.16617
Product version: 6.1.7600.16617
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrnlmp.exe
OriginalFilename: ntkrnlmp.exe
ProductVersion: 6.1.7600.16617
FileVersion: 6.1.7600.16617 (win7_gdr.100618-1621)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.


I have Windows 7 Ultimate 64-bit.. my specs are as follows:

P5GC-MX/1333 Motherboard
1333Mhz FSB, 6 USB ports, Gigabit lan, onboard 256Mb VGA. 4 sata 2 connections, 1 IDE connection, 1 Floppy connection

Intel E5200 CPU
2.5Ghz x 2, 800Mhz FSB, 2MB Cache

Kingston 4Gb Ram
2Gb x 2, 800Mhz

Western Digital 500Gb Hard drive
Sata 2, 3.5"

LG Optical Drive
CD-RW / DVD-RW

Sound Blaster Xtreme Music
7.1 channel, with SPDIF

nVidia GeForce 8400GS
512MB Video Ram, DVI, S-Video, VGA PCI-E 16X

Thank you again for any assistance you can provide.

Please see attached dump file. Thank you for your interest.

Hi,

1 BSOD minidump - blaming ntkrnlmp.exe (the NT Kernel) as a cause. This is unlikely to be the true cause.

Possible causes -

Code:

ASACPI.sys   Mon Mar 28 15:30:36 2005 (42476C4C)
SCDEmu.SYS   Fri Jun 13 09:38:37 2008 (4851975D)

ASACPI.sys - ASUS ACPI Driver; near guaranteed to cause BSODs on Windows 7 systems. Update link here, update instructions (slideshow) here (note that in the last step you select the ATK0110 driver in the list instead of the one mentioned)

SCDEmu.SYS - PowerISO driver. Uninstall PowerISO for now.

If problems continue after dealing with those 2 drivers, run Driver Verifier - Driver Verifier - Enable and Disable

Regards,
Reventon

BUGCHECK SUMMARY

Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 20 10:36:03.152 2010 (GMT+12)
System Uptime: 0 days 0:07:05.009
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dllhost.exe
Bugcheck code 0000001A
Arguments 00000000`00041284 00000000`05b6c001 00000000`00002c87 fffff700`01080000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Thank you for your input reventon. I have updated the ACPI driver and installed PowerISO but am still experiencing the BSOD. I am enabled driver verifier and rebooted.. I don't see if running anywhere.. I assume I will be notified if one of my drivers is determined to be unstable?

Should I be investigating the possibilities of bad memory, overheating, insufficient wattage from PSU, ect.... or is it pretty clear that this is a driver issue?

Thank you again for your assistance.

If Driver Verifier does not pick anything up - then it's a Hardware problem.

So, while I wouldn't go swapping parts out yet (at least until you see if DV causes any BSODs) you can run some hardware tests to try to find a hardware fault.

https://www.sevenforums.com/tutorials...t-prime95.html (run the Blend test as well as the Small FFT test)

RAM - Test with Memtest86+

Video Card - Stress Test with Furmark