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

Fresh Install Win10 - Fails to boot first time, eventviewer: 0xc0000001


  • Please log in to reply
21 replies to this topic

#16 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 24,708 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:30 AM

Posted 15 October 2017 - 12:21 PM

So, yes the stornvme.sys driver is dated correctly - but the date given in the dump files is messed up.

Not unusual since the early days of W10, but still a bit disconcerting.
 

As the Driver Verifier dump blames the OS kernel (core of the OS), we figure that it's another driver causing it.

This is because if the kernel was having problems, we'd expect to see more problems with the system other than the occasional BSOD.

Yet, Driver Verifier didn't blame any 3rd party driver - so we have to presume that this is either a Windows driver or a hardware problem.

And, as we're seeing the presence of stornvme.sys in the dumps, I have to wonder if a corrupted copy of that is to blame.

 

As this is a new install of Windows, I'd suggest trying another fresh, clean install to ensure that Windows isn't to blame.
To do this, create new recovery media (in case the last set you used was corrupted) and then follow the clean install instructions here:

 

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:
**************************Sat Oct 14 22:06:21.442 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\101517-4812-01.dmp]
Windows 10 Kernel Version 15063 MP (8 procs) Free x64
System Uptime:0 days 0:00:02.133
Probably caused by :ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+6b )
BugCheck C4, {2004, ffffd8896ee66758, fffff807f96401f0, ffff80007d9c80a8}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000002004, Code Integrity Issue: The image contains a section that is not page aligned.
Arg2: ffffd8896ee66758, The image file name (Unicode string).
Arg3: fffff807f96401f0, The address of the section header.
Arg4: ffff80007d9c80a8, The section name (UTF-8 encoded string).
BUGCHECK_STR:  0xc4_2004
FAILURE_BUCKET_ID: 0xc4_2004_nt!VerifierBugCheckIfAppropriate
CPUID:        "Intel® Core™ i7-4790K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``



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:

**************************Sat Oct 14 22:06:21.442 2017 (UTC - 4:00)**************************
dump_stornvme.sys           Tue Mar 13 03:19:09 2001 (3AADC9ED)
XtuAcpiDriver.sys           Thu Feb 26 07:51:57 2015 (54EF16ED)
TeeDriverW8x64.sys          Tue Jul  7 13:43:32 2015 (559C0FC4)
LGBusEnum.sys               Mon Jun 13 14:47:08 2016 (575EFFAC)
nvvad64v.sys                Sun May 28 19:04:45 2017 (592B578D)
e2xw10x64.sys               Thu Aug 31 17:11:04 2017 (59A87B68)
nvlddmkm.sys                Sat Sep 16 12:54:01 2017 (59BD5729)
intelppm.sys                ***** Invalid 2007 Invalid 2007 Invalid


dump_stornvme.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=XtuAcpiDriver.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=e2xw10x64.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
 

Edited by usasma, 15 October 2017 - 12:23 PM.

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

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.


BC AdBot (Login to Remove)

 


m

#17 RedArr0w

RedArr0w
  • Topic Starter

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Local time:04:30 PM

Posted 16 October 2017 - 10:44 AM

Hi Usasma,

 

Thank you for getting back to me and for your analysis of that minidump.

 

I understand that the next course of action will be to do a fresh installation of Windows10 64Bit - However this is no 'easy' task for me, as I have much data and programs I need to reconfigure/backup & restore.

 

So would you be so kind to analysis the attached minidump as this one happened today when I booted from cold and it was the 'hidden' one which I have not had for a while as all the othere BSOD's were caused by using that Driver Verifier.

 

If you still feel It's necessary for me to do a Fresh Windows 10 install I shall.

 

Many thanks for your help.

Attached Files



#18 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 24,708 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:30 AM

Posted 16 October 2017 - 11:06 AM

This one was essentially the same as the others.
EIther it's hardware or it's the OS - and it's (IMO) most likely the OS
I'd say that a clean install is called for at this point.

 

Some other options are to get another hard drive and do the clean install on that.

You can also make an image of the hard drive - then do the clean install.  The image will save everything on the hard drive - the drawback is it's size (it's very, very large).  You'll need an external hard drive to save it on.

Either of these will allow you to revert back to the current system state fairly easily.

 

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Mon Oct 16 09:56:52.620 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\101617-14453-01.dmp]
Windows 10 Kernel Version 15063 MP (8 procs) Free x64
System Uptime:1 days 11:46:08.267
Probably caused by :ntkrnlmp.exe ( nt!PspCatchCriticalBreak+c9 )
BugCheck EF, {ffffac80f53337c0, 0, 0, 0}
BugCheck Info: CRITICAL_PROCESS_DIED (ef)
Arguments:
Arg1: ffffac80f53337c0, 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
BUGCHECK_STR:  0xEF
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID: 0xEF_nt!PspCatchCriticalBreak
CPUID:        "Intel® Core™ i7-4790K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4000
  BIOS Version                  V1.13
  BIOS Release Date             02/16/2016
  Manufacturer                  MSI
  Product Name                  MS-7917
  Baseboard Product             Z97 GAMING 5 (MS-7917)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


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:

**************************Mon Oct 16 09:56:52.620 2017 (UTC - 4:00)**************************
MpKsl02a75870.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)
dump_stornvme.sys           Tue Mar 13 03:19:09 2001 (3AADC9ED)
MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
XtuAcpiDriver.sys           Thu Feb 26 07:51:57 2015 (54EF16ED)
lgcoretemp.sys              Tue Jun  9 12:52:10 2015 (557719BA)
TeeDriverW8x64.sys          Tue Jul  7 13:43:32 2015 (559C0FC4)
LGVirHid.sys                Mon Jun 13 14:47:03 2016 (575EFFA7)
LGJoyXlCore.sys             Mon Jun 13 14:47:06 2016 (575EFFAA)
LGBusEnum.sys               Mon Jun 13 14:47:08 2016 (575EFFAC)
RTKVHD64.sys                Tue Dec  6 06:23:15 2016 (58469FA3)
ssdevfactory.sys            Mon May  8 12:03:55 2017 (591096EB)
nvhda64v.sys                Tue May 16 09:02:27 2017 (591AF863)
nvvad64v.sys                Sun May 28 19:04:45 2017 (592B578D)
e2xw10x64.sys               Thu Aug 31 17:11:04 2017 (59A87B68)
nvlddmkm.sys                Sat Sep 16 12:54:01 2017 (59BD5729)
RfeCo10X64.sys              Thu Oct 12 13:32:02 2017 (59DFA712)
intelppm.sys                ***** Invalid 2007 Invalid 2007 Invalid

MpKsl02a75870.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.
dump_stornvme.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=MBfilt64.sys
http://www.carrona.org/drivers/driver.php?id=XtuAcpiDriver.sys
http://www.carrona.org/drivers/driver.php?id=lgcoretemp.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys
http://www.carrona.org/drivers/driver.php?id=LGJoyXlCore.sys
http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=ssdevfactory.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=e2xw10x64.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
RfeCo10X64.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=intelppm.sys
 


Edited by usasma, 16 October 2017 - 11:07 AM.

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

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.


#19 RedArr0w

RedArr0w
  • Topic Starter

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Local time:04:30 PM

Posted 16 October 2017 - 11:50 AM

Okay,

 

I am going to create a new Windows10 Installation media on USB using Microsoft's Media creation tool. (So I know the copy of install isn't causing my problems)

 

Then will reinstall windows, and post back if any news.

Many thanks for your help! :)



#20 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 24,708 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:30 AM

Posted 17 October 2017 - 07:38 AM

Can't recall if I posted this before:

 

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.

 


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

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.


#21 RedArr0w

RedArr0w
  • Topic Starter

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Local time:04:30 PM

Posted 10 November 2017 - 05:43 AM

Hello usasma,

 

I hope you have been well.

 

It's been a while but I have finally reformatted and done a refresh clean install of windows10 and sadly am starting to get BSOD's again. :(

 

Attached is a fresh Sysnative Report.

 

Hoping you will still be willing to help me with my issue!

 

Many thanks,

 

RedArrow

 

P.s. Here is my Dump file https://drive.google.com/file/d/16y_GencadctxjwF6Lc2BLEeUYTD9_BLx/view?usp=sharing

 

(I've turned on the mini dumps now, so anymore bsods will be the smaller dump files)

Attached Files


Edited by RedArr0w, 10 November 2017 - 06:09 AM.


#22 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 24,708 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:30 AM

Posted 10 November 2017 - 07:45 AM

You have only 3 partitions visible (C:\, D:\, E:\ ) on your 4 hard drives  - I'd think that there should be at least 4 partitions visible.

Please check to see which hard drive doesn't show partitions.  I'd suggest disconnecting the power and data cables to that hard drive to see if it helps the problem.

 

Please run these PSU tests:
- while you can measure the output of a PSU with a multimeter, the readings may change dramatically when the PSU is put under load.  PSU testing instructions (by dc3) here:  https://www.bleepingcomputer.com/forums/t/654994/pc-is-crashingfreezing-up-multiple-times-daily/page-2#entry4341756
- there's a free PSU test in the OCCT program at http://www.ocbase.com/

This device still doesn't have drivers installed:

 

H100iGTX Cooler    USB\VID_1B1C&PID_0C03\7289_1.0    The drivers for this device are not installed.

Please download and install the drivers for it.

 

The large MEMORY.DMP and the minidump from the Sysnative upload are from the same crash.

It appears to be a hardware problem.

As such, I'd ensure that you've run ALL of the hardware diagnostics (to include the PSU tests) from this page:  http://www.carrona.org/hwdiag.html

Then, if all of them pass - try this procedure to figure out which component has failed:  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:
**************************Fri Nov 10 05:33:42.499 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\MEMORY.DMP]
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
Built by: 16299.15.amd64fre.rs3_release.170928-1534
System Uptime:0 days 11:19:38.424
*** ERROR: Module load completed but symbols could not be loaded for win32kfull.sys
*** ERROR: Module load completed but symbols could not be loaded for win32kbase.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck 50, {ffffee7700000200, 0, fffff8019af41a6b, 2}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Arguments:
Arg1: ffffee7700000200, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8019af41a6b, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-4790K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4000
  BIOS Version                  V1.13
  BIOS Release Date             02/16/2016
  Manufacturer                  MSI
  Product Name                  MS-7917
  Baseboard Product             Z97 GAMING 5 (MS-7917)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov 10 05:33:42.499 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\111017-4812-01.dmp]
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
Built by: 16299.15.amd64fre.rs3_release.170928-1534
System Uptime:0 days 11:19:38.424
Probably caused by :memory_corruption
BugCheck 50, {ffffee7700000200, 0, fffff8019af41a6b, 2}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Arguments:
Arg1: ffffee7700000200, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8019af41a6b, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-4790K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4000
  BIOS Version                  V1.13
  BIOS Release Date             02/16/2016
  Manufacturer                  MSI
  Product Name                  MS-7917
  Baseboard Product             Z97 GAMING 5 (MS-7917)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


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 Nov 10 05:33:42.499 2017 (UTC - 5:00)**************************
MpKsl2940cfe4.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)
intelppm.sys                Thu Sep 22 06:43:11 2011 (4E7B113F)
Hamdrv.sys                  Mon Mar 30 09:28:42 2015 (55194F8A)
lgcoretemp.sys              Tue Jun  9 12:52:10 2015 (557719BA)
TeeDriverW8x64.sys          Tue Jul  7 13:43:32 2015 (559C0FC4)
LGVirHid.sys                Mon Jun 13 14:47:03 2016 (575EFFA7)
LGJoyXlCore.sys             Mon Jun 13 14:47:06 2016 (575EFFAA)
LGBusEnum.sys               Mon Jun 13 14:47:08 2016 (575EFFAC)
e2xw10x64.sys               Wed Sep 14 16:52:26 2016 (57D9B88A)
nvvad64v.sys                Sun May 28 19:04:45 2017 (592B578D)
nvhda64v.sys                Thu Sep 14 05:55:42 2017 (59BA521E)
nvlddmkm.sys                Thu Oct 12 15:39:32 2017 (59DFC4F4)
VBoxUSBMon.sys              Wed Oct 18 01:25:39 2017 (59E6E5D3)
VBoxDrv.sys                 Wed Oct 18 01:25:39 2017 (59E6E5D3)
VBoxNetAdp6.sys             Wed Oct 18 01:25:39 2017 (59E6E5D3)
VBoxNetLwf.sys              Wed Oct 18 01:25:39 2017 (59E6E5D3)


MpKsl2940cfe4.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=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=Hamdrv.sys
http://www.carrona.org/drivers/driver.php?id=lgcoretemp.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys
http://www.carrona.org/drivers/driver.php?id=LGJoyXlCore.sys
http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys
http://www.carrona.org/drivers/driver.php?id=e2xw10x64.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=VBoxUSBMon.sys
http://www.carrona.org/drivers/driver.php?id=VBoxDrv.sys
http://www.carrona.org/drivers/driver.php?id=VBoxNetAdp6.sys
http://www.carrona.org/drivers/driver.php?id=VBoxNetLwf.sys


 

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

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