BSOD on L501x

[niqushortz]

I have a Dell XPS L501x, about 6 weeks old.... got a couple of BSODs and today i got an instant power off (instead of a BSOD).
Computer is under warranty but im out of the country for a couple of months, so please investigate my BSODs.... maybe its just a software issue not a hardware one.

Thanks.

 

[Jonathan_King]

Hello,

Start by uninstalling your nVidia graphics drivers, and installing fresh ones from here: Drivers - Download NVIDIA Drivers

Also, uninstall Daemon Tools, as it uses SPTD. When that is done, remove SPTD with this tool: http://www.duplexsecure.com/download/SPTDinst-v174-x64.exe

Finally, run driver verifier: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

...Summary of the dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Feb  8 17:48:20.457 2011 (UTC - 5:00)
System Uptime: 6 days 1:39:06.748
*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
Probably caused by : cdd.dll ( cdd+dc51 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  SC2.exe
FAILURE_BUCKET_ID:  X64_0x50_cdd+dc51
SystemProductName = XPS L501X  
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Feb  2 16:08:44.160 2011 (UTC - 5:00)
System Uptime: 0 days 2:10:17.705
Probably caused by : ntkrnlmp.exe ( nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  SC2.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26
SystemProductName = XPS L501X  
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Jan 30 09:53:33.228 2011 (UTC - 5:00)
System Uptime: 0 days 2:40:18.399
Probably caused by : ntkrnlmp.exe ( nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  SC2.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26
SystemProductName = XPS L501X  
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Jan 30 07:12:39.859 2011 (UTC - 5:00)
System Uptime: 1 days 3:59:41.777
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys - 
Probably caused by : win32k.sys ( win32k!memset+86b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!memset+86b
SystemProductName = XPS L501X  
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[niqushortz]

I did all the things u recommended to do, but after i activated Driver Verifier and rebooted, Windows locked up at the boot screen.

 

[Jonathan_King]

Hello,

Try rebooting again, and see if you can boot it. You may have to try several times.

 

[niqushortz]

I restarted, it booted up just fine. But after the lock-up i used "last known good configuration" to boot into Win, so i could write the post. I dont know if that changes anything...

 

[Jonathan_King]

Enter verifier /query into a command prompt; does it show a list of drivers being verified, or does it say "No drivers currently being verifier"?

 

[niqushortz]

No drivers verified

 

[Jonathan_King]

Enable driver verifier again, and reboot; keep rebooting until it lets you in. It may take several tries.

 

[niqushortz]

Ok..it started the 3rd time...now query shows a long list of drivers being verified. What next?

 

[Jonathan_King]

Keep the computer running; see if it BSODs. If it does, upload a new jcgriff2 report.

 

[niqushortz]

Should the Verifier cause system slow-down? And if so, how long does it has to run, cause audio (even windows sounds) is distorted (chopped) by the slowdown.

 

[Jonathan_King]

Verifier does use more resources; a performance hit is not uncommon.

Run it for maybe 24 or 36 hours, unless it BSODs before then.