Windows 10: My first BSOD in ten.

It happened after I just have installed Speccy and let it run for the first time. When it is "Analyzing", the BSOD happened. The screen says it is cpuz138_x64.sys that caused the BSOD.

I dont have CPUz Installed.

The later runs of Speccy went good.

So .... my question is .... what happened actually?

The crash dump also says that Speccy was running when the BSOD happened.
Code: PROCESS_NAME: Speccy64.exe[/quote] So, is the cpuz138_x64.sys an element of Speccy too?? I never know it.

Any confirmation or any insight will be highly appreciated.

:)

 

lost email folders

My Surface pro has lost a number of email folders each of which contain up to 50 emails in them,

how can I retrieve them?

Robin Currie

 

BSODs on windows 10, don't know which driver is failing

You best bet to get some answers on this is to go the the Windows Ten BSOD Crashes and Debugging Forum located

here. They do a good job of analyzing BSOD issues.

JohnD

 

I'm at work now. Will look in depth later on. Process name usually isn't significant in BSODs - but this may be an exception to that. Also, another driver could have crashed due to the Speccy install, which the took down the CPUz driver

 

Thanks a lot John. I was expecting you to take a look. *Smile

 

Arc, anything in \C:\Users\Archan\AppData\Local\Temp\cpuz138\?

 

Yes, Speccy uses a component of CPU-z. There was a bug a few years ago that seems to have resurfaced. I'll see if I can find any detail.

edit-1:
Is your board rev1 or rev2?

edit-2:
1) Speccy (and CPU-Z) will Freeze some systems - careful if you use them

2) Old, but might point you in the direction: Visual C++ error - Speccy Discussion - Piriform Community Forums

3)BIOS - FB is latest for rev2, FB is reported in msinfo32... but if your board is rev1 - F14 is the highest.
a. check your voltages: Ottetal comments on CPU-Z and Speccy aren't showing any change despite higher temps and BIOS changes.
b. check your power setting: Flerbenderper comments on CPU-Z and Speccy aren't showing any change despite higher temps and BIOS changes.
These might not apply to your board/CPU ???
--> done looking - not much else found.

edit-3:
1) Colin might have hit on it, there are a lot of references to %TEMP%\speccycpuz.dll or some variation. Maybe Old Timer - TFC would help?
TFC Download

2) As a test, try installing CPU-z to see if it BSODs
CPU-Z | Softwares | CPUID

3) Download and install Speccy: Latest version: 1.28.709 - Speccy - Builds
See if the portable version causes the same issue (if the BSOD can be reproduced)

edit-4:
Clean Startup - there are two Onedrive items, a download mgr, and Adobe - I don't know what screenpresso is, but it sounds delicious *Wink

Good luck Archie,

Bill
.

 

Sorry for the delay in responding. I live in New England in the US - and we've been hit with a lot of snow over the last week or so!
I've got 5 dogs who are onlyabout 8" tall (the 6th is about 24" tall) - and 40" of snow on the ground!

On to the analysis:

No Windows Updates installed. My copy has 2 updates - and is struggling with a 3rd as I type this.

You have 3 hard drives. What is the make/model/wattage and age of your Power Supply?

These devices have problems in Device Manager:

I'd try to get any available chipset and video drivers. Look for Win10 versions first, then try 8.1, etc The middle device (PCI Simple Communications Controller) is most likely the Intel Management Engine component - check Intel® Download Center if you can't find it at the PC manufacturer's website.

What have you been doing with Resource Hacker? I ask to see if anything critical to the OS might have been modified.

After having a look at the memory dump output, I noticed that there were relatively few 3rd party drivers involved. In some cases this is a clue that there's a hardware/compatibility/Windows problem. It's just a clue, not anything definite - especially since this is an new OS, Also, some of the unrecognized drivers in the output may actually be new Windows drivers for Win10 (I haven't analyzed 10 for those yet - when I do they'll show up here: Windows Driver Comparison Table )

Please note that your networking driver (Rt630x64.sys) dates from before Win8.1 came out. As such it's more likely to have incompatibilities than later drivers. I'd suggest updating it - I believe this is the link to the latest version: Realtek

But, all in all, the dump blames CPUz - so I'd uninstall it. As it's most likely a part of Speccy - uninstall that. If needed you can always reinstall it again - and without it you'll be able to see if the system BSOD's again.

It might be interesting to try Driver Verifier - both before and after removing it - in order to see what it says. But I don't think that it'd be needed in order to solve this. Good luck!

Analysis:
The following is for informational purposes only.
Code: **************************Sun Feb 1 13:17:50.158 2015 (UTC - 5:00)************************** Loading Dump File [C:\Users\John\SysnativeBSODApps\020115-24468-01.dmp] Windows 8 Kernel Version 9926 MP (4 procs) Free x64 Built by: 9926.0.amd64fre.fbl_awesome1501.150119-1648 System Uptime:0 days 1:50:05.839 *** WARNING: Unable to verify timestamp for cpuz138_x64.sys *** ERROR: Module load completed but symbols could not be loaded for cpuz138_x64.sys Probably caused by :cpuz138_x64.sys ( cpuz138_x64+24a2 ) BugCheck 50, {ffffe00100000018, 0, fffff8009ed424a2, 2} BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50) Arguments: Arg1: ffffe00100000018, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff8009ed424a2, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000002, (reserved) BUGCHECK_STR: AV DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: Speccy64.exe FAILURE_BUCKET_ID: AV_cpuz138_x64+24a2 CPUID: "Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz" MaxSpeed: 3400 CurrentSpeed: 3392 BIOS Version FB BIOS Release Date 06/19/2014 Manufacturer Gigabyte Technology Co., Ltd. Product Name B85M-D3H ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` [/quote] 3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code: **************************Sun Feb 1 13:17:50.158 2015 (UTC - 5:00)************************** Rt630x64.sys Fri May 10 05:59:08 2013 (518CC4EC) idmwfp.sys Thu Sep 25 11:44:24 2014 (54243858) cpuz138_x64.sys Thu Oct 23 11:03:05 2014 (544918A9) nvlddmkm.sys Sat Dec 13 01:53:17 2014 (548BE25D) 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) [/quote] http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
http://www.carrona.org/drivers/driver.php?id=idmwfp.sys
http://www.carrona.org/drivers/driver.php?id=cpuz138_x64.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
ntosext.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
win32kbase.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
win32kfull.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
dxgmms2.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
CEA.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
clipsp.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
mmcss.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
cmimcext.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys

 

No, Colin, it is not there .... it was my first seh actually after facing the issue. *Biggrin

Hi John. I actually performed a clean install with 10 just before, no updates were installed till then.

My PSU is Corsair VS 550.

Display showed the problem when I tried to use the intel graphics. It refused to be installed initially, then took a driver automatically. With nvidia, it worked smooth from the beginning. Actually I was trying to test all the devices and drivers there.

Resource is not in action till now, I just checked the system resources to be modded with it to customize the appearance; but not done yet. I have a system image made in case of any trouble with it.

About the drivers, all the drivers other than nvidia are installed by windows .... I havent tried to install any of them manually. Because I was not sure which one is to use.

I will pay earnest attention to your driver suggestions and will update them thoroughly, and then I will report you back.

About the CPUz ... it is not installed in my system. So as you are saying, it came from Speccy. I use speccy for long, never noticed that it includes an element of CPUz there.
But .... I opened Speccy almost 100 times after the incidence, just tried to recreate the issue. No luck. Speccy is running as nicely as it always did. At this point I am stumped .... why it happened at the first time and not again. Do I need to consider that Speccy is not liking my system and I should uninstall it? Right now, or after any more occurence of the issue, to be confirmed? Will wait for your suggestion at this part. To me Speccy is very useful.

Driver verifier .... I think I shall give it a go, at my first chance. *Smile Thanks again, John.

 

Hi Bill .... the DRAM Frequency is 665.1 MHz there. Is not it to be a little more, like 666.5 for my 1333 FSB RAM? May it be an issue?

BTW, CPUz did not cause any BSOD etc, it ran like a good boy.

Attachment 11869

Attachment 11870

Attachment 11871

Attachment 11872

EDIT: My mobo is rev 2, and screenpresso is an app like snipping tool, having some more functions.

EDIT 2: Tried another version of Speccy, all is wall with it.

 

@ Colin, it is there now, after installing CPUz as Bill suggested.

Attachment 11873

 

Archie,

Yes, it surprised me to learn that Speccy employed CPU-z to build some of it's report. I don't recall the details, but Speccy does use a CPUz.dll - renamed to speccycpuz.dll I think.

Three or four years ago, the Speccy / CPU-z issue only affected a few systems. I'm not sure I ever knew what elements (CPU, memory, gfx card, Mobo) caused the issue years ago. I thought Piriform corrected it with an updated DLL from CPUID. In one of the links I posted, there was a reference to msvcrt - I vaguely recall an endless loop condition (rpc?) that was part of the issue - not 100% sure though.

I would leave Speccy on your machine and see if the BSOD reoccurs. I think it is one of the best system reporting tools.

re: DRAM frequency. I'm not the best person to ask ... I mentioned it because of the mention in one of the links. Something to consider. I wish I knew more about those things, but it was a very long time ago that I worked with the hardware side - so long ago, we programed with switches and read lights.

Maybe essenbe, Anak, or ICITOLOL, or any of the other HW fellows can help, if needed.

Good to know that CPU-z doesn't cause any issues. See if you can compare the Speccy DLL and the CPU-z DL - again I wish I could be more specific, but I've been installing Win10 different ways / different machines and this iteration doesn't have Speccy or CPU-z.

If / when I get to some break point, I'll make the effort to install both and see If I see anything.

I wonder if installing CPU-z proper affected Speccy in a small way. Unlikely, but we used to put a print statement in the code to 'fix' a bug.

Anyway, run the machine as is for a while and see how it behaves. I wouldn't worry too much about Speccy - Win10 is more suspect.

Thanks for the other information (board rev 2, and screenpresso) - so your BIOS (FB) is the latest according to Gigabyte.

Man, that was a lot of words for a wait and see post *Wink

Bill
.

 

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. *Sad

 

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.

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!

 

You're most welcome Archie,

I'm sitting on the side so John has your full attention *Smile
I learn much from both of you - remembering it is another issue entirely.

edit: Piriform - Running Speccy in debug mode

-> See, I remembered to look at the source for reliable information - thanks for the nudge John. I'm not sure if debug mode helps since you can't reproduce the BSOD at will. You might consider adding a step to John's list ... run Speccy in debug mode when stressing your system (as opposed to just having it installed). Since there are suspect HW drivers (Speccy lists HW *Wink) there's a good chance that sorting out those Win10 drivers will close this case.

Tip: create a SpeccyDebug shortcut.

Bill
.