Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD, need help!

15 Nov 2010   #1
coparofl

Windows 7
 
 
Random BSOD, need help!

Hi

some backround info, we have a few machines in our company experiencing this exact same issue! so its absolutely critical that the issue is resolved.!

Windows 7
x86
Not orginal OS
Full Retail
ThinkCentre M55 8808-AA4
OS installed 2/7/10

I thought id post this before I start systematically going through updating everything and everything.

btw I already tried the fix of 'powercfg -h on'. I thought it worked, but this particular machine then decided to restart today,


My System SpecsSystem Spec
.
15 Nov 2010   #2
yowanvista

Windows 10 Pro x64, Arch Linux
 
 

SRTSP.SYS which is a component of Symantec/Norton antivirus is the cause of BSODs
Remove any Symantec/Norton product and use MSE or another antivirus


Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 96f534f3, 8a77b898, 0}

Probably caused by : SRTSP.SYS ( SRTSP+1c4f3 )

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

Followup: MachineOwner
My System SpecsSystem Spec
15 Nov 2010   #3
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by coparofl View Post
Please help!

Windows 7 randomly restarts with BSOD

x86
Not orginal OS
Full Retail
ThinkCentre M55 8808-AA4

Memory corruption caused by your Symantec remnants. PLUS really old drivers.

Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support


Old drivers needing update
Code:
PxHelp20.sys        0x83415de0    0x00004de0    8/2/2004 16:08:25            0x410ead49    0x83411000                              
psadd.sys        0x8e3eb380    0x00005380    2/19/2007 13:56:45            0x45d9f2ed    0x8e3e6000                
LHidFilt.Sys        0xa93be000    0x00007000    2/29/2008 05:08:08            0x47c7d988    0xa93b7000                
LMouFilt.Sys        0xa93d0600    0x00007600    2/29/2008 05:08:12            0x47c7d98c    0xa93c9000                
spldr.sys        0x88bf3000    0x00008000    5/11/2009 11:13:47            0x4a084ebb    0x88beb000                
GEARAspiWDM.sys        0x8e308280    0x00005280    5/18/2009 07:16:53            0x4a1151b5    0x8e303000                
amdxata.sys        0x835fe000    0x00009000    5/19/2009 12:57:35            0x4a12f30f    0x835f5000                
b57nd60x.sys        0x8e2d6000    0x00041000    5/28/2009 20:58:23            0x4a1f413f    0x8e295000                
SYMEVENT.SYS        0x8d9ec000    0x00025000    6/24/2009 15:14:58            0x4a428942    0x8d9c7000     

How To Find Drivers:
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads


.
My System SpecsSystem Spec
.

17 Nov 2010   #4
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Hi, coparofl. Sorry you are having problems. I looked at both of your dumps. Both are hardware/hardware related (drivers) errors. Your first dump directly blames SRTSP.SYS, a Norton/Symantec driver for the crash. I recommend that you completely uninstall Norton using this removal tool: Tool. Norton is a known cause of BSOD's on some Win 7 systems. Download and install Microsoft Security Essentials and make sure Windows Firewall is turned on.
Quote:
Error code 24, NTFS_FILE_SYSTEM. Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure.

Error Code A, IRQL_NOT_LESS_OR_EQUAL. Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.
Code:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82813000 PsLoadedModuleList = 0x8295b810
Debug session time: Sun Nov  7 22:15:52.279 2010 (GMT-5)
System Uptime: 0 days 6:50:20.678
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
........
1: kd> !Analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, c403f9d0, c403f5b0, 957270ae}

Probably caused by : SRTSP.SYS ( SRTSP+160ae )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 001904fb
Arg2: c403f9d0
Arg3: c403f5b0
Arg4: 957270ae

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


EXCEPTION_RECORD:  c403f9d0 -- (.exr 0xffffffffc403f9d0)
ExceptionAddress: 957270ae (SRTSP+0x000160ae)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 5aa55b89
Attempt to read from address 5aa55b89

CONTEXT:  c403f5b0 -- (.cxr 0xffffffffc403f5b0)
eax=00000001 ebx=00000000 ecx=5aa55aa5 edx=00000003 esi=853fffb0 edi=855650d0
eip=957270ae esp=c403fa98 ebp=c403fa9c iopl=0         nv up ei ng nz ac pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010297
SRTSP+0x160ae:
957270ae 8b81e4000000    mov     eax,dword ptr [ecx+0E4h] ds:0023:5aa55b89=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  5aa55b89

READ_ADDRESS: GetPointerFromAddress: unable to read from 8297b718
Unable to read MiSystemVaType memory at 8295b160
 5aa55b89 

FOLLOWUP_IP: 
SRTSP+160ae
957270ae 8b81e4000000    mov     eax,dword ptr [ecx+0E4h]

FAULTING_IP: 
SRTSP+160ae
957270ae 8b81e4000000    mov     eax,dword ptr [ecx+0E4h]

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from 8357c5f4 to 957270ae

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
c403fa9c 8357c5f4 853fffb0 00000008 b81445a4 SRTSP+0x160ae
c403fab8 8357c7c0 853fff80 853fff80 c403fadc fltmgr!DoFreeContext+0x66
c403fac8 8358d722 853fff80 853fdb00 853fdad8 fltmgr!DoReleaseContext+0x42
c403fadc 8359a793 853fdb04 853fdb00 ffffffff fltmgr!FltpDeleteContextList+0x15c
c403fafc 8359a9b4 853fdad8 b43283b8 00000000 fltmgr!CleanupStreamListCtrl+0x1b
c403fb10 82a31818 853fdadc d8646ad0 00000000 fltmgr!DeleteStreamListCtrlCallback+0x5a
c403fb50 836bbfb2 b43283b8 b43282c8 b43283b8 nt!FsRtlTeardownPerStreamContexts+0x13a
c403fb6c 836b2b3b 00000705 b43282f0 b43282c8 Ntfs!NtfsDeleteScb+0x214
c403fb84 8362271e 854fcb38 b43283b8 00000000 Ntfs!NtfsRemoveScb+0xc5
c403fba0 836a30d2 854fcb38 b43282c8 00000000 Ntfs!NtfsPrepareFcbForRemoval+0x62
c403fbe4 8361fbec 854fcb38 b43283b8 b4328560 Ntfs!NtfsTeardownStructures+0x68
c403fc0c 8369f55b 854fcb38 b43283b8 b4328560 Ntfs!NtfsDecrementCloseCounts+0xaf
c403fc6c 836be4c3 854fcb38 b43283b8 b43282c8 Ntfs!NtfsCommonClose+0x4f2
c403fd00 82880f3b 00000000 00000000 85fc8690 Ntfs!NtfsFspClose+0x118
c403fd50 82a216d3 80000000 d8646c10 00000000 nt!ExpWorkerThread+0x10d
c403fd90 828d30f9 82880e2e 80000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  SRTSP+160ae

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SRTSP

IMAGE_NAME:  SRTSP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a80e37c

STACK_COMMAND:  .cxr 0xffffffffc403f5b0 ; kb

FAILURE_BUCKET_ID:  0x24_SRTSP+160ae

BUCKET_ID:  0x24_SRTSP+160ae

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

Debug session time: Tue Nov  9 22:58:05.822 2010 (GMT-5)
System Uptime: 0 days 6:14:32.120
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {5aa55acd, 2, 1, 828440e9}

Probably caused by : memory_corruption ( nt!MiIdentifyPfn+1ed )

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

1: 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: 5aa55acd, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 828440e9, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82974718
Unable to read MiSystemVaType memory at 82954160
 5aa55acd 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiIdentifyPfn+1ed
828440e9 f00fba281f      lock bts dword ptr [eax],1Fh

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  92f936ec -- (.trap 0xffffffff92f936ec)
ErrCode = 00000002
eax=5aa55acd ebx=855007d0 ecx=00000000 edx=0801ce16 esi=807c8120 edi=5aa55aa5
eip=828440e9 esp=92f93760 ebp=92f93798 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nt!MiIdentifyPfn+0x1ed:
828440e9 f00fba281f      lock bts dword ptr [eax],1Fh ds:0023:5aa55acd=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 828440e9 to 8285282b

STACK_TEXT:  
92f936ec 828440e9 badb0d00 0801ce16 00000002 nt!KiTrap0E+0x2cf
92f93798 82844562 855007d0 85500000 92f9383c nt!MiIdentifyPfn+0x1ed
92f937c0 82a28462 00500060 8e901dad 92f93850 nt!MmQueryPfnList+0xa6
92f93808 82a48e61 00000001 8e901d2d 00000000 nt!PfpPfnPrioRequest+0xde
92f93888 82a418a5 00000000 00000001 92f93cd0 nt!PfQuerySuperfetchInformation+0xea
92f93d00 82a4250c 0000004f 00000000 00000000 nt!ExpQuerySystemInformation+0x24ce
92f93d1c 8284f44a 0000004f 0140f410 00000014 nt!NtQuerySystemInformation+0x76
92f93d1c 77da64f4 0000004f 0140f410 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0140d2d0 00000000 00000000 00000000 00000000 0x77da64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiIdentifyPfn+1ed
828440e9 f00fba281f      lock bts dword ptr [eax],1Fh

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiIdentifyPfn+1ed

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiIdentifyPfn+1ed

BUCKET_ID:  0xA_nt!MiIdentifyPfn+1ed

Followup: MachineOwner
---------
I see some out of date drivers loaded on your system. Out of date drivers can and do cause memory corruption and your latest dump blames memory corruption for the crash. Some of your drivers are quite obsolete; they are XP drivers. These are in red font. Software and hardware designed for XP and not updated for Win 7 are not going to run on Win 7 except in the XP mode. Update or eliminate the following drivers.
Quote:
b57nd60x.sys Sun Apr 26 07:15:34 2009 - Broadcom NetXtreme Gigabit Ethernet NDIS6.0 DriverBroadcom.com - Downloads & Support

pelmouse.sys Fri Jan 10 00:55:30 2003
- Mouse Suite Driver (For Windows 2000 and Whistler Only) belongs to Mouse Suite Driver by Primax ElectronicsLtd (www.primax.com.tw). If you cannot update this driver, uninstall the software. If your mouse will not work without this software, upgrade to a new mouse and uninstall your current one.

pelusblf.sys Tue Feb 11 00:25:13 2003 - IBM/Lenovo USB mouse filter system driverIBM Support & downloads - United States. See above.

psadd.sys Mon Feb 19 13:56:45 2007 - Lenovo Parties Service Access Device Driver (SMBIOS)Lenovo Support - Home page. Update this driver.

PxHelp20.sys Mon Aug 02 17:08:25 2004 - Sonic CD/DVD driver (used by many different CD/DVD programs) pxHelp20.sys programs
Go to C:\Windows\System32\drivers and rename PxHelp20.sys to PXHelp20.BAK
This will break your CD/DVD program, but can easily be renamed after we've finished.

SYMEVENT.SYS Wed Jun 24 16:14:58 2009 - Norton/Symantec. Uninstall Norton.
How to update drivers -
Quote:
- I have listed links to most of the drivers in the code box above. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.


- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
Uninstall Norton and take care of the above drivers by either updating or uninstalling. Reboot and see how your system runs.

Because of error code 24, I suggest that you run Check Disk.
Quote:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7).

Copy/paste the results into your next post.


My System SpecsSystem Spec
18 Nov 2010   #5
coparofl

Windows 7
 
 

Hello! It just happened again!

I uninstalled Symantec Antivirus as requested,

I took a recapture of the logs

Please help.!
My System SpecsSystem Spec
19 Nov 2010   #6
CarlTR6

Windows 7 Ultimate 32 bit
 
 

I do see that Norton/Symantec is gone. Good job. However I still see outdated drivers that ZigZag listed loading on your system. Out of date drivers can and do cause memory corruption and crashes. Update these drivers.
Quote:
b57nd60x.sys Thu May 28 21:58:23 2009 - Broadcom NetXtreme Gigabit Ethernet NDIS6.0 DriverBroadcom.com - Downloads & Support

LHidFilt.Sys Fri Feb 29 05:08:08 2008 - Downloads

LMouFilt.Sys Fri Feb 29 05:08:12 2008 - Logitech SetPoint HID Filter Driver Downloads

psadd.sys Mon Feb 19 13:56:45 2007 - Lenovo Parties Service Access Device Driver (SMBIOS)Lenovo Support - Home page

PxHelp20.sys Mon Aug 02 17:08:25 2004 - Sonic CD/DVD driver (used by many different CD/DVD programs) pxHelp20.sys programs
Go to C:\Windows\System32\drivers and rename PxHelp20.sys to PXHelp20.BAK
This will break your CD/DVD program, but can easily be renamed after we've finished. This is and XP driver and XP software. It is not going to work with Win 7.
Code:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82844000 PsLoadedModuleList = 0x8298c810
Debug session time: Thu Nov 18 21:32:08.870 2010 (GMT-5)
System Uptime: 0 days 4:37:01.472
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {5aa55acd, 2, 1, 8287c0e9}

Probably caused by : memory_corruption ( nt!MiIdentifyPfn+1ed )

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

1: 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: 5aa55acd, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 8287c0e9, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 829ac718
Unable to read MiSystemVaType memory at 8298c160
 5aa55acd 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiIdentifyPfn+1ed
8287c0e9 f00fba281f      lock bts dword ptr [eax],1Fh

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  97c7b6ec -- (.trap 0xffffffff97c7b6ec)
ErrCode = 00000002
eax=5aa55acd ebx=859277a0 ecx=00000000 edx=0800e4d7 esi=807c8120 edi=5aa55aa5
eip=8287c0e9 esp=97c7b760 ebp=97c7b798 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nt!MiIdentifyPfn+0x1ed:
8287c0e9 f00fba281f      lock bts dword ptr [eax],1Fh ds:0023:5aa55acd=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8287c0e9 to 8288a82b

STACK_TEXT:  
97c7b6ec 8287c0e9 badb0d00 0800e4d7 00000002 nt!KiTrap0E+0x2cf
97c7b798 8287c562 859277a0 85927000 97c7b83c nt!MiIdentifyPfn+0x1ed
97c7b7c0 82a60462 00927060 8ba3cdd1 97c7b850 nt!MmQueryPfnList+0xa6
97c7b808 82a80e61 00000001 8ba3cd51 00000000 nt!PfpPfnPrioRequest+0xde
97c7b888 82a798a5 00000000 00000001 97c7bcd0 nt!PfQuerySuperfetchInformation+0xea
97c7bd00 82a7a50c 0000004f 00000000 00000000 nt!ExpQuerySystemInformation+0x24ce
97c7bd1c 8288744a 0000004f 012eee90 00000014 nt!NtQuerySystemInformation+0x76
97c7bd1c 778964f4 0000004f 012eee90 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
012ecd50 00000000 00000000 00000000 00000000 0x778964f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiIdentifyPfn+1ed
8287c0e9 f00fba281f      lock bts dword ptr [eax],1Fh

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiIdentifyPfn+1ed

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiIdentifyPfn+1ed

BUCKET_ID:  0xA_nt!MiIdentifyPfn+1ed

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

1: kd> lmtsmn
start    end        module name
8341c000 83464000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
8d260000 8d2ba000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62)
8d80f000 8d821000   AgileVpn AgileVpn.sys Mon Jul 13 19:55:00 2009 (4A5BC954)
8356d000 83576000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
97e31000 97e3a000   asyncmac asyncmac.sys Mon Jul 13 19:54:46 2009 (4A5BC946)
83541000 8354a000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
8354a000 8356d000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
93600000 9364d000   ATMFD    ATMFD.DLL    unavailable (00000000)
8d97c000 8d9bd000   b57nd60x b57nd60x.sys Thu May 28 21:58:23 2009 (4A1F413F)
889ee000 889f5000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC)
8d8b7000 8d8c5000   blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8)
82e8c000 82e94000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
824d8000 824f1000   bowser   bowser.sys   Mon Jul 13 19:14:21 2009 (4A5BBFCD)
939c0000 939de000   cdd      cdd.dll      unavailable (00000000)
889cf000 889ee000   cdrom    cdrom.sys    Mon Jul 13 19:11:24 2009 (4A5BBF1C)
82ed6000 82f81000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
88978000 8899d000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
82e94000 82ed6000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
83774000 837d1000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
8d9f0000 8d9fd000   CompositeBus CompositeBus.sys Mon Jul 13 19:45:26 2009 (4A5BC716)
8fb7b000 8fb88000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
8d83b000 8d89f000   csc      csc.sys      Mon Jul 13 19:15:08 2009 (4A5BBFFC)
8d89f000 8d8b7000   dfsc     dfsc.sys     Mon Jul 13 19:14:16 2009 (4A5BBFC8)
8d3b2000 8d3be000   discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214)
88967000 88978000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
8fb62000 8fb7b000   drmk     drmk.sys     Mon Jul 13 20:36:05 2009 (4A5BD2F5)
8fb93000 8fb9c000   dump_atapi dump_atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
8fb88000 8fb93000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:11:16 2009 (4A5BBF14)
8fb9c000 8fbad000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
8fbad000 8fbb7000   Dxapi    Dxapi.sys    Mon Jul 13 19:25:25 2009 (4A5BC265)
8e33c000 8e3f3000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 20:48:33 2009 (4AC54DE1)
8d8f8000 8d931000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:25:25 2009 (4A5BC265)
8d9c7000 8d9d2000   fdc      fdc.sys      Mon Jul 13 19:45:45 2009 (4A5BC729)
835aa000 835bb000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
83576000 835aa000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
837df000 837e8000   Fs_Rec   Fs_Rec.sys   unavailable (00000000)
88935000 88967000   fvevol   fvevol.sys   Fri Sep 25 22:24:21 2009 (4ABD7B55)
88b78000 88ba9000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
8d9ea000 8d9ef280   GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:16:53 2009 (4A1151B5)
8280d000 82844000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
8de0f000 8de2e000   HDAudBus HDAudBus.sys Mon Jul 13 19:50:55 2009 (4A5BC85F)
8fae3000 8fb33000   HdAudio  HdAudio.sys  Mon Jul 13 19:51:46 2009 (4A5BC892)
8fbdb000 8fbee000   HIDCLASS HIDCLASS.SYS Mon Jul 13 19:51:01 2009 (4A5BC865)
8fbee000 8fbf4480   HIDPARSE HIDPARSE.SYS Mon Jul 13 19:50:59 2009 (4A5BC863)
8fbd0000 8fbdb000   hidusb   hidusb.sys   Mon Jul 13 19:51:04 2009 (4A5BC868)
82453000 824d8000   HTTP     HTTP.sys     Mon Jul 13 19:12:53 2009 (4A5BBF75)
8892d000 88935000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
8de33000 8e33c000   igdkmd32 igdkmd32.sys Wed Sep 23 15:18:09 2009 (4ABA7471)
83516000 8351d000   intelide intelide.sys Mon Jul 13 19:11:19 2009 (4A5BBF17)
8d8e6000 8d8f8000   intelppm intelppm.sys Mon Jul 13 19:11:03 2009 (4A5BBF07)
8fa2a000 8fa37000   kbdclass kbdclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
8899d000 889a9000   kbdhid   kbdhid.sys   Mon Jul 13 19:45:09 2009 (4A5BC705)
80bb3000 80bbb000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
8fa4c000 8fa80000   ks       ks.sys       Wed Mar 03 22:57:52 2010 (4B8F2FC0)
83761000 83774000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
888f8000 8891d000   ksecpkg  ksecpkg.sys  Thu Dec 10 23:04:22 2009 (4B21C4C6)
8d800000 8d807000   ldmirror ldmirror.sys Wed Sep 16 06:34:48 2009 (4AB0BF48)
8fbf5000 8fbfc000   LHidFilt LHidFilt.Sys Fri Feb 29 05:08:08 2008 (47C7D988)
82430000 82440000   lltdio   lltdio.sys   Mon Jul 13 19:53:18 2009 (4A5BC8EE)
8fa00000 8fa07600   LMouFilt LMouFilt.Sys Fri Feb 29 05:08:12 2008 (47C7D98C)
889a9000 889c4000   luafv    luafv.sys    Mon Jul 13 19:15:44 2009 (4A5BC020)
82e03000 82e7b000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:06:41 2009 (4A5BDA21)
8d807000 8d80f000   mirrorflt mirrorflt.sys Wed Sep 16 06:35:22 2009 (4AB0BF6A)
8d3eb000 8d3f6000   monitor  monitor.sys  Mon Jul 13 19:25:58 2009 (4A5BC286)
8fa37000 8fa44000   mouclass mouclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
8d22f000 8d23a000   mouhid   mouhid.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
8352b000 83541000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
824f1000 82503000   mpsdrv   mpsdrv.sys   Mon Jul 13 19:52:52 2009 (4A5BC8D4)
82503000 82526000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:32:02 2010 (4B88CA72)
82526000 82561000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:32:21 2010 (4B88CA85)
82561000 8257c000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:32:11 2010 (4B88CA7B)
83400000 8340b000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E)
8346d000 83475000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
83736000 83761000   msrpc    msrpc.sys    unavailable (00000000)
8d3a8000 8d3b2000   mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
8891d000 8892d000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
88803000 888ba000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
8d3be000 8d3c9000   ndistapi ndistapi.sys Mon Jul 13 19:54:24 2009 (4A5BC930)
8d3c9000 8d3eb000   ndiswan  ndiswan.sys  Mon Jul 13 19:54:34 2009 (4A5BC93A)
8fad2000 8fae3000   NDProxy  NDProxy.SYS  Mon Jul 13 19:54:27 2009 (4A5BC933)
8d312000 8d320000   netbios  netbios.sys  Mon Jul 13 19:53:54 2009 (4A5BC912)
8d2ba000 8d2ec000   netbt    netbt.sys    Mon Jul 13 19:12:18 2009 (4A5BBF52)
888ba000 888f8000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
8340b000 83419000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23)
8d39e000 8d3a8000   nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48)
82844000 82c54000   nt       ntkrpamp.exe Fri Jun 18 23:55:24 2010 (4C1C3FAC)
83607000 83736000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
88bf9000 88c00000   Null     Null.SYS     unavailable (00000000)
8d2f3000 8d312000   pacer    pacer.sys    Mon Jul 13 19:53:58 2009 (4A5BC916)
8d9d2000 8d9ea000   parport  parport.sys  Mon Jul 13 19:45:34 2009 (4A5BC71E)
834aa000 834bb000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
8257c000 82583000   parvdm   parvdm.sys   unavailable (00000000)
83475000 8349f000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
8351d000 8352b000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
837d1000 837df000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
97e3b000 97ed2000   peauth   peauth.sys   Mon Jul 13 20:35:44 2009 (4A5BD2E0)
8fb33000 8fb62000   portcls  portcls.sys  Mon Jul 13 19:51:00 2009 (4A5BC864)
8fa44000 8fa49380   psadd    psadd.sys    Mon Feb 19 13:56:45 2007 (45D9F2ED)
82e7b000 82e8c000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
835bb000 835bfde0   PxHelp20 PxHelp20.sys Mon Aug 02 17:08:25 2004 (410EAD49)
8d821000 8d839000   rasl2tp  rasl2tp.sys  Mon Jul 13 19:54:33 2009 (4A5BC939)
8d200000 8d218000   raspppoe raspppoe.sys Mon Jul 13 19:54:53 2009 (4A5BC94D)
8d218000 8d22f000   raspptp  raspptp.sys  Mon Jul 13 19:54:47 2009 (4A5BC947)
8fa09000 8fa20000   rassstp  rassstp.sys  Mon Jul 13 19:54:57 2009 (4A5BC951)
8d35d000 8d39e000   rdbss    rdbss.sys    Mon Jul 13 19:14:26 2009 (4A5BBFD2)
8fa20000 8fa2a000   rdpbus   rdpbus.sys   Mon Jul 13 20:02:40 2009 (4A5BCB20)
889f5000 889fd000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4)
97faa000 97fcf000   rdpdr    rdpdr.sys    Mon Jul 13 20:02:56 2009 (4A5BCB30)
837f4000 837fc000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3)
835ee000 835f6000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5)
97e00000 97e31000   RDPWD    RDPWD.SYS    Mon Jul 13 20:01:50 2009 (4A5BCAEE)
88a00000 88a2d000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
82440000 82453000   rspndr   rspndr.sys   Mon Jul 13 19:53:20 2009 (4A5BC8F0)
97ed2000 97edc000   secdrv   secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528)
8d9bd000 8d9c7000   serenum  serenum.sys  Mon Jul 13 19:45:27 2009 (4A5BC717)
8d320000 8d33a000   serial   serial.sys   Mon Jul 13 19:45:33 2009 (4A5BC71D)
88bf1000 88bf9000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
97f59000 97faa000   srv      srv.sys      Thu Aug 26 23:31:26 2010 (4C77318E)
97f0a000 97f59000   srv2     srv2.sys     Thu Aug 26 23:30:45 2010 (4C773165)
97edc000 97efd000   srvnet   srvnet.sys   Thu Aug 26 23:30:39 2010 (4C77315F)
8fa4a000 8fa4b380   swenum   swenum.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
88a2f000 88b78000   tcpip    tcpip.sys    Sun Jun 13 23:36:59 2010 (4C15A3DB)
97efd000 97f0a000   tcpipreg tcpipreg.sys Mon Jul 13 19:54:14 2009 (4A5BC926)
8d255000 8d260000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C)
97fcf000 97fd9000   tdtcp    tdtcp.sys    Mon Jul 13 20:01:37 2009 (4A5BCAE1)
8d23e000 8d255000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A)
8d34d000 8d35d000   termdd   termdd.sys   Mon Jul 13 20:01:35 2009 (4A5BCADF)
93990000 93999000   TSDDD    TSDDD.dll    unavailable (00000000)
97fd9000 97fe6000   tssecsrv tssecsrv.sys Mon Jul 13 20:01:50 2009 (4A5BCAEE)
8d8c5000 8d8e6000   tunnel   tunnel.sys   Mon Jul 13 19:54:03 2009 (4A5BC91B)
8fa80000 8fa8e000   umbus    umbus.sys    Mon Jul 13 19:51:38 2009 (4A5BC88A)
8fbb7000 8fbce000   usbccgp  usbccgp.sys  Mon Jul 13 19:51:31 2009 (4A5BC883)
8fbce000 8fbcf700   USBD     USBD.SYS     Mon Jul 13 19:51:05 2009 (4A5BC869)
8de00000 8de0f000   usbehci  usbehci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872)
8fa8e000 8fad2000   usbhub   usbhub.sys   Mon Jul 13 19:52:06 2009 (4A5BC8A6)
8d931000 8d97c000   USBPORT  USBPORT.SYS  Mon Jul 13 19:51:13 2009 (4A5BC871)
8e3f3000 8e3fe000   usbuhci  usbuhci.sys  Mon Jul 13 19:51:10 2009 (4A5BC86E)
8349f000 834aa000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
837e8000 837f4000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E)
835c0000 835e1000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D)
88ba9000 88bb2000   vmstorfl vmstorfl.sys unavailable (00000000)
834bb000 834cb000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
834cb000 83516000   volmgrx  volmgrx.sys  unavailable (00000000)
88bb2000 88bf1000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
8d33a000 8d34d000   wanarp   wanarp.sys   Mon Jul 13 19:55:02 2009 (4A5BC956)
835e1000 835ee000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A)
82f81000 82ff2000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
82ff2000 83000000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8d2ec000 8d2f3000   wfplwf   wfplwf.sys   Mon Jul 13 19:53:51 2009 (4A5BC90F)
93730000 9397b000   win32k   win32k.sys   unavailable (00000000)
83464000 8346d000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)
82416000 82430000   WudfPf   WudfPf.sys   Mon Jul 13 19:50:13 2009 (4A5BC835)

Unloaded modules:
97fe6000 97ff1000   hiber_atapor
    Timestamp: unavailable (00000000)
    Checksum:  00000000
97ff1000 97ffa000   hiber_atapi.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
825ed000 825fe000   hiber_dumpfv
    Timestamp: unavailable (00000000)
    Checksum:  00000000
82583000 825ed000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8899d000 889aa000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
889aa000 889b5000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
889b5000 889be000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
889be000 889cf000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
Please only start one thread for one problem. Stick with that thread until the problems is solved. You are getting the same advice in each thread. This makes the third thread you have started for this same problem:

https://www.sevenforums.com/crashes-d...arts-bsod.html. Started yesterday.

https://www.sevenforums.com/crashes-d...need-help.html. Started four days ago.
My System SpecsSystem Spec
23 Nov 2010   #7
coparofl

Windows 7
 
 

thanks carl, yes i did start a few new threads for the same issues it seems, however they are all on different computers!

i am going through each driver individually and seeing which driver is the culprit.
My System SpecsSystem Spec
23 Nov 2010   #8
CarlTR6

Windows 7 Ultimate 32 bit
 
 

OK, that makes sense and that is the right thing to do. What you should do if you are working with problems on different computers is to clearly state in your first post that this is different computer than the one in thread XXXXXXXX. That way it will not confuse us. And some of us, me, get confused easily. Let us know if you need help with the drivers.
My System SpecsSystem Spec
Reply

 Random BSOD, need help!




Thread Tools




Similar help and support threads
Thread Forum
Random BSOD after start and Random stuck on windows logo screen
Heyy.. So yesterday due to a sudden power outage (happens allot here), my windows started behaving erratically. First when the power came on my windows 7 ultimate 64 bit, was stuck on windows logo. i waited for about 20 mins and it was still stuck. The HDD read activity light on my casing was...
BSOD Help and Support
Random BSOD problems in the past 2 days. Random errors at random times
Three days ago my water cooling failed (got up to 77C while gaming is when I noticed the problem as my CPU should not go over 62C). I decided to install an aftermarket heatsink instead of a new water cooling system ,and add a few more fans just to make sure my whole motherboard was getting plenty...
BSOD Help and Support
BSOD at seemingly random times, memory dump blaming random drivers
I've been plagued by odd problems since making this custom build about a month ago, but the latest is the increasing frequency of BSODs. They never occur at load (gaming with high end specs), but often occur at shutdown (forcing a restart before I can then actually shut down). I normally boot into...
BSOD Help and Support
Random BSOD at random moments on Toshiba L500 laptop; graphics card?
My GF has had a Toshiba L500 laptop for 4 years now. It's a great model and it worked well...till now. It started about two weeks ago, with 1 blue screen every 1-2 days. I haven't reinstalled her windows for about a year, so i figured that was the problem. Four days ago it started blue...
BSOD Help and Support
Random BSOD with random error code at random moment
Hello Ok now i'm out of solution so i come here hoping that someone could help me I always had bsod hapening randomly but not like the this week I got 2 bsod/day when i'm playing, when i'm staring at my monitor or even when i'm sleeping with random error code like 0x1e, 0x24, 0x3b, 0x4a or 0xa...
BSOD Help and Support
BSOD doing random things (Google Chrome, minecraft, random times)
I have finally had it up to here with the BSODs, so I really need help. I ran a windows memtest and it detected no errors. I just finished updating to SP1 with pretty much most updates too. The BSODs I get the most are: Driver IRQL not less or Equal System Service Exception and these two I...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 22:47.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App