New
#11
Which one? I'll delete it momentarily.
Although it's old, have you dealt with this program and reinstalled the affected software?
I see you've altered the hosts file to block Malwarebytes from accessing their activation server.Code:Event[7624]: Log Name: System Source: Service Control Manager Date: 2017-02-21T10:14:19.892 Event ID: 7045 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: S-1-5-21-3449498139-531481687-1691142593-1002 User Name: DESKTOP-FM6FKJ2\5ar Computer: DESKTOP-FM6FKJ2 Description: A service was installed in the system. Service Name: WinDivert1.1 Service File Name: C:\ProgramData\KMSAutoS\bin\driver\x64WDV\WinDivert.sys Service Type: kernel mode driver Service Start Type: demand start Service Account:
Must be accidentally. But I've deleted it in any case.
No Malwarebytes. :)Attachment 137608
What about KMSAutoS, you've had it installed and used it.
have you dealt with this program and reinstalled the affected software?
Well, maybe for Office, but that was long time ago. I don't have it now. :)
Attachment 137609
Alright, please check every program one pays for if it is genuinely activated.
Piracy doesn't just costs unnecessary time, but also could be somehow related to this issue.
This time it was 'just' blocking access to a server, but with a little bit surfing the internet there are enough issues caused by this kind of stuff.
This specific BSOD is a new one for me, the 0x133 I've seen are about a driver exceeding its allowed time to spend in a DPC routine.
DPC is basically delaying execution because the current task has not yet been finished. In a DPC routine a driver is finishing the task.
This BSOD is about something being in a DPC routine for an extensive period, according to the 2nd parameter it is 7680ms.
The official time is 100ms for DPCs, and 25ms for ISR, but the actual times are much higher.Code:0: kd> ? 0000000000001e00 Evaluate expression: 7680 = 00000000`00001e00
DPC and ISR are basically the same, DPC is for software and ISR for hardware.
DPC stands for Deferred Procedure Call
ISR stands for Interrupt Service Routine.
Ms is microseconds.
Please remove Avast temporary and use Windows Defender as alternative.
Please run driver verifier, do NOT check the options in the tutorial, select 'deadlock detection'.
WarningPlease make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.
Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.
If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.
NoteYour system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
I did like you said, and it crashed(BSOD) a few minutes after boot up. I think, now is different error.Attachment 137618