BSOD While gaming + video editing, error 0x0000010E

[Masamaki]

Hey guys,
As you can see i'm new to the forums so hopefully I get this right.
I've been having BSOD for months now, and unfortunately I've been unable to figure out the problem.
the latest error i've gotten was 0x0000010E but i've gotten others.
The error varies from IQRL_LESS_THAN_OR_EQUAL to PAGE FAULT IN NONPAGED AREA.
It can happen when gaming on steam, or video editing.
BSOD occurred not too long before posting this thread and I was literally doing nothing on my PC, just sitting on steam not playing any games.
This past day i've gotten 5+ blue screens and I just can't take it anymore.
hopefully the information within the attached file will help solve this issue.
I actually ran SF Diagnostic through safe mode, hope that's ok.
If not I can try to run it while in regular mode.
Thanks in advance.

 

[YoYo155]

Welcome to Seven Forums !

You said you have had experienced many bugchecks lately yet none are found,
all bugchecks are from January and earlier.
View attachment 287436

None the less, I've looked at all the 2013 dumps and they all incriminate Xeno7x64.sys.
Which is very very old;

lmvm Xeno7x64
start             end                 module name
fffff880`02cf2000 fffff880`02d15000   Xeno7x64 T (no symbols)           
    Loaded symbol image file: Xeno7x64.sys
    Image path: \SystemRoot\system32\DRIVERS\Xeno7x64.sys
    Image name: Xeno7x64.sys
    Timestamp:        [COLOR=Red][U][B]Wed Jun 03 02:15:48 2009[/B][/U][/COLOR]

xeno7x64    Killer Xeno Gaming Adapter Service    c:\windows\system32\drivers\xeno7x64.sys

• Driver Reference Table - Xeno7x64.sys

Please remove the driver by uninstalling Bigfoot Networks using RevoUninstaller

Start Menu\Programs\Bigfoot Networks\Xeno Suite

Download


​

Post back with the results!

 

[Masamaki]

Welcome to Seven Forums !

You said you have had experienced many bugchecks lately yet none are found,
all bugchecks are from January and earlier.
View attachment 287436

None the less, I've looked at all the 2013 dumps and they all incriminate Xeno7x64.sys.
Which is very very old;

lmvm Xeno7x64
start             end                 module name
fffff880`02cf2000 fffff880`02d15000   Xeno7x64 T (no symbols)           
    Loaded symbol image file: Xeno7x64.sys
    Image path: \SystemRoot\system32\DRIVERS\Xeno7x64.sys
    Image name: Xeno7x64.sys
    Timestamp:        [COLOR=Red][U][B]Wed Jun 03 02:15:48 2009[/B][/U][/COLOR]

xeno7x64    Killer Xeno Gaming Adapter Service    c:\windows\system32\drivers\xeno7x64.sys

• Driver Reference Table - Xeno7x64.sys

Please remove the driver by uninstalling Bigfoot Networks using RevoUninstaller

Start Menu\Programs\Bigfoot Networks\Xeno Suite

Download


​

Post back with the results!

Hey, thanks for helping.
I also noticed the dumps are from earlier this year which I don't understand.
Ok i've used RevoUninstaller, I will restart my PC and see how things go in normal mode.

UPDATE: Blue Screened after logging in for a few seconds.

 

[YoYo155]

Thank you for the update .
The earliest entry of a bugcheck in the Event Viewer is from 6/4/2013
Please check if your system is still configured to generate dump files;
:: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html ::
Configure a minidump 1-4 > 6.

Keep us posted.

Edit:
Are there any new dumps?
Look for them manually;

C:\Windows\minidump

Copy the new files to your desktop, zip and upload them them.

If no new dumps are created, while following the tutorial above untick the checkbox next to
Automatically restart and the next time it bugchecks take a picture of the screen
and upload it here.

 

[Masamaki]

Thank you for the update .
The earliest entry of a bugcheck in the Event Viewer is from 6/4/2013
Please check if your system is still configured to generate dump files;
:: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html ::
Configure a minidump 1-4 > 6.

Keep us posted.

Edit:
Are there any new dumps?
Look for them manually;

C:\Windows\minidump

Copy the new files to your desktop, zip and upload them them.

If no new dumps are created, while following the tutorial above untick the checkbox next to
Automatically restart and the next time it bugchecks take a picture of the screen
and upload it here.

So I noticed, after searching the xeno7x64.sys in my windows folder there are two instances of it even though I used Revouninstaller to uninstall it!
Is there a way to manually remove them?

 

[YoYo155]

Yes you can follow this tutorial;
:: http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html ::
Then search for them again after the restart to confirm.

Did you look for new dumps manually?
Did you configure it not to auto restart in preparation for the next bugcheck?

 

[Masamaki]

Yes you can follow this tutorial;
:: http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html ::
Then search for them again after the restart to confirm.

Did you look for new dumps manually?
Did you configure it not to auto restart in preparation for the next bugcheck?

Yes and Yes.
Found no new dumps since january of this year.
I've set it to minidump and to not restart, but it hasn't bluescreened since my last restart.

EDIT:
I can't fingure out how to navigate to Xeno7x64.sys using driver sweeper.

 

[Masamaki]

My PC doesn't seem to save the mini dumps for some reason.
I found these files on my HDD in a folder called Live Kernal Reports.
They all have the DMP extension and there's a few from the 24th of this month.
I hope this helps, as soon as my PC blue screens again I will photograph the screen.

 

[YoYo155]

That's odd, please upload a screenshot of the Startup and Recovery window described in the
tutorial on how to configure a dump file.

Now for the dumps, the dumps are all 0x117;

VIDEO_TDR_TIMEOUT_DETECTED (117)

Arguments:
Arg1: fffffa800822e4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88006c81e5c, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

The display driver failed to respond in timely fashion.
(This code can never be used for real bugcheck).

What you are experiencing is a TDR event (Timeout Detection & Recovery). There are many causes of these events, mostly hardware related. Please read my checklist below and see if you can diagnose your particular cause.

*******
"Display driver xxxxx stopped responding and was recovered"

Timeout Detection & Recovery (TDR) = "Display Driver Stopped Responding and was Recovered" is a useful feature that started in Vista and is also in W7 that allows the OS to try and recover from a video timeout so that the system does not crash to a bluescreen. Symptoms included a screen flash with the TDR message appearing one or more times or the screen blinking out to black. If the system cannot recover it will crash (Stop Error 116 typical). The issue is that the video card is not responding as expected. The solution is in the: why?

There is no one-size-fits-all solution to TDR errors. But the problem is usually found in the local environment (your computer). Finding the cause is a matter of checking every possible cause and uncovering the culprit through a simple process of elimination. By methodically running down a checklist of diagnostic procedures you should be able to find the cause and can correct it.

There are numerous reports of hardware solutions to TDR's. The most common are:

• Poor Cooling
• Problems with the power supply
• Overclocking Issues
• Bad System memory or incorrect memory timings
• Defective PC Components

Please read, to understand the troubleshooting procedure.

• http://www.sevenforums.com/graphic-...-keeps-failing-geforce-9500gt.html#post904044

These are all stop 0x116 VIDEO_TDR_FAILURE conditions.

It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash. As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds. If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating. Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU. Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference. If so, it might be as simple as dust buildup and subsequently inadequate cooling.

Uninstall Catalyst Control Center using | AMD Catalyst Un-install Utility
Then follow through with a pass of Driver Sweeper.

Download version 13.1
​

   Note

Install the display driver only! | Do not install the Catalyst Control Center software.

• Download Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.

Post back with the results!

 

[Masamaki]

View attachment 287495Here's the screenshot of my startup and recovery settings.
I will uninstall catalyst right now.
EDIT:After uninstalling AMD drivers using the link you provided my PC prompted for a restart.
It bluescreened once I logged in and I took a picture of the screen.

 

[Masamaki]

You said to not install the catalyst.
It doesn't let me uncheck the first box for catalyst.

Edit:Removed the drivers using both AMD's uninstaller and the Driver Sweeper.

 

[YoYo155]

The picture of the bugcheck you uploaded shows a 0x3B which is usually associated with a graphic driver passing a bad address which causes an access violation where we see that in the value of ht first argument
c0000005, but much is given without the dump file, that along with the fact that the folder you uploaded
is all 0x117 which is only graphics related I believe we have our culprit whether it being the hardware or software
it is yet to be discovered.

Simply install the GPU drivers as seen in the screenshot above and start testing the hardware.

What is the make an model of you PSU?
Fill out this form and post back the result:

• Power Supply Calculator

• Download Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to part 3 of the tutorial "If you have errors"
• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

 

[Masamaki]

The picture of the bugcheck you uploaded shows a 0x3B which is usually associated with a graphic driver passing a bad address which causes an access violation where we see that in the value of ht first argument
c0000005, but much is given without the dump file, that along with the fact that the folder you uploaded
is all 0x117 which is only graphics related I believe we have our culprit whether it being the hardware or software
it is yet to be discovered.

Simply install the GPU drivers as seen in the screenshot above and start testing the hardware.

What is the make an model of you PSU?
Fill out this form and post back the result:

• Power Supply Calculator

• Download Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to part 3 of the tutorial "If you have errors"
• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

Currently running prime 95, here's the screenshots of speccy both idle and under stress from prime 95.
The Cpu temperature sits between 59-60 c.
all cores have passed up to self test 12k and it's still going.
Should I stop and run Furmark now?

I also tried filling out the form to the best of my ability.
A lot of it is over my head unfortunately.
It gave me a result of 330 Watts as the recommended.
My power supply is a 800 Watts - XtremeGear Gaming Power Supply.
This is a custom built PC I ordered from Cyberpower a few years back.
I'm not really tech savvy to be honest.

 

[YoYo155]

Currently running prime 95, here's the screenshots of speccy both idle and under stress from prime 95.
The Cpu temperature sits between 59-60 c.
all cores have passed up to self test 12k and it's still going.
Should I stop and run Furmark now?

I also tried filling out the form to the best of my ability.
A lot of it is over my head unfortunately.
It gave me a result of 330 Watts as the recommended.
My power supply is a 800 Watts - XtremeGear Gaming Power Supply.
This is a custom built PC I ordered from Cyberpower a few years back.
I'm not really tech savvy to be honest.

Well I appreciate your effort but the GPU on it's own is needing of ~400 watts or so (under full load)
I hate to break it to you but that PSU is regarded as fairly low-end combined with the fact that it
is already a few years old now only adds to the fact that it might very well be the cause.

The CPU temperature is looking good, start with Furmark now .

Please fill out your system specification, this to tutorial will assist you with that.
http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html

 

[Masamaki]

Currently running prime 95, here's the screenshots of speccy both idle and under stress from prime 95.
The Cpu temperature sits between 59-60 c.
all cores have passed up to self test 12k and it's still going.
Should I stop and run Furmark now?

I also tried filling out the form to the best of my ability.
A lot of it is over my head unfortunately.
It gave me a result of 330 Watts as the recommended.
My power supply is a 800 Watts - XtremeGear Gaming Power Supply.
This is a custom built PC I ordered from Cyberpower a few years back.
I'm not really tech savvy to be honest.

Well I appreciate your effort but the GPU on it's own is needing of ~400 watts or so (under full load)
I hate to break it to you but that PSU is regarded as fairly low-end combined with the fact that it
is already a few years old now only adds to the fact that it might very well be the cause.

The CPU temperature is looking good, start with Furmark now .

Please fill out your system specification, this to tutorial will assist you with that.
http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html

You think that could be it?
I'm okay with replacing it once I get enough money to do so.
I will start testing with furmark now.
Edit:Furmark keeps giving me an error that says:
Could not initialize ZoomGPU. FurMark startup failed. Bye!
I checked in device manager and saw the yellow hazard sign next to the GPU.

Update: Restarting my PC fixed the issue.

 

[Masamaki]

Tested with FurMark.
The temps reached 77 on the GPU then PC bluescreened.
I took another photo of the screen if that helps any further.

 

[YoYo155]

As a matter of fact it does help.
This BCCode, 0xA0000001, is unique to AMD (ATi) GPU's meaning it was the cause but that doesn't rule out the fact that the PSU is to blame after all it is responsible for the clean current being provided to the components.
77°C is pretty high but inside the tolerant spec so I don't think it is the issue at this point I'm suspecting hardware.

Please upload a new MSINFO32 file to confirm that the drivers version where in fact downgrade.

Start> RUN> "MSINFO32" without the quotes then hit [Enter].
In "MSINFO32" go to, File> Save> name it your user-name and upload.

 

[Masamaki]

Here's the file you asked for.

 

[YoYo155]

Thanks, 13.1 has been installed.
Try furmark once again please to confirm the issue is consistent.

 

[Masamaki]

Thanks, 13.1 has been installed.
Try furmark once again please to confirm the issue is consistent.

Hey,
So I tested with FurMark again.
The temp reached 83 in about 3 minutes and just hung there so I stopped it as the guide said.
No bluescreen, I also did some streaming earlier today on twitch.tv and also got no bluescreen.
I did lower CPU power in the AMD catalyst thing.
Do you think that may have helped?