Windows 10: BSOD at Irregular intervals

Hi, I noticed after the latest windows update a couple of days ago, that I'm getting BSODs with different messages, or PC would freeze and no other option than just to shut down.

Freeze/BSOD can happen in middle of game, middle of email or middle of browing web, no pattern.

What I have done so far is ccleaner to clean registry , updated drivers, uninstalled AMD and reinstalled it.

I noticed in event viewers multiple messages re DCM, tried to follow some online suggestions, but got hung up as permissions were greyed out.

You guys have helped me before rather well, so keeping fingers crossed.

Thanks

:)

 

Notepad Window Opens At Irregular Intervals (about every 10 minutes)

If you downloaded the Win 10 Anniversary Update a couple of days ago, you must be using Windows 10 ... and should have asked your question in the Windows 10 section rather than in the Windows 7 section. I'll move it for you.

Don't delete desktop.ini, at least not yet. Your problem (Notepad popping up every 10 minutes) does not seem to be the same as that of the original poster (Notepad opening at Windows start). Does Notepad pop up when Windows starts AND about every 10 minutes
thereafter?

For a description of Desktop.ini, see
http://www.computerhope.com/issues/ch001060.htm

What are you using for antivirus and antimalware programs?

Is the contents of the Notepad the same (as near as you can tell) each time it pops up?

Take a screenshot of as much of the Notepad window that fits on your screen and include that in your next Reply. See

http://www.howtogeek.com/226280/how-to-take-screenshots-in-windows-10/ After you've saved the screenshot as a file, click the "Insert Picture" icon in the toolbar of the Reply window, browse to the location of the file you saved, click "Open" and then
click "Upload."

 

Notepad Window Opens At Irregular Intervals (about every 10 minutes)

<Split from a thread in Windows 7 | Performance & System Failures>

I have a similar issue, The notepad pops up at irregular intervals and has a file on it that says it is a "metadata" file. It is about a page long. I have deleted that popup numerous times, but periodically - maybe more like every 10 minutes - it pops
up again. it is quite annoying. This started before I downloaded the Win 10 Anniversary Update a couple of days ago ---there - it just popped up again. I use Windows Defender as my primary protection. Is this a factor? Should I use this
or something else, or defender AND something else. Let's see - I seem to be asking more than one question...sorry about that.

Can I attach a copy of the file or do you need that at all? Should I use the same solution - i.e. delete desktop.ini? What does desktop.ini do, anyway? If I delete it, what other functions will be lost?

Thanks.

 

You never responded to my last post in this thread: BSOD - Driver Verifier detected a violation

I don't see anything useful in the latest dumps. Give Driver Verifier a try, see if it shows us anything useful:
===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to


PART TWO


and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it.

Also noticed you have two 2GB memory DIMMs and two 4GB memory DIMMs installed. Running unmatched memory can sometimes cause strange problems. I suggest removing the two 2GB DIMMs and run for awhile without them, see if that makes any difference. If not, swap 2GB abd 4GB DIMMs and test some more.

 

Hi Ztrucker. Had marked it as solved, apologies for not replying.

Yes, did the uninstall AMD and reinstalled it again.

Will do the driver verifier as per this post and reply back.

Noted re memory, will give that a try in the next couple of days since I've heard of stranger things.

Will report back in a couple of days, thks again

 

While playing Starcraft, screen went black in mid game, although PC lights are still on. Did not get blue or red screen, just black and had to manually shut down pc.

Ran tool, enclosed. let me know if shows anything or keep on with
verifier until happens again ?

 

Was in middle of an email, screen froze, had to do a hard shutdown. Event viewer showed this, of which there are plenty of instances;

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
and APPID
{F72671A9-012C-4725-9D2F-2A4D32D65169}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

 

No new dump unfortunately.

Event viewer log does indicate a hardware problem with a PCI Port though:

Code: Event[64018]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2017-01-16T11:50:30.696 Event ID: 17 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: Dad-PC Description: A corrected hardware error has occurred. Component: PCI Express Root Port Error Source: Advanced Error Reporting (PCI Express) Busevice:Function: 0x0:0x0:0x0 Vendor IDevice ID: 0x8086:0x3405 Class Code: 0x30000 The details view of this entry contains further information. Event[64019]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2017-01-16T11:50:31.809 Event ID: 17 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: Dad-PC Description: A corrected hardware error has occurred. Component: PCI Express Root Port Error Source: Advanced Error Reporting (PCI Express) Busevice:Function: 0x0:0x0:0x0 Vendor IDevice ID: 0x8086:0x3405 Class Code: 0x30000 The details view of this entry contains further information.[/quote]

 

How do I correct that ? Its still freezing intermittently.... Something I can fix, or do I disable something..or drivers for it somewhere ?

Thanks as usual

 

Without a dump it's hard to know. There are no Windows 10 drivers from Dell for this PC.

The files you uploaded in the zip indicate you have 18GB of ram which is an odd number. Looking at the dumps, they aregee you have 18GB sing a mix of 2GB and 4GB DIMMs. I would try removing all the 2GB DIMMs running only with identical 4GB DIMMs. See if that makes a difference.

Mixed memory has sometimes caused weird problems.

 

Yup, no such luck in the Dell site. Google reports that the only way of updating this is the updating Intel drivers, which says I have the current drivers.
Event viewer brings up our old friend DCOM:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
and APPID
{F72671A9-012C-4725-9D2F-2A4D32D65169}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Re memory, had the same sticks and configuration since 2011. Will remove the 2 GB ones which still leaves me with a total of 12GB which should be enough for pretty much anything.

Let me know if you have any ideas re the DCOM error, and I'll report back if removing the memory made a difference (fingers crossed)

 

The DCOM error is not unusual, I see it a lot.

Look at Event Viewer as the one entry suggested, see if there is more info available:

The details view of this entry contains further information.

 

Memory changed, now at 12 GB. Will report back depending on what happens.

Here is the details view, I hope it means more to you than me :
- System
- Provider
[ Name] Microsoft-Windows-DistributedCOM
[ Guid] {1B562E86-B7AA-4131-BADC-B6F3A001407E}
[ EventSourceName] DCOM
- EventID 10016
[ Qualifiers] 0

Version 0
Level 2
Task 0
Opcode 0
Keywords 0x8080000000000000
- TimeCreated
[ SystemTime] 2017-01-18T02:49:56.079941300Z
EventRecordID 145759
Correlation
- Execution
[ ProcessID] 744
[ ThreadID] 3896
Channel System
Computer Dad-PC
- Security
[ UserID] S-1-5-18
- EventData
param1 application-specific
param2 Local
param3 Activation
param4 {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
param5 {F72671A9-012C-4725-9D2F-2A4D32D65169}
param6 NT AUTHORITY
param7 SYSTEM
param8 S-1-5-18
param9 LocalHost (Using LRPC)
param10 Unavailable
param11 Unavailable

 

I wanted the details view for the hardware error (WHEA Error)

Code: Event[64018]: Log Name: System Source: Microsoft-Windows-WHEA-Logger[/quote] not the COM/DCOM event.

 

My Mistake, here you go:

- System
- Provider
[ Name] Microsoft-Windows-WHEA-Logger
[ Guid] {C26C4F3C-3F66-4E99-8F8A-39405CFED220}
EventID 17
Version 0
Level 3
Task 0
Opcode 0
Keywords 0x8000000000000000
- TimeCreated
[ SystemTime] 2017-01-18T03:04:23.169287300Z
EventRecordID 145765
- Correlation
[ ActivityID] {72E55B95-E9FE-4EC0-A067-2F6BEE38C193}
- Execution
[ ProcessID] 1288
[ ThreadID] 5116
Channel System
Computer Dad-PC
- Security
[ UserID] S-1-5-19
- EventData
ErrorSource 4
FRUId {00000000-0000-0000-0000-000000000000}
FRUText
ValidBits 0xdf
PortType 4
Version 0x101
Command 0x10
Status 0x0
Bus 0x0
Device 0x0
Function 0x0
Segment 0x0
SecondaryBus 0x0
Slot 0x0
VendorID 0x8086
DeviceID 0x3405
ClassCode 0x30000
DeviceSerialNumber 0x0
BridgeControl 0x0
BridgeStatus 0x0
UncorrectableErrorStatus 0x0
CorrectableErrorStatus 0x0
HeaderLog 00000000000000000000000000000000
Length 672
RawData 435045521002FFFFFFFF02000200000002000000A00200001604030012011114000000000000000000000000000000000000 0000000000000000000000000000BDC407CF89B7184EB3C41F732CB571311FC093CF161AFC4DB8BC9C4DAF67C10424582C5D 3571D20100000000000000000000000000000000000000000000000010010000D0000000000300000100000054E995D9C1BB 0F43AD91B44DCB3C6F3500000000000000000000000000000000020000000000000000000000000000000000000000000000 E0010000C00000000003000000000000ADCC7698B447DB4BB65E16F193C4F3DB000000000000000000000000000000000300 00000000000000000000000000000000000000000000DF000000000000000400000001010000100000000000000086800534 00000300000000000000000000000000000000000000000010E042002080000000000000413C3B000000413000000000C007 000100000000000000003E000000090000000000000000000000000000000000000001000115000000000000000010200600 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000000043010000000000000002000000000000A5060100 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000