Overclock.net › Forums › Software, Programming and Coding › Other Software › MSI causing BSOD
New Posts  All Forums:Forum Nav:

MSI causing BSOD

post #1 of 8
Thread Starter 
Minidump2.zip 42k .zip file

Getting BSOD every time I start it. Can't explain why...

It says that "rtcore64.sys" is the cause. I searched on google and got nothing.

Version is 2.2.0 Beta 15 BTW.
I will try with official version. I hadn't problem last time I used and it was beta 12 I think.
Edited by Just a nickname - 4/20/12 at 7:30pm
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-4790k MSI Z97 Gaming 5 Sapphire R9 290X Tri-X 2x8gb ADATA 2133MHz CL10 
Hard DriveCoolingOSKeyboard
Mushkin 1 TB SSD & Samsung F3 spinpoint 1 TB MCP655A + 2 x MCP320 + EK supreme copper Win10 Corsair K70 Lux 
PowerCaseMouse
Corsair 750W Bitphenix Monstrous water cooling case Logitech G9X 
  hide details  
Reply
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-4790k MSI Z97 Gaming 5 Sapphire R9 290X Tri-X 2x8gb ADATA 2133MHz CL10 
Hard DriveCoolingOSKeyboard
Mushkin 1 TB SSD & Samsung F3 spinpoint 1 TB MCP655A + 2 x MCP320 + EK supreme copper Win10 Corsair K70 Lux 
PowerCaseMouse
Corsair 750W Bitphenix Monstrous water cooling case Logitech G9X 
  hide details  
Reply
post #2 of 8
Thread Starter 
Even official version makes me crash (2.2.0).

Crappy stuff frown.gif
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-4790k MSI Z97 Gaming 5 Sapphire R9 290X Tri-X 2x8gb ADATA 2133MHz CL10 
Hard DriveCoolingOSKeyboard
Mushkin 1 TB SSD & Samsung F3 spinpoint 1 TB MCP655A + 2 x MCP320 + EK supreme copper Win10 Corsair K70 Lux 
PowerCaseMouse
Corsair 750W Bitphenix Monstrous water cooling case Logitech G9X 
  hide details  
Reply
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-4790k MSI Z97 Gaming 5 Sapphire R9 290X Tri-X 2x8gb ADATA 2133MHz CL10 
Hard DriveCoolingOSKeyboard
Mushkin 1 TB SSD & Samsung F3 spinpoint 1 TB MCP655A + 2 x MCP320 + EK supreme copper Win10 Corsair K70 Lux 
PowerCaseMouse
Corsair 750W Bitphenix Monstrous water cooling case Logitech G9X 
  hide details  
Reply
post #3 of 8
Hi smile.gif

RTCore64.sys is the RivaTuner / EVGA Precision / MSI Afterburner driver for 64bit systems, while RTCore32.sys would be 32bit! MSI Afterburner is known to cause some issues in certain systems, specifically systems running W7 (which you are).

I would recommend trying an earlier version than the latest or beta, I've read a lot of issues lately with the latest version of MSI AB. If that doesn't help, it may be an issue with your overclock and how Afterburner is trying to interpret it. For example, if you have MSI AB setup on start up to automatically adjust clocks to what you have them set to, so you don't have to do it after every boot, just a possible cause that I've seen before.

Also, make sure you have unofficial overclocking & all that jazz disabled in the CFG file for MSI AB. It's been a long time since I've used MSI AB, so I'm sorry that I cannot provide any extra information.

I noticed it's a verifier enabled crash dump, so good call on enabling that! thumb.gif

If you have any other questions or concerns, let me know.

Dump for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\BSOD\Downloads\042012-20234-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\MS Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`01c01000 PsLoadedModuleList = 0xfffff800`01e46670
Debug session time: Fri Apr 20 22:10:45.558 2012 (UTC - 4:00)
System Uptime: 0 days 0:07:04.105
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 118, fffffa80088d7360, fffff8800947d122}

Unable to load image \??\E:\Program Files (x86)\MSI Afterburner\RTCore64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RTCore64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTCore64.sys
Probably caused by : RTCore64.sys ( RTCore64+1122 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 0000000000000118, Handle value being referenced.
Arg3: fffffa80088d7360, Address of the current process.
Arg4: fffff8800947d122, Address inside the driver that is performing the incorrect reference.

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


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  MSIAfterburner

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800021073dc to fffff80001c7dc40

STACK_TEXT:  
fffff880`0983c5c8 fffff800`021073dc : 00000000`000000c4 00000000`000000f6 00000000`00000118 fffffa80`088d7360 : nt!KeBugCheckEx
fffff880`0983c5d0 fffff800`0211cae4 : 00000000`00000118 fffffa80`088d7360 00000000`00000002 00000000`00000001 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0983c610 fffff800`01ed5210 : fffff880`0983c740 fffff880`0983c840 00000000`00000000 00000000`00000000 : nt!VfCheckUserHandle+0x1b4
fffff880`0983c6f0 fffff800`01f58375 : 00000000`00000000 00000000`000f001f 00000000`00000000 fffff800`02112c00 : nt! ?? ::NNGAKEGL::`string'+0x212ce
fffff880`0983c7c0 fffff800`0211c878 : 00000000`00000004 00000000`00000002 fffff880`0983c8b0 fffff800`01c79470 : nt!ObReferenceObjectByHandle+0x25
fffff880`0983c810 fffff880`0947d122 : 00000000`bf9e0000 00000000`00000002 00000000`00000004 fffff800`01f98a97 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`0983c860 00000000`bf9e0000 : 00000000`00000002 00000000`00000004 fffff800`01f98a97 fffff880`0983c8e8 : RTCore64+0x1122
fffff880`0983c868 00000000`00000002 : 00000000`00000004 fffff800`01f98a97 fffff880`0983c8e8 00000000`00000000 : 0xbf9e0000
fffff880`0983c870 00000000`00000004 : fffff800`01f98a97 fffff880`0983c8e8 00000000`00000000 fffffa80`088830d8 : 0x2
fffff880`0983c878 fffff800`01f98a97 : fffff880`0983c8e8 00000000`00000000 fffffa80`088830d8 fffff800`0211fbcc : 0x4
fffff880`0983c880 fffff800`02123c16 : fffff980`614b0ee0 fffff980`614b0ee0 fffffa80`0603c2c0 fffffa80`04a22f18 : nt!IopXxxControlFile+0x607
fffff880`0983c9b0 fffff800`01f98a97 : fffffa80`0603c2c0 fffff880`0983cca0 fffffa80`0603c2c0 fffffa80`08617d30 : nt!IovCallDriver+0x566
fffff880`0983ca10 fffff800`01f992f6 : fffffa80`088d7360 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`0983cb40 fffff800`01c7ced3 : fffffa80`088d7360 00000000`00000001 fffffa80`0608c5a0 fffff800`01f754f4 : nt!NtDeviceIoControlFile+0x56
fffff880`0983cbb0 00000000`751a2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008ec08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x751a2e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
RTCore64+1122
fffff880`0947d122 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  RTCore64+1122

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RTCore64

IMAGE_NAME:  RTCore64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e661112

FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_RTCore64+1122

BUCKET_ID:  X64_0xc4_f6_VRF_RTCore64+1122

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

post #4 of 8
Thread Starter 
Well it is a fresh install, everything is stock beside the CPU and I don't see how the CPU could do anything in this.
I will try earlier MSI version. I was sure though I had the 2.2.0 Beta 12 previously and it was working (could be 2.1 too, couldn't say). tongue.gif

Oh my god why do I have so many crash lately? I think I am due for a fresh windows install. frown.gif
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-4790k MSI Z97 Gaming 5 Sapphire R9 290X Tri-X 2x8gb ADATA 2133MHz CL10 
Hard DriveCoolingOSKeyboard
Mushkin 1 TB SSD & Samsung F3 spinpoint 1 TB MCP655A + 2 x MCP320 + EK supreme copper Win10 Corsair K70 Lux 
PowerCaseMouse
Corsair 750W Bitphenix Monstrous water cooling case Logitech G9X 
  hide details  
Reply
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-4790k MSI Z97 Gaming 5 Sapphire R9 290X Tri-X 2x8gb ADATA 2133MHz CL10 
Hard DriveCoolingOSKeyboard
Mushkin 1 TB SSD & Samsung F3 spinpoint 1 TB MCP655A + 2 x MCP320 + EK supreme copper Win10 Corsair K70 Lux 
PowerCaseMouse
Corsair 750W Bitphenix Monstrous water cooling case Logitech G9X 
  hide details  
Reply
post #5 of 8
I doubt this is a CPU related issue since it's pointing right to MSI AB, and I know how that program behaves at times.
post #6 of 8
Thread Starter 
Well no way to get older version. Download link was updated sad-smiley-002.gif

Ah damn I need FPS monitor to see how high I need to overclock...! Thanks anyway mate thumb.gif
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-4790k MSI Z97 Gaming 5 Sapphire R9 290X Tri-X 2x8gb ADATA 2133MHz CL10 
Hard DriveCoolingOSKeyboard
Mushkin 1 TB SSD & Samsung F3 spinpoint 1 TB MCP655A + 2 x MCP320 + EK supreme copper Win10 Corsair K70 Lux 
PowerCaseMouse
Corsair 750W Bitphenix Monstrous water cooling case Logitech G9X 
  hide details  
Reply
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-4790k MSI Z97 Gaming 5 Sapphire R9 290X Tri-X 2x8gb ADATA 2133MHz CL10 
Hard DriveCoolingOSKeyboard
Mushkin 1 TB SSD & Samsung F3 spinpoint 1 TB MCP655A + 2 x MCP320 + EK supreme copper Win10 Corsair K70 Lux 
PowerCaseMouse
Corsair 750W Bitphenix Monstrous water cooling case Logitech G9X 
  hide details  
Reply
post #7 of 8
Thread Starter 
Oh and could you check this please?
Still haven't figured what is causing the crash!

http://www.overclock.net/t/1245612/what-is-that-bsod#post_17021779
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-4790k MSI Z97 Gaming 5 Sapphire R9 290X Tri-X 2x8gb ADATA 2133MHz CL10 
Hard DriveCoolingOSKeyboard
Mushkin 1 TB SSD & Samsung F3 spinpoint 1 TB MCP655A + 2 x MCP320 + EK supreme copper Win10 Corsair K70 Lux 
PowerCaseMouse
Corsair 750W Bitphenix Monstrous water cooling case Logitech G9X 
  hide details  
Reply
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-4790k MSI Z97 Gaming 5 Sapphire R9 290X Tri-X 2x8gb ADATA 2133MHz CL10 
Hard DriveCoolingOSKeyboard
Mushkin 1 TB SSD & Samsung F3 spinpoint 1 TB MCP655A + 2 x MCP320 + EK supreme copper Win10 Corsair K70 Lux 
PowerCaseMouse
Corsair 750W Bitphenix Monstrous water cooling case Logitech G9X 
  hide details  
Reply
post #8 of 8
Sure! I'll check it out now smile.gif
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Other Software
Overclock.net › Forums › Software, Programming and Coding › Other Software › MSI causing BSOD