*** The Official MSI GT75 Owners and Discussions Lounge ***

Yes I have this issue too. It is a bug within the program and the button.

It happens with my Razer Synapse program on other laptops or my Logitech program as well.

It's quite common, they suck at programming.

Restart your WiFi router. It has happened to me.

My partner and my computer could not view the same websites. But totally fine on VPN and totally fine on my iPhone on 4G. We restarted the WiFi and that refreshed some stuff and it worked right after.

When I mean restart WiFi, I mean unplug and wait 30s and reopen.

 

You can blame Killer for that.
I guess your wifi is Intel 8265?

 

Negative. I had the modem/router completely unplugged for 5 minutes.
LAN is Aquantia AQtion 10Gbit Network Adapter
WIFI is Killer Wireless-n/a/ac 1535 Wireless Network Adapter

 

Yes both my partner and me are on Killer.

 

Wait, the GT75VR comes with THAT LAN NIC?
......................

The website says:

Killer MultiGiG 10Gbps LAN

This isn't the same LAN that's in the GT73VR?

......looks like someone has some buggy drivers or something. And I guess the Microsoft basic LAN drivers won't save you this time....(if they even work).

 

Yes it does.

It is on the Aquantia. The drivers are also for Aquantia.

https://www.msi.com/Laptop/support/GT75VR-7RF-Titan-Pro#down-driver&Win10 64

 

seems to be working fine on the wifi, but I certainly prefer the wired connection. i'm not really sure what the issue is. my router is a netgear C3700-100NAS, but I really don't think that is the issue, since it is only impacting this PC - unless it is somehow getting blocked by MAC address, either at the router level, or at the actual websites themselves - since it seems to work on every other device / connection.

 

That's weird, but curious it's related to Killer products, and Wired only.

If you have the full Killer Suite installed try running the installer again and uncheck the apps / features you don't need (all but the drivers), and reboot and see if that fixes it.

Or, try the Drivers Only installer after uninstalling the whole Killer Suite.

 

Still can't find those. It says "No valid crash dumps have been found on your computer"

Ok, i'll give it a try as soon as I can.

 

Did you disable Windows VM, deleting the Pagefile.sys? You need at least a 800MB-1GB pagefile to hold the crash dump before they are copied to the disk. Not sure about what Windows 10 needs...

Here are some instructions for Windows 10:

How to solve Windows 10 crashes in less than a minute.

How to get a complete memory dump in Windows 10

How to Configure Windows 10 to Create Dump Files on BSOD?

Enabling a Kernel-Mode Dump File

 

I've already followed those steps (see the previous screenshots) but still there's no Minidumps in Windows directory.

Dunno how to disable windows VM or how to delete Pagefile.sys.

 

Did you check to see if pagefile is enabled? The steps I posted shows the area to check

Having no pagefile is about the only other thing that can stop dumps from working, besides the other steps enabling dumps.

The section is under "Performance" in this dialog:


How to set paging file to a fixed size to avoid its fragmentation in Windows XP, Vista, 7, 8, 8.1 and 10

Dumps go to different places:

" Windows 10 can produce five types of memory dump files, each of which are described below.

• Automatic Memory Dump. Location:%SystemRoot%\Memory.dmp. ...
• Active Memory Dump. Location: %SystemRoot%\Memory.dmp. ...
• Complete Memory Dump. Location: %SystemRoot%\Memory.dmp. ...
• Kernel Memory Dump. ...
• Small Memory Dump (a.k.a.

...check page 3 of this 9 page article for types and locations, read the rest of the article for debugging info:

How to solve Windows 10 crashes in less than a minute.

 

Also, I wonder if one of the tools used to block MS stuff might enable some kind of registry or other active blocking of dumps, for privacy / security reasons... something else to check - your O&O ShutUp10 settings, and any other tools for blocking Windows 10 cruft.

 

I think O&O one stops transfers of data. It still allows creation of page dump.


Sent from my iPhone using Tapatalk

 

This is on a clean install of windows with the drivers only and no killer suite. I didnt install the killer suite after I reinstalled just to test if that was an issue. It still happening. :-(

 

I've checked page 3 but there's nothing new. The rest of this article is more for advanced users I believe and I'm not. It's hard enough when english is'nt your native language .
I think I did everything I could with my current knowledge... dunno where I messed up.

 

So your pagefile shows as enabled? On which volume(s) is there a pagefile? Is it fixed sized or dynamic - sized on the fly by the system?

 

I'll show you with a screen, it will be a lot easier that way I think. Don't hesitate to tell me if this was'nt what you wanted to see. Again, thanks a lot hmscott, you're always here to help me .

edit: Everything is on default. In one of the link you sent me it says "these instructions are meant for hard disk drives (HDD) and hybrid drives (SSHD) only! Paging files on SSD-s must be automatically managed to prevent decreasing the lifetime of the drives." I did'nt wanted to mess up with thoses settings.

 

That's good, what does your Startup and Recovery dialog look like? Which memory dump type from the popup menu is selected? How much free space do you have available on your C partition?

You need to have enough free space on the root file system, where the pagefile resides, for the dump file to be written, and depending on what you've asked to have dumped, it could be a very large file up to Total RAM + 1MB, which could be much larger than most people have free on their boot SSD...16GB - 64GB free is a lot.

How much free space do you have available on your C partition?

Windows does not save memory dump file after a crash
https://support.microsoft.com/en-us/help/130536/windows-does-not-save-memory-dump-file-after-a-crash

Symptoms
When you receive a STOP error message or a fatal system error message, a Memory.dmp file may not be created.

Note Before troubleshooting the problem, make sure that the computer is correctly configured to save a crash dump file.

Cause
There are several reasons why the Memory.dmp file is not being created when your computer encounters a STOP message:

• The Memory.dmp file already exists and the option Overwrite Any Existing File (found in Control Panel System) is not selected. It is a good idea to leave this box checked and to move or copy the current Memory.dmp file.
• The paging file on the boot drive is not large enough. To use the "Write Debugging Information To" feature to obtain a complete memory dump file, the paging file on the boot drive must be at least as large as physical memory + 1 MB. When you create a kernel memory dump file, the file is usually around one-third the size of the physical memory on the system. Of course, this quantity will vary, depending on your circumstances.
• The paging file is not on the %systemroot% partition. When the STOP error occurs, the system crash dump is written out to the pagefile on the root of the %systemroot% drive.
• There is not room for the Memory.dmp file in the path specified in Control Panel for writing the memory dump.
• It is possible that the SCSI controller is bad or the system crash is caused by a bad SCSI controller board.
• If you specify a non-existent path, a dump file will not be written. For example, if you specify the path as C:\Dumpfiles\Memory.dmp and no C:\Dumpfiles folder exists, a dump file will not be written.

 

Here's mine:

I have about 330go free on my C: drive so I believe that is enough. ActuallyI've selected Kernel memory dump to give it a try, anything else is'nt working properly.

 

Finally it's working! don't ask me how,, don't ask me why...here's results of Whocrashed:

On Thu 19/10/2017 21:17:50 your computer crashed
crash dump file: C:\WINDOWS\Minidump\101917-13234-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x80C22)
Bugcheck code: 0x10D (0x7, 0x59F2AEDA9FD8, 0xFFFFA60D51256020, 0xFFFFA60D4F5FFE10)
Error: WDF_VIOLATION
file path: C:\WINDOWS\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 19/10/2017 21:17:50 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ssdevfactory.sys (ssdevfactory+0x1D87)
Bugcheck code: 0x10D (0x7, 0x59F2AEDA9FD8, 0xFFFFA60D51256020, 0xFFFFA60D4F5FFE10)
Error: WDF_VIOLATION
file path: C:\WINDOWS\system32\drivers\ssdevfactory.sys
product: SteelSeries Engine
company: SteelSeries ApS
description: SteelSeries Device Factory Driver
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ssdevfactory.sys (SteelSeries Device Factory Driver, SteelSeries ApS).
Google query: SteelSeries ApS WDF_VIOLATION




Conclusion
2 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

ssdevfactory.sys (SteelSeries Device Factory Driver, SteelSeries ApS)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Steelseries Engine? Really? Should I unninstal it to see if it's still crashing?

I believe the first one was when I was updating some drivers, I experienced a BSOD while updating.

 

Congratulations

Sure, try uninstalling it first, there may be another driver actually causing the problem - or it is by itself the problem.

Have fun

 

Ok I will unninstall it and we'll see if it crashs again and i'll keep you update for sure.

We still don't know if it causes the issue and if the lappy will be fine yet but one more time: Thank you for your support hmscott

 

Looks like you aren't the only one.

https://answers.microsoft.com/en-us...iolation/1fd8efb0-f68f-4229-831c-0717ce840359

May want to keep it uninstalled for awhile.

 

But if this is true, it means SSE caused the BSOD while updating my drivers but it's also means it was'nt linked to my rebooting issue so I guess i will soon experienced reboots again.

Edit: As expected, the system crashed again. The funny thing is there's minidumps for BSOD but not for my strange reboot.

 

Mine has been restarting very randomly and abruptly as well.

I once saw a message - Some sort of service was terminated, it restarted immediately after that and I think it had to do with XTU. FYI I unclocked my machine but had XTU sitting there. I have uninstalled XTU and will see how it goes.

I'll check and see if I can find the dump.

 

I think we should start a list of issues with the latest MSI GT75VR

1. Random and Abrupt restarts / crashes when gaming. (might be linked to XTU)
2. SteelSeries button not working after creating new profiles in SSE. (SSE program bug)
3. err_connection_timed_out with the Killer WiFi (might be linked to driver issue)

 

I had some issues with XTU as well on my GT73VR so I have unninstalled it on my GT75VR but nothing changes. Next thing I will try is a memtest then a clean install of Windows. What kind of procedure must I follow to install a clean windows? I see there's an option in Settings > Update and security >Recovery and there's an option to do a clean install.

 

Thank you for this. I'm going to stay away from 75VR line. No wonder they don't want to include it in the Trade in program because of this issues the customer might return the laptop and they can't fix this because it's already embedded in all their 75VR units.

 

Are you still getting crashes after uninstalling?

It's not that bad. It's a good and fast computer haha.

I may be doing a clean install of windows to see if the problem replicates itself.

 

It is bad for something that you paid brand new and already having this issues right out of the box but then it's probably because of Windows or drivers that is causing it so probably the best way to solve the issues is a clean installation of Windoze.

 

Well I paid a lot for my XPS15 9550 as well when it was first released. It's the most expensive model/ specification as well.

It had so many issues, don't get me started...

IMO nothing is perfect.

 

Yes it still reboot.

 

I'm not trying to argue but it's unfair for someone who paid a lot for such an expensive machine that had so many issues right out of the box and these companies are making their customers do the QC and troubleshooting for them.

Nothing is perfect sure but like I said it shouldn't have any issues right out of the box. It's acceptable to have an issue later down the road probably after a few months of use but it's not acceptable when it's brand new.

If a clean installation of Windows doesn't fix the problem then it's clear that there is something wrong with the hardware.

 

Tougher for me as mine was bought in Singapore. I am not too sure if Australia will service it if something is wrong. Especially since I've repasted it.

 

It's fine if you opened the laptop for a repaste, upgrade of RAM and storage because it's still covered with MSI warranty.

 

Is it international warranty though?

 

In reseller sites it stated that "1 Year MSI US/Canada Parts + 1 Year Global Warranty" so yes MSI laptops will have a Global/International warranty.

 

You can't be certain of that, all regions of support for vendors can vary their acceptance of user access to internal features - the warranty void sticker is taken literally by many, it's optional but enforceable if they decide so.

I always recommend registering the laptop, and opening a ticket to ask if changing storage or RAM by the user is covered under warranty, as long as we don't damage anything while the laptop is open.

If they give you a positive response, save that ticket text offline for future use.

Then open another ticket asking further if repasting and replacing thermal pads is ok, and doesn't void your warranty.

Again, if you get a positive response save that ticket offline for future use.

If you ever need to RMA the laptop, and a technitian opens it to find you've mucked around inside - repasted - they can and often will as a matter of course try to void the warranty and charge you for repairs. That's when you copy / paste the ticket that gave you permission into a new response to their accusations.

When faced with a response from support saying it was ok to do it, they then need to further prove you damaged something, so make sure you keep it clean in there when "mucking about"

It only takes a few days of back and forth tickets / emails to work this permission out ahead of time, and it's worth it in the long run.

 

Please note that 1-year is overlapped, some models have 2-year regional warranty and you can have accidental warranty plus global warranty on the 1st year, and 2nd year is just regional only.

 

I can confirm that is incorrect. MSI confirmed to me that repasting blows up your warrantly.

 

I've only got the laptop for like a month xD

That's not fun

 

For the 75VR it's only 1 year regional + 1 year global.

Sorry I wasn't trying to spread false information but this is not the case if you buy it from a reseller site e.g HIDevolution or XoticPC because they offered a upgrade/repaste/repad service which means they will open your laptop, same goes if you do it yourself and will not void the warranty.

 

Oh really? Damn! You're lucky
Mine is'nt under warrantly after only 1 day because I repaste it.

 

Re-pasting by these boutique vendors can void your warranty with the original laptop maker, instead the boutique vendor is now responsible for your repairs.

This can be a problem... so don't count on anything being fixable without charge after burning the bridge for repairs via original maker warranty.

 

Yes and I asked the reseller via chat before I upgraded/repasted/repadded/ my MSI GT80S and did not void the warranty. Too bad after 1 year of usage the laptop motherboard died (defect) so I sent it back to the reseller and they sent it to MSI for mobo replacement.

For me that is not the case, I sent the laptop to HIDevolution and they sent the laptop to MSI for mobo replacement and I asked them if I need to pay for the damage part and they said no I don't have to pay for anything since the laptop is covered with warrranty.



It could also be that HIDevolution paid the mobo replacement.

 

You can call MSI office directly to verify repaste information.

 

This for those who bought it in a local shop or online reseller. I bought mine from a reseller and asked them if it's going to void the warranty if I upgrade/repaste/repad the laptop and they said "It's fine and it will not void the warranty" so it's probably different with other resellers.

I also want to ask if GentechPC if we buy an MSI laptop from you and the user upgrade or repaste will void the warranty?

 

Normally, warranty isn't void with reapplication of thermal compound unless the PCB becomes damaged during the process. This is the same situation where users want to perform component upgrades. That being said, as long as we exercise best practice we don't get into trouble with their policies.

 

If you feel the need to be anonymous that works too

I like the direct ticket / email method so I have it on file to quote back in a dispute, it's possible to quote recorded phone calls - but that makes people uncomfortable and may create additional problems.

I have used the phone method the first few times to get a view into their thinking, and when they say it's ok I follow up repeating the same question(s) via a ticket to get the official vendor response in writing.