Blue Screen

[The X]

Hi, Sorry, this is my first post and i do not know where to post it in.

I get 'n bluescreen with this error when i startup:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.6
Locale ID: 7177

Additional information about the problem:
BCCode: 9f
BCP1: 00000003
BCP2: 84273030
BCP3: 84273030
BCP4: 849B7D28
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini020609-01.dmp
C:\Users\Barrie Eksteen\AppData\Local\Temp\WER-54023-0.sysdata.xml
C:\Users\Barrie Eksteen\AppData\Local\Temp\WER79E0.tmp.version.txt

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

Any advice?

 

[Sean Liming]

Was the error stop 9F? If so, you might have a bad driver in the system. Did
you create any custom driver components?

--
Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit

 

[The X]

Yes it is 9F

No, didn't create cutom driver.

How can I eliminate to see what driver is causing the problem?

 

[The X]

Yes it is a 9F error

No didn't create a custom driver component

Is there anyway I can eliminate to see which driver the faulty one is?

 

[Sean Liming]

The only guess is to turn off some hardware in BIOS and see what fails.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit

 

[Srikanth Kamath [MSFT]]

For Bluescreen issues - analyzing the dump will , almost always, pin point
the culprit driver.

1. Install windbg
(http://www.microsoft.com/whdc/devtools/debugging/default.mspx)

2. Set the symbol path to Microsoft public symbol server
(http://www.microsoft.com/whdc/devtools/debugging/debugstart.mspx#a)

3. "!analyze -v" will do the prilimnary analysis for you.

If you need more bluescreen troubleshooting tips - please refer (Support
WebCast: Basic "Blue Screen" Error Troubleshooting -
http://support.microsoft.com/kb/325011)


If none of this works, contact MS product support and have them file a bug.

Thanks
Srikanth