Multiple random BSODs

Hello, I have a new MSI GT70 2OD, and I've experienced multiple BSODs in the few days that I have had it. It may help to know that I purchased this computer with installments from HDIevolution: HARD DRIVE: Super RAID v2 768GB mSATA SSD (3 x 256GB Plextor M5M mSATA SSD) + 1TB 5400RPM Hard Drive - installed by HIDevolution; CPU: 4th Generation Intel® CoreTM i7-4930MX Extreme Processor, 3.0 GHz (Max Turbo Frequency 3.9GHz), 8MB Smart Cache - installed by HIDevolution

The computer came installed with Windows 8. I promptly upgraded to Windows 8.1; however, the first BSOD came before the upgrade. I installed and ran Driver Reviver to make sure the drivers were up to date, and I updated all of the drivers it suggested. Driver Reviver caused a DRIVER_OVERRAN_STACK_BUFFER when it attempted to update one of the drivers for Killer Wireless. I manually updated that driver, and that particular BSOD is no longer an issue.
I have had multiple SYSTEM_SERVICE_EXCEPTION, a kmode exception and an unexpected kernel mode trap. The most recent BSOD occured while running a game, but they seem to come at random times.

I am not very familiar with PCs, or computers in general. This is also my first time using the forums, so please bear with me and let me know if I can assist in any way to diagnose this reoccurring problem.

Hi,

Use Killdisk to wipe the drive clean then install Windows.

You have nasty rootkit. I recommend not to install Norton after.

rikvm_38F51D56 rikvm_38F51D56.sys Mon May 14 03:49:40 2012 (4FB0B914)

Change passwords to everything locally, even on other machines and internet passwords too.

Thank you for your help! I downloaded Killdisk Pro and I attempted to run it. I encountered an error saying that it cannot write to certain sectors, but if I click abort for those sectors it continues to work. When it was around 96% complete I got another blue screen: HAL_INITIALIZATION FAILED. I'm currently running Killdisk again, hopefully this time without the blue screen. Is there anything else I should be doing?

No. Killdisk. It runs in DOS not Windows.

The instructions are on the linked page under "Booting into DOS from a USB Disk"

Good news and bad news (I think). Bad news: I attempted multiple times to run Killdisk in DOS, but I could never get it to boot into DOS properly despite following instructions (It could be an error on my part). Anyway, I was determined to somehow do a complete re-installation so I tried doing a Windows reset, but I couldn't get that to work either (I can't create a recovery drive, it says files are missing and I do not have a hard copy of Windows, nor am I in a place where I can easily purchase one). I tried various methods, but I could never re-install or even do a refresh (apparently Windows 8.1 digital upgrades have had this problem).

Anyway, on to the (hopefully) good news. I stumbled across another thread here posted around the same time as mine and you diagnosed the problem with the same malware: "rikvm_38F51D56 rikvm_38F51D56.sys Mon May 14 03:49:40 2012 (4FB0B914)" I also read that the poster found a solution via checking "beta" on the nvidia driver updater. I also have this nvidia driver, and did not have the "beta" checked, so I checked it with nothing to lose. So far, after being on my computer several hours today trying unsuccessfully to wipe it clean, no BSOD. Now, I was curious that we had the exact same malware, both on brand new computers, so a quick google search brought up this: http://community.norton.com/t5/Norton-Internet-Security-Norton/Is-this-a-virus-RIKVM-38F51D56-SYS/td-p/824762 if you visit that link (sorry that it's norton, I get a sense you despise them), and scroll to the bottom, you'll see a reply from CyberLink confirming that the alleged malware is a legitimate part of CyberLink, which came installed on my computer.

I did uninstall norton from my computer as per your suggestion. After checking that out, are you sure that I have malware? What steps would you advise me to take from here? If I should go ahead with Killdisk, or something of the sort, I may need childproof instructions, because apparently I'm incapable. Thanks again for your help!

Really want to use Killdisk. Anything else is stepping in line to be setup for failure. You're welcome.

Check motherboard manual for how to boot to a USB device.

First, I apologize for the week delay. I hope it is okay to post here rather than starting another thread. I attempted multiple times to run killdisk and could never get it to boot.
As an alternative, I sought help from an anti-virus community, and although they determined I didn't have a rootkit (they could be wrong), the blue screens are still persistent. I could not successfully run killdisk, but I did manage to get a hard copy of windows 8.1 and did a clean install. Despite the clean install, I still get irregular blue screens. I have tried operating on clean boot, and even then I had a blue screen. Perhaps it's hardware related. As I mentioned, I did have upgrades before receiving the computer. You may have been right all along about the rootkit, but please check these most recent logs that have accumulated since the clean install of windows. I will follow your suggestions to the best of my ability (even if it means giving my frustrations with killdisk another go).

Of course I was right about the rootkit. I clearly showed it above. ????

It seems to have been removed with your clean install of Windows, so you might have lucked out. (I certainly would not trust the machine in this state, for my own personal use - because simple software Kildisk has not been used.)

You need to fix Killer Gaming LAN lke this: MSI USA

I followed the instructions to fix the Killer Gaming LAN, which seemed to help some. I left my computer running for nearly an entire day, but another crash did eventually happen. I attached a new file, which also contains the most recent crash. Thank you for your continued support!

EDIT: Now that I'm using it, I just had another crash too. It was odd because it shut down very quickly and didn't seem to leave a dump file. Regardless I replaced the file with a new one after the most recent crash.

Advice is the same as it has been, and that's not going to change at all: Use Killdisk, install Windows.

We can check RAM for good measure. You can attach a screenshot of CPU-Z 1st tab, one of Memory tab and one each for each stick of RAM of the SPD tab.

I will try to run Killdisk this weekend. As you said though, for good measure, I downloaded CPU-Z and attached the images. I wasn't sure about the SPD tab, but I just took a screenshot of every "slot". I hope that is correct.

Yep. Memory looks good. I would however, just for further good measure, set the VDIMM to 1.45v - standard is 1.5v and your modules are designed to run at 1.35v but you have a large amount of memory - so 1.45v will help ensure it gets the power it needs.

...and then it all goes back to Killdisk.

Best of luck with it.

After much struggle, I finally successfully ran Killdisk. I re-installed Windows 8.1 and manually updated all of the drivers that I could find to the latest ones. I also fixed the Killer Gaming LAN like you suggested. I'm not sure how to set the VDIMM though.
I've only used the computer for a couple of hours since running Killdisk, so no blue screens yet. I'll keep you updated though. Any further suggestions in the meantime?

kseoul said:

I've only used the computer for a couple of hours since running Killdisk, so no blue screens yet. Any further suggestions in the meantime?

Click to expand...

:thumb:, no.

Had my first post-Killdisk blue screen.

kseoul said:

Had my first post-Killdisk blue screen.

Click to expand...

It's caused by Killer wireless driver. Personally, with extreme amount of issues Killer (Qualcomm) has been having with this brand/marl, I'd ditch the adapter and get something else.



I would disable from startup:

Killer Network Manager c:\windows\installer\{7411487a-ff21-481e-ab53-bf27ff30e042}\networkmanager.exe_130c27d738f34c89bddf21bcfd74b56d.exe -minimize Public Common Startup

I would prefer to swap the adapter, but I'm out of the country so it would be too difficult.
I have Killer Network Manager disabled from startup in task manager, but if I look in msinfo32 startup programs, I can still see the file you mentioned. I found a solution in another thread to find the file and change the .exe to .BAD, so I changed the .exe after the networkmanager part to .BAD

Is there anything else I should do?

As you can see, MasterChief was banned. I'll try and take over from this point on. Excuse me if I repeat anything that was said previously.

Where did you get the instructions on disabling network manager.
If it was one of my posts, I'd suggest that you wait and see if the system still gives problems.
If it does, post another copy of the report collection logs and we'll move on from there.

Thank you so much. I still have persisting crashes, so let's consider this a fresh start then. I'll try to give you a complete picture, hopefully some of this information helps:
I recently purchased an MSI GT70 2OD with a few upgrades from a company called HIDevolution (as you can see in my first post).
I was having crashes from the first day. When I got the computer, I immediately started downloading all of the applications I wanted and upgraded from Windows 8 to 8.1. As a new PC user, I had no idea that there was a recommended method to upgrade on MSI's website, or that I was supposed to create a recovery disk before any of the upgrades. I came here hoping to find a solution and MasterChief spotted a rootkit virus and recommended using Killdisk. I am not great with computers, and could never figure out how to use it properly, so instead I visited an anti-malware forum that determined, after many tests, that my computer is healthy and they can't help me beyond that.
I returned here and (finally) successfully ran Killdisk. Even after Killdisk and a fresh install of Windows 8.1, I am still experiencing frequent crashes. MasterChief pointed to the Killer Network drivers, and I think a majority, if not all, of the crashes are caused by them. I disabled "InstallShield" from the Startup of Task Manager and "Qualcomm Atheros Killer Service V2" and "ZAtheros Bt and Wlan Coex Agent" from the System Configuration services. However, the file that MasterChief put in his last message is still visible in the Starup Programs from msinfo32. I originally tried what I said in my last post (it was a method I found from one of your posts), but I still had crashes, so I have since re-installed the KillerSuite, and the file I tampered with is back to normal.
It may also be worth noting that I tried a method from the MSI forums to install just the naked drivers without the KillerSuite, which apparently works for some people, but I still had crashes, so I recently switched back to the latest version of the KillerSuite.

The attachment includes all of the crashes since running Killdisk (many have happened since my last post)


EDIT: Update- While attempting to play a game the computer crashed 3 times in an hour. I attached a new log with the latest 3 crashes.

MO3v2Driver MO3v2Driver.sys Sun Nov 21 21:20:58 2010 (4CE9D38A)