Author Topic: HELP! HELP! BIG PROBLEMS AFTER REPAIR ! (Read 114211 times)

sallyb · « **Reply #50 on:** June 17, 2015, 12:07:20 pm »

OK! Here is the deal....Microsoft WOULD NOT let me install that update! I tried it from their website directly and by downloading the update to my computer and installing it there. It said the the update "was not applicable to my computer!" OMG
Anyway, so I was fiddling around with my printer problem when I got the damn ole32.dll error. So it crashed my machine, as usual, and I booted up into safe mode with networking and signed on as administrator. Then I "took control" of both the new file that you sent and the old one in the System32 folder. Now when I went to copy paste I did NOT GET THE NO PERMISSION error. However, it now said that it could not do a copy paste because the file was open in another folder- "close that folder to continue" So I copied the file onto the desktop...same message. But WHEN I DID A CUT PASTE IT WORKED!!!! It asked me if I wanted to delete the old file and replace with the new and I said yes, and it did it! I know it worked because I checked the properties and it said it was created and accessed today, not November, 2010 as before! YEAH, YEAH, YEAH!!!!!!! I am so hopeful that this error is fixed!!
So I went through the check disk and it found errors which I hope were corrected. The log is as follows

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 6/17/2015 2:37:03 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Sally-HP
Description:

Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
488192 file records processed.

File verification completed.
2196 large file records processed.

0 bad file records processed.

0 EA records processed.

61 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
646790 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...
488192 file SDs/SIDs processed.

Cleaning up 377 unused index entries from index $SII of file 0x9.
Cleaning up 377 unused index entries from index $SDH of file 0x9.
Cleaning up 377 unused security descriptors.
Security descriptor verification completed.
79300 data files processed.

CHKDSK is verifying Usn Journal...
37471400 USN bytes processed.

Usn Journal verification completed.
Windows has checked the file system and found no problems.

955629567 KB total disk space.
503266968 KB in 373453 files.
264220 KB in 79301 indexes.
0 KB in bad sectors.
626859 KB in use by the system.
65536 KB occupied by the log file.
451471520 KB available on disk.

4096 bytes in each allocation unit.
238907391 total allocation units on disk.
112867880 allocation units available on disk.

Internal Info:
00 73 07 00 96 e8 06 00 02 ab 0c 00 00 00 00 00 .s..............
ee 64 00 00 3d 00 00 00 00 00 00 00 00 00 00 00 .d..=...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-06-17T18:37:03.000000000Z" />
<EventRecordID>855379</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Sally-HP</Computer>
<Security />
</System>
<EventData>
<Data>

Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
488192 file records processed.

File verification completed.
2196 large file records processed.

0 bad file records processed.

0 EA records processed.

61 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
646790 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...
488192 file SDs/SIDs processed.

Cleaning up 377 unused index entries from index $SII of file 0x9.
Cleaning up 377 unused index entries from index $SDH of file 0x9.
Cleaning up 377 unused security descriptors.
Security descriptor verification completed.
79300 data files processed.

CHKDSK is verifying Usn Journal...
37471400 USN bytes processed.

Usn Journal verification completed.
Windows has checked the file system and found no problems.

955629567 KB total disk space.
503266968 KB in 373453 files.
264220 KB in 79301 indexes.
0 KB in bad sectors.
626859 KB in use by the system.
65536 KB occupied by the log file.
451471520 KB available on disk.

4096 bytes in each allocation unit.
238907391 total allocation units on disk.
112867880 allocation units available on disk.

Internal Info:
00 73 07 00 96 e8 06 00 02 ab 0c 00 00 00 00 00 .s..............
ee 64 00 00 3d 00 00 00 00 00 00 00 00 00 00 00 .d..=...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
</EventData>
</Event>

So then I set up my beloved old computer as a shared network printer on another machine that already had it installed through Bonjour, AND IT WORKED!!

So now, even though Bonjour Printing services seems to be toast on my computer, I can still use the printer. AND the ole32.dll is (maybe) fixed!!! At least System32 has a new copy, so if I get the error again I will post here...but the file cannot be corrupt, can it, since it came from a Microsoft Windows Disk.....crossing my fingers...Thank you so much for all your help!!

Julian · « **Reply #51 on:** June 17, 2015, 12:39:28 pm »

Woooowhoooo!

i'm glad to have assisted you in your Computer repair. All you need now is Just go to the first post you Made hit modify and in the Title put solved. If you have any issues later Sally feel free to post on the forums.

sallyb · « **Reply #52 on:** June 17, 2015, 06:23:19 pm »

NOT SO FAST! I just got the damn ole32.dll error AGAIN!!!!! So I had to do the usual force shut down and this time I didn't even go into the safe mode. I AM SO DISGUSTED!!!! Please tell me what to do! Should I take it somewhere, should I wipe everything out and start over? I can not continue to go through this....I will post another thread and hope that Shane will help me, if not I do not know what to do....

Julian · « **Reply #53 on:** June 17, 2015, 10:27:57 pm »

Quote from: sallyb on June 17, 2015, 06:23:19 pm

NOT SO FAST! I just got the damn ole32.dll error AGAIN!!!!! So I had to do the usual force shut down and this time I didn't even go into the safe mode. I AM SO DISGUSTED!!!! Please tell me what to do! Should I take it somewhere, should I wipe everything out and start over? I can not continue to go through this....I will post another thread and hope that Shane will help me, if not I do not know what to do....

no worries still here let's see.

Boggin · « **Reply #54 on:** June 18, 2015, 01:02:14 am »

See if this MS Hotfix does anything for you https://support.microsoft.com/en-us/kb/2541119

Also can you check Event Viewer to see if anything is recorded with a time stamp of the crash.

Disregard Event ID 41 as that will be your power shutdown.

If you are able to, download BlueScreenView to see if the computer has produced a Dump file. http://www.nirsoft.net/utils/blue_screen_view.html

jraju · « **Reply #55 on:** June 18, 2015, 03:35:18 am »

Hi, I simply cannot believe that windows update could crash the printer.
It is because of some problems in the dll that gives the error. the dependency of the services of other dll files may also be the cause.
The printer drivers may pose an issue or the downloaded files contain some bugs for the printer to properly function. These dll files are difficult to find and fix. If regsvr 32 could not solve, then those are the reasons for the printer not to be recognised.
Normally if you download drivers from HP , and that too full version, then so many errors are possible as the system gets injected with unwanted updates and prompts for updates and system monitoring , solution tools are extra tools in the full version. I had done that, and i had to get rid off only by reinstalling the windows. The system restore would not work and it will swallow the restore points.
If you are having windows 7 , then it will automatically download required minimum driverrs for printer alone, and this is enough.
I think that the removal of updates does not stall anything. If you remove, it will be prompted in the next download.
If the fault is not printer, then some possibility of infection would have been the reason. Just download adware cleaner and scan your system and when it finished scan, remove the infections and everything will be alright.

jraju · « **Reply #56 on:** June 18, 2015, 04:14:24 am »

Hi, Please see this link. Eventhough it relates to some othr dll, see the solution and let me know how it goes
http://csi-windows.com/blog/all/73-windows-64-bit/378-fixing-qregsvr32-the-module-failed-to-load-the-specified-module-could-not-be-foundq

Boggin · « **Reply #57 on:** June 18, 2015, 05:40:06 am »

Quote from: jraju on June 18, 2015, 04:14:24 am

Hi, Please see this link. Eventhough it relates to some othr dll, see the solution and let me know how it goes
http://csi-windows.com/blog/all/73-windows-64-bit/378-fixing-qregsvr32-the-module-failed-to-load-the-specified-module-could-not-be-foundq

Reply #39 states that regsvr32 had been applied and reported as successful - you really must read through the thread, JR.

jraju · « **Reply #58 on:** June 18, 2015, 05:46:47 am »

Hi, Boggins, I read the thread thoroughly,
Then it is not regsvr problem. But the thread goes on to say that his printer is not working. The image pointed to this error. Normally, this error occurs because of non compability of exes of 32 for a 64 supported system. I think he has started another thread and asking solutions for the previous threads of him.

Julian · « **Reply #59 on:** June 18, 2015, 07:01:59 am »

Quote from: jraju on June 18, 2015, 04:14:24 am

Hi, Please see this link. Eventhough it relates to some othr dll, see the solution and let me know how it goes
http://csi-windows.com/blog/all/73-windows-64-bit/378-fixing-qregsvr32-the-module-failed-to-load-the-specified-module-could-not-be-foundq

The .dll that I've uploaded was a x64 dll from windows 7 disk I mounted the install.wim via dism.

sallyb · « **Reply #60 on:** June 18, 2015, 07:24:19 am »

OK, thank you for your responses. I did not download the hotfix thing because Microsoft said not to use it unless I am positive it applies to the problem described...? So I don't know about that and don't want to make a bigger mess. Also I didn't do the bluescreen dump thing because I have not been having the bluescreen. The ole32.dll problem just seems to stop any program. So I am able to shut down the open programs and try to reboot. However when I do the reboot, it goes to shut down, seems to close the background programs, and then just shows an empty desktop with only the screen saver. The computer is stuck there. So I have to press the on/off button to make a force shut down, which then causes more problems.
Yes, the original ole32.dll file was 64 bit and I have a 64 bit system. The new file was 64 bit so that's not the deal. I am enclosing screen shots of the event....
Also, I am able to print. I have another wireless printer which works fine. I just can not print through the modem using Bonjour Printing Services anymore. I can also print through the network printer installed on another computer, but the computer must be awake for it to work.
I will try the adware thing, but really don't know what else to do!

sallyb · « **Reply #61 on:** June 18, 2015, 07:32:11 am »

Can you please send me the link to the adware cleaner program if you think that is my problem? Thank you!

Julian · « **Reply #62 on:** June 18, 2015, 08:10:19 am »

Quote from: sallyb on June 18, 2015, 07:24:19 am

However when I do the reboot, it goes to shut down, seems to close the background programs, and then just shows an empty desktop with only the screen saver. The computer is stuck there. So I have to press the on/off button to make a force shut down, which then causes more problems.

when this happens hit ctrl+shift+esc. It should open task mgr. Than hit new task type shutdown -a then type shutdown -r -01

Julian · « **Reply #63 on:** June 18, 2015, 08:27:38 am »

Hmmm just read the event log pics that is interesting. Give me a bit ill be back in a awhile.

Boggin · « **Reply #64 on:** June 18, 2015, 08:42:38 am »

When you first open Event Viewer and it has read the logs, you'll be presented with Critical/Error etc. for the last 24hrs - 7 days etc.

If you don't have any Critical, click on Error then on Show All Instances of This Event in the lower right pane.

It's those with the corresponding time stamps that will give more info.

You can copy any item in Event Viewer by clicking on it then on Copy/Copy details as text in the lower right pane and then right click in the reply box and select Paste.

When you click on any Error, that will also display in the lower pane where clicking on the blue online help link will take you to a tech page if MS has anything on it.

This will give causes and possible solutions if there is sufficient info for the Event ID No.

sallyb · « **Reply #65 on:** June 18, 2015, 11:18:09 am »

Thank you I will check on all those things a little later because I am not at the machine right now .

sallyb · « **Reply #66 on:** June 18, 2015, 11:23:03 am »

PS when I get this desktop screen thing in the computer shutdown I do a control alternate delete with no response. I will try the other at the next crap out!

Boggin · « **Reply #67 on:** June 18, 2015, 01:58:42 pm »

That Hotfix does apply to you because it's crashing Windows Explorer - if that crashes, your computer will freeze up.

I don't think you have to get a BSOD for a Dump file to be created - from that article, this error was being added to MS Dump Diagnostics so BSV could pick up on a Dump file.

If you are worried about the Hotfix, Windows creates a restore point before applying any MS Fixits but as a belt & braces you can also create your own.

sallyb · « **Reply #68 on:** June 18, 2015, 04:30:56 pm »

OK, as far as the error log...I can not make heads nor tails of it...there are no citical errors, but a million "errors" I can not figure out what it means...

Boggin · « **Reply #69 on:** June 18, 2015, 04:35:36 pm »

Look for the ones that have a time stamp about the same time as you had to power shutdown - they should be near an Event ID 41, but run that Hotfix (see my previous post) and see if there's any improvement.

sallyb · « **Reply #70 on:** June 18, 2015, 05:47:54 pm »

Now I have ANOTHER PROBLEM!!! I am soooo tired of dealing with this, that I was trying to just use my machine for awhile and try to forget about all this. I have always been able to search my computer for files and folders. Specifically, I just opened up the Windows Explorer and went to libraries. I went to the search libraries box in the upper right hand corner and typed in what I was looking for and.....nothing! The computer didn't search like before! This is pretty major for me...HELP!!! I am so sorry to be such a pain, but I am at my wits end.....

sallyb · « **Reply #71 on:** June 18, 2015, 06:10:02 pm »

I think that I have figured that one out by going to control panel/indexing options. Why did indexing stop running, though? I'm going nuts! What else now?

Julian · « **Reply #72 on:** June 18, 2015, 08:23:29 pm »

Quote from: sallyb on June 18, 2015, 06:10:02 pm

I think that I have figured that one out by going to control panel/indexing options. Why did indexing stop running, though? I'm going nuts! What else now?

on the start menu type in services
then look for windows search right click properties change to automatic

jraju · « **Reply #73 on:** June 18, 2015, 09:14:17 pm »

Hi, give me the point of problem. What happens to search engine. Is it slow and take much time for scanning, like showing a green progressive bar slowly trying to capture the files. Or does it hang up and show nothing. Please clearly tell what is your problem. if the folder search is slow,The most likely solution: in Explorer, right click on folder or drive, select properties,- customize,- under "optimize this folder for:", select General items and then click box "Also apply this template to all subfolders", then click apply.
This is a problem caused by some virus or unknown bugs, changing the general items in the properties to picture or video. Searching and scanning thumbnails and picture slow and so the green bar everlasting presence. Hope that this helps
update: I had this problem and this solution helped me very much. As boggins pointed out, if explorer is crashing, nothing could be accomplished. Please use the fixit, it will save you lot of trouble.

sallyb · « **Reply #74 on:** June 19, 2015, 04:52:24 am »

Julian, I did the services/windows search and it was already on automatic. Jraju, the problem was that the windows search engine just was not responding, not working, nothing. So I figured out that the "indexing" was not running. I was able to fix it by going to control panel/indexing options and turning it on for the hard drive. Then it was back to normal. I could quickly and easily find the files and folders I was looking for! I will try the fixit, but I will be upset if more problems arise. I created a restore point just now, though.