Back to BSOD

Kardinal · 30 May 2010

Hey,

So I posted here a while ago:
https://www.sevenforums.com/crashes-d...preciated.html

Having thinking I ironed out all problems relating to those BSOD episodes. I ran MemTest for 20 passes overnight and found 1 failing address around 950mb. So, I unplugged one of my 512mb Ram cards.

(long story short, I did something wrong and my PC wouldn't start up - a Startup Repair could not automatically fix the problem... so with my PC opened up, I resorted to cleaning each individual component... the amount of fluff that came out... haha)

Somehow, it decided to start working again. And I hadn't had a BSOD for a few days (since last posting, so 4).

Please could you take a look and confirm what caused this BSOD - I have replaced the RAM that was in when the BSOD happened with the one I had removed earlier just as a precaution that I had removed the RAM without the error.

The plus side is, they are now a lot less frequent. I am almost happy with a crash once every four days as opposed to 4 to 8 crashes in one day! But, regardless, I still want a crash-free computer as I do a lot of work with 3D Studio Max and game mod software - I simply don't quick-save enough :) - and losing a lot of progress due to a Bluescreen really does annoy me!

Jonathan_King · 30 May 2010

Please enable driver verifier: Using Driver Verifier to identify issues with Drivers

Code:

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


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_Kardinals Minidump #1.zip\053010-27783-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
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02855000 PsLoadedModuleList = 0xfffff800`02a92e50
Debug session time: Sun May 30 17:50:33.999 2010 (GMT-4)
System Uptime: 0 days 4:50:31.347
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

0: 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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000b9b088 -- (.exr 0xfffff80000b9b088)
Unable to load image MRVW13C.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MRVW13C.sys
*** ERROR: Module load completed but symbols could not be loaded for MRVW13C.sys
ExceptionAddress: fffff88003e022b2 (MRVW13C+0x00000000000022b2)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000b9b130 -- (.trap 0xfffff80000b9b130)
Unable to read trap frame at fffff800`00b9b130

LAST_CONTROL_TRANSFER:  from fffff800028bd32e to fffff800028c55d0

STACK_TEXT:  
fffff800`00b9a178 fffff800`028bd32e : fffff800`00b9a240 fffff800`00b9a1b0 fffff800`00b9a8f0 fffff800`028f2524 : nt!KeBugCheck
fffff800`00b9a180 fffff800`028eb2ed : fffff800`02ad3b88 fffff800`02a0ca40 fffff800`02855000 fffff800`00b9b088 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9a1b0 fffff800`028f2950 : fffff800`02a14b24 fffff800`00b9a228 fffff800`00b9b088 fffff800`02855000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9a1e0 fffff800`028ff8df : fffff800`00b9b088 fffff800`00b9a8f0 fffff800`00000000 fffffa80`01eaeb13 : nt!RtlDispatchException+0x410
fffff800`00b9a8c0 fffff800`028c4c42 : fffff800`00b9b088 9c6980ff`fffa8000 fffff800`00b9b130 00000000`00000000 : nt!KiDispatchException+0x16f
fffff800`00b9af50 fffff800`028c354a : fffffa80`01c25000 00000000`00000000 00000000`00000000 fffffa80`027f69f0 : nt!KiExceptionDispatch+0xc2
fffff800`00b9b130 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`028bd32e 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

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