My first BSOD in ten.

Thanks again, Bill.

There was no more BSOD issue after that one, but I am facing another hardware related issue occasionally .... I will take another try to resolve it myself. If failed, I will post it in the appropriate subforum for essenbe, Anak, and ICITOLOL.

A also want to believe that Win10 is the main suspect for teh BSOD (possible, it is a Technical Preview only, it may cause instability at this point.) but I will want to see how it goes after following John's guidance.

Now it seems to me that the BSOD was just a glitch, because I failed to recreate it in identical situation.

Wow! Lot's of suggestions! I'll try not to conflict with them.

First is the missing drivers. They must be installed as there's no telling what the device will do to the system without drivers being installed.

A closer look at the drivers that came out of the dumps shows that they all have the same date stamp (actually 2 datestamps) in common. This makes me suspect that the drivers are Windows drivers (which increases the likelihood that this is a compatibility issue).
Hang on while I check them against my Win10 install......

OK, all of the last 2 datestamps appear to be Windows drivers and are new to Win10 (except for intelppm.sys, dsgmms2.sys, and dump_storahci.sys - but they have been updated for Win10).
I include dump_storahci.sys as it's most likely that the storahci.sys driver is also updated.

ntosext.sys Mon Jan 19 23:07:08 2015 (54BDD46C)
intelppm.sys Mon Jan 19 23:07:14 2015 (54BDD472)
win32kbase.sys Tue Jan 20 02:08:25 2015 (54BDFEE9)
win32kfull.sys Tue Jan 20 02:08:55 2015 (54BDFF07)
dxgmms2.sys Tue Jan 20 02:10:22 2015 (54BDFF5E)
CEA.sys Tue Jan 20 02:10:23 2015 (54BDFF5F)
clipsp.sys Tue Jan 20 02:10:25 2015 (54BDFF61)
mmcss.sys Tue Jan 20 02:10:45 2015 (54BDFF75)
cmimcext.sys Tue Jan 20 02:11:49 2015 (54BDFFB5)
dump_storahci.sys Tue Jan 20 02:12:00 2015 (54BDFFC0)

Based on the other comments I read about Speccy vs CPUz - I have to wonder if the version that Speccy uses is incompatible w/Win10.
I've started this topic in the Speccy Bug Reports forums to see if they can confirm it: Possible bug in Win10 w/CPUz driver - Speccy Bug Reporting - Piriform Community Forums

As for Speccy running fine for many times before the BSOD - it possible that a certain function isn't being called until the time that it crashes. Or, that it may be conflicting with another program (and not with Windows) - so that it only crashes when that other program is doing something different. That's why BSOD's are so difficult to pin down - the dynamics of the system make it difficult to figure exactly what's causing the problem.

I'd run Driver Verifier with Speccy installed, without it installed, and then with CPUz installed.
Let it run long enough to generate a BSOD with each (I'd say about 36 hours - but you're more familiar with it).

Good luck!

John, I have two questions about the drivers you suggested.

First, for intelppm.sys, which one should I take form the intel's page?

Attachment 11941

And for the realtek network driver, as there are no drivers for 10 yet, will it PCIe driver will be ok?

Attachment 11942

Please let me know.

Thanks a lot for the post you made in Speccy's. Let us expect that some good info will be available there.

After updating these two drivers (so that they cannot sneak in) I will go for driver verifier.

Edit: You are absolutely right that all the drivers are windows drivers at that time, other than the nvidia one, the immediate earlier to the latest version. I was unsure which drivers I should install with 10, so decided to use the windows drivers only at that time.

Hi Bill, I just ran speccy in debug mode, it went fine.

Attachment 11943

After getting confirmation from John about those two drivers and updating those, when I will employ DV, I will try Speccy in debug mode again. Thanks. :)

This is why I love working in the online forums. Different opinions and approaches are respected and encouraged. Alone one of us may not be able to reach a resolution - but with many people participating it's almost certain that a fix will be found!

The intelppm.sys driver is best left alone. Windows update will give you the latest version. Please note that it has the same date/timestamp as ntosext.sys (which is one of the new Windows 10 drivers).

Use the Win8.1 driver for the network card and run the installer in Compatibility Mode.

Then check Device Manager to be sure there are no further problem devices.

All drivers other than intelppm is updated. But still there are two devices with yellow triangles.

Attachment 12360

Though there is no such lack of functionality due to that. DV ran well, without any hiccup. I experienced mouse lags, not-to-smooth video, but no more BSOD.

I had another serious issue with this computer in between, So waiting before posting back in this thread, if that issue results any more BSOD.

Overall, the computer is running very smooth now. It goes to the desktop within a few seconds only, everything else works as charm.

Thanks big lots, Colin, John, and Bill. I highly appreciate all the help you provided for me.

Have you installed the Intel Management Engine software as I requested earlier?
If so, what happened?
Could you check the hardware ID on the PCI Simple Communications Controller and see if it's still PCI\VEN_8086&DEV_8C3A&SUBSYS_1C3A1458&REV_04\3&11583659&0&B0

Have you updated the chipset drivers from the Intel Download Center?
If so, what happened?
Could you check the hardware ID on the SM Bus Controller and see if it's still PCI\VEN_8086&DEV_8C22&SUBSYS_50011458&REV_05\3&11583659&0&FB

****************************************************************************************

Just FYI - I've been rather heavily involved the last week or so in figuring out which are the new drivers in Win10 and adding them to the DRT ( Driver Reference Table (DRT) ) and the Windows Drivers Comparison Table ( Driver Compare )

The drivers are added to the DRT, but are awaiting the addition of descriptions before they are released to the public. I'll be adding a new entry (and hopefully a new column) for the OS that the Windows drivers are present in. For now the Information/Description column will have an entry that reads "OS: Win10TP" This table interfaces with the BSOD app (and it trims the Windows drivers out of the output).

The Windows Driver Comparison table is being completely reworked, so we haven't even added the drivers to it yet - but I do have a spreadsheet of them with the required info just waiting for the new table to be finalized.

Not only IME, I needed to install the INF Update Utility too .... which helped to recognize both of those.

And, thanks a lot for all those hard work, John. Your DRT is always the most valuable ready reference for the drivers.