Tweaking.com Support Forums
Main Forum => Tweaking.com Support & Help => Topic started by: Stookza on October 16, 2016, 08:00:42 pm
-
Hello
Im trying to do a repair to my operating system, Its Windows XP x64 but it doesnt work. no matter what i tried even in SAFE MODE, I get the error : "The current repair has failed to start for over 30 sec" and it repeats over and over at least 4 times, So i checked the "Event Viewer" for an error due to another thread's advise [2-3 threads before mine] of someone that had the same problem. I tried to go to the Microsoft link appeared in that error but it doesnt work anymore so no avail and no solution. :-(
I attached the screenshot of the error, Will really appreciate for some help from someone. Thanks.
-
What errors are recorded in Event Viewer with the time stamps for when the program failed to start and does the program start in normal mode ?
What problems do you have that you need to run the program ?
-
Thanks a lot for your reply.
The errors that were recorded and appear in Event Viewer at the exact time when i tried to do the repair, are exactly what i copied to the screenshot above [Microsoft error ID:7000] and i couldnt find something else.
The program doesn't fail to start at all , Not in normal mode or in safe mode, it just unable do to the full repair as u can c at the screenshot and it fails. [All the other stuff i tried with that excellent software has succeed]
Basically i have a minor problem of a very tiny audio stuttering/popping only when i play with the volume bar and grab it to 0 of Winamp/Mediaplayer. 2nd problem is that the bass is a bit strong sometimes but i reduced it some by playing with the settings of Creative "console launcher equalizer". [Sound blaster Creative X-Fi Titanium and i tried all the versions of drivers [include PAX] , with a clean installation and after erasing the old ones with driver sweeper and driver cleaner pro]
Also i have a problem that i can use only 16 gigs of memory [instead of 24] only in 2 channels instead of 3 because slots b1 and b2[of the 2nd channel] simply doesnt recognize the memories[but it did in the past]. So i insert inside of those slots a cheap Chinese dummy memory's slots repair sticks in a try to fix them, also i changed memory QPI voltage jumper, or tried different memory voltage in the Bios. [Mb is Asus P6X58DE with 16g of corsair vengeance 1600mhz memory @ 1.5v at the bios, The CPU and the mobo pins are totally fixed and undamaged, CPU is cooled with "Coolabratory" thermal paste since a year ago and temperature is around 35-48 degrees]
Im almost sure that the problem of the audio stuttering is related to the problem of the unrecognized memories in the 2 slots of channel 2 at the mobo.
Except of those problems, i dont have any problems with that pc, never had any BSOD in the last 2 years and it runs fast and smooth [crossed fingers] so actually i tried to use that software more for tweaking and boosting the performance of that pc. like i use a few others, reliable ones.
-
In Event Viewer can you click on the Event ID 7000 then on Copy/Copy Details as text - right click in the reply box and select Paste as it can reference different services.
-
Yes it shows an error related to some netevent.dll.
-
Not all of your pic shows the netevent.dll but open a command prompt and enter these two cmds then retry or uninstall/reinstall the program after the reboot.
regsvr32 /u netevent.dll
regsvr32 /i netevent.dll
If you get any error messages from those cmds then enter chkdsk /f
Type and enter y when prompted then enter shutdown /r /t 00 to effect an immediate reboot and let it do its thing.
If the regsvr32 cmds report as successful then enter the shutdown cmd.
If you need to run the chkdsk /f - you can view its full report in Event Viewer.
Expand Windows Logs - click on Applications - Action/Find then type chkdsk or wininit into the Find box and press enter.
Cancel the Find box and read the report in the scrollable window.
-
I tried to do uninstall/reinstall of the netevent.dll exactly by your instructions, but i get the error appears at the attached screenshot.
So i typed the chkdsk /f and "y" and shutdown /r /t 00 and during the restart it did the checkdisk pretty fast, windows showed up but still i couldnt do the un/installation of netevent.dll, and also couldnt do the repairs with the software yet.
So i tried to search for the chkdsk.log in the Event Viewer following your instruction, and found the last result only from the 15/10/16 but not the last one i did half hour ago at 20/10/16.
Btw at the full event log of the ID:7000 error, i see that the "source" of the netevent.dll error is "Service Control Manager'
-
Run the second cmd for the netevent.dll
If you are only getting a log from the 15th then scroll down from the top of the list until you see a Wininit for the 20th, but run another chkdsk /f after running regsvr32 /i netevent.dll
-
Thanks for the fast reply, I scrolled up [because i set it by the last date upper] and i didnt find a wininit event, but i found a winlogon event [if it helps] that shows the exact result of chkdsk.log that i saw on the screen during the last boot 2 hours ago.
I still cant do the second cmd for the netevent.dll, Means i can do it but it still fails with the same error that "the file cannot be registered".
-
I'm not familiar with XP so that may be XP's equivalent of wininit.
Run the chkdsk /f again and see if you can find a more recent log.
-
If you have a XP CD then you can run the chkdsk from the Recovery Console where its report will remain on the screen - you can use either /f or /r but the /r switch will take longer.
https://kb.wisc.edu/page.php?id=5097
EDIT - I've just checked with Google and the log is shown as Winlogon.
-
I did the chkdsk from desktop and that was the last result few min ago:
-
That's in read-only mode which doesn't actually repair anything but would tell you that it cannot continue and to use the /f switch if it found corruption - so that looks to be okay.
I'm going to elevate this to one of the Admins to see if they have any suggestions, but in the meantime, if you have a XP CD then read my last post to see how to run the chkdsk from the Recovery Console.
-
Many thanks for going to elevate it to one of the admins Boggin, hope it will help somehow. meanwhile i will do the full chkdsk /r from the recovery console in the next few hours, as i did it already many times in the past 15 years ;-)
-
Okay - I've already sent the email but because of the time difference to the US, it may be a few hours before it's picked up.
-
Np i have the time. thx m8
-
What antivirus are you using?
-
In Safe Mode it wouldn't matter as it won't be loaded if a 3rd party one.
-
Shane has told me that it was never tested on XP x64 because of the x64's unpopularity and he's not sure if it can read the codes, so it may be a no go as far as that is concerned.
He doesn't have a XP x64 disk either to check it out.
-
Im using NOD32 as the main AV. and few other installed AV removal tools and sometimes recovery boot cds of many other avs to check if nod32 has missed something.
Thanks a lot for updating me with that important thing Boggin, that explains a lot... and i admit i actually thought about that thing before i opened the thread and that it might be the main reason, because i forgot to mention that i installed that tweaking software in 2 of my other pcs, and at 1 laptop [laptop with windows 8 and pcs with XP/7 32 bit.] and it did finish the repair in all of them! [i unmarked some of the options, those which i was not interested to change in the "repair" settings] and it really improved the performance of my pcs a bit.
I have all the versions of windows o.s in original discs since windows 95 till windows 10. Now the the main reason that im still using WINDOWS XP x64 as my main o.s, is because i get the best 3D performance compare to any other operating system i tested before, since Vista! I can feel the real difference not only by the tests results, but even by playing games and my personal feeling with the higher fps which is much higher and less lag in xp x64, even that it has only Directx 9/10 and not 11 like windows 7 and above.
I tested the 3d performance with a common and reliable software called "Passmark performance test" and also with "3D mark" and i get 35-40% better result with xp x64 compare to any other o.s, at exactly the same pc and same settings in the Nvidia control panel.
I sent Microsoft a mail about that issue few years ago before they created and released windows 10, a representative of them was very nice and told me that they will take care of that thing, and he will elevate it to the admins above him, but nothing was done since then, and there was no any improvement at windows 10, and no reply from them, Microsoft ignored my second mail totally [i guess because that they have no answer and they know very well that they cant change and reverse back such a thing] and of course cause they simply dont even account me as a simple citizen who sends them emails about something that is truth 100%.
Most of the people dont pay attention to that thing [like they didnt feel the difference between 60hz and 75hz supported screen refresh rate] and they are even not aware, but this thing is pretty annoying a gamer who likes to play a lot of pc games, and i do feel the big difference when playing games, and i cant tolerate and compromise on that thing. Basically the 3D performance's core and kernel of all Ms operating systems since Windows vista hasn't changed almost at all and its almost the same since 2007 and its still bad, according to the results i get with the tests, and for sure i can also feel it by my personal feeling in any game i play and thats enough for me. for example: characters run faster, much less lag of mouse movement, vertical sync enabled is much better with no tearing and much more frames per second.
THE MAIN PROBLEM IS THAT XP X64 IS NOT SUPPORTED ANYMORE BY THE NEWEST PC GAMES OUT ON THE MARKET RECENTLY, ALTHOUGH ITS THE BEST PERFORMANCE OPERATING SYSTEM TO PLAY GAMES WITH!
You are even welcome to do so and test it by yourself, to see that im not bs. Simply install at the exact same pc, windows Xp x64, 7 ,8, 10 [64 bit versions] on a separate hard drives, install Nvidia/Ati drivers and set it exactly at the same settings on all the operating systems, and see the result by yourself.
I tested all the Microsoft operating systems, installed each one at a separate different hard drive on the exact same pc with: CORE I7 [email protected], 16GB CORSAIR 1600MHZ, NVIDIA DOUBLE GTX 680, CORSAIR 1200W PSU.
-
I don't game except for the odd game of Klondike :) but I'm using laptops with Intel and AMD so can't check out your suggestions.
I don't think the repair program would have done anything for your sound problem anyway.
If you have a sound card rather than it being built into the motherboard, you could try gently cleaning the contacts with an eraser or cotton buds and Isopropanol.
Are you using external speakers on your XP machine and do you get the same sound problems when you plug them into your other machines ?
-
Yes i knew that program wouldn't fix my sound problem, i didnt rely on it from the start but i wanted to give it a try, more i wanted to use it for tweaking [as its name] and improve the performance of my o.s.
like Shane said in his quotes: "Why fix what isn't broken?" I reply "To make it better."
So i dont call it a "fix" from the start like others do, but for me its more like improving and boosting the performance of a pc, by cleaning the registry to make it work faster.
Im almost sure that the problem of the tiny stuttering audio i have, is related to the problem of my memory's slots of channel 2 , which even with memories inserted inside, it still being unrecognized by the bios.
Im positive about that because i already tried what u said and cleaned the dust from the contacts of my PCI-X Creative X-FI Titanium sound card, and either the internal built in SB,NETWORK,USB contacts, even that i dont use it. i did with air spray, cotton buds and alcohol, just few days ago [like i do once in a while for maintenance]
And i also tested the speakers with my other pc, but didnt get the same sound problem because the speakers are totally ok, but thx for the advice's anyway ;-)
-
Sometimes the repairs need to run as a service. If it cannot load as a service you will see that error.
95% of the time this is your antivirus app blocking it.
If you reboot into safe mode it should work fine.
-
Im sorry to tell you but you are wrong this time jpm, because i tried already 3-4 times in safe mode and even checked in Task Manager that nod32 is not running in the background, and still it didnt work.
Boggin is right in a chance of almost 100%, according to what he said yesterday, Shane never tested the software with XP x64 because of its unpopularity and thats the reason.
I will be very surprised if anyone in the world, will tell us that he succeed to do the main repair of the tweaking.com software with xp x64.
I can upload my XP x64 with a CD key, if Shane or someone of u has time and wanna try and test it, but if he doesnt, then no matter, i will understand.
-
- Do you recall how many CMD.exe windows opened (& closed) before this error message popped up ? before WR failed ?
- Did you try the latest WR version ?
-
Non of any black CMD windows were opened during the repair's try.
Yes I installed the last version of WR [v3.9.15] this morning after i saw your reply, but it crashed at the start with a "kernel32.dll" error , so i uninstalled it and reversed back to v3.9.13 version again.
-
- Ok. That already gives one clue.
- The 1st picture suggests (!!!) that WR messes with the Service info in the registry ("The Tweaking Run As System 003 Service .......... "). That text is NOT supposed to show up there.
-
Yes that's right. So what does it mean except of messing with the registry? or what can i do about that 0003 error? Or like Boggin said "there is nothing to do with it actually, cause WR wasn't designed or tested on Xp x64,"
Thanks
-
- Perhaps it's a bug that also shows up when run on a 32 bit XP system. Is someone willing to test this ?
- Or did you perhaps tweak your system (too much ??).
-
- I see also something else. Stookza ran WR 3 times and made a screenshot. And then the text "The Tweaking ............... 003" showed up. Stookza ran the program for a 4th time and then the same text appeared but now with "........ 004". So, somehow there's a counter involved that was increased from "003" to "004". Does that provide a better clue of what's going on ?
-
- Perhaps it's a bug that also shows up when run on a 32 bit XP system. Is someone willing to test this ?
- Or did you perhaps tweak your system (too much ??).
Thanks a lot for ur replies Willy
- Its not a bug that also shows up on XP 32 bit because i did the repair again with 1 of my old pcs with XP32bit only 15 min ago, and all the correct CMD windows were opened during the repair, and it finished and works perfect as u can c at the attached screenshots.
- I indeed tweaked all of my pc's a bit, especially the "services", because there are many settings on default that slows our system performance and i really dont need them to be enabled on auto/manual , according to "Blackviper" http://www.blackviper.com/ and "Theeldergeek" http://www.theeldergeek.com/ and Gibson research https://www.grc.com/intro.htm instructions. Those services also expose our systems for hacking attacks, or remote by others, or a backdoor for viruses.
like who needs "Remote registry" or "telnet" or "Net Tcp port sharing" or "Netmeeting" to be enabled??
Or for example even "Printspooler" as enabled, if i dont use any printer on those pcs?
Thats why i removed some options that i dont need to be changed, before applying the repair with WR. because i dont want to set the services back to default again, and my network settings are totally ok, and "print spooler" is already disabled.
-
(I still have a few suggestions)
- When sound is "stuttering" then - in general - something is "interfering". But what ? Graphics card ?
- How much free space do you have on your HD ? I know that when free space comes down to under say 10% Windows becomes "less stable" especially when one has a LARGE HD.
- Open "Services" (Services.msc). Do you see anything unusual (e.g. that word "Tweaking" or "Run as").
- If you know how to use a registry editor then you can manually search the registry for that text string (in the "Services section" of the registry)
You can try the following:
- Make a backup copy of the registry (Tweaking's Registry Backup), grab the file "Services_startup_xp.txt" (in one of the subfolders under where Windows Repair is located) and run it as a *.bat file. It will reset the Services to their defaults on your XP system after a re-boot. Perhaps then will WR run without a hiccup. (After all, you did tweak your system).
- This "Services ......... " file(s) allows you to manually modify the start up state of LOTS of (e.g. XP) Services in one run. You can modify the start up states of the Services. See the repair info for repair #27.
-
Hi and thanks again for not giving up of trying to help me :wink:
- I tried all my PCI-EX slots with or without the double GTX 680 but it still didnt solve my tiny stuttering problem, Now the the sound blaster is in slot 3 under the 2 slots X16 of the GTX video cards.
- I have 442 GB free space at the 1TB hard disk, and 308 GB free at the 500 GB hard disk where windows is installed.
- I dont see something suspicious or unusual at the "Services" , I uploaded for you a screenshot of my services menu from a to z, and i will really appreciate if u can help me and see if something looks wrong in there, or that i disabled something that should be enabled.
I did your suggestion of backing up the registry with "Windows Repair", and i have now the "Services_startup_xp" as a ".bat" file, but i afraid to press on it and reset my services back to default again like u said. I configured it for few hours by the 'Theeldergeek" and "blackviper" instructions [2+- years ago when i installed windows], and i afraid that i wont be able to return it to the tweaked one that i have now. so thats why i uploaded you the screenshot of the services menu.
-
- No, that picture doens't show anything extra-ordinary.
- That *.bat file only "touches" the Services that came with XP and not the ones that were installed afterwards by other software.
- You can use the tool called "MSCONFIG". It's a very powerful tool to modify how Windows starts. And the nice thing is, the user can easily reverse those changes. E.g., disable all the non-Microsoft stuff, reboot and see if the sound problem has gone. (This is only one of the options this tool provides). That could give a clue what is interfering with the sound.
- Perhaps now you're able to run WR as well. The article below explains the tool well, IMO.
http://www.online-tech-tips.com/cool-websites/guide-to-msconfig-windows/
-
- Yes i know "MSCONFIG". since 1998 im using it ;-) But nothing there looks suspicious that might interfere with the sound, and i disabled all the non-Microsoft ones, but it still didnt solve my audio stuttering and WR problem, So i re-enabled again some of the necessary services [like creative sound, AV, Intel Matrix Manager].
The problem of the sound is not so serious actually, but still its annoying a bit , its just a lil "tick" or "popping" sound when i move the cursor of the mouse from one part to another in some music or video files, the second problem is a strong and knocking bass sound in some audio files. [that i can feel very well comes out from the sub-woofers]
I think the problem caused only from the memory's slots 3-4 defect [that i dont use], or cause of the "buggy" and problematic drivers of Creative X-fi Titanium which doesn't fit completely to windows XP x64.
-
- Sound driver problem ?
- I am out of suggestions. Alas.
-
Possibly a shared IRQ problem, check that the soundcard has it's own IRQ. The "click" or "pop" can be a symptom of this.
-
Lol I can understand u already, but thanks again for doing your best of trying to help me!
The strange thing is that in the past, this driver problem wasn't exist at all! Im talking about XP x64 all was just fine with the sound!
Something happened in the last 1.5 years, I remember that i installed windows 8 in my other hard disk a year ago+- , and there was no any problem at all!
The driver or the sound problem doesn't exist at all in windows 8 or 7 , The sound works perfect there! I just cant work with those operating systems cause of the 3D/2ND low performance compares to XP X64.
So i actually might be wrong that the sound related to the memory's slots problem, cause it was simply perfect with windows 7-8 in the exact same pc setup.
But maybe with xp x64 it relates it to the memory slots problem. I can feel the sound problem mostly when i open CPUZ, the sound stops/pops for 1-2 seconds and returns.
-
Possibly a shared IRQ problem, check that the soundcard has it's own IRQ. The "click" or "pop" can be a symptom of this.
Yes thanks for ur advice! i thought about that either long time ago, i checked the IRQS and saw that there is some conflict with ICH10R which belongs to the chipset. Anyway i didnt have any IRQ BSOD or something like that at the last 2 years since i installed that windows.
I attached a screenshot of my system's IRQS, Do u think that it might be the cause of problem??? If yes, how can i change and sign another IRQ to cancel the conflict? i tried to change slots and switched the sound card between all the other PCI-X slots with or without the video cards, but there are no many options and i cant remove 1 of my video cards cause i play on SLI, And even if i remove 1 of my GTX cards, still it has the same IRQ conflict with ICH10R or with another hardware :sad:
[BTW u see on the list double XFX GTX 285 AND not the 680 because i moved them to another pc i have to test with windows 8]
-
I'm just going from personal experience. I have Creative Soundblaster card in an XP (32bit) machine that "popped" and "clicked" on occasion.
Drivers updated etc...problem remained, checked and found it was sharing IRQ with another device. swapped the card to another slot, but it was still sharing the same IRQ, tried a third slot, same IRQ sharing. (From memory it was shared with a USB Universal Host controller.)
I then used an option in the BIOS that allowed setting the IRQ from there. Result, my soundcard was given its own IRQ and worked perfectly since.
-
I did exactly what u did long time ago, and had the same results lol. I think that this time u gave me a direction for the main reason of my audio stuttering problem.
question is how can i change IRQ's sign if i dont have any option in the bios?
I know that i have that option in another pc i use with an ASrock board and AMI bios, but not in the ASUS mb, Its called: "Configure Super IO Chipset" and i can choose IRQ's only for the inputs/outputs. [3F8//IRQ4] but not for Sata ICH10R PCI-Exp root port.
-
I checked on my old machine (that I mentioned above) it is an old HP board, phoenix BIOS, probably similar to your ASrock. That machine allows the BIOS to control IRQs and the OS does not change them.
I am sorry, I don't know how (even if you can) select IRQs on your ASUS board via the OS. :sad:
I do know that some Creative cards had jumpers on them to set the IRQ.
It maybe worth heading over to the Creative Sound Blasters forum and outlining your issues, they might be able to help?
http://forums.creative.com/forumdisplay.php?f=6
I noticed this "sticky", which seemed relevant to your setup?
http://forums.creative.com/showthread.php?t=521634
-
Thanks a lot for the links Samson , I passed on all the "sticky" thread pages, page by page 21 pages, no matter what i tried nothing helped, no solution :cry:
I have no jumper on my sound card, I disabled Virtual Technology in the Bios, I tried to search in google how to turn off "link state power management" of the PCI-EX for XP but couldn't find a link. [it fits only for Windows 7-8]
Im out of any solution how to change IRQ, but now im searching to purchase an external PCI-E slot that ill be able to connect with a USB cable, Ill connect the Sound card to it and maybe it will change the IRQ and solve my problem, but still i cant find some external PCI-E slot without a connector to the internal PSU power cable, I need something with an external & independent PSU and power cable that i wont need to connect straight to my pc's PSU.
And some adapter that ill be able to connect to the pc only with a USB cable and not with a PCI-E extender, so that it will really change the IRQ of the sound card.
Something like that but without PSU power connector, and that connects to the pc straight only with USB cable:
https://www.aliexpress.com/item/30cm-Top-Quality-super-speed-PCI-E-Express-Powered-Riser-Card-USB-3-0-extender-Cable/32751216278.html?spm=2114.30010308.3.227.pMgpzb&ws_ab_test=searchweb0_0,searchweb201602_2_10065_10056_10068_10055_10054_10059_10078_10079_10084_10083_10073_10080_10070_10096_10082_10081_10060_423_10061_10052_10062_10050_424_10051,searchweb201603_2&btsid=bb7cdd5b-7830-4ca2-9d8c-ef8ec205ea2d
-
Thanks a lot for the links Samson , I passed on all the "sticky" thread pages, page by page 21 pages, no matter what i tried nothing helped, no solution :cry:
I must admit I did n't read all 21 pages in the thread. But I got the impression that no one had found a solution that worked for all. It seemed to me that the concensus was that there was a compatibility issue between certain Nvidia and Creative cards with SLI, with neither offering a fix.
Good luck with your new line of attack :wink:
-
I doubt it will success but thanks anyway, i appreciate your help :wink:
I will purchase the cheap adapter and check if it will change the IRQ somehow, If it wont i have nothing to lose but 5$.
There are some expansive external PCI-EX with a box, but it doesnt worth for me to buy them on the start, and i cant connect them straight to the USB hub anyway but with an internal PCI-E to a USB card like the cheap one does.
It may step on the same IRQ again, so thats why its better to try the cheaper one.
https://www.aliexpress.com/item/PCIE-1X-To-PCI-e-16x-slots-Extension-Riser-card-1-to-2-PCI-express-adapter/32257530005.html?spm=2114.30010308.3.194.MK5tbO&ws_ab_test=searchweb0_0,searchweb201602_2_10065_10056_10068_10055_10054_10059_10078_10079_10084_10083_10073_10080_10070_10096_10082_10081_10060_423_10061_10052_10062_10050_424_10051,searchweb201603_2&btsid=d457f8dd-aa1b-4685-9506-96f847d1f860
-
Been having a dig around Google and this was one solution for someone to change the IRQ -
Here is what you do to assign IRQs by the BIOS, which is good enough for me.
Go to open boot.ini with notepad and put /PCILOCK after the '/fastdetect' switch
-
- @StookZa: Run the *.bat file in the weblink. Perhaps that will help the audio problem
https://1drv.ms/u/s!AluvxwylJSzyd5kxDNB0US6vEn8
-
Been having a dig around Google and this was one solution for someone to change the IRQ -
Here is what you do to assign IRQs by the BIOS, which is good enough for me.
Go to open boot.ini with notepad and put /PCILOCK after the '/fastdetect' switch
I did it but it didnt change anything with the IRQs list, but i feel a tiny improvement with the pc perfomrance, or its just a feeling, so im not gonna erase it from the boot.ini .
Now im gonna try the "bat" file of Willy and ill update at the next few hours. thx
-
Were you able to do anything with the IRQs in the BIOS after adding that ?
-
No i dont have any new option in the bios. all the same.
The BAT file of Willy didnt fix it either, but maybe it also improved slightly the performance of the pc, and registered some files that were not been registered.
-
- The *.BAT file registered a whole bunch of audio/media related files.
-
Hi
I want to Update that i erased /PCILOCK from boot.ini cause of win32k.sys BSOD i had this noon [7 hours ago]. it was my first BSOD in almost 2 years since i installed windows.
I think and hope it was the real cause for the BSOD and not something else by mistake, but im not sure yet because there was no any memory dump left after the BSOD occurred, even that the setting of my "Write debbuging information" is on "kernel memory dump".
I will have to wait for few days without the "/PCILOCK" and know if it was really the cause.