Hp dv9000 bsod

Use · 05 Mar 2016

Hello, I just registered hoping to finally find a solution for my BSOD problem before moving back to windows 8, already tried to get help in different forums but no luck.
This is my missus's laptop and I know its old but it's still in perfect working condition and do not feel like recycling it for a new one just to move on to windows 10.
Fresh windows installation, because I found a more recent driver for the Geforce 7150M that came with windows 8 update. I started benching it with Unigine Valley and it ran stable for more the 5 hours, temps were fine. On a finale try I maximised the settings and after a few minutes started crashing. The laptop is used only for internet browsing and SD video watching. I'd just like to make it stable for the mentioned tasks.
I am sure it is caused by the GPU driver, crashing occurs while watching videos.

Thanks in advance.

Attachment 67847

Edit:
I forget to mention, OS is in foreign language, if it is difficult to diagnose let me know and will reproduce the BSOD with English display.

Arc · 07 Mar 2016

Use said:

I found a more recent driver for the Geforce 7150M that came with windows 8 update.
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
I am sure it is caused by the GPU driver, crashing occurs while watching videos.

You are right.
Geforce 7150M is nvidia chipset (nForce 630M) and nvidia chipset drivers are not available nowadays at all.

What you may try here is ....... uninstall the installed driver. Let windows update search for a display driver.

Device Driver Automatic Installation - Turn On or Off in Windows 10 - Windows 10 Forums

If it finds any, the job will be done. It will be usable again.
_____________________________________________________________________________

Code:

BugCheck 3B, {c0000005, fffff80082ca99e2, ffffd0004c179460, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::SuspendPrimaryCpuAccess+4a )

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

Code:

ffffd000`4c178558  fffff800`8327edc9Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0xeedc9

Use · 09 Mar 2016

Arc said:

You are right.
Geforce 7150M is nvidia chipset (nForce 630M) and nvidia chipset drivers are not available nowadays at all.

What you may try here is ....... uninstall the installed driver. Let windows update search for a display driver.

Device Driver Automatic Installation - Turn On or Off in Windows 10 - Windows 10 Forums

If it finds any, the job will be done. It will be usable again.
_____________________________________________________________________________

Code:

BugCheck 3B, {c0000005, fffff80082ca99e2, ffffd0004c179460, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::SuspendPrimaryCpuAccess+4a )

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

Code:

ffffd000`4c178558  fffff800`8327edc9Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0xeedc9

Thanks for confirming.
Well, I restored windows to the state before driver was installed, installed again and now I only get the error: GPU stopped responding then recovered... Every time I start a video file I get this error but at least there is no more BSOD.

I can call this one somewhat SOLVED.

Arc · 10 Mar 2016

Use said:

Thanks for confirming.
Well, I restored windows to the state before driver was installed, installed again and now I only get the error: GPU stopped responding then recovered... Every time I start a video file I get this error but at least there is no more BSOD.

I can call this one somewhat SOLVED.

I would say that it is even worse than a BSOD, based on the probable causes of the issue.
If this issue occurs with multiple versions of the display driver, it is a strong indicator of a failing graphics hardware.

Use · 10 Mar 2016

Arc said:

I would say that it is even worse than a BSOD, based on the probable causes of the issue.
If this issue occurs with multiple versions of the display driver, it is a strong indicator of a failing graphics hardware.

You see I've run Valley benchmark for more then 5 hours, no issue. Older drivers only cause BSOD no error and earlier it had Windows 8.1 on it working with no problems. I'm 100% sure its the incompatible Geforce Go 7 drivers with Win 10 for lack of driver support.

Update:

Not responding error appears only after waking up from hibernation.