BSODs (log attached)

[byterj]

Brand new PC, suspecting hardware.

thanks for the help

 

[byterj]

any thoughts?

 

[Arc]

Hi byterj.

It appears that the issue is critical, and we may need some amount of work to work on this issue.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa8614681ee0, 0, fffff80002ace6a5, 5}


Could not read faulting driver name
[COLOR=Red]Probably caused by : Unknown_Image[/COLOR] ( nt!MiDeleteVirtualAddresses+49d )

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

Apparently we are seeing that he display driver is failing. Install the NVIDIA DRIVERS 314.22WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Let us know the results.

 

[byterj]

Hey Arc, how u doing?

its the same machine from the other topic: http://www.sevenforums.com/bsod-help-support/312726-bsod-every-24-hours-so.html

Do you suspect that maybe Video Card is fauty? I can return it and grab a new one.

I have lots of VMWare Workstation crash logs/dumps, do you know how to read them too?

Thanks again.

Hi byterj.

It appears that the issue is critical, and we may need some amount of work to work on this issue.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa8614681ee0, 0, fffff80002ace6a5, 5}


Could not read faulting driver name
[COLOR=Red]Probably caused by : Unknown_Image[/COLOR] ( nt!MiDeleteVirtualAddresses+49d )

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

Apparently we are seeing that he display driver is failing. Install the NVIDIA DRIVERS 314.22WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Let us know the results.

 

[Arc]

The chance of a corrupt GPU may not be nullified. But at this stage it is not possible to Verdict that. First it is to nullify the other possibilities; and unstable display driver should be removed at first.

Next, Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Plus: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

 

[byterj]

http://speccy.piriform.com/results/gbowIz57UXulJP8dqFK2Bh4

new driver installed, followed instructions, lets see how it goes

Fumark runs great without artifacts, i suspect VGA video memory

Will report next BSOD, thanks.

 

[Arc]

The computer is definitely overheating.

View attachment 297876

If you dont try to control the heat, you will never be able to make it BSODs free.

And, dont start any other thread on this issue.

 

[byterj]

The computer is definitely overheating.

View attachment 297876

If you dont try to control the heat, you will never be able to make it BSODs free.

And, dont start any other thread on this issue.

The motherboard temperature report is incorrect for sure.

I have another PC with same motherboard and bios that is reporting 111c right now and have no problems.

 

[Arc]

The computer is definitely overheating.

View attachment 297876

If you dont try to control the heat, you will never be able to make it BSODs free.

And, dont start any other thread on this issue.

The motherboard temperature report is incorrect for sure.

I have another PC with same motherboard and bios that is reporting 111c right now and have no problems.

100 degrees evaporates the water. I can say nothing more.

 

[byterj]

The computer is definitely overheating.

View attachment 297876

If you dont try to control the heat, you will never be able to make it BSODs free.

And, dont start any other thread on this issue.

The motherboard temperature report is incorrect for sure.

I have another PC with same motherboard and bios that is reporting 111c right now and have no problems.

100 degrees evaporates the water. I can say nothing more.

Yeah Arc, thats why im saying that the program temperature report is incorrect!

Im not saying that 105c is OK, what im saying is theres no way of temperature can be that high, because a have another system with the same motherboard getting 111c MB temperature report that is a rock solid.

I get those +100c reports idle or running prime95, doesnt make any sense. And i checked myself the board, i can keep my fingers over chipset heatskin all day without feeling any heat.

Hope i made myself clear.

No other crashes since video driver reinstall, Vmware or BSOD crashes.

 

[Britton30]

I'm not so sure, Speccy is fairly reliable. The board temp sensor isn't chipset temps. The board temp usually has a thermistor under the CPU socket or the VRM, Voltage Regulator Module. No two systems are alike, you can't rely on what one does to determine temps on another.

 

[byterj]

I'm not so sure, Speccy is fairly reliable. The board temp sensor isn't chipset temps. The board temp usually has a thermistor under the CPU socket or the VRM, Voltage Regulator Module. No two systems are alike, you can't rely on what one does to determine temps on another.

Its normal that temperature of this sensor stays the same under heavy load or idle? If i turn the machine off for half hour, boot windows and just opens the Speccy it will report over 100c.

 

[byterj]

1.24 Displaying Wrong Motherboard Temp - Speccy Bug Reporting - Piriform Community Forums

edit.

Motherboard
ASUSTeK COMPUTER INC. Z87-K (SOCKET 1150) 28 °C

Speccy v1.23.569

 

[Britton30]

Well I take it back, there's something wrong somewhere, maybe Speccy or certain boards. The ones in your Speccy forum link are mostly Haswell as yours, but there is an AMD 880 and a Dell with a pre-Sandy Bridge setup.
I just downloaded the version 1.24 and here's a snip, and you have 1.23, odd stuff.

View attachment 297901

 

[byterj]

Well I take it back, there's something wrong somewhere, maybe Speccy or certain boards. The ones in your Speccy forum link are mostly Haswell as yours, but there is an AMD 880 and a Dell with a pre-Sandy Bridge setup.
I just downloaded the version 1.24 and here's a snip, and you have 1.23, odd stuff.

View attachment 297901

Hello!

The report was made using 1.24 (the high temp one).

I found this post about the bug, so I downgraded to 1.23 and got this:

Motherboard
ASUSTeK COMPUTER INC. Z87-K (SOCKET 1150) 28 °C

About same temp using AIDA64.

So the over 100c temp was a Speccy 1.24 software bug that happens only on some boards!

 

[Britton30]

Well the temp issue is solved at least, lol. Someone should be back about the BSOD, that's above my pay grade.

 

[Arc]

In that case, report the temps using HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools.

 

[Britton30]

I just did another test on my Ivy Bridge rig, it shows proper temps, ver. 1.24.
View attachment 297915

 

[Arc]

I tried the same version, Speccy v1.23.569 ......

View attachment 297917