Weird BSOD problem

Senarium · 25 Feb 2016

Hi Everyone,

I have a weird BSOD problem which I cannot solve for a while(it persists still after upgrade to Windows 10 from Windows 7)

The main strange thing about this is that I get BSOD only after cold boot.
So it acts like this:

1. start PC.
2. Get to Windows Logo Screen
3. BSOD
4. Restart
5. Get to menu where I can try to repair or Start Normally

If I Choose Repair, it will fail to repair and will try to restore

If I Choose Start Normally, it will start OK, no BSOD, can work normally, games, browse internet, everything is normal.

6. Shutdown PC
7. Next time when I start is all over again i.e. Go to Step 1

I have this problem for a while, so what I tried:

Another Windows 7
Another HDD
Only HDD connected
Changed RAM
Tried with built in GPU
Upgraded to Windows 10

Result is the same as above every time.

Please suggest what could be the cause.
Logs collected with DM_Log_Collector, attached.

Thank you

PS. This thread is a continuation of this one: Frequent multiple errors BSOD. Solved - Windows 7 Help Forums the only thing changed is Windows 10 now. instead of Windows 7. If that helps somehow.

Arc · 25 Feb 2016

All are different bugchecks with different probable causes.

Code:

BugCheck A, {ffffe001feff8530, 2, 0, fffff8002f2f3601}

Probably caused by : memory_corruption ( nt!MiRestoreTransitionPte+111 )

Followup:     MachineOwner
---------

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff8008a4a85a8, ffffd00024fdc598, ffffd00024fdbdb0}

Probably caused by : ntkrnlmp.exe ( nt!DeleteNodeFromTree+e0 )

Followup:     MachineOwner
---------

Code:

BugCheck 139, {3, ffffd00027b948e0, ffffd00027b94838, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )

Followup:     MachineOwner
---------

So it would be difficult to arrive at a decision.

Let us go slow. At first, get rid of the most frequent BSOD causer, Daemon Tools. Windows 10 can open any disk image in windows explorer, no Daemon is needed there.

And, remove all the startup entries. Right click on the start button > Task Manager, Startup tab.

Then see how it goes. Let us know.

Senarium · 27 Feb 2016

Removed Daemon Tools.

Removed all startup items.

Shutdown. Cold start.
No BSOD.
Added Dropbox, Catalyst, Letter Zu to start up(essential for my work, no need for others).
Shutdown . Cold start.
No BSOD.
Repeated "Shutdown . Cold start." several times. No BSOD.

Amazing, but apparently remove of Daemon Tools did the trick. I will test it several days, just to make sure this is it, and Mark Solved.

Thank you a lot for your support, much appreciated.

Arc · 27 Feb 2016

Welcome. Now wait and observe how it goes. Let us know for any further issue.

Senarium · 02 Mar 2016

Hi,
So the problem still exists.

Since last time 3 more BSODs, please see attachment.

It seems that if I shutdown and I start PC again immediately in some minutes , BSOD wont happen. It will happen for example on next day. Not sure if this info helps at all...

Thanks

Arc · 02 Mar 2016

Can you update windows to the latest?

Code:

Windows 10 Kernel Version 10240 MP (2 procs) Free x64

It is 10586 now.

Senarium · 03 Mar 2016

Hi, upgraded to latest version yesterday.

Today it started with BSOD, see attached please.

Arc · 03 Mar 2016

Your bugchecks are SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M which is a variant of stop 0x7E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED).

Carrona.org says:

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control

There is a great chance of hardware incompatibility, as P5P41D | Motherboards | ASUS Global
does not reveal anything for windows 10.

Senarium · 04 Mar 2016

Since the problem was when I had Windows 7, I'm not sure if that has anything to do with Windows 10 incompatibility.

Arc · 04 Mar 2016

A valid point.

Have you got windows 10 by a clean install, or it was an upgrade?

If it was an upgrade, perform a clean install as the last way to remove the possibilities of a software/driver caused BSOD. Dont install any driver yourself; let windows update install the drivers for the computer (because the vendor supplied drivers will not be compatible).

If it is already a clean install with windows suggested drivers, then we have to go for hardware tests exclusively.

So let us know.

Weird BSOD problem

Weird BSOD problem

Still exists

Another