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: BSOD Help Please

16 Nov 2010   #1
euckersw

Windows 7 Home Premium 64bit
 
 
BSOD Help Please

Hello,

I'm hoping to find some help identifying the cause of my system's chronic BSODs.

Here is my information:

The system originally came with Windows Vista
I'm now running Windows 7 Home Premium 64bit (installed as of August 2010)
The system is about 4 years old

Thank you in advance for your help!

-Scott


My System SpecsSystem Spec
.
16 Nov 2010   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by euckersw View Post
Hello,

I'm hoping to find some help identifying the cause of my system's chronic BSODs.

Here is my information:

The system originally came with Windows Vista
I'm now running Windows 7 Home Premium 64bit (installed as of August 2010)
The system is about 4 years old

Thank you in advance for your help!

-Scott

Scoot hi and welcome


15 of 24 directly point to memory management. It could be a driver corrupting memory or memory itself.

I would

1- Run memtest


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

2-run driver verifier


Beyond that, please run Verifier with these settings:
Quote:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Code:
Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Using Driver Verifier to identify issues with Windows drivers for advanced users

3- Update the drivers







Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\111410-21028-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c50000 PsLoadedModuleList = 0xfffff800`02e8de50
Debug session time: Sun Nov 14 03:28:19.534 2010 (GMT-5)
System Uptime: 0 days 20:10:51.454
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002dc694c, fffff88005250fb0, 0}

Probably caused by : memory_corruption ( nt!MiEmptyPageAccessLog+21c )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002dc694c, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88005250fb0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
nt!MiEmptyPageAccessLog+21c
fffff800`02dc694c 4d8b7b18        mov     r15,qword ptr [r11+18h]

CONTEXT:  fffff88005250fb0 -- (.cxr 0xfffff88005250fb0)
rax=0000000000000050 rbx=0000000000000001 rcx=fffffa8003c01dc0
rdx=0000000000000054 rsi=fffffa8005f6ffe8 rdi=0000000000000000
rip=fffff80002dc694c rsp=fffff88005251980 rbp=0000000000000000
 r8=0000000000000005  r9=fffffa8005f6f048 r10=fffffa8003c11d00
r11=0000000000000050 r12=fffffa8005f6fff0 r13=fffffa8005f6f000
r14=fffffa8003c01dc0 r15=fffffa8003c01d80
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!MiEmptyPageAccessLog+0x21c:
fffff800`02dc694c 4d8b7b18        mov     r15,qword ptr [r11+18h] ds:002b:00000000`00000068=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002dc694c

STACK_TEXT:  
fffff880`05251980 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiEmptyPageAccessLog+0x21c


FOLLOWUP_IP: 
nt!MiEmptyPageAccessLog+21c
fffff800`02dc694c 4d8b7b18        mov     r15,qword ptr [r11+18h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiEmptyPageAccessLog+21c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff88005250fb0 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x3B_nt!MiEmptyPageAccessLog+21c

BUCKET_ID:  X64_0x3B_nt!MiEmptyPageAccessLog+21c

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


Old drivers
Code:
lmimirr.sys        fffff880`0485d000    0x00007000    4/10/2007 17:32:45            0x461c108d    fffff880`04856000                
RaInfo.sys        fffff880`047e6000    0x00007000    1/4/2008 13:57:14            0x477e818a    fffff880`047df000                
LMIRfsDriver.sys        fffff880`047f9000    0x00013000    7/14/2008 11:26:56            0x487b7e50    fffff880`047e6000                
VSTCNXT6.SYS        fffff880`0430d000    0x000cb000    10/15/2008 19:52:22            0x48f69046    fffff880`04242000                
VSTBS26.SYS        fffff880`03ffd000    0x00070000    10/15/2008 19:54:06            0x48f690ae    fffff880`03f8d000                
VSTDPV6.SYS        fffff880`041b7000    0x00174000    10/15/2008 19:57:45            0x48f69189    fffff880`04043000                
spldr.sys        fffff880`016dd000    0x00008000    5/11/2009 11:56:27            0x4a0858bb    fffff880`016d5000                
GEARAspiWDM.sys        fffff880`043dd000    0x0000d000    5/18/2009 07:17:04            0x4a1151c0    fffff880`043d0000                
amdxata.sys        fffff880`010fd000    0x0000b000    5/19/2009 12:56:59            0x4a12f2eb    fffff880`010f2000                
nvstor.sys        fffff880`00e8f000    0x0002b000    5/20/2009 01:45:37            0x4a13a711    fffff880`00e64000                
dump_nvstor64.sys        fffff880`04d49000    0x0003e000    6/22/2009 17:23:37            0x4a400469    fffff880`04d0b000                
nvstor64.sys        fffff880`010f2000    0x0003e000    6/22/2009 17:23:37            0x4a400469    fffff880`010b4000
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   #3
euckersw

Windows 7 Home Premium 64bit
 
 

Thank you zigzag. As an update, I ran Memtest for 6 passes and received no errors, so everything looks good on that front. I'm now on to running the driver verifier. I've just setup verifier with the parameters you listed and am waiting for a crash. I will let you know what happens.

-Scott
My System SpecsSystem Spec
.

17 Nov 2010   #4
euckersw

Windows 7 Home Premium 64bit
 
 

Ok, my system just crashed using Verifier, however the Memory.DMP file it created is huge (463 MBs, 105 MBs after zipping it)! Can I really zip this file and attach it, or is there something more specific you would like me to zip and attach? Thank you.

-Scott
My System SpecsSystem Spec
17 Nov 2010   #5
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Scott, make sure your system is set for mini dumps. Read the last part of the first post in this tutorial: https://www.sevenforums.com/tutorials...en-forums.html
My System SpecsSystem Spec
18 Nov 2010   #6
euckersw

Windows 7 Home Premium 64bit
 
 

Ok - thank you for the clarification. Attached are the mini dump files created while using Verifier. There were several crashes, so I have attached each mini dump file created. Thank you for your help.
My System SpecsSystem Spec
18 Nov 2010   #7
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Your last three dumps are Driver Verifier enabled dumps. Two of them blame memory corruption and one blames your video driver. You can turn off Driver Verifier for now.

Before we address your video driver/card, you really need to take care of outdated drivers. Some of these, or a combination thereof, may well be responsible for the memory corruption and crashes. I cannot say they are causing the crashes; but I can say they are definitely not contributing to the stability of your system. NVstor64.sys was involved in at least one of the crashes. The drivers in red font are really obsolete and not compatible with Win 7.
Quote:
lmimirr.sys Tue Apr 10 18:32:45 2007 - RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver https://secure.logmein.com/US/home.aspx. RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver https://secure.logmein.com/US/home.aspx

LMIRfsDriver.sys Mon Jul 14 12:26:56 2008 - RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver https://secure.logmein.com/US/home.aspx. Completely uninstall LogMeIn. This version is obsolete and not compatible with Win 7. After you uninstall this version and get your system stable, you can try an updated version if it is compatible with Win 7.

nvstor.sys Wed May 20 02:45:37 2009 - nVidia Storage Drivers Drivers - Download NVIDIA Drivers. Update this driver.

nvstor64.sys Mon Jun 22 18:23:37 2009 - nVidia Storage Driver (nForce chipset driver) Drivers - Download NVIDIA Drivers. Update this driver. There is a later version available.

RaInfo.sys Fri Jan 04 13:57:14 2008 - LogMeIn/RemotelyAnywhere Kernel Information Provider RemotelyAnywhere - Remote Access Solutions. Completely uninstall LogMeIn. This version is obsolete and not compatible with Win 7. After you uninstall this version and get your system stable, you can try an updated version if it is compatible with Win 7.

VSTBS26.SYS Wed Oct 15 20:54:06 2008 - Conexant HSF_HWB2 WDM driverConexant: Support. Update these modem drivers. If there is no update, you need a new modem. If you do not use a modem, you can disable these drivers by navigating to C:\Windows\System32\Drivers, locate each driver file and rename them from .sys to .bak. Reboot and they will not load.

VSTCNXT6.SYS Wed Oct 15 20:52:22 2008 - Conexant SoftK56 Modem Driver Conexant: Support

VSTDPV6.SYS Wed Oct 15 20:57:45 2008 - Conexant SoftK56 Modem Driver Conexant: Support
Take care of these drivers and let's see how your system runs. Update us and let us know.

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

Code:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e66000 PsLoadedModuleList = 0xfffff800`030a3e50
Debug session time: Thu Nov 18 08:16:49.864 2010 (GMT-5)
System Uptime: 0 days 0:08:11.330
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8005c344e0, fffff880105bbc88, ffffffffc000009a, 4}

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

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8005c344e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880105bbc88, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+704c88
fffff880`105bbc88 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`05146b88 fffff880`04b19ef8 : 00000000`00000116 fffffa80`05c344e0 fffff880`105bbc88 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`05146b90 fffff880`04aed867 : fffff880`105bbc88 fffffa80`06894000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05146bd0 fffff880`04b19d07 : fffffa80`ffffd87b ffffffff`fffe7960 fffffa80`05c344e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`05146c80 fffff880`04be8ec1 : fffffa80`06291d50 00000000`00000080 00000000`00000000 fffffa80`06685410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`05146d00 fffff800`0317ac06 : 00000000`220a6578 fffffa80`061dcb60 fffffa80`03686b30 fffffa80`061dcb60 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`05146d40 fffff800`02eb4c26 : fffff800`03050e80 fffffa80`061dcb60 fffffa80`03724040 fffff880`01222534 : nt!PspSystemThreadStartup+0x5a
fffff880`05146d80 00000000`00000000 : fffff880`05147000 fffff880`05141000 fffff880`05146410 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+704c88
fffff880`105bbc88 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+704c88

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c37918e

FAILURE_BUCKET_ID:  X64_0x116_VRF_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_VRF_IMAGE_nvlddmkm.sys

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

0: kd> lmtsmn
start             end                 module name
fffff880`04569000 fffff880`045a7000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`00f2b000 fffff880`00f82000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`03c00000 fffff880`03c8a000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`04a87000 fffff880`04a9d000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`03f25000 fffff880`03f3c000   amdk8    amdk8.sys    Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`010ba000 fffff880`010c5000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`06e00000 fffff880`06e0b000   asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5)
fffff880`00d8a000 fffff880`00d93000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00d93000 fffff880`00dbd000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`00ff3000 fffff880`00fff000   BATTC    BATTC.SYS    Mon Jul 13 19:31:01 2009 (4A5BC3B5)
fffff880`019de000 fffff880`019e5000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`03eee000 fffff880`03eff000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`0577c000 fffff880`0579a000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`00620000 fffff960`00647000   cdd      cdd.dll      unavailable (00000000)
fffff880`019ab000 fffff880`019d5000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00ca0000 fffff880`00d60000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01912000 fffff880`01942000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c42000 fffff880`00ca0000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01183000 fffff880`011f6000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`00fea000 fffff880`00ff3000   compbatt compbatt.sys Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`04a00000 fffff880`04a10000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`053ef000 fffff880`053fd000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`03ed0000 fffff880`03eee000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`03ec1000 fffff880`03ed0000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`018fc000 fffff880`01912000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`04a5f000 fffff880`04a81000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`0fe6f000 fffff880`0fe79000   dump_diskdump dump_diskdump.sys Mon Jul 12 23:32:05 2010 (4C3BDE35)
fffff880`0445f000 fffff880`04472000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`0fe79000 fffff880`0feb7000   dump_nvstor64 dump_nvstor64.sys Mon Jun 22 18:23:37 2009 (4A400469)
fffff880`053e3000 fffff880`053ef000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`04abd000 fffff880`04bb1000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`04bb1000 fffff880`04bf7000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`01111000 fffff880`01125000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`010c5000 fffff880`01111000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`013e2000 fffff880`013ec000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`018c2000 fffff880`018fc000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`01400000 fffff880`0144a000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`04452000 fffff880`0445f000   GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
fffff800`02e1d000 fffff800`02e66000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`045a7000 fffff880`045cb000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`04398000 fffff880`043f4000   HdAudio  HdAudio.sys  Mon Jul 13 20:06:59 2009 (4A5BCC23)
fffff880`10bf4000 fffff880`10bff000   HidBatt  HidBatt.sys  Mon Jul 13 19:31:06 2009 (4A5BC3BA)
fffff880`045d9000 fffff880`045f2000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`04bf7000 fffff880`04bff080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`045cb000 fffff880`045d9000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`056b4000 fffff880`0577c000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`018b9000 fffff880`018c2000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`03f3c000 fffff880`03f5a000   i8042prt i8042prt.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`03f69000 fffff880`03f78000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff800`00b98000 fffff800`00ba2000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`04101000 fffff880`04144000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`013b7000 fffff880`013d1000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`015d0000 fffff880`015fb000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`04a81000 fffff880`04a86200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`04165000 fffff880`0417a000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`04a10000 fffff880`04a17000   lmimirr  lmimirr.sys  Tue Apr 10 18:32:45 2007 (461C108D)
fffff880`05688000 fffff880`0569b000   LMIRfsDriver LMIRfsDriver.sys Mon Jul 14 12:26:56 2008 (487B7E50)
fffff880`04200000 fffff880`04223000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00c21000 fffff880`00c2e000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`0455a000 fffff880`04569000   modem    modem.sys    Mon Jul 13 20:10:48 2009 (4A5BCD08)
fffff880`045f2000 fffff880`04600000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`03f5a000 fffff880`03f69000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`00d70000 fffff880`00d8a000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`0144a000 fffff880`01477000   MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0)
fffff880`05671000 fffff880`05681000   MpNWMon  MpNWMon.sys  Sat Mar 20 01:58:00 2010 (4BA463E8)
fffff880`0579a000 fffff880`057b2000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`057b2000 fffff880`057df000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`05600000 fffff880`0564e000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`0564e000 fffff880`05671000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`03d42000 fffff880`03d4d000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00f8b000 fffff880`00f95000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01125000 fffff880`01183000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`03eb6000 fffff880`03ec1000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`018a7000 fffff880`018b9000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`0147e000 fffff880`01570000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`04a9d000 fffff880`04aa9000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`10b6f000 fffff880`10b9e000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0fe5a000 fffff880`0fe6f000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`03daf000 fffff880`03dbe000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`03c8a000 fffff880`03ccf000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01570000 fffff880`015d0000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`03d4d000 fffff880`03d5e000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`03eaa000 fffff880`03eb6000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02e66000 fffff800`03442000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`01214000 fffff880`013b7000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`019d5000 fffff880`019de000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`10b49000 fffff880`10b4a180   nvBridge nvBridge.kmd Fri Jul 09 17:07:54 2010 (4C378FAA)
fffff880`0feb7000 fffff880`10b48e00   nvlddmkm nvlddmkm.sys Fri Jul 09 17:15:58 2010 (4C37918E)
fffff880`04400000 fffff880`04451500   nvmf6264 nvmf6264.sys Thu Jul 30 19:48:18 2009 (4A723142)
fffff880`00dbd000 fffff880`00de8000   nvstor   nvstor.sys   Wed May 20 02:45:37 2009 (4A13A711)
fffff880`0107c000 fffff880`010ba000   nvstor64 nvstor64.sys Mon Jun 22 18:23:37 2009 (4A400469)
fffff880`03d89000 fffff880`03daf000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`00fd5000 fffff880`00fea000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00f95000 fffff880`00fc8000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00e71000 fffff880`00e78000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00d60000 fffff880`00d70000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`013d1000 fffff880`013e2000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`06e0c000 fffff880`06eb2000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`04a22000 fffff880`04a5f000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`04a17000 fffff880`04a22000   povrtdev povrtdev.sys Wed Feb 24 05:51:44 2010 (4B8504C0)
fffff880`00c2e000 fffff880`00c42000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`05681000 fffff880`05688000   RaInfo   RaInfo.sys   Fri Jan 04 13:57:14 2008 (477E818A)
fffff880`10b4b000 fffff880`10b6f000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`10b9e000 fffff880`10bb9000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`10bb9000 fffff880`10bda000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`10bda000 fffff880`10bf4000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`03e59000 fffff880`03eaa000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`03d27000 fffff880`03d30000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`03d30000 fffff880`03d39000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`03d39000 fffff880`03d42000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`0186d000 fffff880`018a7000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`0417a000 fffff880`04192000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`05202000 fffff880`053e2400   RTKVHD64 RTKVHD64.sys Tue Aug 04 05:50:52 2009 (4A78047C)
fffff880`06eb2000 fffff880`06ebd000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`01866000 fffff880`0186d000   speedfan speedfan.sys Sun Sep 24 09:26:48 2006 (45168798)
fffff880`0185e000 fffff880`01866000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`04000000 fffff880`04071000   spsys    spsys.sys    Mon May 11 13:20:58 2009 (4A085E7A)
fffff880`06f63000 fffff880`06ff9000   srv      srv.sys      Thu Aug 26 23:38:00 2010 (4C773318)
fffff880`06efc000 fffff880`06f63000   srv2     srv2.sys     Thu Aug 26 23:37:46 2010 (4C77330A)
fffff880`06ebd000 fffff880`06eea000   srvnet   srvnet.sys   Thu Aug 26 23:37:24 2010 (4C7732F4)
fffff880`0101a000 fffff880`0107c000   storport storport.sys Mon Jul 13 20:01:18 2009 (4A5BCACE)
fffff880`04aa9000 fffff880`04aaa480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01603000 fffff880`01800000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`06eea000 fffff880`06efc000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`03d7c000 fffff880`03d89000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`03d5e000 fffff880`03d7c000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`03dd9000 fffff880`03ded000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00500000 fffff960`0050a000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`03eff000 fffff880`03f25000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`04aab000 fffff880`04abd000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`053fd000 fffff880`053fef00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`03fd9000 fffff880`03fea000   usbehci  usbehci.sys  Sat Oct 24 00:27:33 2009 (4AE28235)
fffff880`0fe00000 fffff880`0fe5a000   usbhub   usbhub.sys   Sat Oct 24 00:28:24 2009 (4AE28268)
fffff880`03f78000 fffff880`03f83000   usbohci  usbohci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`03f83000 fffff880`03fd9000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`04472000 fffff880`0448d000   USBSTOR  USBSTOR.SYS  Mon Jul 13 20:06:34 2009 (4A5BCC0A)
fffff880`00fc8000 fffff880`00fd5000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`019e5000 fffff880`019f3000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`03cf2000 fffff880`03d17000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`00e00000 fffff880`00e15000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e15000 fffff880`00e71000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01812000 fffff880`0185e000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`04091000 fffff880`04101000   VSTBS26  VSTBS26.SYS  Wed Oct 15 20:54:06 2008 (48F690AE)
fffff880`0448f000 fffff880`0455a000   VSTCNXT6 VSTCNXT6.SYS Wed Oct 15 20:52:22 2008 (48F69046)
fffff880`04224000 fffff880`04398000   VSTDPV6  VSTDPV6.SYS  Wed Oct 15 20:57:45 2008 (48F69189)
fffff880`03dbe000 fffff880`03dd9000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`03d17000 fffff880`03d27000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00e78000 fffff880`00f1c000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f1c000 fffff880`00f2b000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`03ccf000 fffff880`03cd8000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`00060000 fffff960`0036f000   win32k   win32k.sys   unavailable (00000000)
fffff880`00f82000 fffff880`00f8b000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`04144000 fffff880`04165000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)
fffff880`04192000 fffff880`041c3000   WUDFRd   WUDFRd.sys   Mon Jul 13 20:06:06 2009 (4A5BCBEE)

Unloaded modules:
fffff880`01942000 fffff880`01950000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01950000 fffff880`0195a000   dump_storpor
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0195a000 fffff880`01998000   dump_nvstor6
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01998000 fffff880`019ab000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

System Uptime: 0 days 3:42:43.275
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {8884, fffffa8001fb4e30, fffffa8001fb4e60, 502}

Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+c6 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000008884, The subtype of the bugcheck.
Arg2: fffffa8001fb4e30
Arg3: fffffa8001fb4e60
Arg4: 0000000000000502

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


BUGCHECK_STR:  0x1a_8884

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f2ae56 to fffff80002e7c740

STACK_TEXT:  
fffff880`06e1b8b8 fffff800`02f2ae56 : 00000000`0000001a 00000000`00008884 fffffa80`01fb4e30 fffffa80`01fb4e60 : nt!KeBugCheckEx
fffff880`06e1b8c0 fffff800`02f89675 : fffffa80`04ac51c8 fffffa80`04aca000 00000000`00000000 00000000`00000000 : nt!MiRelinkStandbyPage+0xc6
fffff880`06e1b930 fffff800`0328e504 : fffffa80`04ac4000 fffff880`06e1bca0 fffff880`06e1ba08 00000000`00000001 : nt!MmSetPfnListPriorities+0x175
fffff880`06e1b980 fffff800`032ef22a : 00000000`00000020 00000000`00000000 fffffa80`04ac4000 00000000`00000001 : nt!PfpPfnPrioRequest+0x84
fffff880`06e1b9d0 fffff800`032f396e : 00000000`00000000 00000000`016eb788 00000000`0000004f 00000000`00000001 : nt!PfSetSuperfetchInformation+0x199
fffff880`06e1bab0 fffff800`02e7b993 : fffffa80`07636060 00000000`031595a0 00000000`0315c4f8 00000000`0758d558 : nt!NtSetSystemInformation+0xb91
fffff880`06e1bc20 00000000`76e6144a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`016eb6d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e6144a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiRelinkStandbyPage+c6
fffff800`02f2ae56 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiRelinkStandbyPage+c6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1a_8884_VRF_nt!MiRelinkStandbyPage+c6

BUCKET_ID:  X64_0x1a_8884_VRF_nt!MiRelinkStandbyPage+c6

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

System Uptime: 0 days 0:44:42.485
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5003, fffff70001080000, 9e15, 388f000070f8}

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

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 0000000000009e15
Arg4: 0000388f000070f8

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


BUGCHECK_STR:  0x1a_5003

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f46ae6 to fffff80002ed0740

STACK_TEXT:  
fffff880`0723a9a8 fffff800`02f46ae6 : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`00009e15 : nt!KeBugCheckEx
fffff880`0723a9b0 fffff800`02eea743 : ffffffff`ffffff00 fffff880`0723aa68 00000000`00000000 ffffffff`00000000 : nt! ?? ::FNODOBFM::`string'+0x3683c
fffff880`0723aac0 fffff800`02ece82e : 00000000`00000000 00000000`74e0e818 00000000`0000f001 00000000`00004000 : nt!MmAccessFault+0x343
fffff880`0723ac20 000007fe`fd85117a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0215e298 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd85117a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+3683c
fffff800`02f46ae6 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+3683c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1a_5003_VRF_nt!_??_::FNODOBFM::_string_+3683c

BUCKET_ID:  X64_0x1a_5003_VRF_nt!_??_::FNODOBFM::_string_+3683c

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

My System SpecsSystem Spec
18 Nov 2010   #8
euckersw

Windows 7 Home Premium 64bit
 
 

Carl,

I updated/disabled all drivers you included in your post. However, while I downloaded the latest driver package from nVidia, it did not seem to update my nvstor.sys or nvstor64.sys drivers. I have searched on-line and have not found any newer versions of these drivers. Meanwhile I am still getting BSODs - even more frequently than before I started to poke around into these things (about once every hour). I am concerned that these are the drivers that are causing my BSOD. Any suggestions?

I'm attaching my latest mini dumps. Thank you for your help.

-Scott
My System SpecsSystem Spec
18 Nov 2010   #9
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Your dumps from today are four error codes 1A and one error code 7E. All indicate or blame memory corruption. I do see that your have gotten rid of RaInfo.sys and the Coexant modem drivers. However, I still find these out of date drivers loaded on your system in latest dump. I know that you tried to update the nvstor drivers. Did you uninstall LogMeIn and or Remotely Anywhere?
Quote:
lmimirr.sys Tue Apr 10 18:32:45 2007 - RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver https://secure.logmein.com/US/home.aspx. RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver https://secure.logmein.com/US/home.aspx

LMIRfsDriver.sys Mon Jul 14 12:26:56 2008 - RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver https://secure.logmein.com/US/home.aspx. Completely uninstall LogMeIn. This version is obsolete and not compatible with Win 7. After you uninstall this version and get your system stable, you can try an updated version if it is compatible with Win 7.

nvstor.sys Wed May 20 02:45:37 2009 - nVidia Storage Drivers Drivers - Download NVIDIA Drivers. Update this driver.

nvstor64.sys Mon Jun 22 18:23:37 2009 - nVidia Storage Driver (nForce chipset driver) Drivers - Download NVIDIA Drivers. Update this driver. There is a later version available.
I would like for you to run Memtest from a cold boot after your computer has been off for a while. Let it run for at least seven passes. Can you boot in the Safe mode without getting BSOD's? Are you running a RAID array?

Regarding the NVidia storage drivers, here is a link that may help. Make sure you get the 64 bit.

Windows 7 Compatibility for NVIDIA Storage Management Software version 1.00: NVIDIA. Drivers, Updates, Downloads

Check this Google search: nvidia storage driver windows 7 - Google Search
My System SpecsSystem Spec
18 Nov 2010   #10
euckersw

Windows 7 Home Premium 64bit
 
 

Quote   Quote: Originally Posted by CarlTR6 View Post
Your dumps from today are four error codes 1A and one error code 7E. All indicate or blame memory corruption. I do see that your have gotten rid of RaInfo.sys and the Coexant modem drivers. However, I still find these out of date drivers loaded on your system in latest dump. I know that you tried to update the nvstor drivers. Did you uninstall LogMeIn and or Remotely Anywhere?
Ok, not sure why those drivers are still popping up as I did indeed uninstall LogMeIn, but since the program is gone, I renamed the lmimirr.sys and LMIRfsDriver.sys to lmimirr.bak and LMIRfsDriver.bak, so they shouldn't be loading anymore.

Quote:
Regarding the NVidia storage drivers, here is a link that may help. Make sure you get the 64 bit.

Windows 7 Compatibility for NVIDIA Storage Management Software version 1.00: NVIDIA. Drivers, Updates, Downloads

Check this Google search: nvidia storage driver windows 7 - Google Search
Thank you for the links, but they don't provide any updated drivers. I've scoured the Internet and can't find any good details on these drivers. I believe I have the newest version of the drivers. Is there any way to get around using these particular drivers? I am not running a RAID.

I'll try running in Safe Mode tonight and see if the system stays up overnight. While I already ran Memtest for six passes without any errors, I will try running it from a cold boot tomorrow morning and leave it running while I'm at work (that should allow for seven passes).
My System SpecsSystem Spec
Reply

 BSOD Help Please




Thread Tools



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 20:41.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App