Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD few times a day Need Help


  • Please log in to reply
6 replies to this topic

#1 rrdavis

rrdavis

  • Members
  • 41 posts
  • OFFLINE
  •  
  • Local time:01:36 AM

Posted 13 April 2012 - 07:20 PM

Hi,

I have a windows 7 SP1 32bit Dell laptop that BSOD a few times a day lately.
Here are the specs: http://speccy.piriform.com/results/4mHesVLQWVEhdV6n17h5mJT


I did the following:

Please follow the instructions: BSOD Posting Instructions: Windows 7 - Vista
(Note: When you run BSOD_Windows7_Vista_v2.64_jcgriff2_.exe, it will also run autoruns.exe ... and both need to be in the same location!)

... with one exception in the following line:
"4. Zip up the entire output folder + PERFMON and attach the zip file to your next post."

The BC forums will allow a total attachment size of only 512 kb (and what you need to attach will exceed this limit). Please upload the zip file to a file sharing website of your choice and and post a link to it in this thread so that we can access your uploaded zip file. I will have a look at the contained information and see if I can shed some light on your BSOD issue.

I posted the files at http://www.box.com/s/185e98c7a8e8ce164f8b

Thanks for your help

Ryan

BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:04:36 AM

Posted 14 April 2012 - 06:00 AM

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

#3 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:06:36 PM

Posted 14 April 2012 - 06:45 AM

I have started to review the information provided, but I am going to have to continue tomorrow. The minidumps (in total, 41 ... with 37 over the past 12 months) are not overly helpful. The event logs are crammed with continual errors though.

Persistent errors in Application event log:

4/13/2012 7:42 PM Application Error Faulting application name: CALMAIN.exe ...

4/13/2012 4:51 PM Windows Error Reporting Fault bucket , type 0
Event Name: LiveKernelEvent
 ...

4/13/2012 4:51 PM Windows Error Reporting Fault bucket , type 0
Event Name: AppTermFailureEvent
 ...


PERFMON reports:

Abnormally Stopped System Services

A service is reported as having an unexpected error code
One or more services has failed. The service did not stop gracefully, suggesting the service may have crashed or one of its components stopped in an unsupported way.
Service exited with code not equal to 0 or 1077
Restart the service
Top: of 2
Service
CCALib8

Display Name: Canon Camera Access Library 8
Exit Code: 1067
Service Name: CCALib8
Path: C:\Program Files\Canon\CAL\CALMAIN.exe
Service Code: 0
Started: False
State: Stopped

For now, please disable the service: Canon Camera Access Library 8 (CCALib8)
Run the autoruns application (you will find it in Documents, where you put it earlier).
Under HKCU\Software\Microsoft\Windows\CurrentVersion\Run, un-check the box beside:
  • GameXN
  • GameXN (news)
  • GameXN (update)
Let's see if that helps any to start with.

========================
BSOD BUGCHECK SUMMARY: 7 minidumps this month
................................................................
Loading Dump File [C:\CactusIsland\rrdavis_BC\Windows7_Vista_jcgriff2\041112-24726-01.dmp]
Built by: 7601.17727.x86fre.win7sp1_gdr.111118-2330
Debug session time: Thu Apr 12 03:03:19.702 2012 (UTC + 10:00)
System Uptime: 0 days 0:02:17.294
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: GameXNGO.exe
FAILURE_BUCKET_ID: 0x8E_ANALYSIS_INCONCLUSIVE
Bugcheck code 1000008E
Arguments c0000005 00000068 bda47bd4 00000000
BiosVersion = A23
BiosReleaseDate = 09/27/2011
SystemManufacturer = Dell Inc.
SystemProductName = Latitude E4300
CPUID: "Intel® Core™2 Duo CPU P9600 @ 2.53GHz"
MaxSpeed: 2530
CurrentSpeed: 2527
................................................................
Loading Dump File [C:\CactusIsland\rrdavis_BC\Windows7_Vista_jcgriff2\041012-25568-01.dmp]
Built by: 7601.17727.x86fre.win7sp1_gdr.111118-2330
Debug session time: Wed Apr 11 05:35:37.064 2012 (UTC + 10:00)
System Uptime: 0 days 0:01:12.672
Probably caused by : ntkrpamp.exe ( nt!PspExitThread+10a )
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: GameXNGO.exe
FAILURE_BUCKET_ID: 0x8E_nt!PspExitThread+10a
Bugcheck code 1000008E
Arguments c0000005 830ba365 bcc17bd4 00000000
................................................................
Loading Dump File [C:\CactusIsland\rrdavis_BC\Windows7_Vista_jcgriff2\040312-30466-01.dmp]
Built by: 7601.17727.x86fre.win7sp1_gdr.111118-2330
Debug session time: Tue Apr 3 23:31:16.154 2012 (UTC + 10:00)
System Uptime: 0 days 0:01:31.746
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: GameXNGO.exe
FAILURE_BUCKET_ID: 0x8E_ANALYSIS_INCONCLUSIVE
Bugcheck code 1000008E
Arguments c0000005 00000074 bc89bbd4 00000000
................................................................
Loading Dump File [C:\CactusIsland\rrdavis_BC\Windows7_Vista_jcgriff2\040312-29686-01.dmp]
Built by: 7601.17727.x86fre.win7sp1_gdr.111118-2330
Debug session time: Tue Apr 3 23:28:58.918 2012 (UTC + 10:00)
System Uptime: 0 days 0:01:32.526
Probably caused by : ntkrpamp.exe ( nt!PsExitSpecialApc+22 )
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: GameXNGO.exe
FAILURE_BUCKET_ID: 0x8E_nt!PsExitSpecialApc+22
Bugcheck code 1000008E
Arguments c0000005 00000068 be4f3bd4 00000000
................................................................
Loading Dump File [C:\CactusIsland\rrdavis_BC\Windows7_Vista_jcgriff2\040312-26956-01.dmp]
Built by: 7601.17727.x86fre.win7sp1_gdr.111118-2330
Debug session time: Tue Apr 3 23:35:12.714 2012 (UTC + 10:00)
System Uptime: 0 days 0:01:23.322
Probably caused by : ntkrpamp.exe ( nt!PsExitSpecialApc+22 )
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
PROCESS_NAME: GameXNGO.exe
FAILURE_BUCKET_ID: 0x8E_nt!PsExitSpecialApc+22
Bugcheck code 1000008E
Arguments c0000005 00000000 bda2fbd4 00000000
................................................................
Loading Dump File [C:\CactusIsland\rrdavis_BC\Windows7_Vista_jcgriff2\040312-24445-01.dmp]
Built by: 7601.17727.x86fre.win7sp1_gdr.111118-2330
Debug session time: Tue Apr 3 23:33:23.315 2012 (UTC + 10:00)
System Uptime: 0 days 0:01:40.923
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: GameXNGO.exe
FAILURE_BUCKET_ID: 0x8E_ANALYSIS_INCONCLUSIVE
Bugcheck code 1000008E
Arguments c0000005 00000068 9b30fbd4 00000000
................................................................
Loading Dump File [C:\CactusIsland\rrdavis_BC\Windows7_Vista_jcgriff2\040212-22276-01.dmp]
Built by: 7601.17727.x86fre.win7sp1_gdr.111118-2330
Debug session time: Tue Apr 3 01:13:34.105 2012 (UTC + 10:00)
System Uptime: 0 days 0:01:28.572
Probably caused by : ntkrpamp.exe ( nt!PspExitThread+aa )
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: GameXNGO.exe
FAILURE_BUCKET_ID: 0x8E_nt!PspExitThread+aa
Bugcheck code 1000008E
Arguments c0000005 83082305 b9683bd4 00000000
BiosVersion = A23
BiosReleaseDate = 09/27/2011
SystemManufacturer = Dell Inc.
SystemProductName = Latitude E4300
CPUID: "Intel® Core™2 Duo CPU P9600 @ 2.53GHz"
MaxSpeed: 2530
CurrentSpeed: 2527
................................................................

Edited by AustrAlien, 14 April 2012 - 06:48 AM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#4 rrdavis

rrdavis
  • Topic Starter

  • Members
  • 41 posts
  • OFFLINE
  •  
  • Local time:01:36 AM

Posted 16 April 2012 - 05:29 PM

Thanks!

I uploaded the output of bluescreen view to my box: http://www.box.com/s/185e98c7a8e8ce164f8b

I also removed the canon service and GameXNGo registry.

AusrAlien, What did you use to generate your output? I tried loading the windows debuging software with the correct symbols and it never output the same info you have. Curious.

I tried running Driver verify. The computer will BSOD on reboot but no minidumps are generated... followed these instructions: http://www.techsupportforum.com/forums/f299/driver-verifier-windows-7-and-vista-bsod-related-473665.html


Hopefully this will do it. I will keep you posted.

#5 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:06:36 PM

Posted 16 April 2012 - 05:56 PM

Re: "I tried running Driver verify. The computer will BSOD on reboot but no minidumps are generated"
Clearly something is not right there. Try disabling automatic restart and see if you are able to see the BSOD error messages. If so, please let me know what you see.

How To Disable the Automatic Restart on System Failure in Windows 7
Posted Image

Record the error message details (contained in the areas outlined in red, in the above example image), and post in your reply.

Re: WinDbg output
Normally, I copy/paste the following line of commands:
!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck;!peb;!sysinfo cpuinfo;!sysinfo machineid; !sysinfo cpuspeed; !sysinfo smbios
If you are using the same version of WinDbg, and have it set up correctly, you should see exactly what I see. In the summary, I have removed most of the output.

WinDbg output for the most recent minidump:
Spoiler

Edited by AustrAlien, 16 April 2012 - 06:02 PM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#6 rrdavis

rrdavis
  • Topic Starter

  • Members
  • 41 posts
  • OFFLINE
  •  
  • Local time:01:36 AM

Posted 16 April 2012 - 06:34 PM

Thanks for the command line!

I get a device driver attempting to corrupt the sytstem has been caught. The faulty driver currently on the kernel stack must be replaced with a working version.

......

Stop: 0x000000C4 (0x000000E3, 0x8DE76862, 0x000DF5B0, 0x00000000)

vsdatant.sys Address 8DE76862 base at 8DE2D000, Datestamp 4dc3877d

collecting data for crash dump...
Initializing disk for crash dump ....

####################


That's it.

#7 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:06:36 PM

Posted 16 April 2012 - 06:48 PM

Re: "... a device driver attempting to corrupt the sytstem has been caught. .... Stop: 0x000000C4"
That's a VERIFIER_ENABLED crash: Good!

vsdatant.sys belongs to ZoneAlarm.

Un-install ZoneAlarm.
  • Re-start the computer.
  • Ensure that the Windows firewall is enabled.
Now, what problems are we left with?

Edited by AustrAlien, 16 April 2012 - 06:51 PM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users