Windows 7 errors updating since april

[kokos]

I wrote that I did that. Before I made the windows update, I checked if the ImagePath value is without \??\
Okay, I will try again, but the effect will be the same at 100% I know I will lose 20 minutes

 

[Sysnative Windows Update]

I'd be surprised if it didn't, because I am 100% sure that works since I've done this quite a few times.

 

[kokos]

I'd be surprised if it didn't, because I am 100% sure that works since I've done this quite a few times.

It didn't.

I installed the patch KB4457144 from the disk. Installation completed, I click restart now, windows is closing and configuring updates. Then system starts and you can see the screen "starting windows" for a 2-3 minutes(much longer than usualy) and then buum - BSOD. Exactly the same as before. The value ImagePath is still correct - the way you wanted.
And it took me some more time, because at system repair it turned out that all restore points were gone! I specifically created one before doing update. This command saved me:
dism /image:d:\ /cleanup-image /revertpendingactions

 

[Sysnative Windows Update]

Please let me have the following again:

Step#1 - FRST Scan

1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 32-bit Version so please ensure you download that one.
2. Right click to run as administrator. When the tool opens click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please attach the log back here.
7. Another log (Addition.txt - also located in the same directory as FRST.exe) will be generated Please also attach that along with the FRST.txt in your reply.

 

[kokos]

Ok.
Dropbox - Addition.txt
Dropbox - FRST.txt
I will do some RAM test in spare time. Smart ok. I ran chkdsk as well.
Generally, I do not have any BSODs.

 

[Sysnative Windows Update]

No need to do all that.

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 32-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

 

[kokos]

Well, this haspnt driver has been removed. I know what program installed it. It works for now. We will see if all its functions will work. Besides, I have it for a long time and WU worked properly during this whole time - until April.
You could have warned that FRST would delete things, eg empty the basket, delete cookies - I like my cookies. Ok, but if it helps, it's a small price to pay
What should I try now - install update?
Honestly, I do not believe it will work ...
Besides, I wrote to you earlier that I tried to disable everything from autostart and this haspnt too (using autoruns from sysinternalas) and it didn't help

 

[Sysnative Windows Update]

Yes, I should have warned you about EmptyTemp: directive clearing the bin, my apologies.

Yes, please try the updates.

 

[kokos]

I am sorry to write this, it did not help - but BSOD appeared faster than before
I have restored to restore point before your last fix.
Maybe it's hardware issue or Microsoft itself broke something...

 

[Sysnative Windows Update]

Was the Minidump file created?

 

[kokos]

Yes.

 

[Sysnative Windows Update]

Can you please provide the Minidump file for my analysis?

 

[kokos]

aaa, you mean dmp?
I added a file from BlueScreenview as txt
I had to zip it, because can't upload as dmp.

 

[Sysnative Windows Update]

I see a memory card reader attached, can you please disconnect it from your system and retry?

Also, it would help if you could disable automatic restart on System failure as we (you) could maybe see the driver that's causing the crash on the BSOD.

Disable Automatic Restart on WIndows System Failure

 

[kokos]

I see a memory card reader attached, can you please disconnect it from your system and retry?

Hello, I would have to disassembly a laptop to do it. This is simply a factory card reader.


I think everything is in the dmp file. I've seen this BSOD long enough - it says blah blah, maybe the driver, maybe something, but don't know which. And error codes
Dmp files say:
KERNEL_MODE_EXCEPTION_NOT_HANDLED
0x1000008e
intelppm.sys or ntkrnlpa.exe
and one time
DRIVER_IRQL_NOT_LESS_OR_EQUAL
0x000000d1
ntkrnlpa.exe

I made a few more attempts, for example, updated bios. I have two ram modules. I checked on each one separately. In both times, the system went beyond the "starting windows" showing black screen and cursor which can be moved.
And finally: first module - BSOD. Second stucked on this black screen and disk activity - after 15 minutes I turned off the laptop
Ultimately, I give up. No ****** update attempts unless MS writes in some fix: dear kokos, we fixed this bug and you can easily install the update


Thanks for the help. Regards

 

[Sysnative Windows Update]

Aha, this is a laptop. The dump does not actually tell us that much.

And you do have an issue. This is not a bug.

As you wish, but we can continue troubleshooting.