Tweaking.com Support Forums
Main Forum => General Computer Support => Topic started by: sallyb on June 15, 2015, 07:22:56 pm
-
OK, I really need help, now. I signed up for the pro version last Friday and was very happy to find a place where I could find help to fix stuff on my computer. All the "PC fix-it" programs seem to be a big scam..just says that things are being fixed, but nothing seems to change. This place seems different..HOWEVER; I spent all week end trying to clean out my pre scan errors etc so that I could do the repair. I was having trouble with corrupted files on the system scan and Boggin said that they were due to the Windows Update KB3068708. He suggested that I delete that update, which I did, but the errors were still there. Anyway, he said it didn't matter. So I finally was able to get clean scans except for that, and I ran the repairs. I did backup the registry and created restore points. All went well...I thought. But now I can not print from my beloved HP Laserjet 1200 which I have had since around 2002...I know it's old, but it works like a champion. Anyway, I have been printing wirelessly through my Apple Extreme Router for years now on several machines with no problem, but I can't now. I even took it apart a couple of months ago and fixed it because it was jamming. (I need to tell you that I am a 67 year old woman who is NOT AFRAID of computers, and I have been in love with them probably before most of you were even born...cut my teeth on a Texas Instrument machine around 1980...anyway) So I tried everything...uninstalled Bonjour printing services, reinstalled it, deleted the printer, reinstalled it, rebooted, nothing...It WILL NOT WORK NOW!!!
THEN... I get the ole.32.dll error that I have been getting for months! This is the reason that I have been trying to find a solution. When I get this error.. File attached, my computer basically freezes, I also get the other error...file attached....then I am unable to shut down my machine. This happened today...SO THEN...I went through the whole thing again with the Windows repair...this time I needed to do a check disk and I did the long one...took hours, but it fixed everything. Then I did another repair...
So then I got back on my printer problem and GUESS WHAT...got the same damm ole32.dll error and started all over again. When I got to the check disk thing, it said I had errors and needed to run check disk again DuH! this time I bolted and came here! I'm disgusted...I'm worse off than I was before...I would really like this corrected. I am going to enclose some logs but the ones before this last crash.
Here is the System File Scan report:
2015-06-15 17:02:29, Info CSI 00000009 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:02:29, Info CSI 0000000a [SR] Beginning Verify and Repair transaction
2015-06-15 17:02:33, Info CSI 0000000c [SR] Verify complete
2015-06-15 17:02:34, Info CSI 0000000d [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:02:34, Info CSI 0000000e [SR] Beginning Verify and Repair transaction
2015-06-15 17:02:36, Info CSI 00000010 [SR] Verify complete
2015-06-15 17:02:37, Info CSI 00000011 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:02:37, Info CSI 00000012 [SR] Beginning Verify and Repair transaction
2015-06-15 17:02:38, Info CSI 00000014 [SR] Verify complete
2015-06-15 17:02:39, Info CSI 00000015 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:02:39, Info CSI 00000016 [SR] Beginning Verify and Repair transaction
2015-06-15 17:02:40, Info CSI 00000018 [SR] Verify complete
2015-06-15 17:02:42, Info CSI 00000019 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:02:42, Info CSI 0000001a [SR] Beginning Verify and Repair transaction
2015-06-15 17:02:43, Info CSI 0000001c [SR] Verify complete
2015-06-15 17:02:44, Info CSI 0000001d [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:02:44, Info CSI 0000001e [SR] Beginning Verify and Repair transaction
2015-06-15 17:02:45, Info CSI 00000020 [SR] Verify complete
2015-06-15 17:02:46, Info CSI 00000021 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:02:46, Info CSI 00000022 [SR] Beginning Verify and Repair transaction
2015-06-15 17:02:47, Info CSI 00000024 [SR] Verify complete
2015-06-15 17:02:48, Info CSI 00000025 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:02:48, Info CSI 00000026 [SR] Beginning Verify and Repair transaction
2015-06-15 17:02:49, Info CSI 00000028 [SR] Verify complete
2015-06-15 17:02:50, Info CSI 00000029 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:02:50, Info CSI 0000002a [SR] Beginning Verify and Repair transaction
2015-06-15 17:02:51, Info CSI 0000002c [SR] Verify complete
2015-06-15 17:02:51, Info CSI 0000002d [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:02:51, Info CSI 0000002e [SR] Beginning Verify and Repair transaction
2015-06-15 17:02:52, Info CSI 00000030 [SR] Verify complete
2015-06-15 17:02:53, Info CSI 00000031 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:02:53, Info CSI 00000032 [SR] Beginning Verify and Repair transaction
2015-06-15 17:02:54, Info CSI 00000034 [SR] Verify complete
2015-06-15 17:02:54, Info CSI 00000035 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:02:54, Info CSI 00000036 [SR] Beginning Verify and Repair transaction
2015-06-15 17:02:55, Info CSI 00000038 [SR] Verify complete
2015-06-15 17:02:56, Info CSI 00000039 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:02:56, Info CSI 0000003a [SR] Beginning Verify and Repair transaction
2015-06-15 17:02:57, Info CSI 0000003c [SR] Verify complete
2015-06-15 17:02:57, Info CSI 0000003d [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:02:57, Info CSI 0000003e [SR] Beginning Verify and Repair transaction
2015-06-15 17:02:58, Info CSI 00000040 [SR] Verify complete
2015-06-15 17:02:59, Info CSI 00000041 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:02:59, Info CSI 00000042 [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:00, Info CSI 00000044 [SR] Verify complete
2015-06-15 17:03:01, Info CSI 00000045 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:01, Info CSI 00000046 [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:02, Info CSI 00000048 [SR] Verify complete
2015-06-15 17:03:02, Info CSI 00000049 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:02, Info CSI 0000004a [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:04, Info CSI 0000004c [SR] Verify complete
2015-06-15 17:03:05, Info CSI 0000004d [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:05, Info CSI 0000004e [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:06, Info CSI 00000050 [SR] Verify complete
2015-06-15 17:03:06, Info CSI 00000051 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:06, Info CSI 00000052 [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:07, Info CSI 00000054 [SR] Verify complete
2015-06-15 17:03:08, Info CSI 00000055 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:08, Info CSI 00000056 [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:09, Info CSI 00000058 [SR] Verify complete
2015-06-15 17:03:10, Info CSI 00000059 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:10, Info CSI 0000005a [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:11, Info CSI 0000005c [SR] Verify complete
2015-06-15 17:03:12, Info CSI 0000005d [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:12, Info CSI 0000005e [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:13, Info CSI 00000060 [SR] Verify complete
2015-06-15 17:03:13, Info CSI 00000061 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:13, Info CSI 00000062 [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:14, Info CSI 00000064 [SR] Verify complete
2015-06-15 17:03:15, Info CSI 00000065 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:15, Info CSI 00000066 [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:16, Info CSI 00000068 [SR] Verify complete
2015-06-15 17:03:16, Info CSI 00000069 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:16, Info CSI 0000006a [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:18, Info CSI 0000006c [SR] Verify complete
2015-06-15 17:03:18, Info CSI 0000006d [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:18, Info CSI 0000006e [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:20, Info CSI 00000070 [SR] Verify complete
2015-06-15 17:03:20, Info CSI 00000071 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:20, Info CSI 00000072 [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:22, Info CSI 00000074 [SR] Verify complete
2015-06-15 17:03:22, Info CSI 00000075 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:22, Info CSI 00000076 [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:22, Info CSI 00000078 [SR] Verify complete
2015-06-15 17:03:23, Info CSI 00000079 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:23, Info CSI 0000007a [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:26, Info CSI 0000007c [SR] Verify complete
2015-06-15 17:03:26, Info CSI 0000007d [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:26, Info CSI 0000007e [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:31, Info CSI 00000081 [SR] Verify complete
2015-06-15 17:03:31, Info CSI 00000082 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:31, Info CSI 00000083 [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:34, Info CSI 00000088 [SR] Verify complete
2015-06-15 17:03:35, Info CSI 00000089 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:35, Info CSI 0000008a [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:38, Info CSI 0000008d [SR] Verify complete
2015-06-15 17:03:38, Info CSI 0000008e [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:38, Info CSI 0000008f [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:42, Info CSI 00000091 [SR] Verify complete
2015-06-15 17:03:42, Info CSI 00000092 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:42, Info CSI 00000093 [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:47, Info CSI 000000b5 [SR] Verify complete
2015-06-15 17:03:47, Info CSI 000000b6 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:47, Info CSI 000000b7 [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:51, Info CSI 000000bc [SR] Verify complete
2015-06-15 17:03:51, Info CSI 000000bd [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:51, Info CSI 000000be [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:55, Info CSI 000000c0 [SR] Verify complete
2015-06-15 17:03:56, Info CSI 000000c1 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:56, Info CSI 000000c2 [SR] Beginning Verify and Repair transaction
2015-06-15 17:03:58, Info CSI 000000c4 [SR] Verify complete
2015-06-15 17:03:59, Info CSI 000000c5 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:03:59, Info CSI 000000c6 [SR] Beginning Verify and Repair transaction
2015-06-15 17:04:02, Info CSI 000000c8 [SR] Verify complete
2015-06-15 17:04:02, Info CSI 000000c9 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:04:02, Info CSI 000000ca [SR] Beginning Verify and Repair transaction
2015-06-15 17:04:05, Info CSI 000000cc [SR] Verify complete
2015-06-15 17:04:05, Info CSI 000000cd [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:04:05, Info CSI 000000ce [SR] Beginning Verify and Repair transaction
2015-06-15 17:04:09, Info CSI 000000d0 [SR] Verify complete
2015-06-15 17:04:09, Info CSI 000000d1 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:04:09, Info CSI 000000d2 [SR] Beginning Verify and Repair transaction
2015-06-15 17:04:15, Info CSI 000000f5 [SR] Verify complete
2015-06-15 17:04:15, Info CSI 000000f6 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:04:15, Info CSI 000000f7 [SR] Beginning Verify and Repair transaction
2015-06-15 17:04:19, Info CSI 000000f9 [SR] Verify complete
2015-06-15 17:04:20, Info CSI 000000fa [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:04:20, Info CSI 000000fb [SR] Beginning Verify and Repair transaction
2015-06-15 17:04:26, Info CSI 000000fd [SR] Verify complete
2015-06-15 17:04:26, Info CSI 000000fe [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:04:26, Info CSI 000000ff [SR] Beginning Verify and Repair transaction
2015-06-15 17:04:30, Info CSI 00000103 [SR] Verify complete
2015-06-15 17:04:30, Info CSI 00000104 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:04:30, Info CSI 00000105 [SR] Beginning Verify and Repair transaction
2015-06-15 17:04:31, Info CSI 00000107 [SR] Verify complete
2015-06-15 17:04:31, Info CSI 00000108 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:04:31, Info CSI 00000109 [SR] Beginning Verify and Repair transaction
2015-06-15 17:04:32, Info CSI 0000010b [SR] Verify complete
2015-06-15 17:04:32, Info CSI 0000010c [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:04:32, Info CSI 0000010d [SR] Beginning Verify and Repair transaction
2015-06-15 17:04:35, Info CSI 00000116 [SR] Verify complete
2015-06-15 17:04:36, Info CSI 00000117 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:04:36, Info CSI 00000118 [SR] Beginning Verify and Repair transaction
2015-06-15 17:04:39, Info CSI 00000124 [SR] Verify complete
2015-06-15 17:04:39, Info CSI 00000125 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:04:39, Info CSI 00000126 [SR] Beginning Verify and Repair transaction
2015-06-15 17:04:41, Info CSI 00000128 [SR] Verify complete
2015-06-15 17:04:41, Info CSI 00000129 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:04:41, Info CSI 0000012a [SR] Beginning Verify and Repair transaction
2015-06-15 17:04:44, Info CSI 0000012c [SR] Verify complete
2015-06-15 17:04:44, Info CSI 0000012d [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:04:44, Info CSI 0000012e [SR] Beginning Verify and Repair transaction
2015-06-15 17:04:47, Info CSI 00000130 [SR] Verify complete
2015-06-15 17:04:47, Info CSI 00000131 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:04:47, Info CSI 00000132 [SR] Beginning Verify and Repair transaction
2015-06-15 17:04:53, Info CSI 00000135 [SR] Verify complete
2015-06-15 17:04:53, Info CSI 00000136 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:04:53, Info CSI 00000137 [SR] Beginning Verify and Repair transaction
2015-06-15 17:04:57, Info CSI 0000013a [SR] Verify complete
2015-06-15 17:04:58, Info CSI 0000013b [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:04:58, Info CSI 0000013c [SR] Beginning Verify and Repair transaction
2015-06-15 17:04:59, Info CSI 0000013e [SR] Verify complete
2015-06-15 17:04:59, Info CSI 0000013f [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:04:59, Info CSI 00000140 [SR] Beginning Verify and Repair transaction
2015-06-15 17:05:01, Info CSI 00000142 [SR] Verify complete
2015-06-15 17:05:01, Info CSI 00000143 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:05:01, Info CSI 00000144 [SR] Beginning Verify and Repair transaction
2015-06-15 17:05:07, Info CSI 00000146 [SR] Verify complete
2015-06-15 17:05:07, Info CSI 00000147 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:05:07, Info CSI 00000148 [SR] Beginning Verify and Repair transaction
2015-06-15 17:05:10, Info CSI 0000014a [SR] Verify complete
2015-06-15 17:05:10, Info CSI 0000014b [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:05:10, Info CSI 0000014c [SR] Beginning Verify and Repair transaction
2015-06-15 17:05:15, Info CSI 0000014e [SR] Verify complete
2015-06-15 17:05:15, Info CSI 0000014f [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:05:15, Info CSI 00000150 [SR] Beginning Verify and Repair transaction
2015-06-15 17:05:20, Info CSI 00000168 [SR] Verify complete
2015-06-15 17:05:20, Info CSI 00000169 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:05:20, Info CSI 0000016a [SR] Beginning Verify and Repair transaction
2015-06-15 17:05:23, Info CSI 0000016c [SR] Verify complete
2015-06-15 17:05:24, Info CSI 0000016d [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:05:24, Info CSI 0000016e [SR] Beginning Verify and Repair transaction
2015-06-15 17:05:32, Info CSI 00000170 [SR] Verify complete
2015-06-15 17:05:32, Info CSI 00000171 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:05:32, Info CSI 00000172 [SR] Beginning Verify and Repair transaction
2015-06-15 17:05:37, Info CSI 00000175 [SR] Verify complete
2015-06-15 17:05:37, Info CSI 00000176 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:05:37, Info CSI 00000177 [SR] Beginning Verify and Repair transaction
2015-06-15 17:05:42, Info CSI 00000179 [SR] Verify complete
2015-06-15 17:05:42, Info CSI 0000017a [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:05:42, Info CSI 0000017b [SR] Beginning Verify and Repair transaction
2015-06-15 17:05:45, Info CSI 0000017d [SR] Verify complete
2015-06-15 17:05:45, Info CSI 0000017e [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:05:45, Info CSI 0000017f [SR] Beginning Verify and Repair transaction
2015-06-15 17:05:48, Info CSI 00000181 [SR] Verify complete
2015-06-15 17:05:48, Info CSI 00000182 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:05:48, Info CSI 00000183 [SR] Beginning Verify and Repair transaction
2015-06-15 17:05:51, Info CSI 00000187 [SR] Verify complete
2015-06-15 17:05:52, Info CSI 00000188 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:05:52, Info CSI 00000189 [SR] Beginning Verify and Repair transaction
2015-06-15 17:05:55, Info CSI 0000018b [SR] Verify complete
2015-06-15 17:05:55, Info CSI 0000018c [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:05:55, Info CSI 0000018d [SR] Beginning Verify and Repair transaction
2015-06-15 17:06:02, Info CSI 0000018f [SR] Verify complete
2015-06-15 17:06:03, Info CSI 00000190 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:06:03, Info CSI 00000191 [SR] Beginning Verify and Repair transaction
2015-06-15 17:06:07, Info CSI 00000194 [SR] Verify complete
2015-06-15 17:06:07, Info CSI 00000195 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:06:07, Info CSI 00000196 [SR] Beginning Verify and Repair transaction
2015-06-15 17:06:11, Info CSI 00000199 [SR] Verify complete
2015-06-15 17:06:11, Info CSI 0000019a [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:06:11, Info CSI 0000019b [SR] Beginning Verify and Repair transaction
2015-06-15 17:06:15, Info CSI 0000019d [SR] Verify complete
2015-06-15 17:06:15, Info CSI 0000019e [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:06:15, Info CSI 0000019f [SR] Beginning Verify and Repair transaction
2015-06-15 17:06:19, Info CSI 000001a2 [SR] Verify complete
2015-06-15 17:06:20, Info CSI 000001a3 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:06:20, Info CSI 000001a4 [SR] Beginning Verify and Repair transaction
2015-06-15 17:06:22, Info CSI 000001a6 [SR] Verify complete
2015-06-15 17:06:23, Info CSI 000001a7 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:06:23, Info CSI 000001a8 [SR] Beginning Verify and Repair transaction
2015-06-15 17:06:26, Info CSI 000001aa [SR] Verify complete
2015-06-15 17:06:26, Info CSI 000001ab [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:06:26, Info CSI 000001ac [SR] Beginning Verify and Repair transaction
2015-06-15 17:06:29, Info CSI 000001af [SR] Verify complete
2015-06-15 17:06:30, Info CSI 000001b0 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:06:30, Info CSI 000001b1 [SR] Beginning Verify and Repair transaction
2015-06-15 17:06:34, Info CSI 000001b3 [SR] Verify complete
2015-06-15 17:06:34, Info CSI 000001b4 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:06:34, Info CSI 000001b5 [SR] Beginning Verify and Repair transaction
2015-06-15 17:06:35, Info CSI 000001b7 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-06-15 17:06:35, Info CSI 000001b9 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-06-15 17:06:36, Info CSI 000001bb [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-06-15 17:06:36, Info CSI 000001bc [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2015-06-15 17:06:36, Info CSI 000001be [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-06-15 17:06:36, Info CSI 000001bf [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2015-06-15 17:06:37, Info CSI 000001c2 [SR] Verify complete
2015-06-15 17:06:37, Info CSI 000001c3 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:06:37, Info CSI 000001c4 [SR] Beginning Verify and Repair transaction
2015-06-15 17:06:40, Info CSI 000001c7 [SR] Verify complete
2015-06-15 17:06:41, Info CSI 000001c8 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:06:41, Info CSI 000001c9 [SR] Beginning Verify and Repair transaction
2015-06-15 17:06:45, Info CSI 000001cb [SR] Verify complete
2015-06-15 17:06:45, Info CSI 000001cc [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:06:45, Info CSI 000001cd [SR] Beginning Verify and Repair transaction
2015-06-15 17:06:48, Info CSI 000001d1 [SR] Verify complete
2015-06-15 17:06:49, Info CSI 000001d2 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:06:49, Info CSI 000001d3 [SR] Beginning Verify and Repair transaction
2015-06-15 17:06:53, Info CSI 000001d5 [SR] Verify complete
2015-06-15 17:06:53, Info CSI 000001d6 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:06:53, Info CSI 000001d7 [SR] Beginning Verify and Repair transaction
2015-06-15 17:06:57, Info CSI 000001da [SR] Verify complete
2015-06-15 17:06:57, Info CSI 000001db [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:06:57, Info CSI 000001dc [SR] Beginning Verify and Repair transaction
2015-06-15 17:07:00, Info CSI 000001de [SR] Verify complete
2015-06-15 17:07:00, Info CSI 000001df [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:07:00, Info CSI 000001e0 [SR] Beginning Verify and Repair transaction
2015-06-15 17:07:01, Info CSI 000001e2 [SR] Verify complete
2015-06-15 17:07:02, Info CSI 000001e3 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:07:02, Info CSI 000001e4 [SR] Beginning Verify and Repair transaction
2015-06-15 17:07:04, Info CSI 000001e6 [SR] Verify complete
2015-06-15 17:07:04, Info CSI 000001e7 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:07:04, Info CSI 000001e8 [SR] Beginning Verify and Repair transaction
2015-06-15 17:07:08, Info CSI 000001ea [SR] Verify complete
2015-06-15 17:07:08, Info CSI 000001eb [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:07:08, Info CSI 000001ec [SR] Beginning Verify and Repair transaction
2015-06-15 17:07:12, Info CSI 000001ee [SR] Verify complete
2015-06-15 17:07:12, Info CSI 000001ef [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:07:12, Info CSI 000001f0 [SR] Beginning Verify and Repair transaction
2015-06-15 17:07:14, Info CSI 000001f2 [SR] Verify complete
2015-06-15 17:07:14, Info CSI 000001f3 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:07:14, Info CSI 000001f4 [SR] Beginning Verify and Repair transaction
2015-06-15 17:07:17, Info CSI 000001f6 [SR] Verify complete
2015-06-15 17:07:17, Info CSI 000001f7 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:07:17, Info CSI 000001f8 [SR] Beginning Verify and Repair transaction
2015-06-15 17:07:25, Info CSI 000001fa [SR] Verify complete
2015-06-15 17:07:25, Info CSI 000001fb [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:07:25, Info CSI 000001fc [SR] Beginning Verify and Repair transaction
2015-06-15 17:07:34, Info CSI 000001fe [SR] Verify complete
2015-06-15 17:07:34, Info CSI 000001ff [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:07:34, Info CSI 00000200 [SR] Beginning Verify and Repair transaction
2015-06-15 17:07:37, Info CSI 00000202 [SR] Verify complete
2015-06-15 17:07:37, Info CSI 00000203 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:07:37, Info CSI 00000204 [SR] Beginning Verify and Repair transaction
2015-06-15 17:07:40, Info CSI 00000206 [SR] Verify complete
2015-06-15 17:07:40, Info CSI 00000207 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:07:40, Info CSI 00000208 [SR] Beginning Verify and Repair transaction
2015-06-15 17:07:42, Info CSI 0000020a [SR] Verify complete
2015-06-15 17:07:42, Info CSI 0000020b [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:07:42, Info CSI 0000020c [SR] Beginning Verify and Repair transaction
2015-06-15 17:07:43, Info CSI 0000020e [SR] Verify complete
2015-06-15 17:07:43, Info CSI 0000020f [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:07:43, Info CSI 00000210 [SR] Beginning Verify and Repair transaction
2015-06-15 17:07:46, Info CSI 00000212 [SR] Verify complete
2015-06-15 17:07:46, Info CSI 00000213 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:07:46, Info CSI 00000214 [SR] Beginning Verify and Repair transaction
2015-06-15 17:07:47, Info CSI 00000216 [SR] Verify complete
2015-06-15 17:07:47, Info CSI 00000217 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:07:47, Info CSI 00000218 [SR] Beginning Verify and Repair transaction
2015-06-15 17:07:48, Info CSI 0000021a [SR] Verify complete
2015-06-15 17:07:48, Info CSI 0000021b [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:07:48, Info CSI 0000021c [SR] Beginning Verify and Repair transaction
2015-06-15 17:07:52, Info CSI 00000224 [SR] Verify complete
2015-06-15 17:07:52, Info CSI 00000225 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:07:52, Info CSI 00000226 [SR] Beginning Verify and Repair transaction
2015-06-15 17:07:54, Info CSI 00000228 [SR] Verify complete
2015-06-15 17:07:54, Info CSI 00000229 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:07:54, Info CSI 0000022a [SR] Beginning Verify and Repair transaction
2015-06-15 17:07:56, Info CSI 0000022c [SR] Verify complete
2015-06-15 17:07:56, Info CSI 0000022d [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:07:56, Info CSI 0000022e [SR] Beginning Verify and Repair transaction
2015-06-15 17:07:59, Info CSI 00000230 [SR] Verify complete
2015-06-15 17:07:59, Info CSI 00000231 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:07:59, Info CSI 00000232 [SR] Beginning Verify and Repair transaction
2015-06-15 17:08:02, Info CSI 00000234 [SR] Verify complete
2015-06-15 17:08:03, Info CSI 00000235 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:08:03, Info CSI 00000236 [SR] Beginning Verify and Repair transaction
2015-06-15 17:08:07, Info CSI 00000239 [SR] Verify complete
2015-06-15 17:08:07, Info CSI 0000023a [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:08:07, Info CSI 0000023b [SR] Beginning Verify and Repair transaction
2015-06-15 17:08:08, Info CSI 0000023d [SR] Verify complete
2015-06-15 17:08:09, Info CSI 0000023e [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:08:09, Info CSI 0000023f [SR] Beginning Verify and Repair transaction
2015-06-15 17:08:10, Info CSI 00000241 [SR] Verify complete
2015-06-15 17:08:11, Info CSI 00000242 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:08:11, Info CSI 00000243 [SR] Beginning Verify and Repair transaction
2015-06-15 17:08:17, Info CSI 00000248 [SR] Verify complete
2015-06-15 17:08:17, Info CSI 00000249 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:08:17, Info CSI 0000024a [SR] Beginning Verify and Repair transaction
2015-06-15 17:08:23, Info CSI 0000024d [SR] Verify complete
2015-06-15 17:08:23, Info CSI 0000024e [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:08:23, Info CSI 0000024f [SR] Beginning Verify and Repair transaction
2015-06-15 17:08:27, Info CSI 00000253 [SR] Verify complete
2015-06-15 17:08:28, Info CSI 00000254 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:08:28, Info CSI 00000255 [SR] Beginning Verify and Repair transaction
2015-06-15 17:08:31, Info CSI 00000260 [SR] Verify complete
2015-06-15 17:08:32, Info CSI 00000261 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:08:32, Info CSI 00000262 [SR] Beginning Verify and Repair transaction
2015-06-15 17:08:36, Info CSI 00000269 [SR] Verify complete
2015-06-15 17:08:36, Info CSI 0000026a [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:08:36, Info CSI 0000026b [SR] Beginning Verify and Repair transaction
2015-06-15 17:08:39, Info CSI 0000026d [SR] Verify complete
2015-06-15 17:08:40, Info CSI 0000026e [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:08:40, Info CSI 0000026f [SR] Beginning Verify and Repair transaction
2015-06-15 17:08:42, Info CSI 00000273 [SR] Verify complete
2015-06-15 17:08:42, Info CSI 00000274 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:08:42, Info CSI 00000275 [SR] Beginning Verify and Repair transaction
2015-06-15 17:08:45, Info CSI 00000277 [SR] Verify complete
2015-06-15 17:08:45, Info CSI 00000278 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:08:45, Info CSI 00000279 [SR] Beginning Verify and Repair transaction
2015-06-15 17:08:49, Info CSI 0000029e [SR] Verify complete
2015-06-15 17:08:49, Info CSI 0000029f [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:08:49, Info CSI 000002a0 [SR] Beginning Verify and Repair transaction
2015-06-15 17:08:52, Info CSI 000002a2 [SR] Verify complete
2015-06-15 17:08:52, Info CSI 000002a3 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:08:52, Info CSI 000002a4 [SR] Beginning Verify and Repair transaction
2015-06-15 17:08:55, Info CSI 000002a6 [SR] Verify complete
2015-06-15 17:08:55, Info CSI 000002a7 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:08:55, Info CSI 000002a8 [SR] Beginning Verify and Repair transaction
2015-06-15 17:08:58, Info CSI 000002aa [SR] Verify complete
2015-06-15 17:08:58, Info CSI 000002ab [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:08:58, Info CSI 000002ac [SR] Beginning Verify and Repair transaction
2015-06-15 17:09:00, Info CSI 000002ba [SR] Verify complete
2015-06-15 17:09:00, Info CSI 000002bb [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:09:00, Info CSI 000002bc [SR] Beginning Verify and Repair transaction
2015-06-15 17:09:03, Info CSI 000002be [SR] Verify complete
2015-06-15 17:09:03, Info CSI 000002bf [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:09:03, Info CSI 000002c0 [SR] Beginning Verify and Repair transaction
2015-06-15 17:09:07, Info CSI 000002ce [SR] Verify complete
2015-06-15 17:09:07, Info CSI 000002cf [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:09:07, Info CSI 000002d0 [SR] Beginning Verify and Repair transaction
2015-06-15 17:09:09, Info CSI 000002d2 [SR] Verify complete
2015-06-15 17:09:09, Info CSI 000002d3 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:09:09, Info CSI 000002d4 [SR] Beginning Verify and Repair transaction
2015-06-15 17:09:12, Info CSI 000002d6 [SR] Verify complete
2015-06-15 17:09:12, Info CSI 000002d7 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:09:12, Info CSI 000002d8 [SR] Beginning Verify and Repair transaction
2015-06-15 17:09:15, Info CSI 000002db [SR] Verify complete
2015-06-15 17:09:15, Info CSI 000002dc [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:09:15, Info CSI 000002dd [SR] Beginning Verify and Repair transaction
2015-06-15 17:09:16, Info CSI 000002df [SR] Verify complete
2015-06-15 17:09:16, Info CSI 000002e0 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:09:16, Info CSI 000002e1 [SR] Beginning Verify and Repair transaction
2015-06-15 17:09:20, Info CSI 000002e3 [SR] Verify complete
2015-06-15 17:09:20, Info CSI 000002e4 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:09:20, Info CSI 000002e5 [SR] Beginning Verify and Repair transaction
2015-06-15 17:09:23, Info CSI 000002e7 [SR] Verify complete
2015-06-15 17:09:23, Info CSI 000002e8 [SR] Verifying 100 (0x0000000000000064) components
2015-06-15 17:09:23, Info CSI 000002e9 [SR] Beginning Verify and Repair transac
-
So I don't know what happened here because I also copied my check disk logs and repair logs....but I don't see them...so just tell me what is needed....
-
My repairs dont do anything to the system files, Since you have another thread going I will answer here.
When you did the chkdsk did you do the one where it checks for bad sectors? That would be the 5 stage one and not the 3 stage. That scan would take hours, if that is the one you did can you post the log of that one? In the other thread you only posted the 3 stage one, that doesnt check for bad sectors.
The error you are getting ole32.dll is the same error I have seen when a system file is on a bad sector on the drive, since it is on a bad sector the file becomes corrupt and you will get messages such as you are getting about how the file isnt correct.
If other files are on bad sectors that would explain sfc reporting problems as well. Again my program doesn't remove or replace ANY system files at all, so the drive is the first thing we need to verify :wink:
(95% of the repairs in the program are all registry related)
If you havent done a bad sector check yet, open a cmd.exe window as administrator and put in
chkdsk c: /r
It will say it cant because it is in use and would you like to schedule it, hit Y and then reboot. The chkdsk should start before windows does, go watch a movie and come back, when the scan is done the results will be in the event viewer, post those for me :wink:
Shane
-
So I don't know what happened here because I also copied my check disk logs and repair logs....but I don't see them...so just tell me what is needed....
Hmmm I can't find your posted log no worries do this:
If you havent done a bad sector check yet, open a cmd.exe window as administrator and put in
chkdsk c: /r
It will say it cant because it is in use and would you like to schedule it, hit Y and then reboot. The chkdsk should start before windows does, go watch a movie and come back, when the scan is done the results will be in the event viewer, post those for me :wink:
Shane
I've noticed on forums most people understand steps with pictures so ive setup a picture on the steps you need to take
-
I DID do the bad sector check! I will dig up that report and post it here later..I'm on my IPad now. Yes, it took hours..(and hours) and I was hoping that would maybe fix things. But I had just started to try and get my printer working again, (it wouldn't) when I got the dreaded ole32.dll error message! Then it crapped things out again as a preliminary check to "see if I needed to run chkdsk" said there were problems; although, it was clean after the chkdsk/r!
Is there any help for me?
-
I wonder if you've done what I sometimes do Sally and that is after checking the post in Preview, forget to hit the Submit Reply button and think I've posted it just to find later that it is missing.
Your previous chkdsk although just a file check, reported no bad sectors which it still can report if it finds any, but when a chkdsk takes ages to complete then there is major corruption in some form which would tend to suggest there were bad sectors.
The Telemetry errors reported in the sfc are typical of the ones generated by the KB, so I don't think they are a result of any bad sectors, but the chkdsk /r had obviously found something it had to repair.
-
Here is the chkdsk/r report:
Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 6/15/2015 4:22:59 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 5)...
488192 file records processed.
File verification completed.
1087 large file records processed.
0 bad file records processed.
0 EA records processed.
45 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 5)...
633900 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 5)...
488192 file SDs/SIDs processed.
Cleaning up 48 unused index entries from index $SII of file 0x9.
Cleaning up 48 unused index entries from index $SDH of file 0x9.
Cleaning up 48 unused security descriptors.
Security descriptor verification completed.
72855 data files processed.
CHKDSK is verifying Usn Journal...
35558024 USN bytes processed.
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
488176 files processed.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
115019811 free clusters processed.
Free space verification is complete.
Windows has checked the file system and found no problems.
955629567 KB total disk space.
494672948 KB in 360512 files.
252768 KB in 72856 indexes.
0 KB in bad sectors.
624607 KB in use by the system.
65536 KB occupied by the log file.
460079244 KB available on disk.
4096 bytes in each allocation unit.
238907391 total allocation units on disk.
115019811 allocation units available on disk.
Internal Info:
00 73 07 00 dc 9c 06 00 ed 1e 0c 00 00 00 00 00 .s..............
d1 64 00 00 2d 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-15T20:22:59.000000000Z" />
<EventRecordID>854063</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 5)...
488192 file records processed.
File verification completed.
1087 large file records processed.
0 bad file records processed.
0 EA records processed.
45 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 5)...
633900 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 5)...
488192 file SDs/SIDs processed.
Cleaning up 48 unused index entries from index $SII of file 0x9.
Cleaning up 48 unused index entries from index $SDH of file 0x9.
Cleaning up 48 unused security descriptors.
Security descriptor verification completed.
72855 data files processed.
CHKDSK is verifying Usn Journal...
35558024 USN bytes processed.
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
488176 files processed.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
115019811 free clusters processed.
Free space verification is complete.
Windows has checked the file system and found no problems.
955629567 KB total disk space.
494672948 KB in 360512 files.
252768 KB in 72856 indexes.
0 KB in bad sectors.
624607 KB in use by the system.
65536 KB occupied by the log file.
460079244 KB available on disk.
4096 bytes in each allocation unit.
238907391 total allocation units on disk.
115019811 allocation units available on disk.
Internal Info:
00 73 07 00 dc 9c 06 00 ed 1e 0c 00 00 00 00 00 .s..............
d1 64 00 00 2d 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>
-
Should I do a system restore to get my printer back running? :thinking:
-
alright nothing in bad sectors that is good. looks like it cleaned up some unused security descriptors. What I'm wondering is if your ole32.dll is not registered
open up command prompt and type in regsvr32 ole32.dll
-
I did that in safe mode, and I got the error message in image below, I'm at my wits end! Just got the ole32.dll error...it is so bad, WORSE since doing all this Windows Repair stuff. I'm getting the error constantly which requires a bad shut down....HELP!
-
Should I reinstall that Windows update, KB3068708 since things are worse since I uninstalled it? If so, where do I get it? :omg: :thinking: :confused:
-
hmmm is it missing is the question can you open up c:\windows \system32\ and in the search box on the top right type in ole32.dll if you find it can you right click properties and go to details and can you tell me the file version thank you.
-
I'm definitely sure I've done that! I know I searched EVERYWHERE ON MY SYSTEM for that damn file, and couldn't find it, but I'll try again and let you know. I'm running the repairs AGAIN on that machine...(this is another machine) so I'll post what I find out when it's done....
-
Are you running a 32bit or 64 bit version of windows 7 home premium?
-
I'm running 64 bit on that machine. I found that damn file! Attached are images of its properties...
-
What I want you to do is copy the file ole32.dll and save it in a folder on your desktop labeled back up. now I uploaded a zip file I want you to extract the zip file and in that folder is a ole32.dll file that I just copied from the windows 7 x64 sp1 disk I need you to copy it and place it in "c:\windows\system32\" now after that I need you to open command prompt with admin privileges and type in
regsvr32 ole32.dll
reboot and and lets see if this fixed it.
-
OK, I am not able to paste that file into my System32 folder because it says I'll need to provide administer permission to copy to this folder. I have been trying to change the permissions in the System32 folder, but I am stuck...can you tell me how to do it?
-
hmmm did it give you a box to hit continue?
-
Yes. The continue box has an administrator shield on it. When I click on it it says: You need permission to perform this action. I have been in the Security tab of this folder and trying to change permissions, but still get this message!
-
http://www.tweaking.com/articles/pages/add_quottake_ownershipquot_to_right_click_menu_in_vista_amp_7,1.html
download the regfile right click and hit merge right click on system32 folder and take ownership the try copying the file again.
-
If you are unable to take ownership of the file, you may be able to merge it after you have activated the hidden Admin account.
Run a command prompt as an admin and enter net user administrator /active:yes
exit (to close the cmd window)
Then reboot to effect where you will see the Admin icon on the desktop.
It will rearrange the desktop but it should give you cart blanche to do what you want.
When done, repeat the command with active:no as it shouldn't be left enabled for security reasons.
-
I was able to "take ownership" of the system32 folder. It went though a series of command prompt stuff and then completed. However, I am still getting the message...I will try will try the command prompt thing.
-
If you are unable to take ownership of the file, you may be able to merge it after you have activated the hidden Admin account.
Run a command prompt as an admin and enter net user administrator /active:yes
exit (to close the cmd window)
Then reboot to effect where you will see the Admin icon on the desktop.
It will rearrange the desktop but it should give you cart blanche to do what you want.
When done, repeat the command with active:no as it shouldn't be left enabled for security reasons.
Yes this step is even Better I forgot about that thanks boggin! :sleep: Need to sleep got work in 6 hrs I'll be back on after
-
OK, I did all that..rebooted, logged in as administrator instead of me...redownloaded the file, copied the old file into a back up folder, copied the new file, BUT IT STILL WON'T LET ME PASTE IT INTO THE SYSTEM32 FOLDER!! I am logged on as the administrator! Now what?
-
OK, I'm stuck...no printer and can't replace that ole32.dll file!!!!PLEASE PLEASE HELP!!!!!
-
Maybe if I had the correct syntax for the dos command, I could do the copy paste through the command prompt run as administrator?
-
Maybe if I had the correct syntax for the dos command, I could do the copy paste through the command prompt run as administrator?
That's going back a bit :thinking:
I think it would be something like copy [path]\file c:\Windows\System32 but haven't a clue what the path would be for where the .dll is.
Have you tried the drag & drop onto System32 ?
-
No, but I will...
-
OK, so I tried that and did drag it into the System32 folder. It said it was moving it. So then it disappeared from the original place I unzipped it, but there is still only one copy of the file in the folder. It didn't ask me about replacing it or anything. So how do I know if it worked? Both the old file (which I saved a copy in another place) and the new one have the same modified information.... :thinking: :confused:
-
So, does it show up in System32 ?
You could create a restore point then delete it in System32 and then drag it back in again so that you know what is in there is a fresh copy and then run the regsvr32 ole.dll to see what that reports.
If it's worked then so should your printer.
-
My printer is still not working...
-
Is Event Viewer reporting anything related - and do your restore points go back to before running WR ?
-
I don't know about the event viewer, it's saying a bunch of stuff including errors about Bonjour Service that go way back so I quit...The printer works on Bonjour Printing Services, but there is a bonjour also included in itunes. I do have restore points that go back before WR. I posted a question as to whether I should do a restore but got no advice on that one. I'm still nervous about that deleting ole32.dll thing...
-
I can't find in the thread what you did with Bonjour before, but I would expect there to be only one in services.msc - you type that after clicking on the Start button and press enter.
iTunes have been known to create a myriad of problems, but not sure if uninstalling that would also take out Bonjour in which case you may have to reinstall the printer.
One thing you could try is to go to the printer support site and download the drivers for it which could include the ole.dll.
When you dragged the .dll onto System32 I would have thought that you should have gotten the file already exists etc. so not sure why you didn't.
-
OK...First, I uninstalled printer (several times) uninstalled Bonjour printing services, unplugged printer, then plugged the printer back in, reinstalled Bonjour Printing Services and reinstalled the printer as I have been doing for several years...no good. So then I did a restore from a point created a week ago when I knew my printer was still working. See the attached picture ...So now I can not even do that! I may try a restore point that was supposed created by WR right before I did the first repair. So I think it's a good thing I didn't delete that ole32.dll file yet as I may not have been able to do a restore...
This "missing file" may have to do with that Windows update that I deleted. I would like to try reinstalling that again if that might work... As far as if the new ole32.dll file is a fresh one, I will know if the crashes stop; although, sometimes I don't have them for a few weeks and then I may get them alot like I have the last couple of days since I started the WR program.
I wish there was something more I knew what to do.. :thinking: :teeth: :cry: :sad:
-
So WHAT DOES THIS MEAN???? I did not do a restore yesterday????
-
I have downloaded the update KB3068708 from Microsoft. This is the one I deleted and may have caused my printer problems. Should I run it. Deleting it did not correct the system file check errors that are still being described. I will wait to hear from someone who knows if this is something I should do, because I am at my wit's end!!!
-
did you type in regsvr32 ole32.dll
-
The failed restore point is saying it like it is in that your AV program is the probable cause of it failing.
To get round that, boot up into Safe Mode and try whichever point you thought when the printer was working.
The best way to look for relevant errors in Event Viewer is to look for those with a date and time stamp of the most recent problem.
Edit - You should be okay to reinstall the KB.
-
Yes, I just ran the register thing for the ole32.dll and it was successful! I hope this is a good sign!
-
OK, I will try to restore in safe mode...and then see if not maybe reinstall the Windows Update? Thank you..
-
ran restore in safe mode...same thing wouldn't do it... :teeth: :cry: :confused:
WHATEVER!!!!
Printer still won't work..
-
when you restore in safe mode it changes the file back to the last restore point lol
you need to make sure to have the file in the system32 folder then re run regsvr32 ole32.dll
and when its successful reboot and try the printer :wink:
-
If the restore is still failing in Safe Mode then boot back up into the advanced boot options and select Repair your Computer and navigate to the Recovery Environment where you can select the Restore point options - see if that is successful.
You can still choose your restore points by clicking on Show more restore points, but if the one you have been trying had continued to fail, then choose an earlier one.
-
What are these updates, and would they help me?
-
My eyes can't make those out - it's better to save pics with the .png extender, but if you click on each update and then on More info, it will tell you what they are for - or you could list the KBs with the name of them except where they are listed as Security and then with a Google we can find the details of each.
How did you get on trying the restore points from the Recovery Environment ?
-
Didn't try that yet...I'm gonna reinstall that update I uninstalled first.. Will let you know
-
That update is just one of MS's spies to see which machines are Win 10 compatible, so I can't see what effect that would have on your printer.
-
You are probably right, but something happened to my machine from that or the WR that disabled Bonjour Printing services ability to get it to print. Even if the uninstall did cause it, I'm not hopeful that the reinstall will fix it, but I need to try, I'm in my truck now, so it will be a little later. I'll let you know what happens.....
-
Don't forget to let us know what those updates are and then try the restore points as I've suggested.
I'll be shoving off shortly to do my evening meal but will be back later.
-
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!! :smiley: :cheesy:
-
Woooowhoooo! :cheesy: 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.
-
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.... :teeth: :cry: :confused: :sad:
-
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.... :teeth: :cry: :confused: :sad:
no worries still here let's see.
-
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
-
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.
-
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
-
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.
-
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.
-
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.
-
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!
-
Can you please send me the link to the adware cleaner program if you think that is my problem? Thank you!
-
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
-
Hmmm just read the event log pics that is interesting. Give me a bit ill be back in a awhile.
-
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.
-
Thank you I will check on all those things a little later because I am not at the machine right now .
-
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!
-
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.
-
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... :confused:
-
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.
-
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..... :omg: :teeth: :cry: :confused:
-
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? :teeth:
-
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? :teeth:
on the start menu type in services
then look for windows search right click properties change to automatic
-
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.
-
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.
-
I just wanted to let you know that I did download and install the hotfix and I don't know if it has helped...the description says it should help with "known issues of ole32.dll problems" so I am crossing my fingers. I was able to get my rusty, drusty, old hp 1200 laserjet working the way I wanted by manually installing it using my Apple router's IP address as the printer port...I guess that is what the Bonjour Printing Services were suppose to do, but somehow couldn't do anymore. Anyway, it's working so I am happy. Thank you for helping me...I will probably be back with more problems...I wish I could offer help to you as well, but I am limited in my IT knowledge but I have alot of experience with these machines.... :smiley:
-
So I got everything "fixed" I thought this am with the hotfix and printer thing, and I haven't been on the machine all day...doing other things. So I was just in email and got "the blue screen"! I signed up for the dump file report thing, so how do I get to that, and should I restore to before the hotfix? I just can't seem to get back to "normal"! :teeth:
-
hI, sALLY
Like your poetic way of writing. But everything fixed would mean both fix and machine fixed. What do you really meant by blue screen in email.
Please, either i do not know how to correctly gauge or not
What is your problem, after all the fixes, were they fixed or the computer is now BSOD
-
What I meant was that I installed the hot fix patch that you recommended with no obvious events or issues, so I was hoping that it would fix that persistent ole32.dll problem I have or had. Then I figured out how to get my printer up and running like before, so I was hoping that I would not have any more problems with those issues again. But last night at 9:00 I was in gmail answering an email when my monitors suddenly went black followed by the dreaded blue screen. Then it rebooted..asked if I wanted to go to safe mode..but I was sitting there in shock and before I could go into safe mode, it booted up regularly. I noticed something about "memory dump" on the blue screen, and I know that should tell something about what happened.
I think I may have gotten the blue screen maybe only one time before that in the 2+ years I've had this computer, so I DEFINITELY still have problems! So what should I do now? I need to get to that memory dump report I'm sure. Also, should I restore to before I installed the hot Fix?
-
PS what is BSOD.
-
PS what is BSOD.
Blue Screen Of Death
-
Yes, that' sweat I had!
-
When you run Blue Screen View it will open up with an analysis of any Dump files it finds, but Event Viewer may also be able to help with this providing it doesn't just give the ambiguous Event ID 41.
If it had been the Hotfix, I think problems would have been evident before the BSOD.
I think I've had only two or three on start up although not in running in the 4 years I've been using a laptop, but it's usually driver related and BSV should have something if Dump files are enabled on your computer.
-
OK, I don't know what I'm doing here but I have opened the Blue Screen View and here is what is in the lower pane:
ACPI.sys fffff880`00f5e000 fffff880`00fb5000 0x00057000 0x4ce79294 11/20/2010 5:19:16 AM
afd.sys fffff880`020fe000 fffff880`02187000 0x00089000 0x5388291c 5/30/2014 2:45:48 AM
AgileVpn.sys fffff880`05bb1000 fffff880`05bc7000 0x00016000 0x4a5bccf0 7/13/2009 8:10:24 PM
amdxata.sys fffff880`017a0000 fffff880`017ab000 0x0000b000 0x4ba3a3ca 3/19/2010 12:18:18 PM
aswHwid.sys fffff880`084b3000 fffff880`084bd000 0x0000a000 0x55364a20 4/21/2015 9:01:20 AM
aswKbd.sys fffff880`04ba1000 fffff880`04bab000 0x0000a000 0x55364a33 4/21/2015 9:01:39 AM
aswMonFlt.sys fffff880`077b5000 fffff880`077d9000 0x00024000 0x55364a04 4/21/2015 9:00:52 AM
aswNdisFlt.sys fffff880`01d19000 fffff880`01d89000 0x00070000 0x55364aa9 4/21/2015 9:03:37 AM
aswRdr2.sys fffff880`0497a000 fffff880`04994000 0x0001a000 0x55364a2b 4/21/2015 9:01:31 AM
aswRvrt.sys fffff880`020d3000 fffff880`020e6000 0x00013000 0x55364a0b 4/21/2015 9:00:59 AM
aswSnx.sys fffff880`04a1a000 fffff880`04b1e000 0x00104000 0x55364a30 4/21/2015 9:01:36 AM
aswSP.sys fffff880`04b1e000 fffff880`04b91000 0x00073000 0x55364d99 4/21/2015 9:16:09 AM
aswStm.sys fffff880`077d9000 fffff880`077fd000 0x00024000 0x55364e39 4/21/2015 9:18:49 AM
aswVmm.sys fffff880`0208e000 fffff880`020d3000 0x00045000 0x55364d7c 4/21/2015 9:15:40 AM
AtihdW76.sys fffff880`069ae000 fffff880`069c9000 0x0001b000 0x4f463154 2/23/2012 8:30:12 AM
atikmdag.sys fffff880`05e0f000 fffff880`06909000 0x00afa000 0x4f81646a 4/8/2012 6:11:54 AM
atikmpag.sys atikmpag.sys+8728 fffff880`054c9000 fffff880`05521000 0x00058000 0x4f815afb 4/8/2012 5:31:39 AM
Beep.SYS fffff880`04b9a000 fffff880`04ba1000 0x00007000 0x4a5bca8d 7/13/2009 8:00:13 PM
blbdrive.sys fffff880`021dc000 fffff880`021ed000 0x00011000 0x4a5bc4df 7/13/2009 7:35:59 PM
bowser.sys fffff880`08000000 fffff880`0801e000 0x0001e000 0x4d649328 2/23/2011 12:55:04 AM
cdd.dll fffff960`00670000 fffff960`00697000 0x00027000 0x00000000
cdrom.sys fffff880`048fe000 fffff880`04928000 0x0002a000 0x4ce79298 11/20/2010 5:19:20 AM
CI.dll fffff880`00d5a000 fffff880`00dcf000 0x00075000 0x53acd125 6/26/2014 10:04:21 PM
CLASSPNP.SYS fffff880`01437000 fffff880`01467000 0x00030000 0x4ce7929b 11/20/2010 5:19:23 AM
CLFS.SYS fffff880`00cfc000 fffff880`00d5a000 0x0005e000 0x54f67a28 3/3/2015 11:21:12 PM
cng.sys fffff880`01b6b000 fffff880`01bdd000 0x00072000 0x54caf7b4 1/29/2015 11:17:08 PM
CompositeBus.sys fffff880`05b50000 fffff880`05b60000 0x00010000 0x4ce7a3ed 11/20/2010 6:33:17 AM
crashdmp.sys fffff880`0774d000 fffff880`0775b000 0x0000e000 0x4a5bcabd 7/13/2009 8:01:01 PM
dfsc.sys fffff880`0206c000 fffff880`0208a000 0x0001e000 0x4ce79447 11/20/2010 5:26:31 AM
discache.sys fffff880`0205d000 fffff880`0206c000 0x0000f000 0x4a5bc52e 7/13/2009 7:37:18 PM
disk.sys fffff880`01421000 fffff880`01437000 0x00016000 0x4a5bc11d 7/13/2009 7:19:57 PM
drmk.sys fffff880`069c9000 fffff880`069eb000 0x00022000 0x524e24fe 10/3/2013 10:16:30 PM
dump_diskdump.sys fffff880`0775b000 fffff880`07765000 0x0000a000 0x52f04419 2/3/2014 9:36:25 PM
dump_dumpfve.sys fffff880`07765000 fffff880`07778000 0x00013000 0x4a5bc18f 7/13/2009 7:21:51 PM
dump_iaStorA.sys fffff880`0461a000 fffff880`048eb000 0x002d1000 0x5175919d 4/22/2013 3:38:05 PM
Dxapi.sys fffff880`07778000 fffff880`07784000 0x0000c000 0x4a5bc574 7/13/2009 7:38:28 PM
dxgkrnl.sys dxgkrnl.sys+5d134 fffff880`056a9000 fffff880`0579e000 0x000f5000 0x539e411c 6/15/2014 8:58:04 PM
dxgmms1.sys dxgmms1.sys+ff13 fffff880`0579e000 fffff880`057e4000 0x00046000 0x5164dc13 4/9/2013 11:27:15 PM
fastfat.SYS fffff880`06909000 fffff880`0693f000 0x00036000 0x4a5bc1f0 7/13/2009 7:23:28 PM
fileinfo.sys fffff880`01400000 fffff880`01414000 0x00014000 0x4a5bc481 7/13/2009 7:34:25 PM
fltmgr.sys fffff880`017ab000 fffff880`017f7000 0x0004c000 0x4ce7929c 11/20/2010 5:19:24 AM
Fs_Rec.sys fffff880`01bee000 fffff880`01bf8000 0x0000a000 0x4f4eefd2 2/29/2012 11:41:06 PM
fvevol.sys fffff880`01800000 fffff880`0183a000 0x0003a000 0x5100a65c 1/23/2013 11:11:24 PM
fwpkclnt.sys fffff880`01cd0000 fffff880`01d19000 0x00049000 0x533f5b09 4/4/2014 9:23:21 PM
GEARAspiWDM.sys fffff880`05b33000 fffff880`05b39c00 0x00006c00 0x4fa2e2e1 5/3/2012 3:56:17 PM
hal.dll fffff800`033f9000 fffff800`03442000 0x00049000 0x4ce7c669 11/20/2010 9:00:25 AM
HDAudBus.sys fffff880`05600000 fffff880`05624000 0x00024000 0x4ce7a65e 11/20/2010 6:43:42 AM
HECIx64.sys fffff880`05626000 fffff880`05637000 0x00011000 0x4ebb2049 11/9/2011 8:52:25 PM
HIDCLASS.SYS fffff880`07710000 fffff880`07729000 0x00019000 0x51d3a2f1 7/3/2013 12:05:05 AM
HIDPARSE.SYS fffff880`07729000 fffff880`07731080 0x00008080 0x51d3a2f0 7/3/2013 12:05:04 AM
hidusb.sys fffff880`07702000 fffff880`07710000 0x0000e000 0x4ce7a665 11/20/2010 6:43:49 AM
HTTP.sys fffff880`08136000 fffff880`081ff000 0x000c9000 0x54ed3ee3 2/24/2015 11:17:55 PM
hwpolicy.sys fffff880`01c3a000 fffff880`01c43000 0x00009000 0x4ce7927e 11/20/2010 5:18:54 AM
iaStor.sys fffff880`0101c000 fffff880`013c0000 0x003a4000 0x4ed5a567 11/29/2011 11:39:19 PM
iaStorA.sys fffff880`0146b000 fffff880`0173c000 0x002d1000 0x5175919d 4/22/2013 3:38:05 PM
iaStorF.sys fffff880`01def000 fffff880`01dfa000 0x0000b000 0x5175919f 4/22/2013 3:38:07 PM
intelppm.sys fffff880`05b3a000 fffff880`05b50000 0x00016000 0x4a5bc0fd 7/13/2009 7:19:25 PM
iusb3hcs.sys fffff880`00e0d000 fffff880`00e17000 0x0000a000 0x507d8278 10/16/2012 11:51:20 AM
iusb3hub.sys fffff880`05400000 fffff880`0545d000 0x0005d000 0x507d8202 10/16/2012 11:49:22 AM
iusb3xhc.sys fffff880`05521000 fffff880`055e6000 0x000c5000 0x507d8206 10/16/2012 11:49:26 AM
kbdclass.sys fffff880`05885000 fffff880`05894000 0x0000f000 0x4a5bc116 7/13/2009 7:19:50 PM
kbdhid.sys fffff880`07732000 fffff880`07740000 0x0000e000 0x4ce7a3f5 11/20/2010 6:33:25 AM
kdcom.dll fffff800`03800000 fffff800`0380a000 0x0000a000 0x4d4d8061 2/5/2011 12:52:49 PM
ks.sys fffff880`05b6e000 fffff880`05bb1000 0x00043000 0x4ce7a3f3 11/20/2010 6:33:23 AM
ksecdd.sys fffff880`01b50000 fffff880`01b6b000 0x0001b000 0x556353ea 5/25/2015 12:55:06 PM
ksecpkg.sys fffff880`01ca4000 fffff880`01cd0000 0x0002c000 0x55635838 5/25/2015 1:13:28 PM
ksthunk.sys fffff880`05b68000 fffff880`05b6d200 0x00005200 0x4a5bca93 7/13/2009 8:00:19 PM
L1C62x64.sys fffff880`05b17000 fffff880`05b33000 0x0001c000 0x4e76f253 9/19/2011 3:42:11 AM
lltdio.sys fffff880`07600000 fffff880`07615000 0x00015000 0x4a5bcc92 7/13/2009 8:08:50 PM
luafv.sys fffff880`07792000 fffff880`077b5000 0x00023000 0x4a5bc295 7/13/2009 7:26:13 PM
mcupdate_GenuineIntel.dll fffff880`00c99000 fffff880`00ce8000 0x0004f000 0x4ce7c737 11/20/2010 9:03:51 AM
monitor.sys fffff880`07784000 fffff880`07792000 0x0000e000 0x4a5bc58c 7/13/2009 7:38:52 PM
mouclass.sys fffff880`05894000 fffff880`058a3000 0x0000f000 0x4a5bc116 7/13/2009 7:19:50 PM
mouhid.sys fffff880`07740000 fffff880`0774d000 0x0000d000 0x4a5bca94 7/13/2009 8:00:20 PM
mountmgr.sys fffff880`00e41000 fffff880`00e5b000 0x0001a000 0x54d02f0b 2/2/2015 10:14:35 PM
mpsdrv.sys fffff880`0801e000 fffff880`08036000 0x00018000 0x4a5bcc79 7/13/2009 8:08:25 PM
mrxsmb.sys fffff880`08036000 fffff880`08063000 0x0002d000 0x4db78226 4/26/2011 10:40:38 PM
mrxsmb10.sys fffff880`08441000 fffff880`0848f000 0x0004e000 0x4e17c104 7/8/2011 10:46:28 PM
mrxsmb20.sys fffff880`0848f000 fffff880`084b3000 0x00024000 0x4db781e9 4/26/2011 10:39:37 PM
Msfs.SYS fffff880`04a09000 fffff880`04a14000 0x0000b000 0x4a5bc113 7/13/2009 7:19:47 PM
msisadrv.sys fffff880`00fbe000 fffff880`00fc8000 0x0000a000 0x4a5bc0fe 7/13/2009 7:19:26 PM
msrpc.sys fffff880`01af2000 fffff880`01b50000 0x0005e000 0x4ce79334 11/20/2010 5:21:56 AM
mssmbios.sys fffff880`0460f000 fffff880`0461a000 0x0000b000 0x4a5bc3be 7/13/2009 7:31:10 PM
mup.sys fffff880`01ddd000 fffff880`01def000 0x00012000 0x4a5bc201 7/13/2009 7:23:45 PM
ndis.sys fffff880`01a00000 fffff880`01af2000 0x000f2000 0x5034f6b2 8/22/2012 11:11:46 AM
ndistapi.sys fffff880`05beb000 fffff880`05bf7000 0x0000c000 0x4a5bccd8 7/13/2009 8:10:00 PM
ndisuio.sys fffff880`08101000 fffff880`08114000 0x00013000 0x4ce7a7e0 11/20/2010 6:50:08 AM
ndiswan.sys fffff880`05800000 fffff880`0582f000 0x0002f000 0x4ce7a870 11/20/2010 6:52:32 AM
NDProxy.SYS fffff880`06999000 fffff880`069ae000 0x00015000 0x4ce7a864 11/20/2010 6:52:20 AM
netbios.sys fffff880`04600000 fffff880`0460f000 0x0000f000 0x4a5bccb6 7/13/2009 8:09:26 PM
netbt.sys fffff880`04994000 fffff880`049d9000 0x00045000 0x4ce79386 11/20/2010 5:23:18 AM
NETIO.SYS fffff880`01c44000 fffff880`01ca4000 0x00060000 0x5294760d 11/26/2013 6:21:01 AM
netr28x.sys fffff880`058a5000 fffff880`05b0a000 0x00265000 0x54a362f9 12/30/2014 10:44:09 PM
Npfs.SYS fffff880`04928000 fffff880`04939000 0x00011000 0x4a5bc114 7/13/2009 7:19:48 PM
nsiproxy.sys fffff880`02051000 fffff880`0205d000 0x0000c000 0x4a5bc15e 7/13/2009 7:21:02 PM
Ntfs.sys fffff880`01845000 fffff880`019ee000 0x001a9000 0x52e1be8a 1/23/2014 9:14:50 PM
ntoskrnl.exe fffff800`02e0d000 fffff800`033f9000 0x005ec000 0x556356e8 5/25/2015 1:07:52 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.18869 (win7sp1_gdr.150525-0603) Microsoft Corporation C:\windows\system32\ntoskrnl.exe
Null.SYS fffff880`04b91000 fffff880`04b9a000 0x00009000 0x4a5bc109 7/13/2009 7:19:37 PM
nwifi.sys fffff880`080ae000 fffff880`08101000 0x00053000 0x4a5bcc3b 7/13/2009 8:07:23 PM
pacer.sys fffff880`02187000 fffff880`021ad000 0x00026000 0x4ce7a862 11/20/2010 6:52:18 AM
partmgr.sys fffff880`00e17000 fffff880`00e2c000 0x00015000 0x4f641bc1 3/17/2012 1:06:09 AM
pci.sys fffff880`00fc8000 fffff880`00ffb000 0x00033000 0x4ce7928f 11/20/2010 5:19:11 AM
pcw.sys fffff880`01bdd000 fffff880`01bee000 0x00011000 0x4a5bc0ff 7/13/2009 7:19:27 PM
peauth.sys fffff880`084bd000 fffff880`08567000 0x000aa000 0x54d03e30 2/2/2015 11:19:12 PM
portcls.sys fffff880`0545d000 fffff880`0549a000 0x0003d000 0x524e1b82 10/3/2013 9:36:02 PM
PSHED.dll fffff880`00ce8000 fffff880`00cfc000 0x00014000 0x4a5be027 7/13/2009 9:32:23 PM Microsoft® Windows® Operating System Platform Specific Hardware Error Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\windows\system32\PSHED.dll
PxHlpa64.sys fffff880`01414000 fffff880`01420040 0x0000c040 0x4addfcaa 10/20/2009 2:08:42 PM
qknfd.sys fffff880`04968000 fffff880`0497a000 0x00012000 0x50340d10 8/21/2012 6:34:56 PM
rasl2tp.sys fffff880`05bc7000 fffff880`05beb000 0x00024000 0x4ce7a872 11/20/2010 6:52:34 AM
raspppoe.sys fffff880`0582f000 fffff880`0584a000 0x0001b000 0x4a5bcce9 7/13/2009 8:10:17 PM
raspptp.sys fffff880`0584a000 fffff880`0586b000 0x00021000 0x4ce7a86f 11/20/2010 6:52:31 AM
rassstp.sys fffff880`0586b000 fffff880`05885000 0x0001a000 0x4a5bccf1 7/13/2009 8:10:25 PM
rdbss.sys fffff880`02000000 fffff880`02051000 0x00051000 0x4ce79497 11/20/2010 5:27:51 AM
RDPCDD.sys fffff880`04bee000 fffff880`04bf7000 0x00009000 0x4a5bce62 7/13/2009 8:16:34 PM
rdpencdd.sys fffff880`04bf7000 fffff880`04c00000 0x00009000 0x4a5bce62 7/13/2009 8:16:34 PM
rdprefmp.sys fffff880`04a00000 fffff880`04a09000 0x00009000 0x4a5bce63 7/13/2009 8:16:35 PM
rdyboost.sys fffff880`01c00000 fffff880`01c3a000 0x0003a000 0x4ce7982e 11/20/2010 5:43:10 AM
rspndr.sys fffff880`08114000 fffff880`0812c000 0x00018000 0x4a5bcc92 7/13/2009 8:08:50 PM
secdrv.SYS fffff880`08567000 fffff880`08572000 0x0000b000 0x4508052e 9/13/2006 9:18:38 AM
serscan.sys fffff880`05b60000 fffff880`05b68000 0x00008000 0x4a5bd2d4 7/13/2009 8:35:32 PM
spldr.sys fffff880`01dd5000 fffff880`01ddd000 0x00008000 0x4a0858bb 5/11/2009 12:56:27 PM
srv.sys fffff880`0968a000 fffff880`09722000 0x00098000 0x4dba2b1e 4/28/2011 11:06:06 PM
srv2.sys fffff880`09621000 fffff880`0968a000 0x00069000 0x4dba2b0a 4/28/2011 11:05:46 PM
srvnet.sys fffff880`08572000 fffff880`085a3000 0x00031000 0x4dba2aff 4/28/2011 11:05:35 PM
storport.sys fffff880`0173c000 fffff880`017a0000 0x00064000 0x52f04432 2/3/2014 9:36:50 PM
stwrt64.sys fffff880`07642000 fffff880`076ca000 0x00088000 0x4f6d481a 3/24/2012 12:05:46 AM
swenum.sys fffff880`058a3000 fffff880`058a4480 0x00001480 0x4a5bca92 7/13/2009 8:00:18 PM
tcpip.sys fffff880`01e00000 fffff880`01fff000 0x001ff000 0x533f5bd4 4/4/2014 9:26:44 PM
tcpipreg.sys fffff880`085a3000 fffff880`085b5000 0x00012000 0x506c62be 10/3/2012 12:07:26 PM
TDI.SYS fffff880`0495b000 fffff880`04968000 0x0000d000 0x4ce7933e 11/20/2010 5:22:06 AM
tdx.sys fffff880`04939000 fffff880`0495b000 0x00022000 0x54616a72 11/10/2014 9:46:26 PM
termdd.sys fffff880`021c8000 fffff880`021dc000 0x00014000 0x4ce7ab0c 11/20/2010 7:03:40 AM
TSDDD.dll fffff960`00580000 fffff960`0058a000 0x0000a000 0x00000000
tunnel.sys fffff880`013c0000 fffff880`013e6000 0x00026000 0x4ce7a846 11/20/2010 6:51:50 AM
umbus.sys fffff880`057e4000 fffff880`057f6000 0x00012000 0x4ce7a695 11/20/2010 6:44:37 AM
usbccgp.sys fffff880`076e5000 fffff880`07702000 0x0001d000 0x52954dbb 11/26/2013 9:41:15 PM
USBD.SYS fffff880`05624000 fffff880`05625e80 0x00001e80 0x52954daf 11/26/2013 9:41:03 PM
usbehci.sys fffff880`05637000 fffff880`05649000 0x00012000 0x52954db7 11/26/2013 9:41:11 PM
usbhub.sys fffff880`0693f000 fffff880`06999000 0x0005a000 0x52954dd0 11/26/2013 9:41:36 PM
USBPORT.SYS fffff880`05649000 fffff880`0569f000 0x00056000 0x52954db7 11/26/2013 9:41:11 PM
USBSTOR.SYS fffff880`076ca000 fffff880`076e5000 0x0001b000 0x4d79a6fc 3/11/2011 12:37:16 AM
vdrvroot.sys fffff880`00e00000 fffff880`00e0d000 0x0000d000 0x4a5bcadb 7/13/2009 8:01:31 PM
vga.sys fffff880`04bab000 fffff880`04bb9000 0x0000e000 0x4a5bc587 7/13/2009 7:38:47 PM
VIDEOPRT.SYS fffff880`04bb9000 fffff880`04bde000 0x00025000 0x4a5bc58b 7/13/2009 7:38:51 PM
volmgr.sys fffff880`00e2c000 fffff880`00e41000 0x00015000 0x4ce792a0 11/20/2010 5:19:28 AM
volmgrx.sys fffff880`00c00000 fffff880`00c5c000 0x0005c000 0x4ce792eb 11/20/2010 5:20:43 AM
volsnap.sys fffff880`01d89000 fffff880`01dd5000 0x0004c000 0x4d67242a 2/24/2011 11:38:18 PM
vwifibus.sys fffff880`05b0a000 fffff880`05b17000 0x0000d000 0x4a5bcc39 7/13/2009 8:07:21 PM
vwififlt.sys fffff880`049e2000 fffff880`049f8000 0x00016000 0x4a5bcc3a 7/13/2009 8:07:22 PM
vwifimp.sys fffff880`0812c000 fffff880`08136000 0x0000a000 0x4a5bcc40 7/13/2009 8:07:28 PM
wanarp.sys fffff880`021ad000 fffff880`021c8000 0x0001b000 0x4ce7a874 11/20/2010 6:52:36 AM
watchdog.sys fffff880`04bde000 fffff880`04bee000 0x00010000 0x4a5bc53f 7/13/2009 7:37:35 PM
Wdf01000.sys fffff880`00e8c000 fffff880`00f4e000 0x000c2000 0x51c51641 6/21/2013 11:13:05 PM
WDFLDR.SYS fffff880`00f4e000 fffff880`00f5e000 0x00010000 0x5010ab70 7/25/2012 10:29:04 PM
wfplwf.sys fffff880`049d9000 fffff880`049e2000 0x00009000 0x4a5bccb6 7/13/2009 8:09:26 PM
win32k.sys fffff960`00090000 fffff960`003b3000 0x00323000 0x00000000
WMILIB.SYS fffff880`00fb5000 fffff880`00fbe000 0x00009000 0x4a5bc117 7/13/2009 7:19:51 PM
WudfPf.sys fffff880`097c9000 fffff880`097e2000 0x00019000 0x5010aae5 7/25/2012 10:26:45 PM
WUDFRd.sys fffff880`09793000 fffff880`097c9000 0x00036000 0x5010aabe 7/25/2012 10:26:06 PM
Attached is the Properties box with details.
This is what is in the upper pane:
061915-131742-01.dmp 6/19/2015 8:59:44 PM 0x00000116 fffffa80`123e44e0 fffff880`054d1728 00000000`00000000 00000000`0000000d dxgkrnl.sys dxgkrnl.sys+5d134 x64 ntoskrnl.exe+748c0 C:\windows\Minidump\061915-131742-01.dmp 8 15 7601 305,568 6/19/2015 9:03:29 PM
I have NO IDEA WHAT IT MEANS! Can you help and or advise? Thank you!
-
PS Where in the Event Viewer do I find the correct log that gives me information about the BSOD? I have looked in Applications and System....
-
I think that BSOD usually relates to Display drivers and may just have been a glitch, although Shane is usually more conversant with the BSOD errors, but I would have expected BSV to have given a Bug Check String which can give more info.
When you first open Event Viewer and after it has read the logs, you will be presented with Critical, Error etc. and for the last hour, last week etc.
The BSOD would probably have triggered a Critical for when you got the BSOD - these are normally just Event ID 41 but you can check by clicking on Critical and then on Show All Instances of This Event in the lower right pane.
Clicking on any in the upper pane will produce more details in the lower pane.
You can also do this when you click on Error and you are looking for Critical or Error with a time stamp for when the BSOD occurred.
Sometimes MS has more info and possible solutions when you click on the blue online help link, but sometimes you have to enter the details yourself in the brown box and do your own search of the links that produces.
You can use your restore points prior to installing the Hotfix to check if you start getting the ole32.dll errors again, but if you don't get anymore BSODs before restoring, then I would say the BSOD was just a driver glitch - subject to what Shane has to say, but he won't be back until Monday.
If you want to post any of the errors Event Viewer has recorded, click on whichever you want to post then click on Copy/Copy details as text in the lower right pane, right click in the reply box and select Paste.
-
Thank you! I will do that but right now I'm about 80% finished with the long five-step check disk, I did the pre-skan check disk and it said there were errors so then I did the F check disk and there were still errors so now I'm doing the long r one and I hope it will fix all the problems. I will post the results of that long when it's finished and maybe you can help me interpret it. I will not do a restore unless I get another blue screen and maybe Shane would be kind enough to look at all my information on Monday. But if I do get another one I will probably do the restore if it happens before then because I never get them on this machine. I feel bad obviously something has done something to the machine throughout this process of uninstalling the windows update doing the windows repair and downloading the hot fix. But I feel bad obviously something has done something to the machine throughout this process of uninstalling the windows update doing the windows repair and downloading the hot fix but since I can't restore to be for any of that I guess I'll never know, thank you for your help and I will keep you posted!
-
Here is my long check disk log:
Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 6/20/2015 2:14:27 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 5)...
488192 file records processed.
File verification completed.
2206 large file records processed.
0 bad file records processed.
0 EA records processed.
61 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 5)...
647374 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 5)...
488192 file SDs/SIDs processed.
Cleaning up 2 unused index entries from index $SII of file 0x9.
Cleaning up 2 unused index entries from index $SDH of file 0x9.
Cleaning up 2 unused security descriptors.
Security descriptor verification completed.
79592 data files processed.
CHKDSK is verifying Usn Journal...
35311896 USN bytes processed.
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
488176 files processed.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
112469475 free clusters processed.
Free space verification is complete.
Windows has checked the file system and found no problems.
955629567 KB total disk space.
504865784 KB in 375432 files.
266236 KB in 79593 indexes.
0 KB in bad sectors.
619647 KB in use by the system.
65536 KB occupied by the log file.
449877900 KB available on disk.
4096 bytes in each allocation unit.
238907391 total allocation units on disk.
112469475 allocation units available on disk.
Internal Info:
00 73 07 00 75 f1 06 00 a8 b9 0c 00 00 00 00 00 .s..u...........
1b 65 00 00 3d 00 00 00 00 00 00 00 00 00 00 00 .e..=...........
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-20T18:14:27.000000000Z" />
<EventRecordID>856329</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 5)...
488192 file records processed.
File verification completed.
2206 large file records processed.
0 bad file records processed.
0 EA records processed.
61 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 5)...
647374 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 5)...
488192 file SDs/SIDs processed.
Cleaning up 2 unused index entries from index $SII of file 0x9.
Cleaning up 2 unused index entries from index $SDH of file 0x9.
Cleaning up 2 unused security descriptors.
Security descriptor verification completed.
79592 data files processed.
CHKDSK is verifying Usn Journal...
35311896 USN bytes processed.
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
488176 files processed.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
112469475 free clusters processed.
Free space verification is complete.
Windows has checked the file system and found no problems.
955629567 KB total disk space.
504865784 KB in 375432 files.
266236 KB in 79593 indexes.
0 KB in bad sectors.
619647 KB in use by the system.
65536 KB occupied by the log file.
449877900 KB available on disk.
4096 bytes in each allocation unit.
238907391 total allocation units on disk.
112469475 allocation units available on disk.
Internal Info:
00 73 07 00 75 f1 06 00 a8 b9 0c 00 00 00 00 00 .s..u...........
1b 65 00 00 3d 00 00 00 00 00 00 00 00 00 00 00 .e..=...........
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>
Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 6/20/2015 2:14:27 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 5)...
488192 file records processed.
File verification completed.
2206 large file records processed.
0 bad file records processed.
0 EA records processed.
61 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 5)...
647374 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 5)...
488192 file SDs/SIDs processed.
Cleaning up 2 unused index entries from index $SII of file 0x9.
Cleaning up 2 unused index entries from index $SDH of file 0x9.
Cleaning up 2 unused security descriptors.
Security descriptor verification completed.
79592 data files processed.
CHKDSK is verifying Usn Journal...
35311896 USN bytes processed.
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
488176 files processed.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
112469475 free clusters processed.
Free space verification is complete.
Windows has checked the file system and found no problems.
955629567 KB total disk space.
504865784 KB in 375432 files.
266236 KB in 79593 indexes.
0 KB in bad sectors.
619647 KB in use by the system.
65536 KB occupied by the log file.
449877900 KB available on disk.
4096 bytes in each allocation unit.
238907391 total allocation units on disk.
112469475 allocation units available on disk.
Internal Info:
00 73 07 00 75 f1 06 00 a8 b9 0c 00 00 00 00 00 .s..u...........
1b 65 00 00 3d 00 00 00 00 00 00 00 00 00 00 00 .e..=...........
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-20T18:14:27.000000000Z" />
<EventRecordID>856329</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 5)...
488192 file records processed.
File verification completed.
2206 large file records processed.
0 bad file records processed.
0 EA records processed.
61 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 5)...
647374 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 5)...
488192 file SDs/SIDs processed.
Cleaning up 2 unused index entries from index $SII of file 0x9.
Cleaning up 2 unused index entries from index $SDH of file 0x9.
Cleaning up 2 unused security descriptors.
Security descriptor verification completed.
79592 data files processed.
CHKDSK is verifying Usn Journal...
35311896 USN bytes processed.
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
488176 files processed.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
112469475 free clusters processed.
Free space verification is complete.
Windows has checked the file system and found no problems.
955629567 KB total disk space.
504865784 KB in 375432 files.
266236 KB in 79593 indexes.
0 KB in bad sectors.
619647 KB in use by the system.
65536 KB occupied by the log file.
449877900 KB available on disk.
4096 bytes in each allocation unit.
238907391 total allocation units on disk.
112469475 allocation units available on disk.
Internal Info:
00 73 07 00 75 f1 06 00 a8 b9 0c 00 00 00 00 00 .s..u...........
1b 65 00 00 3d 00 00 00 00 00 00 00 00 00 00 00 .e..=...........
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>
My Event View is not showing any critical errors.
Here are the errors at the time of the Blue Screen:
Event ID 6008
Log Name: System
Source: EventLog
Date: 6/19/2015 9:03:09 PM
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Sally-HP
Description:
The previous system shutdown at 8:58:52 PM on 6/19/2015 was unexpected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6008</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-06-20T01:03:09.000000000Z" />
<EventRecordID>123181</EventRecordID>
<Channel>System</Channel>
<Computer>Sally-HP</Computer>
<Security />
</System>
<EventData>
<Data>8:58:52 PM</Data>
<Data>6/19/2015</Data>
<Data>
</Data>
<Data>
</Data>
<Data>37805</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>DF0706000500130014003A003400F300DF0706000600140000003A003400F300600900003C000000010000006009000000000000B0040000010000008A050000</Binary>
</EventData>
</Event>
Next one:
Log Name: Microsoft-Windows-Kernel-EventTracing/Admin
Source: Microsoft-Windows-Kernel-EventTracing
Date: 6/19/2015 9:03:07 PM
Event ID: 3
Task Category: Session
Level: Error
Keywords: Session
User: SYSTEM
Computer: Sally-HP
Description:
Session "UBPM" stopped due to the following error: 0xC0000022
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" />
<EventID>3</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>14</Opcode>
<Keywords>0x8000000000000010</Keywords>
<TimeCreated SystemTime="2015-06-20T01:03:07.368629900Z" />
<EventRecordID>119</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="844" />
<Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
<Computer>Sally-HP</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SessionName">UBPM</Data>
<Data Name="FileName">
</Data>
<Data Name="ErrorCode">3221225506</Data>
<Data Name="LoggingMode">268435840</Data>
</EventData>
</Event>
Next One:
Log Name: System
Source: Microsoft-Windows-Eventlog
Date: 6/19/2015 9:03:16 PM
Event ID: 22
Task Category: Service startup
Level: Error
Keywords: Service availability
User: LOCAL SERVICE
Computer: Sally-HP
Description:
The event logging service encountered an error while initializing publishing resources for channel Security. If channel type is Analytic or Debug, then this could mean there was an error initializing logging resources as well.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Eventlog" Guid="{FC65DDD8-D6EF-4962-83D5-6E5CFE9CE148}" />
<EventID>22</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000020000</Keywords>
<TimeCreated SystemTime="2015-06-20T01:03:16.483044900Z" />
<EventRecordID>123219</EventRecordID>
<Correlation />
<Execution ProcessID="448" ThreadID="512" />
<Channel>System</Channel>
<Computer>Sally-HP</Computer>
<Security UserID="S-1-5-19" />
</System>
<UserData>
<InitChannelPublishingFailure xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2004/08/windows/eventlog">
<Error Code="4201">
</Error>
<ChannelPath>Security</ChannelPath>
</InitChannelPublishingFailure>
</UserData>
</Event>
Next one- The bug Check:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 6/19/2015 9:03:29 PM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Sally-HP
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 (0xfffffa80123e44e0, 0xfffff880054d1728, 0x0000000000000000, 0x000000000000000d). A dump was saved in: C:\windows\MEMORY.DMP. Report Id: 061915-131742-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-06-20T01:03:29.000000000Z" />
<EventRecordID>123224</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>Sally-HP</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x00000116 (0xfffffa80123e44e0, 0xfffff880054d1728, 0x0000000000000000, 0x000000000000000d)</Data>
<Data Name="param2">C:\windows\MEMORY.DMP</Data>
<Data Name="param3">061915-131742-01</Data>
</EventData>
</Event>
The is Greek to me!
But here's more:
Log Name: System
Source: NETLOGON
Date: 6/19/2015 9:03:31 PM
Event ID: 3095
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Sally-HP
Description:
This computer is configured as a member of a workgroup, not as a member of a domain. The Netlogon service does not need to run in this configuration.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="NETLOGON" />
<EventID Qualifiers="0">3095</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-06-20T01:03:31.000000000Z" />
<EventRecordID>123227</EventRecordID>
<Channel>System</Channel>
<Computer>Sally-HP</Computer>
<Security />
</System>
<EventData>
</EventData>
</Event>
Next:
Log Name: System
Source: Microsoft-Windows-Eventlog
Date: 6/19/2015 9:03:35 PM
Event ID: 22
Task Category: Service startup
Level: Error
Keywords: Service availability
User: LOCAL SERVICE
Computer: Sally-HP
Description:
The event logging service encountered an error while initializing publishing resources for channel Security. If channel type is Analytic or Debug, then this could mean there was an error initializing logging resources as well.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Eventlog" Guid="{FC65DDD8-D6EF-4962-83D5-6E5CFE9CE148}" />
<EventID>22</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000020000</Keywords>
<TimeCreated SystemTime="2015-06-20T01:03:35.718078100Z" />
<EventRecordID>123232</EventRecordID>
<Correlation />
<Execution ProcessID="448" ThreadID="516" />
<Channel>System</Channel>
<Computer>Sally-HP</Computer>
<Security UserID="S-1-5-19" />
</System>
<UserData>
<InitChannelPublishingFailure xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2004/08/windows/eventlog">
<Error Code="4201">
</Error>
<ChannelPath>Security</ChannelPath>
</InitChannelPublishingFailure>
</UserData>
</Event>
Here's the next:
Log Name: System
Source: Microsoft-Windows-Eventlog
Date: 6/19/2015 9:03:35 PM
Event ID: 22
Task Category: Service startup
Level: Error
Keywords: Service availability
User: LOCAL SERVICE
Computer: Sally-HP
Description:
The event logging service encountered an error while initializing publishing resources for channel Security. If channel type is Analytic or Debug, then this could mean there was an error initializing logging resources as well.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Eventlog" Guid="{FC65DDD8-D6EF-4962-83D5-6E5CFE9CE148}" />
<EventID>22</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000020000</Keywords>
<TimeCreated SystemTime="2015-06-20T01:03:35.764878100Z" />
<EventRecordID>123233</EventRecordID>
<Correlation />
<Execution ProcessID="448" ThreadID="516" />
<Channel>System</Channel>
<Computer>Sally-HP</Computer>
<Security UserID="S-1-5-19" />
</System>
<UserData>
<InitChannelPublishingFailure xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2004/08/windows/eventlog">
<Error Code="4201">
</Error>
<ChannelPath>Security</ChannelPath>
</InitChannelPublishingFailure>
</UserData>
</Event>
So I could go on and on, but there a millions of errors (?) Everyday.....none critical but just gobs! How can the machine operate with all those errors?
Thank you!
-
The chkdsk report is fine - no file corruption found and no bad sectors on the HDD.
I'm not sure how significant the Event ID 3 for the UBPM is to the BSOD - I can't find it in my services.msc but the Task Scheduler is set as Started and Auto. and I would have thought similar for the UBPM. http://blogs.technet.com/b/askperf/archive/2009/10/04/windows-7-windows-server-2008-r2-unified-background-process-manager-ubpm.aspx
Event ID 22 could also have had a hand in it but Event Viewer always has Errors in it and is what phone scammers use to trap the unwary into parting with cash and allowing them access to your machine to possibly install a key logger to steal personal info.
Event ID 3095 is nothing to worry about.
-
Ok, thanks for responding. I think i'll hold tight for now and see if I get any more weird stuff or crashes, etc before I do anything else.. :sarcastic:
-
Hi, Sally,
It seems that your machine is saddled with some critical issues. Are you downloading any torrent?. The torrent has a knack of tresspassing your safety guard and steal information. If you are , pl stop . Dont uninstall but if possible disable all torrents in your pc.
Downloading from suspicious sites, even genuine downloads, they will try to inject custom toolbar and other injections, if you download standard . Pl select custom and then uncheck those in downloads. Majorgeek is the safest place for program downloading, like filehippo, where blocks the toolbar or alerts you to choose custom installation for these programs.
Wait for Shane suggestion on BSOD
-
No torrents....what makes you think that?
-
Hi, The torrents are the first suspicious and so i queried. Glad that you do not have any torrent.
-
So, here I am ...I'm BAAAAAACK! I have been so disgusted with this situation and all the problems that ARE NOT GETTING RESOLVED, that I took a break from the computer last night. I didn't want to have another BSOD or ole32.dll error to ruin my sleep again. And I didn't mess with it today until about a half hour ago.
Oh yeah, now when I wake it up or reboot it ususlly has a hard time automatically logging onto my wifi network, even though it's been doing it flawlessly for over two years. i have to "connect" I don't have to enter passkey, but have to connect. Anyway, so I woke the thing up, got on the wifi, opened up Firefox and was viewing a page. I wanted to print the page, which I did, turned my head, and when I looked again...I HAD THE DAMN OLE32.DLL ERROR!!!!!!!! So obviously the Hotfix DID NOT WORK. I, again, was not able to shut down, but got the desktop screen saver void of icons just sitting its pretty little face there and doing NOTHING1111 Would not shut down, as usual. I have not been able to call up the task manager by Cntr-Alt-Del and Julian told me to do Cntr-Shift-Escp to call up the task manager...NOT! Still had to press and hold on/off button to shut the sucker down.
So of course it asked me if I wanted to go into safe mode which I did with networking. Went right to Tweaking.com WR and ran #2...all ok..the in #3 I ran the preliminary check disk and it told me I had errors, EVEN THOUGH I RAN THE 4 HOUR CHECK DISK YESTERDAY....log contained above somewhere. So I just ran the check disk F and it just finished, so I will get off my Ipad and get the log off the machine and post it here in a few.
Meanwhile I still have a mess....nothing works!!!!YIKES!!!!!! Do you think that Shane will have time to look at this tomorrow? How should I contact him?
-
So I'm going onto the Event Viewer and so far it says: On or more logs in the query have errors, then: Log-Security and Error-The instance name passed was not recognized as valid by a WMI data provider So I am unable to open the Security log cause it says this plus Event Viewer cannot open the event log or custom view. Verify that Event log service is running or query is too long. (Whatever that means!)
Still no "Critical " Event in Viewer
Oh, also, I forgot when I got the ole32.dll error it always also gives me an "exception" box. The one said: Process ID =0x1354(4948) Thread ID=0x16C0 (5824)
Anyway, here is the check disk log:
Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 6/21/2015 5:30:38 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.
2206 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)...
647624 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 10 unused index entries from index $SII of file 0x9.
Cleaning up 10 unused index entries from index $SDH of file 0x9.
Cleaning up 10 unused security descriptors.
Security descriptor verification completed.
79717 data files processed.
CHKDSK is verifying Usn Journal...
37177432 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.
955629567 KB total disk space.
505234144 KB in 376557 files.
266420 KB in 79718 indexes.
0 KB in bad sectors.
621191 KB in use by the system.
65536 KB occupied by the log file.
449507812 KB available on disk.
4096 bytes in each allocation unit.
238907391 total allocation units on disk.
112376953 allocation units available on disk.
Internal Info:
00 73 07 00 57 f6 06 00 96 c2 0c 00 00 00 00 00 .s..W...........
1b 65 00 00 3d 00 00 00 00 00 00 00 00 00 00 00 .e..=...........
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-21T21:30:38.000000000Z" />
<EventRecordID>856575</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.
2206 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)...
647624 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 10 unused index entries from index $SII of file 0x9.
Cleaning up 10 unused index entries from index $SDH of file 0x9.
Cleaning up 10 unused security descriptors.
Security descriptor verification completed.
79717 data files processed.
CHKDSK is verifying Usn Journal...
37177432 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.
955629567 KB total disk space.
505234144 KB in 376557 files.
266420 KB in 79718 indexes.
0 KB in bad sectors.
621191 KB in use by the system.
65536 KB occupied by the log file.
449507812 KB available on disk.
4096 bytes in each allocation unit.
238907391 total allocation units on disk.
112376953 allocation units available on disk.
Internal Info:
00 73 07 00 57 f6 06 00 96 c2 0c 00 00 00 00 00 .s..W...........
1b 65 00 00 3d 00 00 00 00 00 00 00 00 00 00 00 .e..=...........
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 that's all I can think of to report...PLEASE HELP!!!
-
OK, This is it! I got the black screen and then the BSOD while doing a simple email reply. Tried to restore to before the hotfix in safe mode...wouldn't do it. Tried to do it in regular mode...wouldn't do it...said my antivirus was blocking it...turned off the avast antivirus tried to restore to 05-29-15 and WOULDN'T DO IT...I'M IN DEEP DO DO AND JUST SINCE USING WR!!! If no one can help me, just say so...I will figure it out.
-
Sometimes just disabling an AV isn't sufficient to prevent it interfering with a restore action and you need to boot up into Safe Mode.
Prior to running WR you were asked to back up the registry - start WR again and use the registry restore option which should take you back to before all of this, except for the ole32.dll problem which you originally had.
You could try running BSV again to see if you are getting the same cause of the previous BSOD and it may also be worth going to the computer support site and re-downloading the drivers starting with the Chipset (if available), the video and then the audio drivers.
If all else fails and given what has already been tried, I think you should then consider a factory reset or repair install.
-
- I fear Windows Repair is/could be a bit too agressive. And I looking at the repair called "Repair Printer Spooler". I think it deletes too much files & drivers.
-
Don't know, all I know is I HAVE A MESS!
-
Hi, Did you update network frame to the latest. The error code refers to some services error.
-
I finally took my machine to a computer repair place. My Windows is corrupted, and he is in the process of reformatting my drive and reinstalling Windows. Apparently, when I uninstalled that Windows update, everything got screwed up...oh well, I tried, and now, I'm going to have fun reconstructing my system and getting back to normal. Through this whole thing, my biggest disappointment was that Shane did not give me any advice or help. I, without even trying the program, subscribed to the pro edition based upon the allocades of Major Geeks!
-
Uninstalling a Windows Update from Installed Updates will not screw your system up and from what I understand, your problem with ole32.dll pre-dates that update removal.
If the repair shop that you took your machine to had done a repair install instead of a format and clean install, your programs and personal stuff would have remained intact and we could have helped you to perform a repair install had you come back after my suggestion for you to do just that.
It is the repair shop that has added the extra work for you.
This thread that I had created explains Shane's unavoidable absence. http://www.tweaking.com/forums/index.php/topic,3252.0.html
-
Hi, I also feel that if you had opted for WRepair, then you would have the problem solved without losing your entire applications and other programs.
Windows updates deletion will not do any wrong on any computer. It will not update those updates. It does not change basic file structure in any of the installaton wim. So, the problem is that some of the windows files got corrupted which could not be repaired .
Anyhow, glad that you are going to have a fresh experience of windows install
-
Oh, well.....my luck! :teeth:
-
Sorry for the late reply!
I have been doing 16 hour days for the last week getting my family moved and my new office built in my garage, it is now 3;10 am for me and I have over 60 threads to look over and answer, so I didnt read the 5 pages worth of posts on this one lol
So sally, how have things gone so far?
Shane
-
Thank you for replying, Shane. I haven't picked up my machine yet..it's not ready but should be this morning! I have never had to take my computer to a shop in the 30 + years I have been nutty over them. I'm not a tech, but I can usually fix my own problems! I have had techs come to me occasionally, though, over the years to help with a glitch or so....the worst time was around 2000 when I had been on vacation for a couple of weeks and my son had ruined my hard drive by turning it into a recording studio using Napster...( he was forbidden to use my machine as I needed it for my business, but you probably know how teenagers are...if you don't yet. YOU WILL..I promise :cheesy:)
Anyway a tech helped me install a new hard drive and get back running. Other than that, no serious problems as I am careful.
-
Good to hear it is getting fixed, a new hard drive was a good idea. :cheesy:
If you had a normal Windows install disk you could have done this yourself, but Microsoft wnet and made that a pain in the butt to get because of their goal to have 1 billion machines on Windows 10 by 2020.
A happy note for myself, my old house I could only get a 15 mb internet connection, my new house I am now on a 100 mb connection. Ohhhh yeah :artist:
Shane
-
Do you mean a new format and install? The others Boggin and Jraju said it should have been a repair install?
-
If you had the disk you could have tried a repair install first, this lets you keep all the files and programs. If it didnt do the trick then a fresh install would be needed, which you could have done if you had the install disk :-)
Shane
-
I did not have the install disks, but Windows is being reloaded with the repair tech's OEM disks? Could he have done a repair/install?
-
Yes, he could have done a repair install with a Win 7 SP1 ISO disk.
I could - and still can supply you with a couple of those as I've done for others, with which you could have performed your own repair install.
-
Yes he could have tried a repair install first, and if a new drive was needed he could have imaged the old drive over to the new and then did the repair install, but if the drive wasnt readable then a fresh install would have been the only option.
Shane
-
Well, I don't know about that, but it's too late now, anyway..... :teeth: :cry: :confused: :sad:
-
Well, I don't know about that, but it's too late now, anyway..... :teeth: :cry: :confused: :sad:
Hey Sally any update how'd everything go with the tech?
-
So far, so good! I had to reinstall everything, but looks like everything is back to normal...FINALLY!! I'll keep you posted if I have any problems. Thanks for inquiring and helping... :smiley:
-
So far, so good! I had to reinstall everything, but looks like everything is back to normal...FINALLY!! I'll keep you posted if I have any problems. Thanks for inquiring and helping... :smiley:
No problem I tried my best.
but sometimes starting fresh is the only option. and it makes the computer feel new. :wink: