Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

WIN 10 multiple blue screens


  • Please log in to reply
10 replies to this topic

#1 Bilove

Bilove

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:41 PM

Posted 12 January 2017 - 03:26 PM

Hello First off I'd like to say that there is similar topic a created back in march, and as it was so long ago I don't know how much different my problem was then than it is now as I have done a couple of things since. So if a mod sees this please delete my previous post.

 

I am receiving different blue screens and i suspect that it may be the motherboard drivers. This also seems to be causing all of my games to crash as not a single other person is having crash issues with any of the same games.

 

· OS - Windows 10
· 64bit
· What was original installed OS on system? Windows 7
· the OS is a free upgrade from Microsoft.
· Age of system: 1yr
· Age of OS installation- less than a year.

·cpu: i5-4590
· Video Card: GTX970
· MotherBoard - H81M-ITX
· Power Supply - DeepCool 650W

· System Manufacturer:
cutom build

· Laptop or Desktop: Desktop

 

The PERFORM seemed to lock up so couldn't get a report from that.

The page is also not letting my upload the minidump file i got from running driver verifier "no file was selected for upload" . In any case the verifier did give two blue screens before i had to restore the system.

 

Attached Files



BC AdBot (Login to Remove)

 


#2 shadow_647

shadow_647

  • Banned
  • 1,430 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:41 PM

Posted 13 January 2017 - 02:59 PM

Mind doing the following, could be helpfull.

 

https://www.bleepingcomputer.com/forums/t/323892/publish-a-snapshot-using-speccy/



#3 Bilove

Bilove
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:41 PM

Posted 13 January 2017 - 04:57 PM

http://speccy.piriform.com/results/aKKh5N8NwlwNpdU0cCxxAJW



#4 shadow_647

shadow_647

  • Banned
  • 1,430 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:41 PM

Posted 13 January 2017 - 07:01 PM

Ok all your ilde temp are a bit on the high side so im guessing bad case ventilation or hot part of the world or speccy getting it wrong combined with anytime to load up your system like trying to play a game the system bombs, as well ill take a guess here as well stock Intel cooler ?

 

As well did the system just have this problem and didn't have problems before this time when doing the same kinds of tasks, if it happened out of the blue down the road what was the last things you changed/happened on your computer when it started acting oddly if any.

 

Mind doing the following and see what happens, stop the test if you see 80C or higher as fast as possible, max recommended temp by Intel for your cpu is 73c and its a 83TDP cpu at stock speed

 

As well if your overclocking you should stop and put everything back at stock speed.

 

http://www.mersenne.org/download/

 

http://openhardwaremonitor.org/



#5 Bilove

Bilove
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:41 PM

Posted 13 January 2017 - 08:11 PM

The problems have pretty much persisted since i've built the system. I always thought it was drivers because i had a hard time finding the ones for the motherboard, the only hardware changes there has been is a new PSU. The case does have pretty bad cooling.CPU does  use the stock cooler and i am not overclocking. I ran the test for about 30minutes or so, not sure how long to run it, temps were fine, but I don't see where or how to grab the results or logs to post them here.It also only ran one core, the rest seem to have cited errors

Edited by Bilove, 13 January 2017 - 08:19 PM.


#6 shadow_647

shadow_647

  • Banned
  • 1,430 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:41 PM

Posted 13 January 2017 - 08:42 PM

You simply press the print key on your keyboard to take a screen shot of your desktop then paste the image in to ms-paint and edit as needed,save it to your hdd then upload it to a place like this as link the image location to this forum.

 

http://postimage.org/

 

As well you should do the custom test and select one thread for each cpu core in your case min 4 threads.

 

It also only ran one core, the rest seem to have cited errors

you shouldn't be getting any errors and it should be all cores.

 

And my self im a freelance hardware repair tech, and i don't do the log file side of things when it comes to this part of the forum, ill let the other guy that's pro on that topic "usamsa" that camps this part of the forum take care of that if and when it comes down to it.

 

My strong site is hardware diagnostics, and my self when doing it often i do it only on clean/minimum installs of windows so that the windows install dousen't confuse the hardware diagnostics on hdd that are wiped in a way so that only something like a bios virus can survive that kind of wipe.



#7 Bilove

Bilove
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:41 PM

Posted 14 January 2017 - 02:39 PM

I ran it again this time it ran all cores, it hit 80 pretty quickly, about five minutes. i stopped the test and took this screen shot https://postimg.org/image/qogxz3v5d/



#8 shadow_647

shadow_647

  • Banned
  • 1,430 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:41 PM

Posted 14 January 2017 - 03:08 PM

Well with temps like that i would guess this is just one more case of stock Intel cooler with maybe a side order of dust and weak case ventilation.

 

Things you can do about it for now is...

 

{clean dust off heat sink/check heat sink to make shore it on tight/get a better cooler/improve case ventilation/ go in to the bios and under-clock/under volt the cpu or disable some cores}

 

This may or may not be why your crashing when to try and play games but the dots do connect and your cpu temps are out of bounds as recommended by Intel.



#9 Bilove

Bilove
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:41 PM

Posted 14 January 2017 - 04:50 PM

I've monitored temps before, even playing CPU intensive games and the temps are just fine, nor does the system ever crash more while playing a CPU intensive game. It crashes while doing casual web browsing even, I've never had a difference in crashes between idle usage and heavy loads



#10 shadow_647

shadow_647

  • Banned
  • 1,430 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:41 PM

Posted 14 January 2017 - 07:49 PM

No problem, run your cpu at 90c at max load thinking its good, in the end the customer is always right ^^

 

But your right that is odd that it crash's when not doing much vs when loaded with a game, odd.

 

ill let usamsa/others take over from here, sorry i couldn't have bin of more help :/



#11 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:08:41 PM

Posted 15 January 2017 - 07:09 AM

Unfortunately it appears that the system has pirated software.
Please get a legitimate copy installed and we'll be glad to help.

Here's suggestions on how to ensure that your version is legitimate:  http://windows.microsoft.com/en-us/windows/genuine

Please be aware that we may not be able to fix it (as the hacks that were done to activate it will cause the OS to behave differently than we expect it to). If that's the case, our efforts to help may just waste your time. Secondly, the forum rules prohibit assisting with pirated software - so the topic would be closed if that is the case.

As a courtesy, I will offer an analysis of your issues using the reports you provided.
I will not answer any questions about the analysis until the system is made legitimate.
If you do make it legitimate, please submit a new set of reports for us to check.

Just FYI, sometimes the owner won't know about this.  So here's 2 scenarios that might ring a bell:
- if they had a "friend" help with the computer - and the "friend" installed a pirated copy.
- or they used a copy that they had from another OEM computer.  The OEM license is tied to the hardware that it came from - so you can't just use it on another system (that means that it's pirated).

And here's the analysis:
 

Your UEFI/BIOS (version P2.30) dates from 2016.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a more recent update.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Only 5 Windows Update hotfixes installed.  Most build 14393 (1607) systems have more than this.  Please visit Windows Update and get ALL available Windows Updates.
The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

Start by uninstalling the software for your MotioninJoy simulate Xbox 360 controller (virtual Xinput device), then physically remove the device from the system

Test to see if that stops the BSOD's (Don't forget to turn Driver Verifier off - as it's done it's job and isn't needed any more)

 

I also note the xusb21.sys driver - a driver for a wireless XBox controller that's known to cause BSOD's in some Windows systems.

Uninstall it's software and then physically remove it from the system in order to test.

There is no updated driver for this device, so you'll have to test it individually to see if it causes BSOD's or not.

If it is the cause, there's no other choice than to uninstall it and leave it uninstalled.

 

Out of 50 memory dumps there were 15 different BSOD  (aka STOP or BugCheck) error codes.  The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things (the list is not in any sort of order):
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- dirt/dust/hair/fur/crud inside the case.  Blow out the case/vents with canned air (DO NOT use an air compressor or vacuum as they can cause damage to the system)
- missing Windows Updates
- compatibility issues (3rd party hardware/drivers), older systems, or even pirated systems
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from http://www.carrona.org/initdiag.html or http://www.carrona.org/hwdiag.html ).

Please get a head start on the hardware diagnostics - they are located here:  http://www.carrona.org/hwdiag.html
If ALL of the tests pass, then start with this (designed for desktop systems/doesn't work well on laptops):  http://www.carrona.org/strpdown.html

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Thu Jan 12 14:44:52.802 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\011217-4000-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 0:00:16.505
*** WARNING: Unable to verify timestamp for MijXfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
Probably caused by :MijXfilt.sys ( MijXfilt+1b638 )
BugCheck D1, {fffff8015fb4b638, 2, 8, fffff8015fb4b638}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments:
Arg1: fffff8015fb4b638, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff8015fb4b638, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID: AV_VRF_CODE_AV_PAGED_IP_MijXfilt!unknown_function
CPUID:        "Intel® Core™ i5-4590 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3299
  BIOS Version                  P2.30
  BIOS Release Date             03/17/2016
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             H81M-ITX
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 12 14:21:33.930 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\011217-4734-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
System Uptime:0 days 23:52:50.856
Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+25de6 )
BugCheck 1A, {41201, fffff100008565d0, 887000013603b867, ffff9e8230529a00}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Arguments:
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff100008565d0
Arg3: 887000013603b867
Arg4: ffff9e8230529a00
BUGCHECK_STR:  0x1a_41201
PROCESS_NAME:  Empyrion.exe
FAILURE_BUCKET_ID: 0x1a_41201_nt!_??_::FNODOBFM::_string_
CPUID:        "Intel® Core™ i5-4590 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3299
  BIOS Version                  P2.30
  BIOS Release Date             03/17/2016
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             H81M-ITX
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jan 11 00:08:00.545 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\011017-4531-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
System Uptime:0 days 5:54:22.208
Probably caused by :dxgmms2.sys ( dxgmms2+2040 )
BugCheck 1000007E, {ffffffffc0000005, fffff80815d72040, ffffd1812863a088, ffffd181286398b0}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80815d72040, The address that the exception occurred at
Arg3: ffffd1812863a088, Exception Record Address
Arg4: ffffd181286398b0, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID: AV_dxgmms2!unknown_function
CPUID:        "Intel® Core™ i5-4590 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3299
  BIOS Version                  P2.30
  BIOS Release Date             03/17/2016
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             H81M-ITX
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.

Spoiler



3rd Party Drivers:
The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Thu Jan 12 14:44:52.802 2017 (UTC - 5:00)**************************
xusb21.sys                  Wed Apr  8 10:28:44 2009 (49DCB49C)
MijXfilt.sys                Sat May 12 00:27:12 2012 (4FADE6A0)
L1C63x64.sys                Sun Mar 31 23:15:17 2013 (5158FBC5)
WinDivert.sys               Mon Dec  2 22:46:09 2013 (529D5401)
xspltspk.sys                Wed Jun 11 16:59:54 2014 (5398C34A)
TeeDriverW8x64.sys          Tue Jul  7 13:43:32 2015 (559C0FC4)
rzpnk.sys                   Wed Sep 16 20:16:35 2015 (55FA0663)
rzpmgrk.sys                 Thu Sep 17 14:42:44 2015 (55FB09A4)
RzSurroundVAD.sys           Mon Feb 15 02:57:35 2016 (56C184EF)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
aswRvrt.sys                 Thu Aug 18 10:12:01 2016 (57B5C231)
aswKbd.sys                  Thu Aug 18 10:12:06 2016 (57B5C236)
aswRdr2.sys                 Thu Aug 18 10:12:58 2016 (57B5C26A)
aswMonFlt.sys               Thu Aug 18 10:30:14 2016 (57B5C676)
aswStm.sys                  Thu Aug 18 10:36:29 2016 (57B5C7ED)
aswSnx.sys                  Mon Sep 12 08:37:08 2016 (57D6A174)
aswSP.sys                   Mon Sep 12 08:59:01 2016 (57D6A695)
nvhda64v.sys                Thu Sep 29 09:25:06 2016 (57ED1632)
igdkmd64.sys                Thu Sep 29 10:43:27 2016 (57ED288F)
nvvad64v.sys                Tue Oct  4 03:20:09 2016 (57F35829)
aswVmm.sys                  Thu Oct  6 05:26:20 2016 (57F618BC)
nvlddmkm.sys                Thu Nov 24 14:04:44 2016 (583739CC)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 12 14:21:33.930 2017 (UTC - 5:00)**************************
EasyAntiCheat.sys           Sat Dec 10 18:17:16 2016 (584C8CFC)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jan  8 13:38:46.142 2017 (UTC - 5:00)**************************
GPU-Z.sys                   Wed Oct  6 12:14:37 2010 (4CACA06D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Dec 24 13:12:38.026 2016 (UTC - 5:00)**************************
IntcDAud.sys                Tue May 10 04:08:56 2016 (57319718)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Dec 13 23:26:10.201 2016 (UTC - 5:00)**************************
X6va063                     Thu Jul 28 03:40:11 2016 (5799B6DB)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Dec  3 01:20:29.944 2016 (UTC - 5:00)**************************
nvvad64v.sys                Thu Sep 22 12:46:30 2016 (57E40AE6)
nvlddmkm.sys                Tue Oct 25 15:38:31 2016 (580FB4B7)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Nov  6 17:50:36.664 2016 (UTC - 5:00)**************************
xhunter1.sys                Mon Aug 22 03:21:52 2016 (57BAA810)


http://www.carrona.org/drivers/driver.php?id=xusb21.sys
http://www.carrona.org/drivers/driver.php?id=MijXfilt.sys
http://www.carrona.org/drivers/driver.php?id=L1C63x64.sys
http://www.carrona.org/drivers/driver.php?id=WinDivert.sys
http://www.carrona.org/drivers/driver.php?id=xspltspk.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=rzpnk.sys
http://www.carrona.org/drivers/driver.php?id=rzpmgrk.sys
http://www.carrona.org/drivers/driver.php?id=RzSurroundVAD.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=aswRvrt.sys
http://www.carrona.org/drivers/driver.php?id=aswKbd.sys
http://www.carrona.org/drivers/driver.php?id=aswRdr2.sys
http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys
http://www.carrona.org/drivers/driver.php?id=aswStm.sys
http://www.carrona.org/drivers/driver.php?id=aswSnx.sys
http://www.carrona.org/drivers/driver.php?id=aswSP.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=aswVmm.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=EasyAntiCheat.sys
http://www.carrona.org/drivers/driver.php?id=GPU-Z.sys
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
X6va063 - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=xhunter1.sys


 

 


XXXXX


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users