[SOLVED] Computer Reset loop when certain I/O drivers activate

Status
Not open for further replies.
Sep 30, 2018
13
0
20
Hi All,

Currently have a problem where some I/O devices inserted via USB cause Windows 10 to reset. This includes my wired Xbox One Controller, as well as my keyboard and mouse when Logitech Gaming Software is installed.

With the xbox one controller, after I plug it into any USB port I can see the Xbox controller appearing in device manager. The controller actually works at this point, as pressing the "Xbox" button will attempt to bring up the game bar. if I then mouse click or use my keyboard the computer will immediately reset with no BSOD but I do have a memory dump file here (zipped to 95.4 MB): https://1drv.ms/u/s!AjYbfOW_DSQ4hOY-TAmclnZJXPsSTw

There was one time I got a bsod. It was a [DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION (D6)] error caused by "xboxgip.sys", I found a very similar forum post on this exact issue a week ago (This guy also had an MSI board): http://www.tomshardware.com/forum/id-3771686/bsod.html

I know that this minidump (894kb) relates to that bsod: https://1drv.ms/u/s!AjYbfOW_DSQ4hOY-TAmclnZJXPsSTw

If I leave the xbox controller plugged in after the reset and attempt to log back in, the computer will reset before I see the desktop. I can simply stop the resets by leaving the xbox controller unplugged.

The other issue, which I think is likely related, is Logitech gaming software resetting the computer after it notices my Logitech keyboard OR Logitech mouse. When I have this software installed and log in, I'll have the desktop open for about 5 seconds before I hear the "USB input detected" sound and then the computer will crash/reset while this sound is playing. This will continue on every boot until I go into safe mode and uninstall Logitech Gaming Software.

My mouse and keyboard work fine without this software installed but without Logitech Gaming software I can't rebind the extra G-keys.

What I have tried:

  • ■Uninstalling/Reinstalling the Windows USB Drivers
    ■Updating the Bios (confirmed updated by MSI live update 6)
    ■ Removing the overclock on the CPU.
    ■ Trying different USB ports, including the front panel.
    ■ Installing MB Drivers
    ■ Performing a "Clean boot" with no other third party programs running, Xbox controller still resets PC. (followed instructions from here: https://support.microsoft.com/en-au/help/929135/how-to-perform-a-clean-boot-in-windows)
    ■ Uninstalling/Reinstalling the Windows Keyboard and mouse drivers
    ■ /sfc scannow in cmd.exe with administor which stated no issues.
    ■ Intel CPU diagnostic Scan which passed with no issues.
    ■ Tried a microsoft wireless mouse, and a different logitech keyboard, no difference.

I'm starting to lose hope on resolving this issue but want to see if I can do anything else before I reinstall Windows again. I really hope it's not a problem with my motherboard - to me signs point to some sort of I/O Driver issue.

This issue started happening on a (almost) brand new build, with also a fresh install of windows.
CPU: i7 8700k 3.7Ghz
Motherboard: MSI Z370 Gaming Plus LGA-1151-CL ATX
RAM: Corsair Vengeance LPX Black C15 3000MHz
GPU: Nvidia Geforce GTX 1070
Sound card: Asus Xonar DGX
Mouse: Logitech Proteus Core G502
Keyboard: Logitech G710+ Mechanical keyboard

 
Have you tried safe mode? That will remove the chance of it being a driver conflict

go to settings/update & security/recovery
under advanced startup, choose restart now button
choose troubleshoot
choose advanced
choose start up options
hit the restart button
choose a safe mode (it doesn't matter which) by using number associated with it.
Pc will restart and load safe mode

try to plug in USB devices that cause issues. Safe mode won't let LGS run so try the xbox controller, since those drivers should be part of win 10 already.

looks at link.. no wonder this seems familiar.

seems like a USB problem, since its not just Xbox. USB 3 drivers built into win 10, your motherboard has Intel USB controller. wonder if there are any new drivers...

Windows* 8, Windows* 8.1, and Windows® 10 have a native in-box USB 3.0 driver. Intel is not releasing a specific Intel® USB 3.0 eXtensible Host Controller Driver for Windows 8, 8.1, or 10.

https://www.intel.com/content/www/us/en/support/articles/000005537/software/chipset-software.html

So much for that thought

I found someone with exact same problem - https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_devices-insiderplat_pc/xboxgipsys-causes-irqlnotlessorequal-bsod-on/8f231367-02e8-466a-988c-3b71a9823497 - see last person in thread.

and another - https://www.reddit.com/r/Windows10/comments/98l4vq/driver_page_fault_beyond_end_of_allocation_when/

and another - https://www.windowsphoneinfo.com/threads/ntoskrnl-exe-driver_page_fault_beyond_end_of_allocation-xboxgip-sys.81989/
https://www.reddit.com/r/Windows10/comments/96afp5/windows_10_bluescreening_after_plugging_in_xbox/

seems that error follows the xbox drivers around. Looks like Microsoft are to blame here.

I don't have a fix for you, I can't see any solutions on the threads I have found or I would offer it.
 


Thanks for your help on this Colif and the extra links, it certainly is looking like a Windows and/or Intel problem, which is no good for me. What's interesting is that all these issues seem to be posted really recently, like in the past month, and the one from May was a Windows Insider build...

I plugged the Xbox controller in on Safe mode and the computer doesn't reset. The controller doesn't light up either but I can see it appearing in the device manager at the very least.

I'm prepared to try a Windows reset at this point, but there's a good chance it probably won't work with these dodgy intel/microsoft drivers.



 
I wouldn't reset yet, wait a week or so and see if the new version of win 10 due this month fixes it. You should get it as an update sometime in next 2 weeks.

That guy on insider might just prove it won't since his version number 17672 is actually a higher version than Build 1809 (due next 2 weeks) is. Build 1809 is version 17604

the bit that stands out on yours is LGS also has same problem. Are you on latest build of it? I am currently using an older build and have not had any issues that I am aware of

see if you can do this - https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/ntoskrnlexe/bb2d56a7-03ed-4892-af2c-8cf538b1c845
 


I don't seem to have KB4284848 or KB4338819. in the update uninstaller under Microsoft Windows I have the KB4458469, KB4100347, and KB4456655, and two adobe flash security updates. My Windows is up-to-date.


I tried the three most recent LGS builds (9.02.61, 9.00.42, 8.98.234). I'll have a go now at attempting to install a version from 2017 and let you know how I go.

 
I'll have a go now at attempting to install a version from 2017 and let you know how I go.
Attempting to install LGS Version 8.92.67 from April 2017 had the exact same effect as the newer versions of LGS - a crash and reset without bsod message as soon as the keyboard or mouse USB input is detected. I once again went back into safe mode to uninstall it.

I'm pretty convinced that the problem isn't a software problem with LGS and is instead a driver problem when they have to interact with an I/O device via a USB. The only I/O devices that works over USB is my Blue Yeti Microphone and Logitech G920 camera, I think because they both don't need any special drivers to work. Non-I/O devices like My external hard drive and USB sticks work fine.
 
@Colif it seems I might have been wrong about this situation being a USB problem. Resets also seem to happen when I do other things. I tried to convert my HDD from MBR to GPT using EaseUS and the computer reset when I tried to do this. I was able to convert the HDD to GPT using a command line program called gptgen.

The reason why I wanted to change the HDD to GPT is because I have Intel Optane Memory installed, and it only works with GPT drives. However, when installing the Intel Optane Memory... the blasted thing resets again. Upon loggin back the Intel Optane Memory has disabled itself.

I'm so sick of these resets, at least if it gave me a BSOD I'd know where to start looking for the problem, but it doesn't.
 


Man if plugging in a xbox controller reinstalled windows then that would be quite a bug!

Thanks for your extended help on all this Colif. Some more things have happened. I ran memtest86 and found 98 errors on the RAM. I've already gone done to the computer store and put in new RAM. However, after putting in the NEW ram I got a Memory_Management BSOD in safe mode when trying to get the xbox controller to work! Here's the Memory_Management BSOD Dump: https://1drv.ms/u/s!AjYbfOW_DSQ4hOZTfAiLrvEa57ekUg

Overnight I'll be running a new Memtest to see what happens.

Microsoft forum is being slow so I tried the /r/techsupport subreddit and got some good advice on things, but nothing has worked yet. Sorry for all the forums but more forum posts means more chance someone will see it and might know what to do. Link to the reddit post is here: https://www.reddit.com/r/techsupport/comments/9kpij0/blue_screens_and_computer_resets_driver_verifier/


 
post all you like to other places, its what i would do. Just have to be careful as you might get contradictory advice. Or the same advice all over the place.

What PSU do you have?

Safe mode only uses windows drivers, but as the Xbox drivers are made by MS and part of win 10, that doesn't really tell me anything. besides drivers being broken
 
Hi, I'm not sure that I got all of the dump files or not. Some are 0 bytes long which means they are invalid. There was no zipped up memory.dmp that I could find, maybe I missed it.

I ran the dump files through the debugger and got the following information: https://pste.eu/p/L1Cg.html

File: 100218-28406-01.dmp (Oct 2 2018 - 09:52:20)
BugCheck: [MEMORY_MANAGEMENT (1A)]
Probably caused by: memory_corruption (Process: chrome.exe)
Uptime: 0 Day(s), 0 Hour(s), 15 Min(s), and 40 Sec(s)

File: 100218-17093-01.dmp (Oct 2 2018 - 07:34:20)
BugCheck: [MEMORY_MANAGEMENT (1A)]
Probably caused by: memory_corruption (Process: explorer.exe)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 31 Sec(s)

File: 100218-15609-01.dmp (Oct 2 2018 - 03:21:50)
BugCheck: [DRIVER_VERIFIER_DETECTED_VIOLATION (C4)]
*** WARNING: Unable to verify timestamp for cmudaxp.sys
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 14 Sec(s)

File: 093018-13468-01.dmp (Sep 30 2018 - 11:04:35)
BugCheck: [DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION (D6)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 12 Sec(s)
Motherboard: https://www.msi.com/Motherboard/Z370-GAMING-PLUS.html
It appears you have the latest available BIOS already installed.

I can't help you with this. Wait for additional replies. Good luck.
 
Tests from the memtest are in and they are shocking! I'll use this opportunity to list the results I got with the first memtest86 (which is with the original Corsair Vengence LPX 3000Mhz RAM that I got (I'll call this alpha from now on)) and second memtest which had the replacement ram (I'll call this beta).

memtest created 2 .html reports which you can download.

Alpha Ram Test: Total 98 errors. (Original Corsair Vengence LPX 3000MHz, 2x8GB)
https://1drv.ms/u/s!AjYbfOW_DSQ4hOZYuPqeBNPJBfHFRA

Beta Ram test: total 7366 errors (Replacement Corsair Vengence LPX 3000MHz, 2x8GB)
https://1drv.ms/u/s!AjYbfOW_DSQ4hOZXyAa6MfOx6YNhiQ

Only the second (beta) ram is getting Memory_Management blue screens. The first (alpha) was not getting these, only driver blue screens, but with how much I tried it made sense to replace that ram.
 
Given only error count you want is 0, both of those tests fail

You need to test 1 stick at a time, your results and description show 2 sticks in both times. It might not be both sticks of each set, it might even be a slot of motherboard causing it. See if you can get 1 stick with zero errors and then use it to test both slots.
 
Thanks for those links Gardenman.

I've ran a few more memtest in different DIMM slots and the amount of errors only got worse, over 10000+ errors which caused memtest to abort. Right now I can't do any more actions though as I've passed the motherboard and RAM over to the local computer store where I bought the components, and they are going to test the Mobo/ram themselves over the next 2-3 days. Probably for the best as they can swap out components more easily and get to a final answer on what's going wrong.

Will report back when the computer is built again as the initial driver problem may still be present.
 


The new ram failed worse!

Haven't tried a Windows reset yet, but that'll probably be my next action if the mobo and ram are actually good. Since my computer store has the mobo and ram for a few days while they test then I can't do much till then. Will be interesting to see what component actually failed, my bet is the mobo too.
 
If its the motherboard, its doubtful the driver problem will return as its possible the problem was the hardware, not the drivers themselves. Explains why it was all USB devices and not just the xbox controller.

repair place should have a spare motherboard that they know works that they can swap in to test if it is cause. They won't give that to you, its just for testing.
 
Hello Everyone,

Many things have happened since I last updated you all.

I come with fantastic news. My problems have been completely resolved. No more blue screening. No more driver issues. No more xbox controller issues.

TL;DR BAD RAM, and maybe a bad CPU too.

I left you all with a message saying that my local computer store will take 2-3 days to test my Motherboard and RAM sticks. I was surprised when they called me only one day later, and they said that on their memtest with their own CPU, my motherboard and RAM had ZERO errors.

I found this quite surprising, but we hadn't ruled out a bad CPU. So I went down to the store and I got a new i7 8700k 3.7Ghz.

I took the fresh CPU, and my MSI motherboard and Corsair RAM home, and then I decided to test the components before I put them into my old case. I fired up memtest86 and let it run with both ram sticks installed. I was looking on with intent as it got all the way through the first pass with absolutely no errors. I was jumping for joy! Who would've thought all this time it was the CPU that was bad! The Computer store was right!

But then it happened. 301 errors flashed onto my screen, and my soul left my body for a very sad moment.

Determined as I am, I sucked my soul back into my body and decided to test some more. With the testbench configuration it was much easier for me to move the ram sticks around. I got to work recording what I found.

I put a single ram stick in slot A2 and let it run. The test only ran for about 15 seconds and it got 22665 Errors found before it aborted. Holy shit.

I put the other ram stick in slot A2 and let it run. Pass 1, zero issues. Then pass 2, zero issues. two and half hours later, this ram stick got through all 4 passes with no problem.

To ensure that the first ram stick was bad I continued and tested 1 pass on each DIMM slot with each stick. The bad ram stick consistantly got 10000+ errors and the good ram stick got zero errors.

I have no idea how my computer store's memtest found zero issues with that bad ram stick. But I headed back down and asked them to swap out my ram sticks for a third time (I have to hand them both in as they are a part of a kit).

This time the guy at the counter suggested that I try a different brand of ram, as maybe there was some crazy ultra-specific incompatibility with the Corsair ram and my computer setup. I agreed and picked up (2x8GB) sticks of G.Skill TridentZ RGB DDR4 3000MHz RAM.

I went back to my testbench and installed this shiny new RGB ram, and to my absolute joy there were no errors in memtest in single-channel and dual-channel. I even turned on XMP and CPU enhanced Turbo, still zero errors. Glorious day, a setup that worked.

There was still the worry of the driver issues though, I was convinced like just about everyone else here/reddit that there was some sort of USB driver problem or maybe Microsoft screwed up, so bad ram alone probably wouldn't fix that... I built my computer in my case and fired it up. After checking that all my hardware was showing up, I nervously plugged in my xbox controller and held my breath.

I waited. I clicked around. I clicked more. I clicked everywhere. IT DIDN'T RESTART, HOLY SHIT. I was shocked that having good ram actually resolved this seemingly-unrelated issue, but Colif had the right guess! The bad ram can matter with this issue!

I went and installed Logitech Gaming Software, I restarted the PC after installation, logged in, and anxiously waited for the crash/restart... The USB Input detected sound played, and my COMPUTER DID NOT RESTART.

And so my problems are solved, and even better, my Computer feels lightning fast compared to before, everything is zip-zooming around as hardware of this caliber should and it's just so great to see.

With this I present a possible solution to everyone who is having restarts caused by plugging in an xbox controller. Test your memory with Memtest86. The only things I have changed are my CPU and RAM, and it was probably just the RAM that was giving me the problems (but I'll never know for sure if my first 8700k CPU was bad). I didn't need to reset Windows.

Thank you all for giving suggestions on resolving my issue. Especially Colif and u/Bjoolzern on Reddit.

Oh, and despite Corsair's good name, I'm going to stay away from Corsair RAM for the rest of my life.

@Colif, I don't think I can pick my own comment as the solution, so can you mark this thread as solved?
 
Status
Not open for further replies.