Nvidia BSOD problems

Your onboard chip should be Aero capable. Performance might not be as good as the 8400, but sufficient for everyday tasks.

I made a call with the man that bought the pc,and he told me that the bsod should be result of drivers. I just finished Ram memory testing with MemTest,SFC ( it found some errors and say that repair them),and also I enabled Driver Verifier to see in next 24h if I have some random reboots/BSOD's.
For mu PSU,I just checked it and it don't have any SATA power connectors and all of my drives are sata connected. Also it have less power connectors from this current.

Also,JK did you change out your laptop's antena ? (just to inform you)

Just I think that all things are good,then again bsod.
Attachment 172728

I guess that this one is because that I have turned on Driver Verifier. Should I turn it off now?

That seems like a different crash. Haspnt.sys was blamed, although I cannot find much info on it. The description is "HASP Kernel Device Driver", manufacturer being Aladdin. Do you know what the program is? If so, you might remove it.

Code:

Haspnt.sys        Fri Nov 02 10:31:06 2001 (3BE2AE2A)

Daemon Tools/SPTD is one other thing to consider. SPTD is known for causing BSODs, Daemon Tools/Alcohol 120% being the programs that use it. You might uninstall whichever program is installed, and then remove SPTD with the tool found here: DuplexSecure - Downloads

Keep Driver Verifier running for a while; upload and new crashes. Be sure to create a jcgriff2 report: https://www.sevenforums.com/crashes-d...tructions.html

After the jcgriff2 report has been created, you can upload just the dump files.

...Summary of the dumps:

Code:

Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Aug 29 14:21:58.143 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:29.891
*** WARNING: Unable to verify timestamp for Haspnt.sys
*** ERROR: Module load completed but symbols could not be loaded for Haspnt.sys
*** WARNING: Unable to verify timestamp for spsys.sys
*** ERROR: Module load completed but symbols could not be loaded for spsys.sys
*** WARNING: Unable to verify timestamp for spldr.sys
*** ERROR: Module load completed but symbols could not be loaded for spldr.sys
Probably caused by : Haspnt.sys ( Haspnt+3218 )
BUGCHECK_STR:  DISABLED_INTERRUPT_FAULT
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  sppsvc.exe
FAILURE_BUCKET_ID:  DISABLED_INTERRUPT_FAULT_Haspnt+3218
BiosReleaseDate = 02/11/2010
SystemProductName = MS-7592
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  

I don't have installed Daemon and Alcohol. I'm using PowerISO.
Here is that zip.
Attachment 172739

PowerISO shouldn't be using SPTD. Go ahead and run the SPTD installation/uninstallation tool, and we'll watch to see if it is reinstalled automatically.

I got a little info on that driver, mostly from Googling "Aladdin hasp". Follow the link to see the results. I gather that it is an anti-piracy driver installed along with one of your games or other programs. Which program it is evades me.

If you have any ideas, follow them by all means. If you really cannot figure out what is using the driver, go into C:\Windows\system32\drivers, and delete Haspnt.sys. If a program starts throwing fits, you'll know why.

I just right click on that file and select Media Info. This is that info that I got.

General
Complete name : C:\Windows\System32\drivers\Haspnt.sys
Format : MZ
Format profile : Executable / Intel i386
File size : 46.5 KiB
Encoded date : UTC 2001-11-02 14:31:06

Attachment 172789

What is MediaInfo?

MediaInfo supplies technical and tag information about a video or audio file.
It is free software (free of charge and free access to source code: GPL or LGPL licence)

Also I have uninstalled SPTD.

If you can find MediaInfo listed in Programs and Features, uninstall it. Otherwise, delete the driver and see what happens.

Jonathan_King said:

If you can find MediaInfo listed in Programs and Features, uninstall it. Otherwise, delete the driver and see what happens.

Driver deleted. Untill now,no problems.

Am I right in assuming you've had no problems since switching to the onboard graphics? The MediaInfo problem might be separate, an issue flagged by Driver Verifier but wasn't actually causing you BSODs under normal usage.