Tweaking.com Support Forums
Main Forum => General Computer Support => Topic started by: qaz on June 29, 2018, 11:49:29 am
-
hi
win repairs says ive got 3 files missing so i cant run
any help appreciated
Missing File: Files\Permissions\10\windows.7z
Missing File: Files\registry_backup_tool\Codejock.Controls.Unicode.v17.2.0.ocx
Missing File: msinet.ocx
-
Have you ran an antimalware scan to check if your machine has been infected ?
Have you performed the pre steps of running a chkdsl /r and a sfc /scannow ?
Can you use Tweaking.com's uninstaller to remove the program and then download it again to see if you get the same error.
-
hi
done all except chkdsl /r and a sfc /scannow. how can an new install help missing files
thanx
-
I think those missing files relate to the program, so an uninstall/reinstall may resolve - has it ?
To see what the chkdsk /r reported, open Event Viewer and ensure Event Viewer (Local) is highlighted in the left pane - if it isn't then just click on it.
When it has finished reading the data and you see Critical, Error etc. expand Windows Logs in the left pane - click on Application - Action/Find then type chkdsk or wininit into the Find box and press enter.
Cancel the Find box and read the log in the scrollable window below.
You are looking to see if it reports any KBs in bad sectors.
Also let us know what the sfc /scannow reports.
-
yes a new instal worked...thanx. did a chhdisc [both checks plus repair] but could catch the report.
importantly i have another problem u may be able to assist with if u have time. cant get linux or windows pe disc [made at Aomei backup site to restore Aomei images] to boot, but other disks are ok.
some error about communicating with the attached drive
is this correct connection pls: h/d to sata 0 and optical drive to sata 1 [nothing else]
thanx
-
Glad to see the reinstall sorted that missing file problem.
Just used to using laptops, I'm not into desktop hardware of things.
If this not communicating error is a recent thing then I would say the way you have them connected is fine, but you could run a chkdsk /r on the ext. drive.
The cmd would be chkdsk x: /r where x is your drive letter for the ext. drive.
It's report would remain on screen without the need for a reboot to execute.
As for checking to see what the chkdsk /r reported for the internal HDD, open Event Viewer ensuring Event Viewer (Local) is highlighted in the left pane, expand Windows Logs when it has read the data then click on Application/Action/Find then type chkdsk or wininit into the Find box and press enter.
Cancel the Find box then read the log in the scrollable window below, noting if it reports any KBs in bad sectors.
-
dont understand how could i run a chkdsk /r on the ext. drive....its an optical drive!
thanks
i can post a jpeg of error i got
-
error, thanx for looking
-
I was under the impression that it couldn't communicate with an ext. HDD that you had the image on.
You could try creating new disks or put them onto USBs which could eliminate the DVD drive.
-
yes ur right image is on usb hhd, i need linux or pe to access it at boot time
i could make new disc but ive got several linux disks which don't work either, and a couple of others that do. do u still think next step is make new disk?
any ideas about the photo i posted above?
thanx
-
If it relates to an USB ext. HDD then you could run a chkdsk on it but you can also download the 30 trial version of HDSentinel which will analyze all connected HDDs and give a written report on them.
https://www.hdsentinel.com/hard_disk_sentinel_trial.php
Hit the Download button and select Save and then you can extract it in your Downloads folder and then uninstall it when done to stop the clock and then reinstall it from there as and when.
It's interesting that some disks work and some don't which could point to either the disks or the disk drive.
I'd start by creating either new disks or put the PEs onto USBs.
-
am sure ive failed to explain well. image is on usb drive but to install it i need to boot from linux or pe.
connection to the usb drive is fine far as i know. i dont know what the error msg relates to other than the optical drive, can u make sense of it
thanks
-
I use Macrium Reflect Free and have to boot up with a WPE disk to load the program and then I connect my ext. HDD.
The error message could relate to either a disk drive or ext. HDD.
At what point does the message pop up ?
Try HDSentinel and if that gives your ext. HDD a clean bill of health then see if new disks will work, but I'd try putting the PE onto an USB and then see what you get.
-
heres the report but im not understanding something , im sure. that msg pops up after i tell it to boot from pe disk. i will simply unplug the usb drive then its out of the evasion
c drive is perfect apparently
yes i will put pe on a memory stick tomorrow and let u know
thanks
Hard disk case: weak sectors
There are weak sectors found on the hard disk surface.
This example shows the status of a Seagate 250 GB SATA hard disk.
Hard disk problems reported
increased boot times, blue screen (BSOD) during boot, system restore required
files / folders hardly or slowly accessed or even can't be read at all
chkdsk / scandisk reported "bad sectors" on the partition
First hard disk checks
Initially, the hard disk health reported was 81 %. The text description shows the actual problems with the hard disk:
There are 31 weak sectors found on the disk surface. They may be remapped any time in the later use of the disk.
The Disk -> Short self test and Disk -> Extended self test functions quickly stop with an error indicating that there is a problem:
Test failed by read element
Using chkdsk to "repair" the bad sectors also confirm that there is a problem with the partition (notice the 13928 KB in bad sectors):
CHKDSK shows bad sectors
Hard disk weak sectors
A "weak sector" or "pending sector" (the same but with different name) is a sector where the CRC check showed problems on a read operation, but (currently) no physical problem encountered. The drive marks such sector as "pending sector" and on next write operation(s) the drive verifies the status of the corresponding sector to confirm if it can be re-used or not.
If things are good, the drive sector could read back and there are no signs of problems, then the status of the sector set back to normal (the number of such weak sectors may decrease and there is no re-allocation). But if this verification shows failure, then the drive starts the reallocation process and marks the sector as bad - to completely disable its later use and re-direct all further reads and writes to the spare area instead. Then the number of bad (reallocated) sectors may incrase and they may be reported in Hard Disk Sentinel.
Usually, weak sectors can be caused by
real drive failure (error with internal memory, problem with drive head or surface)
power loss (the write operation could not be completed because of power loss)
power failure (weak power supply or not stable power line)
data cable failure or improper connection (usually cause also communication errors )
system memory or motherboard problem
overclocking
general overheating of the motherboard, chipset, hard disk controller
Because weak sectors may not indicate real failure of the hard disk drive, they are not counted as seriously as real bad sectors or other attributes / issues. Anyway, these should be noticed also because they can cause serious problems if they are located in the administrative areas of the hard disk drive (boot record, MFT, critical system files) and/or if the number of weak sectors is high.
This may sound weird, but in most cases the weak sectors do not indicate real problems with the hard disk. As a side effect, chkdsk may detect bad sectors on the actual partition (logical drive) and marks them as bad to prevent accessing that particular logical drive area. However, this is not the best solution because chkdsk does not repair the hard disk drive itself, only the partition (the logical drive). It means that if a re-partition and re-format would be ever required, the problems are still there, the problematic sectors would be used again, they may cause data loss / corruption again and re-running chkdsk may find them again - a vicious circle.
Not stable hard disk status
When weak sectors reported by Hard Disk Sentinel, the first thing to be considered that the problem may not be the failure of the hard disk itself, but a problem caused by the operating environment. It is recommended to check the items listed above, replace data / power cables, verify the power supply. If this does not happen, we may expect further weak sectors to be detected during the later use of the hard disk. For example, if the status is not stable, performing even an antivirus scan or using Disk -> Read Test function may reveal further "weak sectors" on the hard disk surface. Notice that the number of red spots (unreadable sectors, showing the position of the weak sectors) are higher than the previously reported weak sectors:
Read test shows new problems on hard disk surface
Repair weak sectors
To completely repair weak sectors, it is required to perform the overwrite of the disk surface. This would ensure that the currently reported and all possible new (currently not detected) weak sectors would be carefully re-tested and the hard disk can perform the required steps: to reallocate the sector (if it can't be re-used and required to replace with a spare sector) or to repair it if the sector can be re-used without problems. The best way is to perform the overwrite with special initialisation patterns to help the hard disk to perform the verification of the underlying weak sectors and test if the sector is usable and works accurately after different overwrite passes and then could be read back without problems.
The Disk menu -> Surface test -> Reinitialise disk surface is the best way to repair the hard disk. The test permanently fixes the weak sectors and make the hard disk drive more usable in general.
After using Disk menu -> Surface test -> Reinitialise disk surface test, the hard disk status will be stable and the complete surface can be used without problems. Ideally, absolutely no reallocation required: the hard disk may return to PERFECT status and 100% health would be reported again:
The hard disk status is PERFECT. Problematic or weak sectors were not found and there are no spin up or data transfer errors.
Re-running the Disk -> Extended self-test function confirms that now there are no problems:
Disk -> Extended self-test successfully completed
Re-running the Disk -> Surface test -> Read test function also confirms that the disk surface is now perfect, there are no damaged or bad blocks found:
Read test shows there are no problems on hard disk surface
And even the performance graph shows that the complete hard disk surface is correctly accessible, without any significant delays:
Read test shows the performance
And re-running chkdsk to check and repair bad sectors would show no bad sectors (notice the 0 KB in bad sectors):
CHKDSK shows 0 KB in bad sectors
Recommendations
The best way is to prevent weak sectors. When they reported, Hard Disk Sentinel can help to diagnose and repair them, usually they can be completely repaired with Hard Disk Sentinel by using Disk -> Surface test -> Reinitialise disk surface test.
Consider using high quality cables, for example SATA cables with SATA 6G designation (especially if you prefer to use a SATA 6G device)
Avoid using power cable extenders, Y power splitters, 4 pin -> SATA power cable converters
Use good quality power supply with higher output rating to make sure the drives would get enough power to operate correctly
Consider using an UPS to prevent power spikes / power loss which can cause weak sectors
Consider extra cooling for the system in general, especially if you use high-level video cards and/or other devices producing excessive heat
When weak sectors reported, start Disk -> Surface test -> Read test in Hard Disk Sentinel and save the resulting disk surface map before starting Disk -> Surface test -> Reinitialise disk surface test. This way after repairing the hard disk drive, if "weak sectors" would be reported again in the future, running Disk -> Surface test -> Read test again would confirm the situation: if the problem is reported in the same block on the hard disk surface area, it may be related to the hard disk itself, but if the issue is reported in other areas (usually random areas as shown in this example), the status may be more related to the operating environment - not the actual hard disk drive.
It is good idea to test and repair the hard disk drive in a completely different environment: connecting the hard disk to a different computer where different power supply, hard disk controller, devices, drivers used.
Update in version 5.00 : Disk Repair test
Hard Disk Sentinel Pro since 5.00 version has a new function designed exactly to repair such weak sectors on any disk drive (hard disks, SSDs, flash media and so) without the need of complete backup and without performing disk erase. The new Disk menu -> Surface test -> Disk repair test designed to diagnose and attempt to repair easier by performing a read test - and attempting the repair specifically on the affected sectors found problematic during this test. After the test, possible damaged files (located on the original problematic, damaged sectors) listed for reference.
Ideally Disk menu -> Surface test -> Disk repair test can help to repair drive completely, especially if the number of problems are relatively low and the hard disk is stable otherwise. In case of bigger problems and/or if weak sectors still reported, it is recommended to perform the above check-list (verify cables, connections, power source etc. and then re-run the Disk repair function) and if required, consider using the Reinitialise disk surface test too.
-
From what I understand from the HDS report, the surface test resolved any errors on the HDD ?
Have you checked the connections etc. as it advises ?
When you remove the ext. HDD after putting an image onto it, do you just unplug it or use the safe to eject function as you should do ?
When you boot up from a disk and you have an ext. HDD plugged in, it can confuse the machine and cause boot problems.
-
g/morning
am at it again. tried to make another PE on memory stick but got an error . i think its related to the fact that if i try to make a new folder on desktop or move a file into one i get error: cant find item. no longer located in c: desktop. verify location and try again. when i try again it always succeeds
in properties the folder appears to be on c: even before i "try again"
any ideas appreciated
thanks
-
Reboot and try the pe onto the USB again without doing anything else.
I assume the program allows for the pe to be put onto an USB ?
-
its called a pe builder , i saw no option to put on usb.
but i fixed the "no longer located in c: desktop." by restoring registry in win tweaking, i recall make changes i didn't fully understand.
anyway im back to the error when trying to install pe builder, error msg: error while trying to rename file in destination directory. move file failed. try again
-
Let's see if you can make a bootable USB from the PE disk using Diskpart.
This article will walk you through the steps, but first check that the drive can read the disk by inserting it to see if it comes up in Windows Explorer and then double clicking on its drive to open to the files.
https://www.dell.com/support/article/us/en/04/sln153692/how-to-transfer-your-operating-system-from-a-cd-dvd-to-a-bootable-usb?lang=en
-
retraced my steps, am trying to put pe on a bootable usb stick but no luck, [apparently it can be done] . cant install pe environment either , do u know what it is and whether i need it?
i should be able to do these surely even if i take ur advice and put the pe disc un usb using Diskpart
thanx
-
I don't know the program so I can't advise you about the pe installer - I use Macrium Reflect Free.
Have you checked to see if it can be done in Safe Mode With Networking ?
The Diskpart steps are clearly described if you still have problems in that mode.
-
was just about to go and use diskpart, but i opened Aomie and to my surprise it started installing the failed pe environment and then pe ....aghhh . these Chinese are well meaning but there English causes so many problems often. i gave up with them last time:)
anyway all is well now it seems except i need to find why pe install didnt see my usb, i'll run tweaking repair
thanx very much for ur help
mark
-
Before you do that, does the pe disk boot up now for you to restore with an image ?
-
when i returned from shops it had done that after a new full backup , but will check tomorrow
-
Weren't you wanting to restore from an earlier image ?
-
i was but it was all tangled up with 3 days of mixed problems which turned out to be bad memory modual. after pc recovered still wanted to tackle the mirror image access
i installed hd sentinel which reported my seagate usb drive with problems but seagates own program says its ok [short generic test] will do long one tomorrow
any ideas here?
thanks
-
You'll have to wait to see what it reports.
On one of my laptops HDS reported quite a lot of bad sectors which increased with each analysis but a chkdsk, SeaTools for Windows and SeaTools for DOS said it was okay.
Erring on the side of caution although I wasn't experiencing any problems that could be associated with a bad drive, I replaced the HDD.
On another instance on another laptop, a chkdsk reported bad sectors and having to restore with a system image for a particular reason, when I ran another chkdsk, it came up clean.
That was on this machine which has been running fine ever since.
-
oh dear, there seems no obvious solution..... i dont fully trust hds as it only took 2 mins or less to conclude.
i had another blue screen/crash today, but just one
thanx
-
It doesn't take HDS long to check a HDD, but download BlueScreenView which will analyze the memory dump files to see what could be causing the BSOD - do these just occur when you have your ext. HDD plugged in ?
https://www.nirsoft.net/utils/blue_screen_view.html
You can post its report.
-
brilliant. installing it now. only happened once since the big recovery [usb drive in place] if it happens again will unplug it and wait
pc's been in constant use today since about 10 am when bsd occurred, what have done by coincidence is remove ram strips and re seat [to check notches in their boards] any idea which numbers in speccy or whatever relate to the position of the notch as i find that 2 strips of ddr2 can be different
thanks
update
i see it collects info about previous bsd. here it is if u have a moment, i cant se anything meaningful or highlighted:
ntoskrnl.exe ntoskrnl.exe+10caa6 fffff800`03015000 fffff800`035f8000 0x005e3000 0x5add19ea 23/04/2018 00:25:30 Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.24117 (win7sp1_ldr_escrow.180422-1430) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe
hal.dll fffff800`035f8000 fffff800`03640000 0x00048000 0x5add2228 23/04/2018 01:00:40 Microsoft® Windows® Operating System Hardware Abstraction Layer DLL 6.1.7601.24117 (win7sp1_ldr_escrow.180422-1430) Microsoft Corporation C:\Windows\system32\hal.dll
kdcom.dll fffff800`00bbd000 fffff800`00bc7000 0x0000a000 0x4d4d8061 05/02/2011 17:52:49 Microsoft® Windows® Operating System Serial Kernel Debugger 6.1.7601.17556 (win7sp1_gdr.110204-2120) Microsoft Corporation C:\Windows\system32\kdcom.dll
mcupdate_AuthenticAMD.dll fffff880`00c0c000 fffff880`00c19000 0x0000d000 0x4a5bdf65 14/07/2009 02:29:09 Microsoft® Windows® Operating System AMD Microcode Update Library 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\mcupdate_AuthenticAMD.dll
PSHED.dll fffff880`00c19000 fffff880`00c2d000 0x00014000 0x4a5be027 14/07/2009 02:32:23 Microsoft® Windows® Operating System Platform Specific Hardware Error Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\PSHED.dll
CLFS.SYS fffff880`00c2d000 fffff880`00c8c000 0x0005f000 0x5ac8e7a4 07/04/2018 16:45:40 Microsoft® Windows® Operating System Common Log File System Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\CLFS.SYS
CI.dll fffff880`00c8c000 fffff880`00d01000 0x00075000 0x53acd215 27/06/2014 03:08:21 Microsoft® Windows® Operating System Code Integrity Module 6.1.7601.24117 (win7sp1_ldr_escrow.180422-1430) Microsoft Corporation C:\Windows\system32\CI.dll
Wdf01000.sys fffff880`00d01000 fffff880`00dc3000 0x000c2000 0x51c51641 22/06/2013 04:13:05 Microsoft® Windows® Operating System Kernel Mode Driver Framework Runtime 1.11.9200.16384 (win8_rtm.120725-1247) Microsoft Corporation C:\Windows\system32\drivers\Wdf01000.sys
WDFLDR.SYS fffff880`00dc3000 fffff880`00dd3000 0x00010000 0x5010ab70 26/07/2012 03:29:04 Microsoft® Windows® Operating System Kernel Mode Driver Framework Loader 1.11.9200.16384 (win8_rtm.120725-1247) Microsoft Corporation C:\Windows\system32\drivers\WDFLDR.SYS
ACPI.sys fffff880`00e5f000 fffff880`00eb6000 0x00057000 0x5a7f2a31 10/02/2018 18:21:53 Microsoft® Windows® Operating System ACPI Driver for NT 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\ACPI.sys
WMILIB.SYS fffff880`00eb6000 fffff880`00ebf000 0x00009000 0x4a5bc117 14/07/2009 00:19:51 Microsoft® Windows® Operating System WMILIB WMI support library Dll 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\WMILIB.SYS
msisadrv.sys fffff880`00ebf000 fffff880`00ec9000 0x0000a000 0x5a7f2a29 10/02/2018 18:21:45 Microsoft® Windows® Operating System ISA Driver 6.1.7601.24056 (win7sp1_ldr.180210-0600) Microsoft Corporation C:\Windows\system32\drivers\msisadrv.sys
pci.sys fffff880`00ec9000 fffff880`00efc000 0x00033000 0x5a7f2a42 10/02/2018 18:22:10 Microsoft® Windows® Operating System NT Plug and Play PCI Enumerator 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\pci.sys
vdrvroot.sys fffff880`00efc000 fffff880`00f09000 0x0000d000 0x5a7f2e25 10/02/2018 18:38:45 Microsoft® Windows® Operating System Virtual Drive Root Enumerator 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\vdrvroot.sys
partmgr.sys fffff880`00f09000 fffff880`00f1e000 0x00015000 0x4f641bc1 17/03/2012 06:06:09 Microsoft® Windows® Operating System Partition Management Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\partmgr.sys
volmgr.sys fffff880`00f1e000 fffff880`00f32000 0x00014000 0x5a7f2a34 10/02/2018 18:21:56 Microsoft® Windows® Operating System Volume Manager Driver 6.1.7601.24056 (win7sp1_ldr.180210-0600) Microsoft Corporation C:\Windows\system32\drivers\volmgr.sys
volmgrx.sys fffff880`00f32000 fffff880`00f8e000 0x0005c000 0x595fa074 07/07/2017 15:53:40 Microsoft® Windows® Operating System Volume Manager Extension Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\volmgrx.sys
pciide.sys fffff880`00f8e000 fffff880`00f95000 0x00007000 0x4a5bc115 14/07/2009 00:19:49 Microsoft® Windows® Operating System Generic PCI IDE Bus Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\pciide.sys
PCIIDEX.SYS fffff880`00f95000 fffff880`00fa5000 0x00010000 0x4a5bc114 14/07/2009 00:19:48 Microsoft® Windows® Operating System PCI IDE Bus Driver Extension 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\PCIIDEX.SYS
mountmgr.sys fffff880`00fa5000 fffff880`00fbf000 0x0001a000 0x590f3498 07/05/2017 15:52:08 Microsoft® Windows® Operating System Mount Point Manager 6.1.7601.18933 (win7sp1_gdr.150715-0600) Microsoft Corporation C:\Windows\system32\drivers\mountmgr.sys
atapi.sys fffff880`00fbf000 fffff880`00fc8000 0x00009000 0x4a5bc113 14/07/2009 00:19:47 Microsoft® Windows® Operating System ATAPI IDE Miniport Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\atapi.sys
ataport.SYS fffff880`00fc8000 fffff880`00ff2000 0x0002a000 0x51fef9b5 05/08/2013 02:02:45 Microsoft® Windows® Operating System ATAPI Driver Extension 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\ataport.SYS
nvstor.sys fffff880`00e00000 fffff880`00e2b000 0x0002b000 0x4ba3e257 19/03/2010 21:45:11 NVIDIA nForce(TM) SATA Driver NVIDIA® nForce(TM) Sata Performance Driver 10.6.0.18 (NT.091202-1659) NVIDIA Corporation C:\Windows\system32\drivers\nvstor.sys
storport.sys fffff880`010da000 fffff880`0113e000 0x00064000 0x52f044c7 04/02/2014 02:39:19 Microsoft® Windows® Operating System Microsoft Storage Port Driver 6.1.7601.22589 (win7sp1_ldr.140203-1432) Microsoft Corporation C:\Windows\system32\drivers\storport.sys
amdxata.sys fffff880`0113e000 fffff880`01149000 0x0000b000 0x4ba3a3ca 19/03/2010 17:18:18 Storage Filter Driver Storage Filter Driver 1.1.2.5 (NT.091202-1659) Advanced Micro Devices C:\Windows\system32\drivers\amdxata.sys
fltmgr.sys fffff880`01149000 fffff880`01193000 0x0004a000 0x5a4991bc 01/01/2018 02:41:16 Microsoft® Windows® Operating System Microsoft Filesystem Filter Manager 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\fltmgr.sys
fileinfo.sys fffff880`01193000 fffff880`011a7000 0x00014000 0x4a5bc481 14/07/2009 00:34:25 Microsoft® Windows® Operating System FileInfo Filter Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\fileinfo.sys
Ntfs.sys fffff880`01233000 fffff880`013da000 0x001a7000 0x5a4991dc 01/01/2018 02:41:48 Microsoft® Windows® Operating System NT File System Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\Ntfs.sys
msrpc.sys fffff880`01000000 fffff880`0105e000 0x0005e000 0x5a7f2a40 10/02/2018 18:22:08 Microsoft® Windows® Operating System Kernel Remote Procedure Call Provider 6.1.7601.24056 (win7sp1_ldr.180210-0600) Microsoft Corporation C:\Windows\system32\drivers\msrpc.sys
ksecdd.sys fffff880`013da000 fffff880`013f5000 0x0001b000 0x5add1985 23/04/2018 00:23:49 Microsoft® Windows® Operating System Kernel Security Support Provider Interface 6.1.7601.24117 (win7sp1_ldr_escrow.180422-1430) Microsoft Corporation C:\Windows\system32\drivers\ksecdd.sys
cng.sys fffff880`0105e000 fffff880`010d3000 0x00075000 0x583077df 19/11/2016 17:03:43 Microsoft® Windows® Operating System Kernel Cryptography, Next Generation 6.1.7601.23600 (win7sp1_ldr.161119-0600) Microsoft Corporation C:\Windows\system32\drivers\cng.sys
pcw.sys fffff880`01200000 fffff880`01211000 0x00011000 0x4a5bc0ff 14/07/2009 00:19:27 Microsoft® Windows® Operating System Performance Counters for Windows Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\pcw.sys
Fs_Rec.sys fffff880`01211000 fffff880`0121b000 0x0000a000 0x4f4eefd2 01/03/2012 04:41:06 Microsoft® Windows® Operating System File System Recognizer Driver 6.1.7601.17787 (win7sp1_gdr.120229-1502) Microsoft Corporation C:\Windows\system32\drivers\Fs_Rec.sys
ndis.sys fffff880`0142c000 fffff880`0151e000 0x000f2000 0x5a4991d1 01/01/2018 02:41:37 Microsoft® Windows® Operating System NDIS 6.20 driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\ndis.sys
NETIO.SYS fffff880`0151e000 fffff880`0157e000 0x00060000 0x5a58dc01 12/01/2018 17:02:09 Microsoft® Windows® Operating System Network I/O Subsystem 6.1.7601.24024 (win7sp1_ldr.180112-0600) Microsoft Corporation C:\Windows\system32\drivers\NETIO.SYS
ksecpkg.sys fffff880`0157e000 fffff880`015a9000 0x0002b000 0x5add1b64 23/04/2018 00:31:48 Microsoft® Windows® Operating System Kernel Security Support Provider Interface Packages 6.1.7601.24117 (win7sp1_ldr_escrow.180422-1430) Microsoft Corporation C:\Windows\system32\drivers\ksecpkg.sys
tcpip.sys fffff880`01602000 fffff880`017fd000 0x001fb000 0x5a58dc42 12/01/2018 17:03:14 Microsoft® Windows® Operating System TCP/IP Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\tcpip.sys
fwpkclnt.sys fffff880`015a9000 fffff880`015f2000 0x00049000 0x5a58dbf5 12/01/2018 17:01:57 Microsoft® Windows® Operating System FWP/IPsec Kernel-Mode API 6.1.7601.24024 (win7sp1_ldr.180112-0600) Microsoft Corporation C:\Windows\system32\drivers\fwpkclnt.sys
vmstorfl.sys fffff880`01400000 fffff880`01410000 0x00010000 0x4ce79b8a 20/11/2010 10:57:30 Microsoft® Windows® Operating System Virtual Storage Filter Driver 6.1.7601.17514 (win7sp1_rtm.101119-1850) Microsoft Corporation C:\Windows\system32\drivers\vmstorfl.sys
volsnap.sys fffff880`011a7000 fffff880`011f3000 0x0004c000 0x5080417e 18/10/2012 18:50:54 Microsoft® Windows® Operating System Volume Shadow Copy Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\volsnap.sys
spldr.sys fffff880`01410000 fffff880`01418000 0x00008000 0x4a0858bb 11/05/2009 17:56:27 Microsoft® Windows® Operating System loader for security processor 6.1.7127.0 (fbl_security_bugfix(sepbld-s).090511-0943) Microsoft Corporation C:\Windows\system32\drivers\spldr.sys
rdyboost.sys fffff880`0183a000 fffff880`01874000 0x0003a000 0x5a499288 01/01/2018 02:44:40 Microsoft® Windows® Operating System ReadyBoost Driver 6.1.7601.24000 (win7sp1_ldr.171231-1547) Microsoft Corporation C:\Windows\system32\drivers\rdyboost.sys
mup.sys fffff880`01874000 fffff880`01892000 0x0001e000 0x54ac906b 07/01/2015 02:48:27 Microsoft® Windows® Operating System Multiple UNC Provider Driver 6.1.7601.18711 (win7sp1_gdr.150106-1506) Microsoft Corporation C:\Windows\system32\drivers\mup.sys
hwpolicy.sys fffff880`01892000 fffff880`0189b000 0x00009000 0x4ce7927e 20/11/2010 10:18:54 Microsoft® Windows® Operating System Hardware Policy Driver 6.1.7601.17514 (win7sp1_rtm.101119-1850) Microsoft Corporation C:\Windows\system32\drivers\hwpolicy.sys
fvevol.sys fffff880`0189b000 fffff880`018d5000 0x0003a000 0x5100a65c 24/01/2013 04:11:24 Microsoft® Windows® Operating System BitLocker Drive Encryption Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\fvevol.sys
eppdisk.sys fffff880`018d5000 fffff880`018de000 0x00009000 0x5ab90eea 26/03/2018 16:16:58 Emsisoft Protection Platform Emsisoft Protection Platform 2018.03.0.1024 Emsisoft Ltd C:\Windows\system32\drivers\eppdisk.sys
disk.sys fffff880`018de000 fffff880`018f4000 0x00016000 0x4a5bc11d 14/07/2009 00:19:57 Microsoft® Windows® Operating System PnP Disk Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\disk.sys
CLASSPNP.SYS fffff880`018f4000 fffff880`01924000 0x00030000 0x4ce7929b 20/11/2010 10:19:23 Microsoft® Windows® Operating System SCSI Class System Dll 6.1.7601.17514 (win7sp1_rtm.101119-1850) Microsoft Corporation C:\Windows\system32\drivers\CLASSPNP.SYS
ambakdrv.sys fffff880`01924000 fffff880`0192e000 0x0000a000 0x50d967eb 25/12/2012 09:46:35 C:\Windows\system32\ambakdrv.sys
cdrom.sys fffff880`01984000 fffff880`019ae000 0x0002a000 0x4ce79298 20/11/2010 10:19:20 Microsoft® Windows® Operating System SCSI CD-ROM Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\cdrom.sys
epp.sys fffff880`019ae000 fffff880`019d0000 0x00022000 0x5af2e902 09/05/2018 13:26:42
360Box64.sys fffff880`03a37000 fffff880`03a8e000 0x00057000 0x573d8989 19/05/2016 10:38:17 360Box64 2.1.0.1193 360.cn C:\Windows\system32\drivers\360Box64.sys
360FsFlt.sys fffff880`03a8e000 fffff880`03b54000 0x000c6000 0x5b19ff0e 08/06/2018 04:59:10 360 Total Security 360 Total Security 6.9.1.1751 360.cn C:\Windows\system32\drivers\360FsFlt.sys
Null.SYS fffff880`03b54000 fffff880`03b5d000 0x00009000 0x4a5bc109 14/07/2009 00:19:37 Microsoft® Windows® Operating System NULL Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\Null.SYS
Beep.SYS fffff880`03b5d000 fffff880`03b64000 0x00007000 0x4a5bca8d 14/07/2009 01:00:13 Microsoft® Windows® Operating System BEEP Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\Beep.SYS
vga.sys fffff880`03b64000 fffff880`03b72000 0x0000e000 0x4a5bc587 14/07/2009 00:38:47 Microsoft® Windows® Operating System VGA/Super VGA Video Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\vga.sys
VIDEOPRT.SYS fffff880`03b72000 fffff880`03b97000 0x00025000 0x5add1a8f 23/04/2018 00:28:15 Microsoft® Windows® Operating System Video Port Driver 6.1.7601.24117 (win7sp1_ldr_escrow.180422-1430) Microsoft Corporation C:\Windows\system32\drivers\VIDEOPRT.SYS
watchdog.sys fffff880`03b97000 fffff880`03ba7000 0x00010000 0x4a5bc53f 14/07/2009 00:37:35 Microsoft® Windows® Operating System Watchdog Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\watchdog.sys
RDPCDD.sys fffff880`03ba7000 fffff880`03bb0000 0x00009000 0x4a5bce62 14/07/2009 01:16:34 Microsoft® Windows® Operating System RDP Miniport 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\RDPCDD.sys
rdpencdd.sys fffff880`03bb0000 fffff880`03bb9000 0x00009000 0x4a5bce62 14/07/2009 01:16:34 Microsoft® Windows® Operating System RDP Encoder Miniport 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\rdpencdd.sys
rdprefmp.sys fffff880`03bb9000 fffff880`03bc2000 0x00009000 0x4a5bce63 14/07/2009 01:16:35 Microsoft® Windows® Operating System RDP Reflector Driver Miniport 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\rdprefmp.sys
Msfs.SYS fffff880`03bc2000 fffff880`03bcd000 0x0000b000 0x4a5bc113 14/07/2009 00:19:47 Microsoft® Windows® Operating System Mailslot driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\Msfs.SYS
Npfs.SYS fffff880`03bcd000 fffff880`03bde000 0x00011000 0x4a5bc114 14/07/2009 00:19:48 Microsoft® Windows® Operating System NPFS Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\Npfs.SYS
tdx.sys fffff880`03bde000 fffff880`03c00000 0x00022000 0x597ca21d 29/07/2017 15:56:29 Microsoft® Windows® Operating System TDI Translation Driver 6.1.7601.23880 (win7sp1_ldr.170729-0600) Microsoft Corporation C:\Windows\system32\drivers\tdx.sys
TDI.SYS fffff880`03a00000 fffff880`03a0d000 0x0000d000 0x4ce7933e 20/11/2010 10:22:06 Microsoft® Windows® Operating System TDI Wrapper 6.1.7601.17514 (win7sp1_rtm.101119-1850) Microsoft Corporation C:\Windows\system32\drivers\TDI.SYS
afd.sys fffff880`02c6a000 fffff880`02cf3000 0x00089000 0x58e3b35c 04/04/2017 15:53:16 Microsoft® Windows® Operating System Ancillary Function Driver for WinSock 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\afd.sys
netbt.sys fffff880`02cf3000 fffff880`02d38000 0x00045000 0x598d47df 11/08/2017 06:59:59 Microsoft® Windows® Operating System MBT Transport driver 6.1.7601.23889 (win7sp1_ldr.170810-1615) Microsoft Corporation C:\Windows\system32\drivers\netbt.sys
wfplwf.sys fffff880`02d38000 fffff880`02d41000 0x00009000 0x4a5bccb6 14/07/2009 01:09:26 Microsoft® Windows® Operating System WFP NDIS 6.20 Lightweight Filter Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\wfplwf.sys
pacer.sys fffff880`02d41000 fffff880`02d67000 0x00026000 0x5a4994f8 01/01/2018 02:55:04 Microsoft® Windows® Operating System QoS Packet Scheduler 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\pacer.sys
netbios.sys fffff880`02d67000 fffff880`02d77000 0x00010000 0x5a4994f4 01/01/2018 02:55:00 Microsoft® Windows® Operating System NetBIOS interface driver 6.1.7601.24000 (win7sp1_ldr.171231-1547) Microsoft Corporation C:\Windows\system32\drivers\netbios.sys
wanarp.sys fffff880`02d77000 fffff880`02d92000 0x0001b000 0x5a499504 01/01/2018 02:55:16 Microsoft® Windows® Operating System MS Remote Access and Routing ARP Driver 6.1.7601.24000 (win7sp1_ldr.171231-1547) Microsoft Corporation C:\Windows\system32\drivers\wanarp.sys
termdd.sys fffff880`02d92000 fffff880`02da6000 0x00014000 0x5a7f2f9e 10/02/2018 18:45:02 Microsoft® Windows® Operating System Remote Desktop Server Driver 6.1.7601.24056 (win7sp1_ldr.180210-0600) Microsoft Corporation C:\Windows\system32\drivers\termdd.sys
SASKUTIL64.SYS fffff880`02da6000 fffff880`02db0000 0x0000a000 0x4e1cb5d1 12/07/2011 22:00:01
SASDIFSV64.SYS fffff880`02db0000 fffff880`02dba000 0x0000a000 0x4e28b024 22/07/2011 00:03:00
rdbss.sys fffff880`02c00000 fffff880`02c53000 0x00053000 0x59deb54c 12/10/2017 01:20:28 Microsoft® Windows® Operating System Redirected Drive Buffering SubSystem Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\rdbss.sys
nsiproxy.sys fffff880`02c53000 fffff880`02c5f000 0x0000c000 0x598d479f 11/08/2017 06:58:55 Microsoft® Windows® Operating System NSI Proxy 6.1.7601.23889 (win7sp1_ldr.170810-1615) Microsoft Corporation C:\Windows\system32\drivers\nsiproxy.sys
mssmbios.sys fffff880`02c5f000 fffff880`02c6a000 0x0000b000 0x5a7f2b12 10/02/2018 18:25:38 Microsoft® Windows® Operating System System Management BIOS Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\mssmbios.sys
HWiNFO64A.SYS fffff880`02dba000 fffff880`02dc4000 0x0000a000 0x551a6e24 31/03/2015 10:51:32
discache.sys fffff880`02dc4000 fffff880`02dd3000 0x0000f000 0x4a5bc52e 14/07/2009 00:37:18 Microsoft® Windows® Operating System System Indexer/Cache Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\discache.sys
csc.sys fffff880`03ef9000 fffff880`03f7e000 0x00085000 0x50804270 18/10/2012 18:54:56 Microsoft® Windows® Operating System Windows Client Side Caching Driver 6.1.7601.22137 (win7sp1_ldr.121018-0535) Microsoft Corporation C:\Windows\system32\drivers\csc.sys
dfsc.sys fffff880`03f7e000 fffff880`03f9d000 0x0001f000 0x5a4991e3 01/01/2018 02:41:55 Microsoft® Windows® Operating System DFS Namespace Client Driver 6.1.7601.24000 (win7sp1_ldr.171231-1547) Microsoft Corporation C:\Windows\system32\drivers\dfsc.sys
blbdrive.sys fffff880`03f9d000 fffff880`03fae000 0x00011000 0x4a5bc4df 14/07/2009 00:35:59 Microsoft® Windows® Operating System BLB Drive Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\blbdrive.sys
BAPIDRV64.sys fffff880`03fae000 fffff880`03fe3000 0x00035000 0x5adff8e5 25/04/2018 04:41:25 BAPIDRV 2.0.0.1221 360.cn C:\Windows\system32\drivers\BAPIDRV64.sys
tunnel.sys fffff880`03e00000 fffff880`03e26000 0x00026000 0x4ce7a846 20/11/2010 11:51:50 Microsoft® Windows® Operating System Microsoft Tunnel Interface Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\tunnel.sys
amdk8.sys fffff880`03e26000 fffff880`03e3d000 0x00017000 0x4a5bc0fd 14/07/2009 00:19:25 Microsoft® Windows® Operating System Processor Device Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\amdk8.sys
usbohci.sys fffff880`03e3d000 fffff880`03e48000 0x0000b000 0x59e6b72f 18/10/2017 03:06:39 Microsoft® Windows® Operating System OHCI USB Miniport Driver 6.1.7601.23933 (win7sp1_ldr.171017-1700) Microsoft Corporation C:\Windows\system32\drivers\usbohci.sys
USBPORT.SYS fffff880`03e48000 fffff880`03e9f000 0x00057000 0x59e6b730 18/10/2017 03:06:40 Microsoft® Windows® Operating System USB 1.1 & 2.0 Port Driver 6.1.7601.23933 (win7sp1_ldr.171017-1700) Microsoft Corporation C:\Windows\system32\drivers\USBPORT.SYS
usbehci.sys fffff880`03e9f000 fffff880`03eb1000 0x00012000 0x59e6b730 18/10/2017 03:06:40 Microsoft® Windows® Operating System EHCI eUSB Miniport Driver 6.1.7601.23933 (win7sp1_ldr.171017-1700) Microsoft Corporation C:\Windows\system32\drivers\usbehci.sys
HDAudBus.sys fffff880`03eb1000 fffff880`03ed5000 0x00024000 0x4ce7a65e 20/11/2010 11:43:42 Microsoft® Windows® Operating System High Definition Audio Bus Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\HDAudBus.sys
nvmf6264.sys fffff880`04029000 fffff880`0407ca80 0x00053a80 0x4b9058a7 05/03/2010 02:04:39 NVIDIA Networking Driver NVIDIA MCP Networking Function Driver. 7.03.01.07330 NVIDIA Corporation C:\Windows\system32\drivers\nvmf6264.sys
CompositeBus.sys fffff880`0407d000 fffff880`0408d000 0x00010000 0x4ce7a3ed 20/11/2010 11:33:17 Microsoft® Windows® Operating System Multi-Transport Composite Bus Enumerator 6.1.7601.17514 (win7sp1_rtm.101119-1850) Microsoft Corporation C:\Windows\system32\drivers\CompositeBus.sys
AgileVpn.sys fffff880`0408d000 fffff880`040a3000 0x00016000 0x4a5bccf0 14/07/2009 01:10:24 Microsoft® Windows® Operating System RAS Agile Vpn Miniport Call Manager 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\AgileVpn.sys
rasl2tp.sys fffff880`040a3000 fffff880`040c7000 0x00024000 0x4ce7a872 20/11/2010 11:52:34 Microsoft® Windows® Operating System RAS L2TP mini-port/call-manager driver 6.1.7601.17514 (win7sp1_rtm.101119-1850) Microsoft Corporation C:\Windows\system32\drivers\rasl2tp.sys
ndistapi.sys fffff880`040c7000 fffff880`040d3000 0x0000c000 0x5a4994fb 01/01/2018 02:55:07 Microsoft® Windows® Operating System NDIS 3.0 connection wrapper driver 6.1.7601.24000 (win7sp1_ldr.171231-1547) Microsoft Corporation C:\Windows\system32\drivers\ndistapi.sys
ndiswan.sys fffff880`040d3000 fffff880`04102000 0x0002f000 0x4ce7a870 20/11/2010 11:52:32 Microsoft® Windows® Operating System MS PPP Framing Driver (Strong Encryption) 6.1.7601.17514 (win7sp1_rtm.101119-1850) Microsoft Corporation C:\Windows\system32\drivers\ndiswan.sys
raspppoe.sys fffff880`04102000 fffff880`0411d000 0x0001b000 0x4a5bcce9 14/07/2009 01:10:17 Microsoft® Windows® Operating System RAS PPPoE mini-port/call-manager driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\raspppoe.sys
raspptp.sys fffff880`0411d000 fffff880`0413e000 0x00021000 0x4ce7a86f 20/11/2010 11:52:31 Microsoft® Windows® Operating System Peer-to-Peer Tunneling Protocol 6.1.7601.17514 (win7sp1_rtm.101119-1850) Microsoft Corporation C:\Windows\system32\drivers\raspptp.sys
rassstp.sys fffff880`0413e000 fffff880`04158000 0x0001a000 0x4a5bccf1 14/07/2009 01:10:25 Microsoft® Windows® Operating System RAS SSTP Miniport Call Manager 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\rassstp.sys
rdpbus.sys fffff880`04158000 fffff880`04163000 0x0000b000 0x4a5bceaa 14/07/2009 01:17:46 Microsoft® Windows® Operating System Microsoft RDP Bus Device driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\rdpbus.sys
kbdclass.sys fffff880`04163000 fffff880`04172000 0x0000f000 0x4a5bc116 14/07/2009 00:19:50 Microsoft® Windows® Operating System Keyboard Class Driver 6.1.7601.17514 (win7sp1_rtm.101119-1850) Microsoft Corporation C:\Windows\system32\drivers\kbdclass.sys
mouclass.sys fffff880`04172000 fffff880`04181000 0x0000f000 0x4a5bc116 14/07/2009 00:19:50 Microsoft® Windows® Operating System Mouse Class Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\mouclass.sys
swenum.sys fffff880`04181000 fffff880`04182480 0x00001480 0x5a7f2e02 10/02/2018 18:38:10 Microsoft® Windows® Operating System Plug and Play Software Device Enumerator 6.1.7601.24056 (win7sp1_ldr.180210-0600) Microsoft Corporation C:\Windows\system32\drivers\swenum.sys
ks.sys fffff880`04183000 fffff880`041c6000 0x00043000 0x4ce7a3f3 20/11/2010 11:33:23 Microsoft® Windows® Operating System Kernel CSA Library 6.1.7601.17514 (win7sp1_rtm.101119-1850) Microsoft Corporation C:\Windows\system32\drivers\ks.sys
umbus.sys fffff880`041c6000 fffff880`041d8000 0x00012000 0x4ce7a695 20/11/2010 11:44:37 Microsoft® Windows® Operating System User-Mode Bus Enumerator 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\umbus.sys
usbhub.sys fffff880`04283000 fffff880`042dd000 0x0005a000 0x59e6b740 18/10/2017 03:06:56 Microsoft® Windows® Operating System Default Hub Driver for USB 6.1.7601.23933 (win7sp1_ldr.171017-1700) Microsoft Corporation C:\Windows\system32\drivers\usbhub.sys
NDProxy.SYS fffff880`042dd000 fffff880`042f2000 0x00015000 0x5a4994fd 01/01/2018 02:55:09 Microsoft® Windows® Operating System NDIS Proxy 6.1.7601.24000 (win7sp1_ldr.171231-1547) Microsoft Corporation C:\Windows\system32\drivers\NDProxy.SYS
HdAudio.sys fffff880`042f2000 fffff880`0434e000 0x0005c000 0x4ce7a687 20/11/2010 11:44:23 Microsoft® Windows® Operating System High Definition Audio Function Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\HdAudio.sys
portcls.sys fffff880`0434e000 fffff880`0438b000 0x0003d000 0x56671d76 08/12/2015 19:12:06 Microsoft® Windows® Operating System Port Class (Class Driver for Port/Miniport Devices) 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\portcls.sys
drmk.sys fffff880`0438b000 fffff880`043ad000 0x00022000 0x5667276c 08/12/2015 19:54:36 Microsoft® Windows® Operating System Microsoft Trusted Audio Drivers 6.1.7601.19091 (win7sp1_gdr.151208-0600) Microsoft Corporation C:\Windows\system32\drivers\drmk.sys
ksthunk.sys fffff880`043ad000 fffff880`043b2200 0x00005200 0x4a5bca93 14/07/2009 01:00:19 Microsoft® Windows® Operating System Kernel Streaming WOW Thunk Service 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\ksthunk.sys
crashdmp.sys fffff880`043b3000 fffff880`043c1000 0x0000e000 0x4a5bcabd 14/07/2009 01:01:01 Microsoft® Windows® Operating System Crash Dump Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\crashdmp.sys
dump_diskdump.sys fffff880`043c1000 fffff880`043cb000 0x0000a000 0x52f04419 04/02/2014 02:36:25
dump_nvstor.sys fffff880`043cb000 fffff880`043f6000 0x0002b000 0x4ba3e257 19/03/2010 21:45:11
dump_dumpfve.sys fffff880`04200000 fffff880`04213000 0x00013000 0x4a5bc18f 14/07/2009 00:21:51
USBSTOR.SYS fffff880`04213000 fffff880`0422e000 0x0001b000 0x56b244c6 03/02/2016 19:19:50 Microsoft® Windows® Operating System USB Mass Storage Class Driver 6.1.7601.23344 (win7sp1_ldr.160203-0600) Microsoft Corporation C:\Windows\system32\drivers\USBSTOR.SYS
USBD.SYS fffff880`0422e000 fffff880`0422fe80 0x00001e80 0x59e6b72b 18/10/2017 03:06:35 Microsoft® Windows® Operating System Universal Serial Bus Driver 6.1.7601.23933 (win7sp1_ldr.171017-1700) Microsoft Corporation C:\Windows\system32\drivers\USBD.SYS
hidusb.sys fffff880`04230000 fffff880`0423e000 0x0000e000 0x5a58df41 12/01/2018 17:16:01 Microsoft® Windows® Operating System USB Miniport Driver for Input Devices 6.1.7601.24024 (win7sp1_ldr.180112-0600) Microsoft Corporation C:\Windows\system32\drivers\hidusb.sys
HIDCLASS.SYS fffff880`0423e000 fffff880`04257000 0x00019000 0x5a58df40 12/01/2018 17:16:00 Microsoft® Windows® Operating System Hid Class Library 6.1.7601.24024 (win7sp1_ldr.180112-0600) Microsoft Corporation C:\Windows\system32\drivers\HIDCLASS.SYS
HIDPARSE.SYS fffff880`04257000 fffff880`0425f080 0x00008080 0x5a58df3f 12/01/2018 17:15:59 Microsoft® Windows® Operating System Hid Parsing Library 6.1.7601.24024 (win7sp1_ldr.180112-0600) Microsoft Corporation C:\Windows\system32\drivers\HIDPARSE.SYS
mouhid.sys fffff880`04260000 fffff880`0426d000 0x0000d000 0x4a5bca94 14/07/2009 01:00:20 Microsoft® Windows® Operating System HID Mouse Filter Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\mouhid.sys
win32k.sys fffff960`000b0000 fffff960`003d8000 0x00328000 0x5accde0b 10/04/2018 16:53:47 Microsoft® Windows® Operating System Multi-User Win32 Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\win32k.sys
Dxapi.sys fffff880`0426d000 fffff880`04279000 0x0000c000 0x4a5bc574 14/07/2009 00:38:28 Microsoft® Windows® Operating System DirectX API Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\Dxapi.sys
kbdhid.sys fffff880`041d8000 fffff880`041e6000 0x0000e000 0x4ce7a3f5 20/11/2010 11:33:25 Microsoft® Windows® Operating System HID Keyboard Filter Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\kbdhid.sys
dxg.sys fffff960`00520000 fffff960`0053e000 0x0001e000 0x4a5bc574 14/07/2009 00:38:28 Microsoft® Windows® Operating System DirectX Graphics Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\dxg.sys
TSDDD.dll fffff960`00700000 fffff960`0070a000 0x0000a000 0x4a5bce62 14/07/2009 01:16:34 Microsoft® Windows® Operating System Framebuffer Display Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\TSDDD.dll
framebuf.dll fffff960`00880000 fffff960`00889000 0x00009000 0x00000000 Microsoft® Windows® Operating System Framebuffer Display Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\framebuf.dll
luafv.sys fffff880`04000000 fffff880`04023000 0x00023000 0x59deb539 12/10/2017 01:20:09 Microsoft® Windows® Operating System LUA File Virtualization Filter Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\luafv.sys
MBAMChameleon.sys fffff880`019d0000 fffff880`01a00000 0x00030000 0x58a5da64 16/02/2017 17:59:16 Malwarebytes Chameleon Malwarebytes Chameleon 3.0.0.155 Malwarebytes C:\Windows\system32\drivers\MBAMChameleon.sys
lltdio.sys fffff880`041e6000 fffff880`041fb000 0x00015000 0x4a5bcc92 14/07/2009 01:08:50 Microsoft® Windows® Operating System Link-Layer Topology Mapper I/O Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\lltdio.sys
nwifi.sys fffff880`0192e000 fffff880`01982000 0x00054000 0x59b94930 13/09/2017 16:05:20 Microsoft® Windows® Operating System NativeWiFi Miniport Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\nwifi.sys
ndisuio.sys fffff880`03ed5000 fffff880`03ee8000 0x00013000 0x50804feb 18/10/2012 19:52:27 Microsoft® Windows® Operating System NDIS User mode I/O driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\ndisuio.sys
rspndr.sys fffff880`03fe3000 fffff880`03ffb000 0x00018000 0x4a5bcc92 14/07/2009 01:08:50 Microsoft® Windows® Operating System Link-Layer Topology Responder Driver for NDIS 6 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\rspndr.sys
HTTP.sys fffff880`04a3d000 fffff880`04b05000 0x000c8000 0x5a4991d1 01/01/2018 02:41:37 Microsoft® Windows® Operating System HTTP Protocol Stack 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\HTTP.sys
bowser.sys fffff880`04b05000 fffff880`04b22000 0x0001d000 0x57f51433 05/10/2016 15:54:43 Microsoft® Windows® Operating System NT Lan Manager Datagram Receiver Driver 6.1.7601.23567 (win7sp1_ldr.161005-0600) Microsoft Corporation C:\Windows\system32\drivers\bowser.sys
mpsdrv.sys fffff880`04b22000 fffff880`04b3a000 0x00018000 0x5a4994e2 01/01/2018 02:54:42 Microsoft® Windows® Operating System Microsoft Protection Service Driver 6.1.7601.24000 (win7sp1_ldr.171231-1547) Microsoft Corporation C:\Windows\system32\drivers\mpsdrv.sys
mrxsmb.sys fffff880`04b3a000 fffff880`04b67000 0x0002d000 0x5add19d5 23/04/2018 00:25:09 Microsoft® Windows® Operating System Windows NT SMB Minirdr 6.1.7601.24117 (win7sp1_ldr_escrow.180422-1430) Microsoft Corporation C:\Windows\system32\drivers\mrxsmb.sys
mrxsmb10.sys fffff880`04b67000 fffff880`04bb5000 0x0004e000 0x5add19b2 23/04/2018 00:24:34 Microsoft® Windows® Operating System Longhorn SMB Downlevel SubRdr 6.1.7601.24117 (win7sp1_ldr_escrow.180422-1430) Microsoft Corporation C:\Windows\system32\drivers\mrxsmb10.sys
mrxsmb20.sys fffff880`04bb5000 fffff880`04bd9000 0x00024000 0x5add19b1 23/04/2018 00:24:33 Microsoft® Windows® Operating System Longhorn SMB 2.0 Redirector 6.1.7601.24117 (win7sp1_ldr_escrow.180422-1430) Microsoft Corporation C:\Windows\system32\drivers\mrxsmb20.sys
ammntdrv.sys fffff880`04bd9000 fffff880`04c00000 0x00027000 0x50d967ed 25/12/2012 09:46:37 C:\Windows\system32\ammntdrv.sys
amwrtdrv.sys fffff880`04a00000 fffff880`04a08000 0x00008000 0x50d967ee 25/12/2012 09:46:38 C:\Windows\system32\amwrtdrv.sys
peauth.sys fffff880`056f2000 fffff880`0579c000 0x000aa000 0x57603aaa 14/06/2016 18:11:06 Microsoft® Windows® Operating System Protected Environment Authentication and Authorization Export Driver 6.1.7601.23471 (win7sp1_ldr.160614-0600) Microsoft Corporation C:\Windows\system32\drivers\peauth.sys
srvnet.sys fffff880`0579c000 fffff880`057cd000 0x00031000 0x5accdc84 10/04/2018 16:47:16 Microsoft® Windows® Operating System Server Network driver 6.1.7601.24114 (win7sp1_ldr.180410-0600) Microsoft Corporation C:\Windows\system32\drivers\srvnet.sys
tcpipreg.sys fffff880`057cd000 fffff880`057df000 0x00012000 0x506c62be 03/10/2012 17:07:26 Microsoft® Windows® Operating System TCP/IP Registry Compatibility Driver 6.1.7601.17964 (win7sp1_gdr.121003-0333) Microsoft Corporation C:\Windows\system32\drivers\tcpipreg.sys
srv2.sys fffff880`05600000 fffff880`05668000 0x00068000 0x5accdc94 10/04/2018 16:47:32 Microsoft® Windows® Operating System Smb 2.0 Server driver 6.1.7601.24114 (win7sp1_ldr.180410-0600) Microsoft Corporation C:\Windows\system32\drivers\srv2.sys
srv.sys fffff880`05cb8000 fffff880`05d4f000 0x00097000 0x5accdcae 10/04/2018 16:47:58 Microsoft® Windows® Operating System Server driver 6.1.7601.24114 (win7sp1_ldr.180410-0600) Microsoft Corporation C:\Windows\system32\drivers\srv.sys
360AntiHacker64.sys fffff880`05d4f000 fffff880`05d82000 0x00033000 0x59dc7e0d 10/10/2017 09:00:13 360安全卫士 360安全卫士 网络防黑模块 1.0.0.1143 360.cn C:\Windows\system32\drivers\360AntiHacker64.sys
WudfPf.sys fffff880`05db8000 fffff880`05dd1000 0x00019000 0x5010aae5 26/07/2012 03:26:45 Microsoft® Windows® Operating System Windows Driver Foundation - User-mode Driver Framework Platform Driver 6.2.9200.16384 (win8_rtm.120725-1247) Microsoft Corporation C:\Windows\system32\drivers\WudfPf.sys
WUDFRd.sys fffff880`05c00000 fffff880`05c36000 0x00036000 0x5010aabe 26/07/2012 03:26:06 Microsoft® Windows® Operating System Windows Driver Foundation - User-mode Driver Framework Reflector 6.2.9200.16384 (win8_rtm.120725-1247) Microsoft Corporation C:\Windows\system32\drivers\WUDFRd.sys
-
It's a bit difficult to read with it all merged in together, but I'll ask someone to look at it for you.
-
wow...thanks very much to u both. i will look now to see if theres a better format
theres an htlm report but it wont paste
trying again:
070618-18517-01.dmp 06/07/2018 07:33:07 MEMORY_MANAGEMENT 0x0000001a 00000000`00008884 fffffa80`0110dab0 fffffa80`0031f6e0 00000000`00000500 ntoskrnl.exe ntoskrnl.exe+a44a0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.24117 (win7sp1_ldr_escrow.180422-1430) x64 ntoskrnl.exe+a44a0 C:\Windows\Minidump\070618-18517-01.dmp 2 15 7601 270,160 06/07/2018 07:34:40
-
cant tell if this is any better till i post it:
no better its deleted now
-
A quick scan through the wall of text and I'm thinking some kind of interference between Emsisoft, Malwarebytes Chameleon and/or 360.cn drivers and the kernel, they all run close to the Windows kernel and any glitch there could easily cause a BSOD.
Bad RAM can't be ruled out either. The chances of the kernel itself being at fault are miniscule.
Carrona's site (http://carrona.org/bsodindx.html#0x0000001A) says:
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
Your BSOD subtype gives no further clues: unknown.
-
A quick scan through the wall of text and I'm thinking some kind of interference between Emsisoft, Malwarebytes Chameleon and/or 360.cn drivers and the kernel, they all run close to the Windows kernel and any glitch there could easily cause a BSOD.
Bad RAM can't be ruled out either. The chances of the kernel itself being at fault are miniscule.
Carrona's site (http://carrona.org/bsodindx.html#0x0000001A) says:
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
Your BSOD subtype gives no further clues: unknown.
thanx very much satrow, will keep an eye on it and if i happens again will remove the most recent program , 360 security center
-
Your BSOD subtype gives no further clues: unknown.
thanx very much satrow, will keep an eye on it and if i happens again will remove the most recent program , 360 security center
A quick scan through the wall of text and I'm thinking some kind of interference between Emsisoft, Malwarebytes Chameleon and/or 360.cn drivers and the kernel, they all run close to the Windows kernel and any glitch there could easily cause a BSOD.
Bad RAM can't be ruled out either. The chances of the kernel itself being at fault are miniscule.
Carrona's site (http://carrona.org/bsodindx.html#0x0000001A) says:
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
Your BSOD subtype gives no further clues: unknown.
thanx very much satrow, will keep an eye on it and if i happens again will remove the most recent program , 360 security center
-
A quick scan through the wall of text and I'm thinking some kind of interference between Emsisoft, Malwarebytes Chameleon and/or 360.cn drivers and the kernel, they all run close to the Windows kernel and any glitch there could easily cause a BSOD.
Bad RAM can't be ruled out either. The chances of the kernel itself being at fault are miniscule.
Carrona's site (http://carrona.org/bsodindx.html#0x0000001A) says:
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
Your BSOD subtype gives no further clues: unknown.
thanx very much satrow, will keep an eye on it and if i happens again will remove the most recent program , 360 security center
-
Going back to what you were saying about the RAM modules - are you using a desktop or laptop ?
When you remove the modules from a laptop you should always note where the slots are but are clearly visible and will be the same for each module.
To check that each is okay, remove each one then go Start - type memory and click on Memory Diagnostic and see what that reports.
If one is bad then that should be apparent from the start when you boot up with only that module installed.
Does Speccy recognise both modules ?
For the bad memory module problem, have you replaced that module or just cleaned up the pins ?
-
ah ha,...didnt think of cleaning pins. will try
it is a desktop.
can u clarify this pls: "When you remove the modules from a laptop you should always note where the slots are but are clearly visible and will be the same for each module." do u mean put each modual backing the same slot?
memtest 86 said memory passed test [one pass] . ive always wanted to know how to start windows memory test...thanx.
speccy sees all 3 strips as one total . just calls it 3 gb. i need a replacement strip of ddr2, each strip is 1gb
-
I advised running memory diagnostic on just one module at a time because the diagnostic whether it's MemTest86+ or Windows own, if one or more modules are okay, that can mask a bad one.
It's advised to run MemTest86+ over 8 passes on each stick but because this can take some time, to run it overnight.
On my Toshiba laptops, the slots are on the right of the sticks but when you replace/refit them you can see where they go.
To clean the pins, use either a spirit or rub gently with a clean pencil eraser and brush away any debris.
It doesn't matter which slot you put the modules back in to what they were as long as they are the correct ones - a laptop usually just has two.
When you expand RAM in Speccy it should expand further to the slots.
How do you know that one of the modules is bad ?
-
THATS very interesting about modules that can mask a bad one, if any more trouble i'll do that, or maybe i will anyway. but to more worrying thing is that i dont know weather to believe hard disk sentinel or seatools for windows [after all they made the damn thing] about my hhd, as u say results will change
all seems ok right now though
-
I once did a chkdsk /f on one of my laptops which reported a number of bad sectors, but after restoring with a system image for which I can't remember now, when I ran another chkdsk /f, that came back clean.
As hardware as always trumped software, I was at loss as to how that happened.
I took the word of HDS over the other methods I'd used because the number of bad sectors were spiralling which each HDS test.
That HDD was a 640GB one with quite a lot of free space on it, but because I wasn't experiencing any symptoms of a failing HDD, I didn't know where HDS was finding these bad sectors.
Anyway, I decided to err on the side of caution and replace it.
You can pre-empt a failure by ensuring you have a system image and a system repair disk to boot up with should you need to image a replacement HDD.
You haven't said how you knew you had a bad RAM module.
-
oh sorry...the ram: i had errors or all kinds and a couple relating to ram, as last resort i pulled a strip and that was it. credit came from Kingston yesterday
i need a replacement ddr2 strip but i see that 2 ddr2's can have the board notch in different places. do u know which number relates to the notch in the Ram's board?
friend of mine said yesterday in email which i thought may interest you: "yes results can vary and it can / could be simple things like the temperature of the drive. I know I did have one that would only work well when it was not just warm but hot. For the first 20 / 30 minutes nothing. Bare in mind that your house and hence the ambient temperature of the air around your PC is now 30'C+ when usually it is sub 20'C. So your PC is MUCH hotter than usual."
he designs Bios'S and things so hes a bit out of my league :), he goes on to talk about spinright as being the one he goes to when mixes messages are generated when testing discs....just remembered ive got a copy somewhere
-
Go for the same make and part number that Speccy gives for the other modules.
I've just noticed an error in one of my replies in that the notch is on the left and not the right.
-
just did a search for "notch" and cant find mention of it.
the same make is an odd one, never seen it before. will try
-
All DDR2 memory sticks have the notch in the exact same position, it's part of the standards laid out before they went into production. Same goes for the other DDR* series. It's impossible to fit one into a slot built for another without causing breakage to RAM, slot, or both. Even if you made use of a file to remove the 'pip' inside the slot, I'm pretty sure the contacts wouldn't line up and the PC would fail a BIOS check, I very much doubt it would get as far as attempting to boot to Windows..
-
All DDR2 memory sticks have the notch in the exact same position, it's part of the standards laid out before they went into production. Same goes for the other DDR* series. It's impossible to fit one into a slot built for another without causing breakage to RAM, slot, or both. Even if you made use of a file to remove the 'pip' inside the slot, I'm pretty sure the contacts wouldn't line up and the PC would fail a BIOS check, I very much doubt it would get as far as attempting to boot to Windows..
thanks. i must be making mistake, duhh
-
so would u confirm pls that if i order DDR2 [ignoring the other numbers] it will at physically fit. i know there is the speed/make/size consideration as well but for my very old machines a mix and match approach works. on a good pc i'd choose carefully
thanx
-
DDR2 sticks will fit DDR2 slots. Ensure all sticks are as close as possible in terms of base DDR2 standards and frequencies and that they're all either single- or dual-sided.
Best to check the specs on the 'board maker's QVL list for RAM tested in 4's (Qualified Vendor List, which will contain many more pairs of RAM than quads, the lists are never fully comprehensive, most aren't updated once the 'board goes on sale) for sticks that most resemble your 'good' ones.
Best compatibility/results will always be on matched pairs/quads that most resemble those in the QVL at, or closest to, the max. memory capacity of the 'board.
Checking RAM for that 'board on the Crucial comparator (http://www.crucial.com/usa/en/memory-info?cm_re=us-top-nav-_-us-flyout-memory-_-us-memory) is often quite educational.
-
very informative, thanx