About blue screen
Recently i faced a problem in my system that suddenly a blue screen appeared , then iwas unable todo anything without restarting it.I tried to find the reason for that blue screen in event viewer , it showed the bellow error.Event Type:ErrorEvent Source:System ErrorEvent Category:(102)Event ID:1003Date:5/26/2009User:N/ADescription:Error code 1000000a, parameter1 00000026, parameter2 d0000002, parameter3 00000001, parameter4 80a603de. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Data:0000: 53 79 73 74 65 6d 20 45 System E0008: 72 72 6f 72 20 20 45 72 rror Er0010: 72 6f 72 20 63 6f 64 65 ror code0018: 20 31 30 30 30 30 30 30 10000000020: 61 20 20 50 61 72 61 6d a Param0028: 65 74 65 72 73 20 30 30 eters 000030: 30 30 30 30 32 36 2c 20 000026, 0038: 64 30 30 30 30 30 30 32 d00000020040: 2c 20 30 30 30 30 30 30 , 0000000048: 30 31 2c 20 38 30 61 36 01, 80a60050: 30 33 64 65 03de Event Type:WarningEvent Source:USER32Event Category:NoneEvent ID:1076Date:5/26/2009Description:The reason supplied by user SBVRaja for the last unexpected shutdown of this computer is: System Failure: Stop errorReason Code: 0x805000fBug ID: Bugcheck String: 0x1000000a (0x00000026, 0xd0000002, 0x00000001, 0x80a603de)Comment: 0x1000000a (0x00000026, 0xd0000002, 0x00000001, 0x80a603de) For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Data:0000: 0f 00 05 08 .... when i tried to open memory dump for rootcause, it showed the below error*** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************* WARNING: Unable to verify timestamp for NDIS.sys*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys*** WARNING: Unable to verify timestamp for b57xp32.sys*** ERROR: Module load completed but symbols could not be loaded for b57xp32.sys**************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ************************************************************************************************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ **********************************************************************Probably caused by : b57xp32.sys ( b57xp32+9205 ) Followup: MachineOwnerCan anybody please tell me thecause for the above problem so that i can fix any hotfix to resolve that problem in future.
May 26th, 2009 3:15pm

hi there,In order to troubleshoot the issue you will be required to provide us the complete memory dump for analysis, it will be difficult to diagonize with the minimum info above you have provided. It points to b57xp32.sys but this module might call other module which might be real suspect of the issue. microsoft employee from this forum will be sending you the link to upload the dump. Meanwhile i would appreciate if you could capture the dump ready for analysis.also you can check what is b57xp32.sys and who is the vendor of it ? and try upgrading the driver for the specific platform.sainath windows driver development.
Free Windows Admin Tool Kit Click here and download it now
May 26th, 2009 7:53pm

Hi, Please understand that to troubleshoot the blue screen issues, we usually need to perform debugging. However, in this forum, we do not provide debugging support. If you would like to perform debugging, please contact Microsoft Customer Support Service (CSS). To obtain the phone numbers for specific technology request, please refer to the website listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS If you are outside the US, please refer to http://support.microsoft.com for regional support phone numbers. Tim Quan - MSFT
May 27th, 2009 5:01am

Thanks for your response Sainath,But there i provided u full memory dump , i think in that dump it showed some problem( Your debugger is not using the correct symbols). I think because of this it was unable to give what the exact problem is.
Free Windows Admin Tool Kit Click here and download it now
May 27th, 2009 12:50pm

Hello Raja, If you see the dump correctly it states "Probably caused by : b57xp32.sys" b57xp32.sys is driver for Broadcom Network Interface Cardhttp://www.broadcom.com/support/ethernet_nic/faq_drivers.php.In order to sollve your problem please download the new updated driversandmonitor your server for some days.Thanks and Hope it helpshttp://technetfaqs.wordpress.com
May 27th, 2009 12:57pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics