I have a Toshiba Satellite A135-S4407 running pre-installed Windows Vista
with SP1 T2060 2GB. I just got it to start-up again after several messages of
Stop, IRQL, NTFS errors by using repair on OS disk. I am getting several more
errors now and will only run in safe mode.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: c2
BCP1: 00000007
BCP2: 0000110B
BCP3: 32503239
BCP4: B08D61D8
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini082208-02.dmp
C:\Users\DeLunatic\AppData\Local\Temp\WER-77048-0.sysdata.xml
C:\Users\DeLunatic\AppData\Local\Temp\WERF8DE.tmp.version.txt

I heard many fear this PC due to either motherboard or video-card issues. I
see no hope for this Laptop as it will soon make a YouTube video of being
abliterated with some flashy pyrotechnics. Can anyone help the helpless?!

Sincerly,
Losing It 2008

On Fri, 22 Aug 2008 21:29:00 -0700, DeLunatic
<DeLunatic@discussions.microsoft.com> wrote:
[color=blue]
>I have a Toshiba Satellite A135-S4407 running pre-installed Windows Vista
>with SP1 T2060 2GB. I just got it to start-up again after several messages of
>Stop, IRQL, NTFS errors by using repair on OS disk. I am getting several more
>errors now and will only run in safe mode.[/color]

You are probably seeing the results of developing hardware issues.

Have you tried starting with last known configuration that worked?

Have you tried doing System Restore?

Do you have a full system backup that you can restore from?

Do you have a recovery DVD or a hidden recovery partition that you can
use to return the computer to out-of-the-box condition?

Not one of those steps addresses the actual issue, they merely disable
proper reporting of it. In fact, those steps merely try to mask the fact
that there is a problem. The cause needs to be addressed, not hidden.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
[url]http://mvp.support.microsoft.com/[/url]
Windows help - [url]www.rickrogers.org[/url]
My thoughts [url]http://rick-mvp.blogspot.com[/url]

"rajinisback" <guest@unknown-email.com> wrote in message
news:f6bdc1c6ce5bbefafa34a5deaee7eea1@nntp-gateway.com...[color=blue]
>
> Hi DeLunatic,
>
> There are several methods to resolve this issue. Follow the
> instructions in the first section. If the problem is not resolved,
> proceed to the next
> section.
>
> I. Resize the Swap File
> When a serious error occurs, by default the system dumps the system
> state to the swap file for later retrieval. However, it is possible that
> the swap file is not properly cleaned up and the system thinks that it
> is rebooting from a crash. To resolve this, you will need to resize the
> swap file:
>
> 1. Click the Start button.
> 2. Right click the My 'Computer' ([url]http://www.ozzu.com/#[/url]) menu option,
> and then click Properties on the context menu that appears.
> 3. Click the Advanced tab, and then click the Settings button in the
> Performance section. The Performance Options window appears.
> 4. Click the Advanced tab, and then click the Change button in the
> Virtual Memory section. The Virtual memory window appears.
> 5. Click Custom Size, and then record the Initial Size and Maximum
> Size.
> 6. Set the Initial Size and Maximum Size to the same value as the
> amount of RAM that is installed in the system.
> 7. Click Set and then click OK. The system will advise you to restart
> the computer.
> 8. Click OK.
> 9. Click OK at the Performance Options window. The system prompts you
> to restart the computer.
> 10. Click Yes.
>
> After the system has restarted, repeat the above steps to restore the
> original Initial Size and Maximum Size values for your swap file.
>
> II. Delete the Minidump Files and the Sysdata.xml File
>
> When a serious error occurs, by default the system writes out a
> miniature memory dump along with an XML description of the system status
> (which notes the program at fault and other pertinent system 'data'
> ([url]http://www.ozzu.com/#[/url])) that can be uploaded to 'Microsoft'
> ([url]http://www.ozzu.com/#[/url]). If this data is not correctly closed out, the
> system may present a Serious Error screen upon boot. To resolve this
> problem, perform
> the following steps:
>
> 1. Click the Start button.
> 2. Right click the My Computer icon, and then click Explore on the
> context menu that appears.
> 3. Browse to the c:\Windows\Minidump directory.
> 4. Delete everything located in this directory.
>
> NOTE : You will need to be able to view hidden and 'system files'
> ([url]http://www.ozzu.com/#[/url]) and the system should not be hiding protected
> 'operating system' ([url]http://www.ozzu.com/#[/url]) files.
>
> 5. Browse to the c:\Documents and Settings folder.
> 6. Search for the following file: sysdata.xml file.
> 7. Delete all instances (you may find more than one) of this file.
> 8. Click the Start button, click Turn off the computer, and then click
> Restart.
>
> III. Disable the Automatically Restart setting
>
> This attacks the same class of Serious Errors that resizing the swap
> file fixes, but it tries to ensure that the errors do not happen
> beforehand.
> However, this does not help to rid the persistent Serious 'Error
> message' ([url]http://www.ozzu.com/#[/url]) after the fact.
>
> 1. Click the Start button.
> 2. Right click the My Computer icon, and then click Properties on the
> context menu that appears.
> 3. Click the Advanced tab and then click the Settings button in the
> Start-up and Recovery section.
> 4. Click to remove the check next to Automatically Restart checkbox and
> then click OK.
> 5. Click OK. The system will no longer automatically restart after a
> Serious Error message appears.
>
> IV. Disable Memory Dumps\
>
> This option totally disables memory dumps altogether, which may help
> fix some persistent Serious Error messages. To disable memory dumps,
> perform the following steps:
>
> 1. Click the Start button
> 2. Right click the My Computer icon, and then click Properties on the
> context menu that appears.
> 3. Click the Advanced tab, and then click the Settings button in the
> Start-up and Recovery section.
> 4. In the Write debugging information tab, click to select (none) and
> then click OK.
> 5. Click OK.
>
>
> --
> rajinisback
>
> RAJ :P
> *Please give Karma if I helped you fix the issue. Thanks :)*[/color]

Hi,

BCCode 0xC2 is usually driver related. If the system is new, you should
first contact Toshiba support to engage warranty support. If not, then send
this file to me at rick_at_mvps_dot_org with a subject line of 'per req':
[color=blue]
> C:\Windows\Minidump\Mini082208-02.dmp[/color]

I'll see if it contains information necessary to tell you which driver file
is the problem. Most likely a file is corrupt, incompatible, or missing and
the driver will need to be replaced or updated. There is also a chance that
it may be in conflict with another bit of software on the system.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
[url]http://mvp.support.microsoft.com/[/url]
Windows help - [url]www.rickrogers.org[/url]
My thoughts [url]http://rick-mvp.blogspot.com[/url]

"DeLunatic" <DeLunatic@discussions.microsoft.com> wrote in message
news:74A97600-35AB-499D-A5B3-F817B3EDB776@microsoft.com...[color=blue]
>I have a Toshiba Satellite A135-S4407 running pre-installed Windows Vista
> with SP1 T2060 2GB. I just got it to start-up again after several messages
> of
> Stop, IRQL, NTFS errors by using repair on OS disk. I am getting several
> more
> errors now and will only run in safe mode.
> Problem signature:
> Problem Event Name: BlueScreen
> OS Version: 6.0.6001.2.1.0.768.3
> Locale ID: 1033
>
> Additional information about the problem:
> BCCode: c2
> BCP1: 00000007
> BCP2: 0000110B
> BCP3: 32503239
> BCP4: B08D61D8
> OS Version: 6_0_6001
> Service Pack: 1_0
> Product: 768_1
>
> Files that help describe the problem:
> C:\Windows\Minidump\Mini082208-02.dmp
> C:\Users\DeLunatic\AppData\Local\Temp\WER-77048-0.sysdata.xml
> C:\Users\DeLunatic\AppData\Local\Temp\WERF8DE.tmp.version.txt
>
> I heard many fear this PC due to either motherboard or video-card issues.
> I
> see no hope for this Laptop as it will soon make a YouTube video of being
> abliterated with some flashy pyrotechnics. Can anyone help the helpless?!
>
> Sincerly,
> Losing It 2008[/color]

"rajinisback" <guest@unknown-email.com> wrote in message
news:f6bdc1c6ce5bbefafa34a5deaee7eea1@nntp-gateway.com...[color=blue]
>
> Hi DeLunatic,
>
> There are several methods to resolve this issue. Follow the
> instructions in the first section. If the problem is not resolved,
> proceed to the next
> section.
>
> I. Resize the Swap File
> When a serious error occurs, by default the system dumps the system
> state to the swap file for later retrieval. However, it is possible that
> the swap file is not properly cleaned up and the system thinks that it
> is rebooting from a crash. To resolve this, you will need to resize the
> swap file:
>
> 1. Click the Start button.
> 2. Right click the My 'Computer' ([url]http://www.ozzu.com/#[/url]) menu option,
> and then click Properties on the context menu that appears.
> 3. Click the Advanced tab, and then click the Settings button in the
> Performance section. The Performance Options window appears.
> 4. Click the Advanced tab, and then click the Change button in the
> Virtual Memory section. The Virtual memory window appears.
> 5. Click Custom Size, and then record the Initial Size and Maximum
> Size.
> 6. Set the Initial Size and Maximum Size to the same value as the
> amount of RAM that is installed in the system.
> 7. Click Set and then click OK. The system will advise you to restart
> the computer.
> 8. Click OK.
> 9. Click OK at the Performance Options window. The system prompts you
> to restart the computer.
> 10. Click Yes.
>
> After the system has restarted, repeat the above steps to restore the
> original Initial Size and Maximum Size values for your swap file.
>
> II. Delete the Minidump Files and the Sysdata.xml File
>
> When a serious error occurs, by default the system writes out a
> miniature memory dump along with an XML description of the system status
> (which notes the program at fault and other pertinent system 'data'
> ([url]http://www.ozzu.com/#[/url])) that can be uploaded to 'Microsoft'
> ([url]http://www.ozzu.com/#[/url]). If this data is not correctly closed out, the
> system may present a Serious Error screen upon boot. To resolve this
> problem, perform
> the following steps:
>
> 1. Click the Start button.
> 2. Right click the My Computer icon, and then click Explore on the
> context menu that appears.
> 3. Browse to the c:\Windows\Minidump directory.
> 4. Delete everything located in this directory.
>
> NOTE : You will need to be able to view hidden and 'system files'
> ([url]http://www.ozzu.com/#[/url]) and the system should not be hiding protected
> 'operating system' ([url]http://www.ozzu.com/#[/url]) files.
>
> 5. Browse to the c:\Documents and Settings folder.
> 6. Search for the following file: sysdata.xml file.
> 7. Delete all instances (you may find more than one) of this file.
> 8. Click the Start button, click Turn off the computer, and then click
> Restart.
>
> III. Disable the Automatically Restart setting
>
> This attacks the same class of Serious Errors that resizing the swap
> file fixes, but it tries to ensure that the errors do not happen
> beforehand.
> However, this does not help to rid the persistent Serious 'Error
> message' ([url]http://www.ozzu.com/#[/url]) after the fact.
>
> 1. Click the Start button.
> 2. Right click the My Computer icon, and then click Properties on the
> context menu that appears.
> 3. Click the Advanced tab and then click the Settings button in the
> Start-up and Recovery section.
> 4. Click to remove the check next to Automatically Restart checkbox and
> then click OK.
> 5. Click OK. The system will no longer automatically restart after a
> Serious Error message appears.
>
> IV. Disable Memory Dumps\
>
> This option totally disables memory dumps altogether, which may help
> fix some persistent Serious Error messages. To disable memory dumps,
> perform the following steps:
>
> 1. Click the Start button
> 2. Right click the My Computer icon, and then click Properties on the
> context menu that appears.
> 3. Click the Advanced tab, and then click the Settings button in the
> Start-up and Recovery section.
> 4. In the Write debugging information tab, click to select (none) and
> then click OK.
> 5. Click OK.[/color]


What a load of nonsense. The swap file (page file) is not the same as the
crash dump file, and disabling them, and the minidumps is just going to make
problems harder to discover. What's with all the [url]www.ozzu.com[/url] links?

ss.

Thank You Mr. Rogers. I'm going to send both my dmp files to you tonight. I'm
on business travel and my warranty just expired. (my luck) I recall my laptop
being current with all updates and drivers so I probably have to uninstall
and/or re-install a driver. So far uninstalling stuff helps me continue
working sometimes. Just wondering is there some magical place that describes
BCCodes?!

Thanks for the quick responses from all. I'm sure glad I found this place.

"Rick Rogers" wrote:
[color=blue]
> Hi,
>
> BCCode 0xC2 is usually driver related. If the system is new, you should
> first contact Toshiba support to engage warranty support. If not, then send
> this file to me at rick_at_mvps_dot_org with a subject line of 'per req':
>[color=green]
> > C:\Windows\Minidump\Mini082208-02.dmp[/color]
>
> I'll see if it contains information necessary to tell you which driver file
> is the problem. Most likely a file is corrupt, incompatible, or missing and
> the driver will need to be replaced or updated. There is also a chance that
> it may be in conflict with another bit of software on the system.
>
> --
> Best of Luck,
>
> Rick Rogers, aka "Nutcase" - Microsoft MVP
> [url]http://mvp.support.microsoft.com/[/url]
> Windows help - [url]www.rickrogers.org[/url]
> My thoughts [url]http://rick-mvp.blogspot.com[/url]
>
> "DeLunatic" <DeLunatic@discussions.microsoft.com> wrote in message
> news:74A97600-35AB-499D-A5B3-F817B3EDB776@microsoft.com...[color=green]
> >I have a Toshiba Satellite A135-S4407 running pre-installed Windows Vista
> > with SP1 T2060 2GB. I just got it to start-up again after several messages
> > of
> > Stop, IRQL, NTFS errors by using repair on OS disk. I am getting several
> > more
> > errors now and will only run in safe mode.
> > Problem signature:
> > Problem Event Name: BlueScreen
> > OS Version: 6.0.6001.2.1.0.768.3
> > Locale ID: 1033
> >
> > Additional information about the problem:
> > BCCode: c2
> > BCP1: 00000007
> > BCP2: 0000110B
> > BCP3: 32503239
> > BCP4: B08D61D8
> > OS Version: 6_0_6001
> > Service Pack: 1_0
> > Product: 768_1
> >
> > Files that help describe the problem:
> > C:\Windows\Minidump\Mini082208-02.dmp
> > C:\Users\DeLunatic\AppData\Local\Temp\WER-77048-0.sysdata.xml
> > C:\Users\DeLunatic\AppData\Local\Temp\WERF8DE.tmp.version.txt
> >
> > I heard many fear this PC due to either motherboard or video-card issues.
> > I
> > see no hope for this Laptop as it will soon make a YouTube video of being
> > abliterated with some flashy pyrotechnics. Can anyone help the helpless?!
> >
> > Sincerly,
> > Losing It 2008[/color]
>
>[/color]