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

Many Weird Problems on Windows 10 PC


  • Please log in to reply
6 replies to this topic

#1 KillTheCube

KillTheCube

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:11:09 AM

Posted 25 September 2017 - 11:43 AM

Hi everyone,
 

my PC is having a variety of problems I and none of the people I showed them to can explain.

This has been going on for a while, and I am now deciding to ask in this Forum in hope of finally finding a solution.

PC Details:

The PC is self-built, I ordered the Components online, and it worked fine for a while, so I think that component mismatches are unlikely.

OS:

Microsoft Windows 10 Pro N

Version 10.0.14393 Build 14393

Processor:

Intel Core i5-4440 CPU @ 3.10GHz

Mainboard:

Gigabyte H97-HD3

Graphics Card:

NVidia GeForce GTX 750

Main hard drive:

SanDisk SDSSDP128G

Additional hard drives:

Samsung SSD 850 EVO 1TB;

TOSHIBA STOR.E ALU 2S USB Device (1TB, used for backup)

I hope that's enough information , I will provide further details on request.

 

Now on to the problems I am experiencing, in order of appearance:

1. PC crashing on startup

Whenever I start up my PC from shutdown, it goes into a kind of blue screen and attempts to restart. This happens from 5 to 20 times, sometimes ever more often, until the system reaches that magical state of stability, where I can use the PC normally. This does not happen after energy saving mode, or after a normal restart.

Different "Stopcodes" that have appeared on a sample startup, which had a total of 14 crashes:

BAD_POOL_HEADER

MEMORY_MANAGEMENT (happened 6 times in total)

KERNEL_SECURITY_CHECK_FAILURE

DPC_WATCHDOG VIOLATION (happened 4 times in total)

REFERENCE_BY_POINTER

CRITICAL_PROCESS_DIED

I should probably also mention that there is no fixed point at which the crashes occur. Sometimes the PC seems stable for a couple of minutes before crashing again.

Once it's completely stable though, it never crashes again until you shut down the pc and start it up again.

2. Updates failing multiple times

A small but annoying problem. My PC always needs a couple of days and thereby multiple attempts to install windows updates, and so my pc almost always wakes up form power save mode during my sleep.

I don't know if it is a common problem that windows updates take a couple of tries, but I don't see a reason why it should be.

3. Task Bar and other things don't function properly

There are multiple functions of my pc that stopped working at some point (I don't remember exactly what I did beforehand).

Here are the things I noticed to not be working:

1. The start button as well as the notifications button and the return to desktop button do absolutely nothing.

2. The Task bar can't be disabled anymore, meaning it is present during anything that isn't a fullscreen game.

3. When right-clicking the task bar, I can't access the system settings anymore. Pressing the "settings" button just does nothing.

4. Opening a picture with the standard windows pictures program throws out this error: [image path] Class not registered

 

That's my PC, and I am really embarrased to be having so many problems with it. Any help you can give is greatly appreciated.

Thanks,

Robert

 

Edit: Report Set #1 Attached File  ROBERT_PC_26.09.2017_18_02_06.zip   9.75MB   2 downloads


Edited by KillTheCube, 26 September 2017 - 11:15 AM.


BC AdBot (Login to Remove)

 


#2 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:05:09 AM

Posted 26 September 2017 - 08:06 AM

Have you tried reinstalling Windows?

 

Let's try looking at these 2 sets of reports:

Report Set #1)  Please run this report collecting tool (even though you may not be experiencing BSOD's) so that we can provide a complete analysis: (from the pinned topic at the top of the forum)   http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/

If you have problems with it running it, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR or other compression utilities. 
.ZIP is the type file that can be uploaded to the forums.

Report Set #2)  Please do the following:
- open Event Viewer (run eventvwr.msc from the "Run" dialog)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on the "Administrative Events" heading
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

FYI - If we're looking for Event ID 41 errors (unexplained shutdowns), there's more info on that here:  http://support.microsoft.com/kb/2028504

While waiting for a reply, please monitor your temps with this free utility: 

SpeedFan v. 4.5.1 and later (free from here:  http://www.almico.com/sfdownload.php ) can log temperatures in a CSV file:
You may not need to log temps - if uncertain, please ask.

To make it work (log the temps to a file) you have to do BOTH of the below:

1. Enable logging in general: Configure...Log...check "Enabled" then click on OK to save.

2. Enable logging for specific checks: Configure...Temperatures..left click on each sensor, then click on "Logged" at the bottom of the Window (for our purposes we want them all) then once you've selected "Logged" for all sensors, then click on OK to save.

The log will be located at C:\Program Files (x86)\SpeedFan

Naming: log files are named SFLogYYYYMMDD.csv, where YYYY is the year (four digits), MM is the month (2 digits, zero padded) and DD is the day (2 digits, zero padded). If a file already exists by that name, the file that already exists is renamed according to the following naming scheme: SFLogYYYYMMDD-CCCC.csv, where CCCC is a increasing number. The new file is then created with the standard file name scheme.

Notes: whenever you change the options related with logging, SpeedFan starts a new log file.

NOTE:You may want to turn logging off when we're done - as I don't know it's impact on performance or on the system.



 
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.

#3 KillTheCube

KillTheCube
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:11:09 AM

Posted 26 September 2017 - 11:23 AM

Hello usasma,

thank you for your quick reply!

I have not tried reinstalling Windows, as I do not know how I should accomplish it. I don't have an installation disc because I upgraded from windows 7 as part of the free update event.

The results to the first report set are attached to my original post, and I have also followed the steps of the second report set:

https://drive.google.com/open?id=0B_EkbEraTMYuMjluNm84eHdLSDQ

 



#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:05:09 AM

Posted 27 September 2017 - 06:19 AM

Your UEFI/BIOS (version F4) dates from 2014.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it.  WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.
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 the outdated UEFI/BIOS' may be the cause of some compatibility issues).

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

J: drive has much, much less than 1% free space.  Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance.  Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty).  Low free space can cause BSOD's - but the actual amount depends on the files being used by the system.  I strongly suspect that this is contributing to your problem.

 

These 2 devices have problems in Device Manager:

 

LogMeIn Hamachi Virtual Ethernet Adapter    ROOT\NET\0000    Das Gerät wurde deaktiviert.
Unbekanntes USB-Gerät (Fehler beim Anfordern einer Gerätebeschreibung.)    USB\VID_0000&PID_0002\5&E658374&0&11    43

Please uninstall LogMeIn. If it's needed again, you can always download a fresh copy (disabled devices still load their device drivers before they are disabled)

The second one seems to be a USB failure (my Deutsch is very limited).  I'd suggest removing all USB devices to see if you can figure out which device is causing the problem.

 

There's a lot of Live Kernel Events (without corresponding BSOD events) in the WER section of the MSINFO32 report.

Sometimes this is a sign of a hardware problem.

Please run these free hardware diagnostics and let us know the results:  http://www.carrona.org/hwdiag.html

 

Out of 50 memory dumps there were 11 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
- overfull hard drives (drives with less than 15% free space)
- 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.

 

Please update these older drivers.  Links are provided in order to assist you with looking up the source of the drivers.  
If unable to find an update, please uninstall the program that is responsible for that driver.  

DO NOT manually delete/rename the driver as it may make the system unbootable!!!:

PTSimBus.sys                Wed Jun 17 22:20:48 2009 (4A39A480)
PenTablet Bus enumerator Unknown, clue here: http://driverscollection.com/?aid=420646578662c19a8e75a3a31ae
http://www.carrona.org/drivers/driver.php?id=PTSimBus.sys
 
PTSimHid.sys                Fri Jun 22 03:20:14 2012 (4FE41CAE)
Wacom PenTablet Simulated HID Port Driver http://www.wacom.com/en/CustomerCare/Drivers.aspx or at the OEM support website if it came built in to your system
http://www.carrona.org/drivers/driver.php?id=PTSimHid.sys
 
rtwlanu.sys                 Thu Sep 27 04:45:41 2012 (50641235)
Realtek RTLxxxxx Wireless USB 2.0 Adapter [br]Used by different manufacturer's http://www.realtek.com.tw/downloads/
http://www.carrona.org/drivers/driver.php?id=rtwlanu.sys
 
UCTblHid.sys                Mon Nov 11 04:16:09 2013 (5280A059)
Wacom PenTablet HID Tablet Port Driver http://www.wacom.com/en/CustomerCare/Drivers.aspx or at the OEM support website if it came built in to your system
http://www.carrona.org/drivers/driver.php?id=UCTblHid.sys
 
TClass2k.sys                Mon Nov 11 04:17:19 2013 (5280A09F)
Wacom PenTablet Tablet Class Driver http://www.wacom.com/en/CustomerCare/Drivers.aspx or at the OEM support website if it came built in to your system
http://www.carrona.org/drivers/driver.php?id=TClass2k.sys
 
Hamdrv.sys                  Mon Mar 30 09:28:42 2015 (55194F8A)
LogMeIn Hamachi Virtual Miniport Driver https://secure.logmein.com/products/ios/
http://www.carrona.org/drivers/driver.php?id=Hamdrv.sys
 
usbaapl64.sys               Thu Jun 11 02:08:10 2015 (557925CA)
Apple iPod/iPhone Mobile USB device driver http://www.apple.com/downloads/
http://www.carrona.org/drivers/driver.php?id=usbaapl64.sys
 
TeeDriverW8x64.sys          Tue Jul  7 13:43:32 2015 (559C0FC4)
Intel Management Engine Interface (MEI) driver OEM or http://downloadcenter.intel.com[br][br]Installation instructions - http://www.sysnative.com/forums/windows-10-a/18573-windows-10-error-0x800f081f-source-file-not-found.html#post144391
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
 

The Analysis information from the 50 memory dumps that I analyzed will be posted in the next post (it's too large for this one).

 

The next step after this (if the above doesn't fix things), is to try a clean install of Windows.  Here's how I suggest that you do that (if it's needed):

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.

Edited by usasma, 27 September 2017 - 06:27 AM.

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.

#5 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:05:09 AM

Posted 27 September 2017 - 06:28 AM

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Thu Sep 21 07:51:51.826 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\092117-8734-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.953.amd64fre.rs1_release_inmarket.170303-1614
System Uptime:1 days 6:37:22.532
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by :hardware ( igdkmd64+d3dd6 )
BugCheck 50, {ffffbd894bdaf8c7, 2, fffff80a29d73dd6, 2}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Arguments:
Arg1: ffffbd894bdaf8c7, memory referenced.
Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.
Arg3: fffff80a29d73dd6, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: IP_MISALIGNED_igdkmd64.sys
CPUID:        "Intel® Core™ i5-4440 CPU @ 3.10GHz"
MaxSpeed:     3100
CurrentSpeed: 3100
  BIOS Version                  F4
  BIOS Release Date             06/10/2014
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  H97-HD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Sep 19 09:20:35.914 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\091917-6203-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.953.amd64fre.rs1_release_inmarket.170303-1614
System Uptime:0 days 0:01:16.620
Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 133, {0, 501, 500, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding this single DPC timeout
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  ZEROED_STACK_0x133
PROCESS_NAME:  System
FAILURE_BUCKET_ID: ZEROED_STACK_0x133
CPUID:        "Intel® Core™ i5-4440 CPU @ 3.10GHz"
MaxSpeed:     3100
CurrentSpeed: 3100
  BIOS Version                  F4
  BIOS Release Date             06/10/2014
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  H97-HD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Sep 19 09:18:39.831 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\091917-6781-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.953.amd64fre.rs1_release_inmarket.170303-1614
System Uptime:0 days 0:01:45.537
Probably caused by :Pool_Corruption ( nt!ExFreePool+825 )
BugCheck 19, {e, ffffd106a6a22990, ffffd106a6a21a58, 9b6b6bfe1c71f7b4}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments:
Arg1: 000000000000000e,
Arg2: ffffd106a6a22990
Arg3: ffffd106a6a21a58
Arg4: 9b6b6bfe1c71f7b4
BUGCHECK_STR:  0x19_e
PROCESS_NAME:  SearchFilterHo
FAILURE_BUCKET_ID: 0x19_e_nt!ExFreePool
CPUID:        "Intel® Core™ i5-4440 CPU @ 3.10GHz"
MaxSpeed:     3100
CurrentSpeed: 3100
  BIOS Version                  F4
  BIOS Release Date             06/10/2014
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  H97-HD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
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 Sep 21 07:51:51.826 2017 (UTC - 4:00)**************************
PTSimBus.sys                Wed Jun 17 22:20:48 2009 (4A39A480)
PTSimHid.sys                Fri Jun 22 03:20:14 2012 (4FE41CAE)
UCTblHid.sys                Mon Nov 11 04:16:09 2013 (5280A059)
TClass2k.sys                Mon Nov 11 04:17:19 2013 (5280A09F)
TeeDriverW8x64.sys          Tue Jul  7 13:43:32 2015 (559C0FC4)
rt640x64.sys                Thu Jan 21 03:17:40 2016 (56A09424)
IntcDAud.sys                Tue May 10 04:08:56 2016 (57319718)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
hiber_storport.sys          Fri Jul 15 22:21:57 2016 (57899A45)
nvhda64v.sys                Thu Sep 29 09:25:06 2016 (57ED1632)
igdkmd64.sys                Thu Sep 29 10:43:27 2016 (57ED288F)
nvvad64v.sys                Fri Nov 25 10:43:56 2016 (58385C3C)
SYMEVENT64x86.SYS           Mon Dec 12 21:53:18 2016 (584F629E)
nvlddmkm.sys                Thu Dec 29 07:39:24 2016 (586503FC)
ccSetx64.sys                Thu Jun  8 17:26:21 2017 (5939C0FD)
Ironx64.SYS                 Thu Jun  8 17:58:52 2017 (5939C89C)
SYMEFASI64.SYS              Fri Jun  9 18:10:12 2017 (593B1CC4)
eeCtrl64.sys                Tue Jun 13 20:10:51 2017 (59407F0B)
EraserUtilRebootDrv.sys     Tue Jun 13 20:10:52 2017 (59407F0C)
SYMNETS.SYS                 Wed Jun 14 15:55:08 2017 (5941949C)
SRTSP64.SYS                 Sun Jun 25 13:52:36 2017 (594FF864)
SRTSPX64.SYS                Sun Jun 25 13:55:10 2017 (594FF8FE)
IDSvia64.sys                Wed Jul 26 16:25:09 2017 (5978FAA5)
RTKVHD64.sys                Tue Aug  8 06:41:38 2017 (59899562)
BHDrvx64.sys                Wed Sep  6 19:34:58 2017 (59B08622)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Sep 18 14:30:47.012 2017 (UTC - 4:00)**************************
usbaapl64.sys               Thu Jun 11 02:08:10 2015 (557925CA)
BHDrvx64.sys                Fri Jun 23 00:20:53 2017 (594C9725)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Aug 27 03:59:02.919 2017 (UTC - 4:00)**************************
EraserUtilDrv11720.sys      Tue Jun 13 20:10:52 2017 (59407F0C)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Aug 26 08:49:34.488 2017 (UTC - 4:00)**************************
magdrvamd64.sys             Wed Aug 26 07:30:12 2015 (55DDA344)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Aug 25 13:33:49.680 2017 (UTC - 4:00)**************************
rtwlanu.sys                 Thu Sep 27 04:45:41 2012 (50641235)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Aug  8 22:15:17.044 2017 (UTC - 4:00)**************************
xusb22.sys                  Fri Jul 15 22:28:13 2016 (57899BBD)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Aug  4 22:39:20.675 2017 (UTC - 4:00)**************************
SYMNETS.SYS                 Wed Nov  2 00:07:06 2016 (5819666A)
Ironx64.SYS                 Fri Jan  6 18:32:48 2017 (58702920)
SYMEFASI64.SYS              Mon Apr 17 22:16:23 2017 (58F576F7)
ccSetx64.sys                Mon Apr 17 22:35:05 2017 (58F57B59)
SRTSP64.SYS                 Tue Apr 18 14:07:15 2017 (58F655D3)
SRTSPX64.SYS                Tue Apr 18 14:09:51 2017 (58F6566F)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Aug  4 08:14:51.786 2017 (UTC - 4:00)**************************
SYMEVENT64x86.SYS           Thu Sep  8 15:47:29 2016 (57D1C051)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Aug  4 05:55:27.499 2017 (UTC - 4:00)**************************
ccSetx64.sys                Thu May  5 18:33:33 2016 (572BCA3D)
SYMEFASI64.SYS              Wed Aug  3 01:50:18 2016 (57A1861A)
Ironx64.SYS                 Fri Sep  2 17:44:25 2016 (57C9F2B9)
SRTSPX64.SYS                Fri Sep  2 21:56:42 2016 (57CA2DDA)
SRTSP64.SYS                 Tue Sep 13 21:14:58 2016 (57D8A492)
SYMNETS.SYS                 Wed Sep 14 22:43:10 2016 (57DA0ABE)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Aug  2 22:38:05.818 2017 (UTC - 4:00)**************************
eeCtrl64.sys                Fri Sep 16 22:16:39 2016 (57DCA787)
SYMEFASI64.SYS              Wed Oct 12 14:18:04 2016 (57FE7E5C)
IDSvia64.sys                Wed Oct 19 18:31:54 2016 (5807F45A)
BHDrvx64.sys                Fri Nov  4 05:39:20 2016 (581C5748)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Aug  2 10:46:32.624 2017 (UTC - 4:00)**************************
MpKsl1d88cf45.sys           Tue May 19 21:50:37 2015 (555BE86D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jul 20 23:07:13.883 2017 (UTC - 4:00)**************************
Hamdrv.sys                  Mon Mar 30 09:28:42 2015 (55194F8A)
MpKslce23a185.sys           Tue May 19 21:50:37 2015 (555BE86D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jul 20 09:00:15.942 2017 (UTC - 4:00)**************************
MpKsl32d12aea.sys           Tue May 19 21:50:37 2015 (555BE86D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul 17 10:31:06.059 2017 (UTC - 4:00)**************************
MpKsl1f0bc630.sys           Tue May 19 21:50:37 2015 (555BE86D)
MpKsld817f598.sys           Tue May 19 21:50:37 2015 (555BE86D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jul  8 05:26:01.766 2017 (UTC - 4:00)**************************
MpKslfd19bdb4.sys           Tue May 19 21:50:37 2015 (555BE86D)


http://www.carrona.org/drivers/driver.php?id=PTSimBus.sys
http://www.carrona.org/drivers/driver.php?id=PTSimHid.sys
http://www.carrona.org/drivers/driver.php?id=UCTblHid.sys
http://www.carrona.org/drivers/driver.php?id=TClass2k.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=hiber_storport.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=SYMEVENT64x86.SYS
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=ccSetx64.sys
http://www.carrona.org/drivers/driver.php?id=Ironx64.SYS
http://www.carrona.org/drivers/driver.php?id=SYMEFASI64.SYS
http://www.carrona.org/drivers/driver.php?id=eeCtrl64.sys
http://www.carrona.org/drivers/driver.php?id=EraserUtilRebootDrv.sys
http://www.carrona.org/drivers/driver.php?id=SYMNETS.SYS
http://www.carrona.org/drivers/driver.php?id=SRTSP64.SYS
http://www.carrona.org/drivers/driver.php?id=SRTSPX64.SYS
http://www.carrona.org/drivers/driver.php?id=IDSvia64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys
http://www.carrona.org/drivers/driver.php?id=usbaapl64.sys
http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys
EraserUtilDrv11720.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=magdrvamd64.sys
http://www.carrona.org/drivers/driver.php?id=rtwlanu.sys
http://www.carrona.org/drivers/driver.php?id=xusb22.sys
http://www.carrona.org/drivers/driver.php?id=SYMNETS.SYS
http://www.carrona.org/drivers/driver.php?id=Ironx64.SYS
http://www.carrona.org/drivers/driver.php?id=SYMEFASI64.SYS
http://www.carrona.org/drivers/driver.php?id=ccSetx64.sys
http://www.carrona.org/drivers/driver.php?id=SRTSP64.SYS
http://www.carrona.org/drivers/driver.php?id=SRTSPX64.SYS
http://www.carrona.org/drivers/driver.php?id=SYMEVENT64x86.SYS
http://www.carrona.org/drivers/driver.php?id=ccSetx64.sys
http://www.carrona.org/drivers/driver.php?id=SYMEFASI64.SYS
http://www.carrona.org/drivers/driver.php?id=Ironx64.SYS
http://www.carrona.org/drivers/driver.php?id=SRTSPX64.SYS
http://www.carrona.org/drivers/driver.php?id=SRTSP64.SYS
http://www.carrona.org/drivers/driver.php?id=SYMNETS.SYS
http://www.carrona.org/drivers/driver.php?id=eeCtrl64.sys
http://www.carrona.org/drivers/driver.php?id=SYMEFASI64.SYS
http://www.carrona.org/drivers/driver.php?id=IDSvia64.sys
http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys
MpKsl1d88cf45.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=Hamdrv.sys
MpKslce23a185.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.
MpKsl32d12aea.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.
MpKsl1f0bc630.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.
MpKsld817f598.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.
MpKslfd19bdb4.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.
 
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.

#6 KillTheCube

KillTheCube
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:11:09 AM

Posted 27 September 2017 - 12:03 PM

Hello John,

Thank you so very much for your help.

I downloaded the latest stable BIOS update for my mainboard, and after installing it, the problems concerning the startup crashes disappeared.

After that I installed WIndows 10 from a Stick, deleting all my files(I backed important files up before doing so), and voila, everything is working as intended.

You, sir, are a genius. Now I only have to reinstall the programs I need for my everyday use, and I am good to go :).

Robert



#7 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:05:09 AM

Posted 28 September 2017 - 06:31 AM

Thanks for the kind words  :0)

I'm glad that you've gotten it back up and running without problems.

Thanks for letting us know - it'll help others who come looking for help with similar problems!


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