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

Can only boot in safemode!


  • Please log in to reply
3 replies to this topic

#1 Fadel

Fadel

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:02:32 PM

Posted 08 September 2017 - 06:26 PM

It is impossible for me to boot on normal mode. I can only boot on safemode for some reason. Also, I recently uninstalled my graphics driver to see if it will have any effect, sadly not.

 

https://i.imgur.com/oAuG6HY.png

 

Attached Files



BC AdBot (Login to Remove)

 


#2 Havachat

Havachat

  • Members
  • 1,018 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sleepy Hollow - Geelong - Go Cats.
  • Local time:09:32 PM

Posted 08 September 2017 - 07:07 PM

Until someone can read your reports , have you tried any repairs ? 

You can have a look here or wait for an expert to guide you.

https://www.howtogeek.com/164876/how-to-use-safe-mode-to-fix-your-windows-pc-and-when-you-should/



#3 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,089 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:07:32 AM

Posted 10 September 2017 - 05:04 AM

Out of 22 memory dumps there were 9 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
Please finish ALL of them and let us know the results.

Beyond that, I'll try to get back this afternoon with some more suggestions (been working 7am to 9 pm the last 2 days - today is only 7am to 11am :0)


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.

#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,089 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:07:32 AM

Posted 10 September 2017 - 04:46 PM

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 0404) 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).

 

Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  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.

 

IMO this is most likely a hardware problem.

As such, here's the steps I suggest:

1)  run ALL of these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

2)  a clean install of Windows 10 (see the quote box following this list)

3)  then perform this procedure to help isolate the problem device:  http://www.carrona.org/strpdown.html
 

Clean Install:

 

A clean install is:
- Windows is installed to a freshly partitioned hard drive with legitimate installation media (W10:  https://www.microsoft.com/en-us/software-download/windows10 ).
- The installation media is only a copy of Windows, not the OEM recovery disks that you can make on some systems.
- Windows is fully updated after it's installed.  That's ALL updates - none excepted.
- NO 3rd party software is installed.
- There are no errors in Device Manager (if you find any, post back for suggestions).

This will wipe everything off of the computer, so it's advisable to backup your stuff first.
Also, it will wipe out all the special software that the OEM added to the system, so if you rely on any of that - let us know what it is so we can figure out a way to save/download it (the easiest way is to create/obtain the OEM;s recovery media)

If unable to find recovery media that has the software (or if you suspect that this is a hardware problem), you can make an image of your system that'll preserve everything in the state that it was in when you made the image.
One drawback to this is that you're making an image of a malfunctioning system - so, if there are errors in the system software, you'll have a nice copy of them :(
Another drawback is that the image of the system will be very large - so you'll most likely need a large external drive to store it on.
But, this will allow you to save everything on the hard drive (although you'll need an image viewer to get things out of the image).
The point here is that, if it's a hardware problem, then you can restore the system to the point it was when you made the image - after you repair the hardware problem.
You can obtain more info on imaging in the Backup/Imaging/DiskMgmt forums located here:  http://www.bleepingcomputer.com/forums/f/238/backup-imaging-and-disk-management-software/

The point of doing this (the clean install) is to:
- rule out Windows as a problem (if the problem continues, it's not a Windows problem as you completely replaced Windows
- rule out 3rd party software (if the problem continues, it's not a 3rd party software problem as you didn't install any 3rd party software)
- so, if the problem continues, it must be a hardware problem.

OTOH, if the problem stops, then it was either a Windows or 3rd party software problem.  If the problem doesn't come back, then you've fixed it.  Then all that remains is setting the computer back up the way that you'd like it and importing your data from the backup you made.

 

 

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Fri Sep  8 19:02:21.861 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\090917-15593-02.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.3.amd64fre.th2_release_sec.151104-1948
System Uptime:0 days 0:00:07.603
Probably caused by :CI.dll ( CI!CiFreePolicyInfo+3b47 )
BugCheck 1A, {41793, fffff68103800000, 1, 0}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Arguments:
Arg1: 0000000000041793, The subtype of the bugcheck.
Arg2: fffff68103800000
Arg3: 0000000000000001
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41793
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x1a_41793_CI!CiFreePolicyInfo
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Sep  8 18:58:31.051 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\090917-15406-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.3.amd64fre.th2_release_sec.151104-1948
System Uptime:0 days 0:00:05.794
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by :ntkrnlmp.exe ( nt!PspCatchCriticalBreak+a4 )
BugCheck EF, {ffffe001662f97c0, 0, 0, 0}
BugCheck Info: CRITICAL_PROCESS_DIED (ef)
Arguments:
Arg1: ffffe001662f97c0, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000
PROCESS_NAME:  smss.exe
BUGCHECK_STR:  0xEF
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID: 0xEF_smss.exe_BUGCHECK_CRITICAL_PROCESS_662f7040_nt!PspCatchCriticalBreak
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Sep  8 18:42:37.173 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\090917-15578-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.3.amd64fre.th2_release_sec.151104-1948
System Uptime:0 days 0:00:05.917
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for ahcache.sys
Probably caused by :memory_corruption
BugCheck 1E, {ffffffffc0000005, fffff800f69ffacd, 0, ffffffffffffffff}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800f69ffacd, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  smss.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
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:

**************************Fri Sep  8 19:02:21.861 2017 (UTC - 4:00)**************************
SiSRaid2.sys                Wed Sep 24 14:28:20 2008 (48DA86C4)
sisraid4.sys                Wed Oct  1 17:56:04 2008 (48E3F1F4)
iaStorV.sys                 Mon Apr 11 14:48:16 2011 (4DA34CF0)
stexstor.sys                Mon Nov 26 19:02:51 2012 (50B4032B)
amdide64.sys                Tue Dec  4 04:49:28 2012 (50BDC728)
amdsbs.sys                  Tue Dec 11 16:21:44 2012 (50C7A3E8)
vstxraid.sys                Mon Jan 21 14:00:28 2013 (50FD904C)
bxvbda.sys                  Mon Feb  4 14:47:18 2013 (51101046)
lsi_sss.sys                 Fri Mar 15 19:39:38 2013 (5143B13A)
HpSAMD.sys                  Tue Mar 26 17:36:54 2013 (515214F6)
megasr.sys                  Mon Jun  3 18:02:39 2013 (51AD127F)
nvraid.sys                  Mon Apr 21 14:28:42 2014 (5355635A)
nvstor.sys                  Mon Apr 21 14:34:03 2014 (5355649B)
vsmraid.sys                 Tue Apr 22 15:21:41 2014 (5356C145)
mvumis.sys                  Fri May 23 16:39:04 2014 (537FB1E8)
evbda.sys                   Mon Jan 12 05:29:16 2015 (54B3A1FC)
percsas3i.sys               Wed Feb  4 17:52:41 2015 (54D2A2B9)
percsas2i.sys               Thu Feb  5 17:51:05 2015 (54D3F3D9)
iaStorAV.sys                Thu Feb 19 07:08:39 2015 (54E5D247)
megasas.sys                 Wed Mar  4 21:36:29 2015 (54F7C12D)
lsi_sas.sys                 Wed Mar 25 15:36:48 2015 (55130E50)
lsi_sas2i.sys               Wed Apr  8 16:58:43 2015 (55259683)
lsi_sas3i.sys               Thu Apr  9 14:07:43 2015 (5526BFEF)
arcsas.sys                  Thu Apr  9 15:12:07 2015 (5526CF07)
ADP80XX.SYS                 Thu Apr  9 16:49:48 2015 (5526E5EC)
amdxata.sys                 Thu Apr 30 20:55:35 2015 (5542CF07)
amdsata.sys                 Thu May 14 08:14:52 2015 (555491BC)
3ware.sys                   Mon May 18 18:28:03 2015 (555A6773)
klbackupdisk.sys            Tue Jun  2 16:18:33 2015 (556E0F99)
klwtp.sys                   Wed Jun  3 11:29:28 2015 (556F1D58)
kl1.sys                     Thu Jun 18 14:58:13 2015 (558314C5)
cm_km.sys                   Wed Jul  1 14:08:29 2015 (55942C9D)
klflt.sys                   Thu Sep 24 07:48:42 2015 (5603E31A)
intelide.sys                Thu Oct 29 22:09:42 2015 (5632D166)
nv_agp.sys                  Thu Oct 29 22:39:06 2015 (5632D84A)
agp440.sys                  Thu Oct 29 22:39:51 2015 (5632D877)
hvsocket.sys                Thu Oct 29 22:46:55 2015 (5632DA1F)
klim6.sys                   Fri Feb 26 07:35:04 2016 (56D04678)
klwfp.sys                   Fri Apr 15 07:26:03 2016 (5710CFCB)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Sep  8 18:58:31.051 2017 (UTC - 4:00)**************************
asmtxhci.sys                Mon Aug 29 04:18:36 2016 (57C3EFDC)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Sep  8 17:45:53.247 2017 (UTC - 4:00)**************************
ASACPI.sys                  Thu Nov  1 21:54:34 2012 (509327DA)
rt640x64.sys                Wed Oct  7 11:03:55 2015 (5615345B)
nvvad64v.sys                Sun May 28 19:04:45 2017 (592B578D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Sep  8 14:01:52.957 2017 (UTC - 4:00)**************************
klbackupflt.sys             Wed Apr 15 21:09:36 2015 (552F0BD0)
klmouflt.sys                Tue Jun  2 08:36:12 2015 (556DA33C)
klkbdflt.sys                Tue Jun  2 08:36:30 2015 (556DA34E)
kneps.sys                   Fri Jun 19 08:22:49 2015 (55840999)
klpd.sys                    Wed Sep 23 07:10:31 2015 (560288A7)
kldisk.sys                  Fri Jan 22 05:56:11 2016 (56A20ACB)
klhk.sys                    Thu May 12 13:03:02 2016 (5734B746)
RTKVHD64.sys                Fri Jun  3 07:28:58 2016 (575169FA)
nvlddmkm.sys                Tue Jul 18 18:00:50 2017 (596E8512)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Sep  8 13:46:47.491 2017 (UTC - 4:00)**************************
klif.sys                    Tue Apr 12 07:21:38 2016 (570CDA42)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Sep  8 13:37:25.338 2017 (UTC - 4:00)**************************
klhk.sys                    Thu Jul  2 12:29:39 2015 (559566F3)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Sep  7 22:58:07.093 2017 (UTC - 4:00)**************************
MpKslc3f454d2.sys           Tue May 19 21:50:37 2015 (555BE86D)
kldisk.sys                  Tue Jun  2 08:49:29 2015 (556DA659)
klpd.sys                    Thu Jun  4 08:19:18 2015 (55704246)
klim6.sys                   Mon Jun  8 04:49:57 2015 (55755735)
klwfp.sys                   Mon Jun 15 05:39:28 2015 (557E9D50)
klflt.sys                   Tue Jun 16 08:29:30 2015 (558016AA)
klif.sys                    Tue Jun 23 11:12:16 2015 (55897750)


http://www.carrona.org/drivers/driver.php?id=SiSRaid2.sys
http://www.carrona.org/drivers/driver.php?id=sisraid4.sys
http://www.carrona.org/drivers/driver.php?id=iaStorV.sys
http://www.carrona.org/drivers/driver.php?id=stexstor.sys
http://www.carrona.org/drivers/driver.php?id=amdide64.sys
http://www.carrona.org/drivers/driver.php?id=amdsbs.sys
http://www.carrona.org/drivers/driver.php?id=vstxraid.sys
http://www.carrona.org/drivers/driver.php?id=bxvbda.sys
http://www.carrona.org/drivers/driver.php?id=lsi_sss.sys
http://www.carrona.org/drivers/driver.php?id=HpSAMD.sys
http://www.carrona.org/drivers/driver.php?id=megasr.sys
http://www.carrona.org/drivers/driver.php?id=nvraid.sys
http://www.carrona.org/drivers/driver.php?id=nvstor.sys
http://www.carrona.org/drivers/driver.php?id=vsmraid.sys
http://www.carrona.org/drivers/driver.php?id=mvumis.sys
http://www.carrona.org/drivers/driver.php?id=evbda.sys
percsas3i.sys - 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.
percsas2i.sys - 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=iaStorAV.sys
http://www.carrona.org/drivers/driver.php?id=megasas.sys
http://www.carrona.org/drivers/driver.php?id=lsi_sas.sys
lsi_sas2i.sys - 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.
lsi_sas3i.sys - 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=arcsas.sys
http://www.carrona.org/drivers/driver.php?id=ADP80XX.SYS
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=amdsata.sys
http://www.carrona.org/drivers/driver.php?id=3ware.sys
http://www.carrona.org/drivers/driver.php?id=klbackupdisk.sys
http://www.carrona.org/drivers/driver.php?id=klwtp.sys
http://www.carrona.org/drivers/driver.php?id=kl1.sys
http://www.carrona.org/drivers/driver.php?id=cm_km.sys
http://www.carrona.org/drivers/driver.php?id=klflt.sys
http://www.carrona.org/drivers/driver.php?id=intelide.sys
http://www.carrona.org/drivers/driver.php?id=nv_agp.sys
http://www.carrona.org/drivers/driver.php?id=agp440.sys
hvsocket.sys - 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=klim6.sys
http://www.carrona.org/drivers/driver.php?id=klwfp.sys
http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys
http://www.carrona.org/drivers/driver.php?id=ASACPI.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=klbackupflt.sys
http://www.carrona.org/drivers/driver.php?id=klmouflt.sys
http://www.carrona.org/drivers/driver.php?id=klkbdflt.sys
http://www.carrona.org/drivers/driver.php?id=kneps.sys
http://www.carrona.org/drivers/driver.php?id=klpd.sys
http://www.carrona.org/drivers/driver.php?id=kldisk.sys
http://www.carrona.org/drivers/driver.php?id=klhk.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=klif.sys
http://www.carrona.org/drivers/driver.php?id=klhk.sys
MpKslc3f454d2.sys - 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=kldisk.sys
http://www.carrona.org/drivers/driver.php?id=klpd.sys
http://www.carrona.org/drivers/driver.php?id=klim6.sys
http://www.carrona.org/drivers/driver.php?id=klwfp.sys
http://www.carrona.org/drivers/driver.php?id=klflt.sys
http://www.carrona.org/drivers/driver.php?id=klif.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