Blue screen of Death

[vasujain]

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7100.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1000008e
BCP1: C0000005
BCP2: 8FBC68A2
BCP3: B423B9A0
BCP4: 00000000
OS Version: 6_1_7100
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
F:\Windows\Minidump\070709-33353-01.dmp
F:\Users\Vasu\AppData\Local\Temp\WER-63929-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
F:\Windows\system32\en-US\erofflps.txt

This is the error messgae i got when my computer Restarted...its running Windows 7 Built 7100

What can be the reason

 

[Lordbob75]

Vasujain, this looks to be a problem with the MBR. Try a repair install.

~Lordbob

 

[vasujain]

my laptop is brand new...hardly 50 days since i have purchased it.dell studio 15.du u still reconsider getting MBR repaired?

 

[Lordbob75]

Yeah. It needs to be fixed. Since you are dual booting, you may want to try the repair. If you installed Ubuntu last, like I did, it screws with the startup screen.

~Lordbob

 

[vasujain]

although i have a dual boot but it is of windows Vista Premium and Seven Ultimate.
No ubuntu.
Are there any possible reasons for corruption of MBR?

 

[Lordbob75]

although i have a dual boot but it is of windows Vista Premium and Seven Ultimate.
No ubuntu.
Are there any possible reasons for corruption of MBR?

Your specs say Ubuntu.
You may have installed wrong or something, but I can't think of anything. Have you tried the repair yet?

~Lordbob

 

[usasma]

Here is a brief description of the error message: Troubleshooting Windows STOP Messages
The first parameter (c0000005) indicates that the error occurred while accessing memory (not necessarily a problem with your RAM). Most times that I've seen this error it's been due to a corrupted driver.

Zip up the files located at F:\Windows\Minidump\ and upload the .zip file with your next post. We'll take a look at them to see if they tell us anything significant.

 

[zigzag3143]

Bsod

This is the error messgae i got when my computer Restarted...its running Windows 7 Built 7100

What can be the reason

It would help a great deal if you were to go to thr dmp files and zip them and upload to us.

You are looking for the files that end in dmp. and the path is shown in your message

Hope this helps

Ken

 

[vasujain]

yeah i wud upload the same...meanwhile my specs says ubuntu as i used it earlier....i m nt using it now....hey is there any way the reason could be that i havent shutted down my laptop from last over 50 hours...?

 

[vasujain]

In minidump i have 4 .dmp files.
i remmber atleast 3 BsOD in the past time,that can be 4 too.so does it mean evry time i get a BSD it has a dump in there?

anywayz i have attached the latest dump file...if anyone has problem opening it...plzz du change the file ext to .rar and then extract....sorry guyz i dont hav winzip installed

the one with smaller size is the latest dump and rest 3 are older dumps

 

[Jacee]

Download 7zip and use that:
7-Zip

 

[vasujain]

Jacee i have already uploaded the files w/o any problems and they are extracted evn when i have changed the extension to zip from rar.

anywayz i would downoad the same as wlll

 

[usasma]

With Vista, just right click on the files and select the Send to option.
Then select the "Compressed (zipped) folder" option and it'll zip it up for you.

Here's a listing of your older drivers:

rimmptsk.sys Wed Nov 16 21:28:31 2005 [B][URL="http://www.google.com/search?q=%22RICOH%20MMC%20Driver%22"]RICOH MMC Driver[/URL][/B]

The first dump file (from May 16, 2009) is due to Intel video drivers
The next one (June 11, 2009) is uncertain
The next one (July 5, 2009) is due to SPSYS.SYS - security processor driver for Windows
The last one (July 7, 2009) is due to OA008Ufd.sys (dated Sep 2008) - which is related to your Creative Camera

My first guess would be the video drivers, followed closely by the camera drivers. But the spsys.sys and the unknown errors have me also wondering if you may be infected. Try a couple of these free, online scanners: Free Online Malware Scan(s) (originally posted 09Mar08) - Vox

Here's a summary of the crash dumps:

*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7100.0.x86fre.winmain_win7rc.090421-1700
Debug session time: Sat May 16 04:23:46.629 2009 (GMT-4)
System Uptime: 0 days 10:37:51.252
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
*** WARNING: Unable to verify timestamp for igdkmd32.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7100.0.x86fre.winmain_win7rc.090421-1700
Debug session time: Thu Jun 11 12:01:54.709 2009 (GMT-4)
System Uptime: 0 days 3:33:52.332
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7100.0.x86fre.winmain_win7rc.090421-1700
Debug session time: Sun Jul  5 10:40:54.650 2009 (GMT-4)
System Uptime: 0 days 19:48:52.587
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 1000008E, {c0000005, 8, b2311794, 0}
Probably caused by : spsys.sys ( spsys+27d30 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7100.0.x86fre.winmain_win7rc.090421-1700
Debug session time: Tue Jul  7 10:35:23.052 2009 (GMT-4)
System Uptime: 1 days 15:28:05.675
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
*** WARNING: Unable to verify timestamp for OA008Ufd.sys
*** ERROR: Module load completed but symbols could not be loaded for OA008Ufd.sys
BugCheck 1000008E, {c0000005, 8fbc68a2, b423b9a0, 0}
Probably caused by : OA008Ufd.sys ( OA008Ufd+18a2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

 

[vasujain]

Usasma if u have figured out can you help me with a link that can help me upgrade my Video drivers.
I have purchased this laptop recently..studio 15 (Dell) i believe all the drivers are updated....i have a recent virus problem after which both 5,7 july errors might have come but i cleaned the virus.it actually was a trojan.it was KIllav.gen!A

So can you help me with this??i mean exactly what i must do now...

and one more thing i wud like to know how can i decode my dump files? and what all information can be extracted froom there....

 

[usasma]

At work we follow this procedure:
- test the hardware (and repair if needed)
- scan for viruses (and remove if needed)
- fix the OS

If you're confident about the hardware, then move on to the scans that I mentioned in my last post. For further assistance, please post over in the Security forums: System Security - Windows 7 Forums

You must be clean of viruses before we can fix the OS issues. Without that assurance any attempts at repairs will be futile.

As for the dump files, I've posted the essential information from them in my previous post. If you're interested in reading them, you can start with my post at the following link (there is a link at the bottom to another post where I describe what I do to analyze them): Diagnosing Bsod's (originally posted 02Oct08) - Vox