BSOD's

M

Mamamegs

Hi all,

In the past 14 days I had a total of 7 BSOD's:
0x0a,(2x)
0x01,
0xD1 (2x) caused by TM_CFW.sys (part of Trend Micro 2007)
0x7F,
0x8E.

Who can make sence of this list? I've solved the TM_CFW.sys, but
every time I try to fix one BSOD, I get a new different one...
If you look at it all it seems to point at a hardware error, but XP
runs oké and doesn't BSOD. No heat problems, CPU is at 29C, mobo 30C
HD's around 33C.

Specs:
Home Premium RTM, XP Home
ASRock 775dual 880Pro mobo
Pentium D 2.80 GHz
2x512MB dual channel memory (tested with Memtest86 for 12hrs, no
errors)
2x IDE HD
1x SATA HD
1x IDE DVD drive
GeForce 6200 TC. (ForceWare 97.46)
Audigy LS 7.1 (1.04.0065)

Your input would be greaty appreciated.

--
Mamamegs.

I reject your reality and substitute my own.
(Adam Savage)

Nederlandse nieuwsgroepen voor Vista
alt.nl.os.windows.vista
microsoft.public.nl.windows.vista

_*[email protected]*_
 
M

Marco

Well I had similar problems - guess what - changed my power supply and they
went away
 
M

Mamamegs

Thanks Jane, I know the site. I'm actually hoping that someone with a
bit more technical knowledge then me can see a common denominator here.
Especially the 0x01 APC_INDEX_MISMATCH, which, even after reading the
MSDN article, goes over my head...
Quote:
"The most common reason to see this message is if a file system has a
mismatched number of KeEnterCriticalRegion compared to
KeLeaveCriticalRegion"
From what I understand this has to do with drivers?

Jane C formulated on Friday :
http://www.aumha.org/win5/kbestop.php A good place to start in
determining BSODs.

--
Mamamegs.

I reject your reality and substitute my own.
(Adam Savage)

Nederlandse nieuwsgroepen voor Vista
alt.nl.os.windows.vista
microsoft.public.nl.windows.vista

_*[email protected]*_
 
M

Mamamegs

Thanks Marco, the PSU I'm using is relatively new. (Asus 450W) Testing
it reads normal values.(no peaks or lows) If I use XP (dual boot) it
runs fine without errors.


Marco explained :
Well I had similar problems - guess what - changed my power supply
and they went away

--
Mamamegs.

I reject your reality and substitute my own.
(Adam Savage)

Nederlandse nieuwsgroepen voor Vista
alt.nl.os.windows.vista
microsoft.public.nl.windows.vista

_*[email protected]*_
 
M

mikeyhsd

uninstall Trend Micro and see if it goes away.



(e-mail address removed)



Hi all,

In the past 14 days I had a total of 7 BSOD's:
0x0a,(2x)
0x01,
0xD1 (2x) caused by TM_CFW.sys (part of Trend Micro 2007)
0x7F,
0x8E.

Who can make sence of this list? I've solved the TM_CFW.sys, but
every time I try to fix one BSOD, I get a new different one...
If you look at it all it seems to point at a hardware error, but XP
runs oké and doesn't BSOD. No heat problems, CPU is at 29C, mobo 30C
HD's around 33C.

Specs:
Home Premium RTM, XP Home
ASRock 775dual 880Pro mobo
Pentium D 2.80 GHz
2x512MB dual channel memory (tested with Memtest86 for 12hrs, no
errors)
2x IDE HD
1x SATA HD
1x IDE DVD drive
GeForce 6200 TC. (ForceWare 97.46)
Audigy LS 7.1 (1.04.0065)

Your input would be greaty appreciated.

--
Mamamegs.

I reject your reality and substitute my own.
(Adam Savage)

Nederlandse nieuwsgroepen voor Vista
alt.nl.os.windows.vista
microsoft.public.nl.windows.vista

_*[email protected]*_
 
C

Chad Harris

If I were you, Mamamegs, I'd take this approach:

That particular message

"mismatched number of KeEnterCriticalRegion compared to
KeLeaveCriticalRegion"

you're zeroing in on is generally from the addition of new hardware that is
causing a problem--perhaps via it's driver(s). See:
www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/w2000msgs/1117.mspx

That said I'd do this:

1) You can often prevent a gamut of BSOD's from a panoply of causes by
opening up Driver Verifier Ref.
How to Use Driver Verifier to Troubleshoot Windows Drivers
http://support.microsoft.com/kb/q244617/


and

1) Disable deadlock detection
2) Disable *the inspection of and note this does not one scintilla impact
the functionality of the software drivers of your antivirus program.

Simply put again, disble driver verifier's inspection of your software
drivers for whatever antivirus progam Mamamegs has chosen to use. That
program is from a well known vendor. It's not going to pitch in drivers
that will harm your system, however disabling the inspection of them by
driver verifier and disabling deadlock detection often prevents the BSOD's
you've been getting. I have found it to be very very effective, and MSFT
has not come around to showcasing it or emphasizing this yet but some of us
are trying to change that.

Many of the population never learns there are software drivers in their
equations as well as hdw drivers.

If that doesn't do the trick, try running the Startup Repair Tool (you do
not have to have a BSOD no boot Vista to run it and get a repair from
it--this may solve your problems:

You run the startup repair tool this way:

http://support.microsoft.com/kb/925810/en-us

How To Run Startup Repair In Vista Ultimate (Multiple Screenshots)
http://www.windowsvista.windowsreinstall.com/vistaultimate/repairstartup/index.htm

Note The computer must be configured to start from a CD or from a DVD. For
information about how to configure the computer to start from a CD or from a
DVD, see the information that came with the computer.
2. Restart the computer. To do this, click Start, click the arrow next to
the Lock button, and then click Restart.

This usually means that you enter bios setup by whatever key or keys
(sometimes there is more than one key that will do it for your model--go to
pc manufacturer site) and configure CD to be first in the boot order.

See for ref:
Access/Enter Motherboard BIOS
http://www.michaelstevenstech.com/bios_manufacturer.htm

Note If you cannot restart the computer by using this method, use the power
button to turn off the computer. Then, turn the computer back on.
3. Set your language preference, and then click Next.

Note In most cases, the startup repair process starts automatically, and you
do not have the option to select it in the System Recovery Options menu.
4. Click Repair your computer.
5. In the System Recovery Options dialog box, click the operating system
that you want to repair, and then click Next.
6. In the System Recovery Options menu, click Startup Repair to start the
repair process.
7. When the repair process is complete, click Finish.

Additional References for Startup Repair With Screenshots:

How to Use Startup Repair:

***Accessing Windows RE (Repair Environment):***

1) Insert Media into PC (the DVD you burned)

2) ***You will see on the Vista logo setup screen after lang. options in the
lower left corner, a link called "System Recovery Options."***

Screenshot: System Recovery Options (Lower Left Link)
http://blogs.itecn.net/photos/liuhui/images/2014/500x375.aspx

Screenshot: (Click first option "Startup Repair"
http://www.leedesmond.com/images/img_vista02ctp-installSysRecOpt2.bmp

How To Run Startup Repair In Vista Ultimate (Multiple Screenshots)
http://www.windowsvista.windowsreinstall.com/vistaultimate/repairstartup/index.htm

3) Select your OS for repair.

4) Its been my experience that you can see some causes of the crash from
theWin RE feature:

You'll have a choice there of using:

1) Startup Repair
2) System Restore
3) Complete PC Restore


Good luck,

CH
 
M

Mamamegs

Chad,
Thanks for your ellaborate answer, I'll get to work with it!

Myranda.

Chad Harris submitted this idea :
If I were you, Mamamegs, I'd take this approach:

That particular message

"mismatched number of KeEnterCriticalRegion compared to
KeLeaveCriticalRegion"

you're zeroing in on is generally from the addition of new hardware
that is causing a problem--perhaps via it's driver(s). See:
www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/w2000msgs/1117.mspx

That said I'd do this:

1) You can often prevent a gamut of BSOD's from a panoply of causes
by opening up Driver Verifier Ref.
How to Use Driver Verifier to Troubleshoot Windows Drivers
http://support.microsoft.com/kb/q244617/


and

1) Disable deadlock detection
2) Disable *the inspection of and note this does not one scintilla
impact the functionality of the software drivers of your antivirus
program.

Simply put again, disble driver verifier's inspection of your
software drivers for whatever antivirus progam Mamamegs has chosen to
use. That program is from a well known vendor. It's not going to
pitch in drivers that will harm your system, however disabling the
inspection of them by driver verifier and disabling deadlock
detection often prevents the BSOD's you've been getting. I have
found it to be very very effective, and MSFT has not come around to
showcasing it or emphasizing this yet but some of us are trying to
change that.

Many of the population never learns there are software drivers in
their equations as well as hdw drivers.

If that doesn't do the trick, try running the Startup Repair Tool
(you do not have to have a BSOD no boot Vista to run it and get a
repair from it--this may solve your problems:

You run the startup repair tool this way:

http://support.microsoft.com/kb/925810/en-us

How To Run Startup Repair In Vista Ultimate (Multiple Screenshots)
http://www.windowsvista.windowsreinstall.com/vistaultimate/repairstartup/index.htm

Note The computer must be configured to start from a CD or from a
DVD. For
information about how to configure the computer to start from a CD or
from a
DVD, see the information that came with the computer.
2. Restart the computer. To do this, click Start, click the arrow
next to
the Lock button, and then click Restart.

This usually means that you enter bios setup by whatever key or keys
(sometimes there is more than one key that will do it for your
model--go to
pc manufacturer site) and configure CD to be first in the boot order.

See for ref:
Access/Enter Motherboard BIOS
http://www.michaelstevenstech.com/bios_manufacturer.htm

Note If you cannot restart the computer by using this method, use the
power
button to turn off the computer. Then, turn the computer back on.
3. Set your language preference, and then click Next.

Note In most cases, the startup repair process starts automatically,
and you
do not have the option to select it in the System Recovery Options
menu.
4. Click Repair your computer.
5. In the System Recovery Options dialog box, click the operating
system
that you want to repair, and then click Next.
6. In the System Recovery Options menu, click Startup Repair to start
the
repair process.
7. When the repair process is complete, click Finish.

Additional References for Startup Repair With Screenshots:

How to Use Startup Repair:

***Accessing Windows RE (Repair Environment):***

1) Insert Media into PC (the DVD you burned)

2) ***You will see on the Vista logo setup screen after lang. options
in the
lower left corner, a link called "System Recovery Options."***

Screenshot: System Recovery Options (Lower Left Link)
http://blogs.itecn.net/photos/liuhui/images/2014/500x375.aspx

Screenshot: (Click first option "Startup Repair"
http://www.leedesmond.com/images/img_vista02ctp-installSysRecOpt2.bmp

How To Run Startup Repair In Vista Ultimate (Multiple Screenshots)
http://www.windowsvista.windowsreinstall.com/vistaultimate/repairstartup/index.htm

3) Select your OS for repair.

4) Its been my experience that you can see some causes of the crash
from
theWin RE feature:

You'll have a choice there of using:

1) Startup Repair
2) System Restore
3) Complete PC Restore


Good luck,

CH

--
Mamamegs.

I reject your reality and substitute my own.
(Adam Savage)

Nederlandse nieuwsgroepen voor Vista
alt.nl.os.windows.vista
microsoft.public.nl.windows.vista

_*[email protected]*_
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

POST problem. (repost) 4
POST problem. 6

Top