Windows 10: Who can read enclosed error log?

Hello every1:
Is anyone here able to read enclosed error log? It was created right after very long try to start my PC (a tad old) which I upgraded from Win7 Ultimate some time ago. I've done it in safe mode after about 45 minutes since computer was turned on and I couldn't go any further because 2 BSOD with DPC watchdog stuff and countless restarts. I am experiencing this thing since about two weeks when (I believe so but I am not sure) installed some upgrade from MSoft. I am suspecting some hardware or drivers incompatibility but about first two weeks after upgrade my comp was working flawlessly. Then something happened and my horror with countless BSODs began. In the meantime I did reinstall Win10 again using "GetWindows10-sds" file. But it didn't help me much. I was experiencing extremely long lime of boot up (average 1 hour) with a few BSODs and many restarts on the way. And booting wasn't always successful. I have a whole bunch of zipped errors logs since last few days. I don't need to add that my option of going back to Win7 is already history as well as windows. old, $windows.~bt and $windows.~ws folders. So only solution when I won't be able to resolve this problem is installing Win7 from scratch what will be disaster for me because of necessity of reinstalling many programs I use.
Here is what I have:
ASUS M2N32 SLI DeLuxe MoBo
AMD Athlon 64 X2 Dual Core 5600+ CPU
8 gig Corsair memory
ASUS Radeon R7 240 Graphic card
Samsung SSD 840EVO drive (Registry shows that is operating in AHCI mode but I can't find this option in my BIOS (updated to last version available (v5002))).
3 regular SATA HDs

chkdsk and sfc scannow was performed 2 or days ago and didn't find nothing.

I am asking some GURU here who is able to read and interpret errors so I could perform check or some upgrades/updates.

Here is error log created in safe mode:
Attachment 69569

And this one was created seconds ago in normal mode:
Attachment 69571

Any help, folks, will be really appreciated.

:)

 

Back up for Nokia C3-01.5

I am new to Nokia Suite. I have recently backed up my phone. When i went into word to view it i found it unreadable. Can anyone please tell be how i can read it? I have enclosed attachment.

 

You do not have permission to open a text file…

Setting the same password on each machine didn't cure the problem. "Everyone" already had read and write privileges on the desktop where the text file was.

In the end I got it to work on the Mac by making a new folder in the root directory, sharing it, giving it read and write privileges, and clicking the settings at the bottom to set "Apply to enclosed items".

I guess I could also do the "enclose items" thing with the desktop folder but it seems less secure with all the items I have there...

Thanks for you help.

 

Strange thing happened. I opened BIOS and changed SATA to RAID on all drives. Restarted computer and got horrible BSOD saying that I need repair my PC with error code 0xc000000e. Restarted again and I saw all my drives gone in BIOS. So I set my BIOS to default and restarted again. All drives came back and computer booted up immediately. I was ready to work within 20 seconds or so.

So I guess this may help our gurus in proper diagnose.

Anyone?

 

You can't change the drive type in BIOS after installing the OS with SATA drives.

 

Looking at the crash dumps there is some persistence in it. The storport.sys, storage port driver from Windows, is present everytime in the stack. My guess is that your controller drivers are a main cause in this problem, you have also some other outdated drivers which also are a cause for some crashes but can't be updated because there haven't been drivers released in years for your motherboard.
Driver Reference Table - storport.sys
Code: 0: kd> k # Child-SP RetAddr Call Site 00 fffff800`982b6ce8 fffff800`96767e61 nt!KeBugCheckEx 01 fffff800`982b6cf0 fffff800`96629196 nt! ?? ::FNODOBFM::`string'+0xad61 02 fffff800`982b6d80 fffff800`9662b3df nt!KiUpdateRunTime+0x56 03 fffff800`982b6de0 fffff800`96ddaa46 nt!KeClockInterruptNotify+0x44f 04 fffff800`982b6f40 fffff800`966f5197 hal!HalpTimerClockInterrupt+0x56 05 fffff800`982b6f70 fffff800`9674fb8a nt!KiCallInterruptServiceRoutine+0x87 06 fffff800`982b6fb0 fffff800`9674ffb7 nt!KiInterruptSubDispatchNoLockNoEtw+0xea 07 fffff800`982afb10 fffff800`9666d3c4 nt!KiInterruptDispatchNoLockNoEtw+0x37 08 fffff800`982afca0 fffff800`9666d374 nt!KxWaitForLockOwnerShip+0x34 09 fffff800`982afcd0 fffff800`3ea94a3f nt!KeAcquireInStackQueuedSpinLock+0x44 0a fffff800`982afd00 fffff800`9667a2c6 storport!RaidpAdapterTimerDpcRoutine+0x5f 0b fffff800`982afd60 fffff800`96753495 nt!KiRetireDpcList+0x5f6 0c fffff800`982affb0 fffff800`967532a0 nt!KxRetireDpcList+0x5 0d ffffd000`23445950 fffff800`96751d75 nt!KiDispatchInterruptContinue 0e ffffd000`23445980 fffff800`96750031 nt!KiDpcInterruptBypass+0x25 0f ffffd000`23445990 00000000`00000000 nt!KiInterruptDispatchNoLockNoEtw+0xb1[/quote]

 

Wylman68 and axe0:
Thanks for your replies. I will dig on internet a little to find how to resolve driver problem. And I must tell you 2 things:
first - computer was working with no problem for about 2 weeks after upgrade from Win7 so I'm giving myself a question "how was it possible if my mobo has old drivers?" second: today, after this mess with BIOS setup (posted above), my computer started within 20 seconds with NO ANY PROBLEM. Miracle? I wish it is miracle. But just in case I've performed dm test and I am enclosing latest logs just to compare with an older one.

Attachment 69695

 

A new log without new dumps is a bit useless. No offense but there is nothing new to analyse or something.

 

I have also noticed this but I thought that's normal.

Anyway. MY PC crashed again and I am writing this message using my laptop (BTW working with no problem on Win10). I'll check my PC later however my patience is going to its limit and my next step (which I don't like at all) will be reinstalling Win7 and all my programs from scratch. And its gonna be disaster because so many things to reinstall and go through registration/activaction things. I have some older versions of some programs and I am expecting problems with its re-registration.

Oh well......

Unless miracle will happen......*Sad

 

No miracles. I decided to end my Win10 odyssey and reinstalled Win7. I think that I need new PC to install W10 again. When its gonna happen? Perhaps within next few months or so.....
Thanks to all of you for your suggestions and help.*Biggrin