BSOD (Crash info included)

[HOT97ECLIPSEGSX]

I've had several BSODs over the past month or so, and I don't believe I've installed anything out of the ordinary.

Attached is my perfmon and BSOD file per the BSOD posting thread.

My hard drive and CPU may be under load as I'm running a full system scan with MSE right now.

 

[Maguscreed]

can you please navigate to c:\windows\minidump and zip and upload whatever files may be there?

 

[HOT97ECLIPSEGSX]

There are no files!

I have my computer set to full dump and have an 8GB page file. I'm not sure how to fix this.

 

[Maguscreed]

To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header
Select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

 

[HOT97ECLIPSEGSX]

Done. I guess I'll have to wait until next time for any assistance. For some reason my full Kernel dumps were not working.

 

[Maguscreed]

well others might have a go on what you have, I personally prefer the minidumps they give me a better picture of the machine.

 

[HOT97ECLIPSEGSX]

Thanks. If anyone else has any ideas as to the cause with the attached information please let me know.

 

[Maguscreed]

If you are feeling impatient you can try this to force a bsod

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html
(Please read all instructions for driver verifier before using as it's possible it will make the machine behave badly and you need to know how to undo it.)

 

[HOT97ECLIPSEGSX]

Thanks. I hope you didn't read into my response as being impatient. I'm grateful for forums like this and appreciate any and all help towards solving my problem.

 

[MvdB]

You could have a look at your Malcode Analyzer. It is mentioned in quite a few errors in your log. Delete it or be sure it fits your system..

Also, looks like you are OC-ing.... if so, set back to default just to be sure that's not it...

But, as Magnus said... we need the dumps to be sure....

 

[HOT97ECLIPSEGSX]

Okay, after "forcing" the computer to BSOD, I have a dump for you. From what I gathered on the screen when I saw it, I see it was caused by Core Temp 64. I know this is a known program for monitoring CPU temps. I just uninstalled and reinstalled before I "forced" the BSOD.

I remember reading that something was trying to corrupt system files, or change a system driver, or something like that.

EDIT: I haven't reported this, but a month ago or so I lowered my processor back to 3.0 from 3.5. Still getting the same BSODs.

 

[HOT97ECLIPSEGSX]

Here's another BSOD.

 

[MvdB]

The first one was cause bij RTCore64... normally a part of MSI Afterburner....

Please delete / uninstall Afterburner and check that RTCore64 is gone and test for BSOD's.

If you have the right version of MSI Afterburner.... it shouldn't be a problem but your's certainly is...

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 00000000000000fc, Handle value being referenced.
Arg3: fffffa8009e5b5e0, Address of the current process.
Arg4: fffff880088dd522, Address inside the driver that is performing the incorrect reference.

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


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  MSIAfterburner

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000311f3dc to fffff80002c98d00

STACK_TEXT:  
fffff880`074975a8 fffff800`0311f3dc : 00000000`000000c4 00000000`000000f6 00000000`000000fc fffffa80`09e5b5e0 : nt!KeBugCheckEx
fffff880`074975b0 fffff800`03134ae4 : 00000000`000000fc fffffa80`09e5b5e0 00000000`00000002 00000000`00000001 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`074975f0 fffff800`02eedab0 : 00000000`00000000 fffff880`07497820 00000000`00000000 00000000`00000000 : nt!VfCheckUserHandle+0x1b4
fffff880`074976d0 fffff800`02f72a75 : 00000000`00000000 00000000`000f001f 00000000`00000000 fffff800`02f72a00 : nt! ?? ::NNGAKEGL::`string'+0x2164e
fffff880`074977a0 fffff800`03134878 : 00000000`00000004 00000000`00000002 fffff880`07497890 fffff800`02c94530 : nt!ObReferenceObjectByHandle+0x25
fffff880`074977f0 fffff880`088dd522 : 00000000`fd000000 00000000`00000002 00000000`00000004 fffff800`00000000 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`07497840 00000000`fd000000 : 00000000`00000002 00000000`00000004 fffff800`00000000 fffff880`074978c8 : RTCore64+0x1522
fffff880`07497848 00000000`00000002 : 00000000`00000004 fffff800`00000000 fffff880`074978c8 00000000`00000000 : 0xfd000000
fffff880`07497850 00000000`00000004 : fffff800`00000000 fffff880`074978c8 00000000`00000000 fffff800`02fb3127 : 0x2
fffff880`07497858 fffff800`00000000 : fffff880`074978c8 00000000`00000000 fffff800`02fb3127 fffff800`02fb3127 : 0x4
fffff880`07497860 fffff880`074978c8 : 00000000`00000000 fffff800`02fb3127 fffff800`02fb3127 fffffa80`09098010 : 0xfffff800`00000000
fffff880`07497868 00000000`00000000 : fffff800`02fb3127 fffff800`02fb3127 fffffa80`09098010 fffff800`02fb3127 : 0xfffff880`074978c8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
RTCore64+1522
fffff880`088dd522 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  RTCore64+1522

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RTCore64

IMAGE_NAME:  RTCore64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  42941d90

FAILURE_BUCKET_ID:  X64_0xc4_f6_RTCore64+1522

BUCKET_ID:  X64_0xc4_f6_RTCore64+1522

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

2: kd> lmvm RTCore64
start             end                 module name
fffff880`088dc000 fffff880`088e2000   RTCore64 T (no symbols)           
    Loaded symbol image file: RTCore64.sys
    Image path: RTCore64.sys
    Image name: RTCore64.sys
    Timestamp:        Wed May 25 08:39:12 2005 (42941D90)
    CheckSum:         00004158
    ImageSize:        00006000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[HOT97ECLIPSEGSX]

So MSI Afterburner is causing my PC to crash? I have the latest version of the software. Another one of my BSOD threads a member had told me to delete the program. I use it solely to monitor GPU temps and modify fan speed based off of temp. If there is an (free) alternative program please let me know.

 

[MvdB]

So MSI Afterburner is causing my PC to crash? I have the latest version of the software. Another one of my BSOD threads a member had told me to delete the program. I use it solely to monitor GPU temps and modify fan speed based off of temp. If there is an (free) alternative program please let me know.

Let's see if you have no more BSOD's after removing.. first?

I'm not sure yet if it is the only problem... sometimes Afterburner comes up as the problem when, actually, faulty old video drivers are the real reason... so we need to make sure that you have both the right and latest version of afterburner or something like it but ALSO the right video drivers for your card...

 

[HOT97ECLIPSEGSX]

I installed the latest video drivers directly from Nvidia today. I know they are current.

Should I set the verifier back on and see if I get any more BSODs?

 

[MvdB]

I installed the latest video drivers directly from Nvidia today. I know they are current.

Should I set the verifier back on and see if I get any more BSODs?

Yes, after removing Afterburner. Please check that the driver is really gone or use Driversweeper in Safemode to be sure....