Blue Screen of Death runnig a Batch File on Vista

I have been running multiple Microsoft Vista 32-bit SP1 Ultimate laptops
(Dell D820/D830/E6500) for some time now on a 2003 SP2 native domain. Within
the past week all of a sudden when a batch file is run the Vista machines
will freeze and will then go to a blue screen of death with code 0x00000008
0x803D3130 0x00000000 0x00000000 and reboots. Doesn't matter if you are an
administrator or domain user. I am inspecting th event log, but haven't
found any leads.

Any ideas

go into system properties advanced and uncheck the box that allows automatic
reboot. You will then get an error message you can use to troubleshoot.

"Jeff" <> wrote in message
news:10EFC082-F615-4B79-B1E8-...
>I have been running multiple Microsoft Vista 32-bit SP1 Ultimate laptops
> (Dell D820/D830/E6500) for some time now on a 2003 SP2 native domain.
> Within
> the past week all of a sudden when a batch file is run the Vista machines
> will freeze and will then go to a blue screen of death with code
> 0x00000008
> 0x803D3130 0x00000000 0x00000000 and reboots. Doesn't matter if you are
> an
> administrator or domain user. I am inspecting th event log, but haven't
> found any leads.
>
> Any ideas

Hi Jeff,

any solution yet? I have a Dell XPS M1710 with Vista Ultimate and Office
2007, I have been getting the exact same error code and BSOD for the last 3
weeks. My desktop also just did the BSOD today for the very first time.

That error code only comes on the restart after another BSOD with 7F,
(0x00000008,0x81056000,0x00000000,0x00000000)

Any ideas out there, I have called microsoft but they hang up on you after
8pm when you have been speaking with them for 30mins!)

"Jeff" wrote:

> I have been running multiple Microsoft Vista 32-bit SP1 Ultimate laptops
> (Dell D820/D830/E6500) for some time now on a 2003 SP2 native domain. Within
> the past week all of a sudden when a batch file is run the Vista machines
> will freeze and will then go to a blue screen of death with code 0x00000008
> 0x803D3130 0x00000000 0x00000000 and reboots. Doesn't matter if you are an
> administrator or domain user. I am inspecting th event log, but haven't
> found any leads.
>
> Any ideas

That's an uncommon error and difficult to troubleshoot. It can be caused
by bad RAM, a corrupt device driver, and other hardware problems. I suggest
you start by running a memory diagnostic.
--

"Dylan" <> wrote in message
news:92D7A632-4934-4EB6-ABFD-...
> Hi Jeff,
>
> any solution yet? I have a Dell XPS M1710 with Vista Ultimate and Office
> 2007, I have been getting the exact same error code and BSOD for the last
> 3
> weeks. My desktop also just did the BSOD today for the very first time.
>
> That error code only comes on the restart after another BSOD with 7F,
> (0x00000008,0x81056000,0x00000000,0x00000000)
>
> Any ideas out there, I have called microsoft but they hang up on you after
> 8pm when you have been speaking with them for 30mins!)
>
> "Jeff" wrote:
>
>> I have been running multiple Microsoft Vista 32-bit SP1 Ultimate laptops
>> (Dell D820/D830/E6500) for some time now on a 2003 SP2 native domain.
>> Within
>> the past week all of a sudden when a batch file is run the Vista machines
>> will freeze and will then go to a blue screen of death with code
>> 0x00000008
>> 0x803D3130 0x00000000 0x00000000 and reboots. Doesn't matter if you are
>> an
>> administrator or domain user. I am inspecting th event log, but haven't
>> found any leads.
>>
>> Any ideas

Thanks GTS,

I have done MEMTEST+86, all passed.

I think your write that it may be a driver issue, I have just installed
drivermax and they are all updated, but still does it. About 3 times a day.

My guess is still an automatic update that sucked???

And firefox is stalling regularly now, so may have to go back to IE.
I have Dell PC Tuneup (I know its probably not the best but I thought it
would be the best for a dell) No other Reg Cleaners on it.

I cleared the index history and reindexed, only last night though, as some
other threads suggested this. No BSOD today yet, but will let you know if it
comes back.

Any other tests I can run?

"GTS" wrote:

> That's an uncommon error and difficult to troubleshoot. It can be caused
> by bad RAM, a corrupt device driver, and other hardware problems. I suggest
> you start by running a memory diagnostic.
> --
>

If you think it was an update, you can always uninstall them back to where
you feel the need to, or try system restore back. That is reversible if it
doesn't help. If you find an update is at fault, you can reinstall one at a
time until the problem reoccurs and report the bad update to Microsoft or
back here.

"Dylan" <> wrote in message
news:4D5E83DB-D403-481A-85CC-...
> Thanks GTS,
>
> I have done MEMTEST+86, all passed.
>
> I think your write that it may be a driver issue, I have just installed
> drivermax and they are all updated, but still does it. About 3 times a
> day.
>
> My guess is still an automatic update that sucked???
>
> And firefox is stalling regularly now, so may have to go back to IE.
> I have Dell PC Tuneup (I know its probably not the best but I thought it
> would be the best for a dell) No other Reg Cleaners on it.
>
> I cleared the index history and reindexed, only last night though, as some
> other threads suggested this. No BSOD today yet, but will let you know if
> it
> comes back.
>
> Any other tests I can run?
>
> "GTS" wrote:
>
>> That's an uncommon error and difficult to troubleshoot. It can be
>> caused
>> by bad RAM, a corrupt device driver, and other hardware problems. I
>> suggest
>> you start by running a memory diagnostic.
>> --
>>

Hi John,

Yes, I know about system restore, the problem waswhen it first happened it
was not long after I updated to TrendMicro2009, so I spent a couple of weeks
messing around unistalling andreinstalling that and by the time I realised it
wasn't that I had gone past saved good restore points.

Anyway, seem to have had a bit of luck, in another thread in googleland
someone suggested clearing the index and rebuild from default, which so far
(48hrs) has worked on both computers - No BSOD for 2 days is going good,
touchwood!

Anyway before this I was watching processes for a while and the NT Kernel
system one was just chewing the CPU so it seems it was a kernel error or
something and clearing the index seems to have fixed it. For now.

So if you have the 0x803D31310 BSOD give the index a clean and rebuild,see
if it helps and let us know.

I hope I don't write back tomorrow that this was only luck!!

"John Barnes" wrote:

> If you think it was an update, you can always uninstall them back to where
> you feel the need to, or try system restore back. That is reversible if it
> doesn't help. If you find an update is at fault, you can reinstall one at a
> time until the problem reoccurs and report the bad update to Microsoft or
> back here.
>
> "Dylan" <> wrote in message
> news:4D5E83DB-D403-481A-85CC-...
> > Thanks GTS,
> >
> > I have done MEMTEST+86, all passed.
> >
> > I think your write that it may be a driver issue, I have just installed
> > drivermax and they are all updated, but still does it. About 3 times a
> > day.
> >
> > My guess is still an automatic update that sucked???
> >
> > And firefox is stalling regularly now, so may have to go back to IE.
> > I have Dell PC Tuneup (I know its probably not the best but I thought it
> > would be the best for a dell) No other Reg Cleaners on it.
> >
> > I cleared the index history and reindexed, only last night though, as some
> > other threads suggested this. No BSOD today yet, but will let you know if
> > it
> > comes back.
> >
> > Any other tests I can run?
> >
> > "GTS" wrote:
> >
> >> That's an uncommon error and difficult to troubleshoot. It can be
> >> caused
> >> by bad RAM, a corrupt device driver, and other hardware problems. I
> >> suggest
> >> you start by running a memory diagnostic.
> >> --
> >>
>
>

Oh well I'm back. Just got BSOD again, I walkedback into the office and it
did it right then, I hadn't even been doing anything! I guess I'll have to do
the dreaded reinstall soon. I'll put up with it for as long as I can in th
ehope someone finds a solution.

Cheers,

Dylan