BSOD two days in a row

[l Thomas l]

Weird, it was the same type of blue screen twice in a row. I just got a new WD Passport so I don't know if that has anything to do with it. Once was when I was in the middle of backing up my old external to the new WD Passport. This time I wasn't doing anything but browsing with a lot of windows open. The last time I had been browsing with a lot of windows open too. I have Opera. I think I had Flash sites open both times, which has caused me problems before. Never blue screen, just usually browser crashes. I'm pretty sure I have the latest Flash. Running Vista SP1 Business. It's a Dell Vostro I haven't made any modifications to or even opened the case.

It's weird usually blue screens will appear, let me read it, and then I have to shut down manually. (Well haven't had many on this computer but I mean in general) But these just started by the monitor going blank, an obvious glitch with some random noise with a blank white screen. Then quickly go to the blue screen, then it says starting physical memory dump, then completes, then shuts down, all very quickly.

Here's the error message:

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

Additional information about the problem:
BCCode: 101
BCP1: 00000031
BCP2: 00000000
BCP3: 803D1120
BCP4: 00000001
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini072810-01.dmp
C:\Users\User\AppData\Local\Temp\WER-44865-0.sysdata.xml
C:\Users\User\AppData\Local\Temp\WERE9D1.tmp.version.txt

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

The files don't really have any information except for my system information as far as I can tell.

Thanks

 

[RebateMonger]

I found a couple of other posters who had identical Error codes. An analysis of one of their dump files gave the error details:

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts.

Arg1: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 803d1120, The PRCB address of the hung processor.
Arg4: 00000001, 0.

As to solutions, one person on Experts-Exchange claimed that removing one memory module fixed his/her BSOD problem that had given the same error codes.

 

[VinDSL]

It's a Dell Vostro I haven't made any modifications to or even opened the case.[...]

Sorry for being rudimentary, but the above comments made me think...

Have you blown the dirt out of your lappy lately?

Last summer, a friend asked me if I could fix his Toshy. It would run for a while, then blue-screen.

Long story short: His lappy looked like a lawnmower inside, from using it on his lap, on the bed, the couch, the kitchen table, et cetera.

When summer arrived, his Toshy said, "FU buddy!" LoL!

Cooling is V marginal on portables, and "weird" things happen when they accumulate dust bunnies.

Just saying... :hmm:

 

[l Thomas l]

I found a couple of other posters who had identical Error codes. An analysis of one of their dump files gave the error details:

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts.

Arg1: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 803d1120, The PRCB address of the hung processor.
Arg4: 00000001, 0.

As to solutions, one person on Experts-Exchange claimed that removing one memory module fixed his/her BSOD problem that had given the same error codes.

Hmm a memory module as in RAM? Well I'm pretty sure all my 2GB of RAM is in one stick.

It's actually a desktop Vostro, but yeah I haven't really vacuumed it in the year that I've had it, so I'll do that.

 

[NoQuarter]

Run memtest86+ on it, and download your hard drive manufacturer's hard drive test suite. Usually prebuilts use Seagate hard drives.