Windows 7 - Help BSOD's are back.

notyuh · 10-19-2010

I had an issue with BSOD's a few months back, in the end I did a reinstall using all new drivers and this cured the problem.

I haven't changed anything since but from out of the blue they have started again can someone please help me.

I thank you all for being so kind in advance.

The dumps are attached.

zigzag3143 · 10-19-2010

Quote: Originally Posted by notyuh

I had an issue with BSOD's a few months back, in the end I did a reinstall using all new drivers and this cured the problem.

I haven't changed anything since but from out of the blue they have started again can someone please help me.

I thank you all for being so kind in advance.

The dumps are attached.

These crashes point to several causes. Your video driver and a HD emulation package (daemon tools/alcohol), memory corruption.

I would remove the HD emulation package.

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

Second reinstall your video driver.
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

Also run a system file check

SFC /SCANNOW Command - System File Checker

Finally run a memory test as several crashes show memory corruption

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.

Let us know if you need further assistance

Ken J

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\New folder\090610-24788-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a1c000 PsLoadedModuleList = 0xfffff800`02c59e50
Debug session time: Mon Sep  6 09:03:52.510 2010 (GMT-4)
System Uptime: 0 days 0:09:27.570
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 1E, {ffffffffc0000005, fffff80002ab335f, 0, ffffffffffffffff}

Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ab335f, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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!MiReplenishPageSlist+100
fffff800`02ab335f f00fba6b1000    lock bts dword ptr [rbx+10h],0

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc40e0
 ffffffffffffffff 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  Hearts.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002acda17 to fffff80002a8df00

STACK_TEXT:  
fffff880`0a2e8f28 fffff800`02acda17 : 00000000`0000001e ffffffff`c0000005 fffff800`02ab335f 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a2e8f30 fffff800`02a8d542 : fffff880`0a2e9708 05fffa80`00176610 fffff880`0a2e97b0 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x460da
fffff880`0a2e95d0 fffff800`02a8be4a : fffffa80`03402870 fffffa80`03342870 00000000`00000002 00000000`00000005 : nt!KiExceptionDispatch+0xc2
fffff880`0a2e97b0 fffff800`02ab335f : ffffffff`ffffffff 00000000`00000001 00000000`00000000 fffffa80`00190fe0 : nt!KiGeneralProtectionFault+0x10a
fffff880`0a2e9940 fffff800`02ab388f : fffff800`02cc6400 00000000`000000cb fffffa80`0017c610 fffffa80`00179610 : nt!MiReplenishPageSlist+0x100
fffff880`0a2e99a0 fffff800`02aa927a : fffff680`000514e0 00000000`00000002 00000000`00000000 ffffffff`ffffffff : nt!MiRemoveAnyPage+0x24f
fffff880`0a2e9ac0 fffff800`02a8bfee : 00000000`00000001 00000000`03265320 fffff900`c00bf001 00000000`00000000 : nt!MmAccessFault+0x169a
fffff880`0a2e9c20 00000000`ffc36506 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0022ec50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffc36506


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiReplenishPageSlist+100
fffff800`02ab335f f00fba6b1000    lock bts dword ptr [rbx+10h],0

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!MiReplenishPageSlist+100

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1E_nt!MiReplenishPageSlist+100

BUCKET_ID:  X64_0x1E_nt!MiReplenishPageSlist+100

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

Windows 7 - Help BSOD's are back.

Help BSOD's are back. problems?