Blue screen O.D. twice a day

G

Guest

I recieve a blue screen or critical stop around twice a day with diferent
error codes such as:-
irq-not-equal-or-somthing error code 4a
pfn list corrupt error code 4e
and some others, all at very random time although it dose seem to be worse
when the machine is working hard
I have updated or reinstalled everthing I can think of and have run several
debug programs, my windows seem to run realy good apart from the blue screens.
Could defective memory cause different error codes, I would like to pin
point the error before spending £60 on new modules ????
 
G

Guest

Stevie said:
I recieve a blue screen or critical stop around twice a day with diferent
error codes such as:-
irq-not-equal-or-somthing error code 4a
pfn list corrupt error code 4e
and some others, all at very random time although it dose seem to be worse
when the machine is working hard
I have updated or reinstalled everthing I can think of and have run several
debug programs, my windows seem to run realy good apart from the blue screens.
Could defective memory cause different error codes, I would like to pin
point the error before spending £60 on new modules ????

First of all how much Disk Space you have on your computer and how much RAM
installed.
Then you can look in the Event Viewer for Error messages which willl show
you applicatiins,hardwares, security crashes that happend on this machine and
point out or shed some light on what is going on, to access the Event Viewer
do this:
Open a run command and type in: eventvwr and click [OK] you are on check
under these options:
Application
System
Security

Download the AutoRun tools to decide what runing in the background:
http://www.microsoft.com/technet/sysinternals/utilities/autoruns.mspx

Download this Resource Kit for troubleshooting and read this article for
more Info:
http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/c28621675.mspx

HTH.
REgards,
nass
 
N

NewScience

Have fast of a Network Connection do you have?
If it's pretty fast, you can download the Windows Debugging Tools and the
Windows XP Symbols package.

Each time the system crashes, do you get a Crash Dump file in
C:\Windows\Memory.dmp or C:\Windows\MiniDump folder?

If so, you can run the debugger on it and it will tell you exactly what went
on that caused the crash.

If you are not getting crash dumps:

1. Open Control Panel | System | Advanced ... click on Startup and Recovery
Settings button
2. Make sure that Full dump is selected for system dumps
3. Make sure that Automatic Restart is unchecked
 
G

Guest

Running 160gb disc with around 10gb free space and 768mb ram

Event viewer shows:-
nothing in aplications
nothing in security
in system:- system error category (102) event 1003
The perramitors of the error very but i will post them if it will help.

I run check disc reguly but is there any way of viewing the chkdsc log
????????

I am runnign the bare minimum background proseses

Thank for any help.

nass said:
Stevie said:
I recieve a blue screen or critical stop around twice a day with diferent
error codes such as:-
irq-not-equal-or-somthing error code 4a
pfn list corrupt error code 4e
and some others, all at very random time although it dose seem to be worse
when the machine is working hard
I have updated or reinstalled everthing I can think of and have run several
debug programs, my windows seem to run realy good apart from the blue screens.
Could defective memory cause different error codes, I would like to pin
point the error before spending £60 on new modules ????

First of all how much Disk Space you have on your computer and how much RAM
installed.
Then you can look in the Event Viewer for Error messages which willl show
you applicatiins,hardwares, security crashes that happend on this machine and
point out or shed some light on what is going on, to access the Event Viewer
do this:
Open a run command and type in: eventvwr and click [OK] you are on check
under these options:
Application
System
Security

Download the AutoRun tools to decide what runing in the background:
http://www.microsoft.com/technet/sysinternals/utilities/autoruns.mspx

Download this Resource Kit for troubleshooting and read this article for
more Info:
http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/c28621675.mspx

HTH.
REgards,
nass
 
N

NewScience

According to articles, this can be due to a driver writing into memory that
it does not own (PFN).

I had this a couple of times, performed a chkdsk /r on the drive (which
found some bad clusters) and periodically also had intermittent IRQ errors.

Since I had added new RAM and a slew of upgrades to the hardware, I leaned
toward the Power Supply (which was 230W - old system and motherboard).

I added a 350W Ultra Max ... and have not had a single problem now for 2
months ... knock PC (wood).

In my earlier post, you can try debugging, or disconnect external hardware
(USB devices, ....), move RAM sticks around, ....

Also try running MemTest86+ , http://www.memtest86.com/ to test your memory.
 
G

Gerry Cornell

Stevie

You have insufficient free disk space but I would not put the Stop
Errors
down to this. I am adding some notes regarding how you might increase
free disk space at the end of this message.

You need to post proper copies of the Stop Error Reports.

Disable automatic restart on system failure. This should help by
allowing time to write down the STOP code properly. Right click
on the My Computer icon on the Desktop and select Properties,
Advanced, Start-Up and Recovery, System Failure and uncheck
box before Automatically Restart.

Do not re-enable automatic restart on system failure until you have
resolved the problem. Check for variants of the Stop Error message.

There will also be Error Reports in Event Viewer. Look in the
System log. Please post a copy.

You can access Event Viewer by selecting Start, Administrative Tools,
Event Viewer. When researching the meaning of the error, information
regarding Event ID, Source and Description are important.

HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;308427&Product=winxp

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Double click the button and close Event
Viewer. Now start your message (email) and do a paste into the body of
the message. This will paste the info from the Event Viewer Error
Report. Make sure this is the first paste after exiting from Event
Viewer.

http://aumha.org/win5/kbestop.htm

Try testing your memory

Memtest86 - Memory Diagnostic Page:
http://www.memtest86.com/

http://msdn.microsoft.com/library/d..._299217d6-98d1-4d1d-8068-883e89933845.xml.asp
if link broken try
http://snipurl.com/l6o7

http://msdn.microsoft.com/library/d..._299217d6-98d1-4d1d-8068-883e89933845.xml.asp
if link broken try
http://snipurl.com/l6o7

Are there any yellow question marks in Device Manager? Right
click on the My Computer icon on your Desktop and select
Properties. Hardware, Device Manager. If yes what is the
Device Error code?

You could try Start, Run, type "sfc /scannow" without quotes
and hit Enter.

Description of Windows XP and Windows Server 2003 System
File Checker (Sfc.exe)
http://support.microsoft.com/default.aspx?scid=kb;en-us;310747

To increase you free space on your C partition select Start, All
Programs, Accessories, System Tools, Disk CleanUp, More
Options, System Restore and remove all but the latest System
Restore points? Restore points can be quite large.

You should use Disk CleanUp regularly to Empty your Recycle Bin
and Remove Temporary Internet Files. Whenever you remove
redundant files you should always run Disk Defragmenter by selecting
Start, All Programs, Accessories, System Tools, Disk Defragmenter.

It is likely that an allocation of 12% has been made to System Restore
on your C partition which is over generous. I would reduce it to 700 mb.
Right click your My Computer icon on the Desktop and select System
Restore.Place the cursor on your C drive select Settings but this time
find the slider and drag it to the left until it reads 700 mb and exit.
When
you get to the Settings screen click on Apply and OK and exit.

If your hard drive is formatted as NTFS another potential gain arises
with your operating system on your C drive. In the Windows Directory
of your C partition you will have some Uninstall folders in your Windows
folder typically: $NtServicePackUninstall$ and
$NtUninstallKB282010$ etc.

These files may be compressed or not compressed. If compressed the
text of the folder name appears in blue characters. If not compressed
you can compress them. Right click on each folder and select Properties,
General, Advanced and check the box before Compress contents to
save Disk Space. On the General Tab you can see the amount gained
by deducting the size on disk from the size. Folder compression is
only an option on a NTFS formatted drive / partition.

Another default setting on a large drive which could be wasteful is that
for temporary internet files especially if you do not store offline
copies
on disk. The default allocation is 3% of drive. Depending on your
attitude
to offline copies you could reduce this to 1% or 2%. In Internet
Explorer
select Tools, Internet Options, General, Temporary Internet Files,
Settings to make the change. At the same time look at the number of
days history is held.

The default allocation for the Recycle Bin is 10 % of drive. On your
drive 5% should be sufficient. In Windows Explorer place the cursor
on your Recycle Bin, right click and select Properties, Global and
move the slider from 10% to 5%.


--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Stevie said:
Running 160gb disc with around 10gb free space and 768mb ram

Event viewer shows:-
nothing in aplications
nothing in security
in system:- system error category (102) event 1003
The perramitors of the error very but i will post them if it will
help.

I run check disc reguly but is there any way of viewing the chkdsc log
????????

I am runnign the bare minimum background proseses

Thank for any help.

nass said:
Stevie said:
I recieve a blue screen or critical stop around twice a day with
diferent
error codes such as:-
irq-not-equal-or-somthing error code 4a
pfn list corrupt error code 4e
and some others, all at very random time although it dose seem to
be worse
when the machine is working hard
I have updated or reinstalled everthing I can think of and have run
several
debug programs, my windows seem to run realy good apart from the
blue screens.
Could defective memory cause different error codes, I would like to
pin
point the error before spending £60 on new modules ????

First of all how much Disk Space you have on your computer and how
much RAM
installed.
Then you can look in the Event Viewer for Error messages which willl
show
you applicatiins,hardwares, security crashes that happend on this
machine and
point out or shed some light on what is going on, to access the Event
Viewer
do this:
Open a run command and type in: eventvwr and click [OK] you are on
check
under these options:
Application
System
Security

Download the AutoRun tools to decide what runing in the background:
http://www.microsoft.com/technet/sysinternals/utilities/autoruns.mspx

Download this Resource Kit for troubleshooting and read this article
for
more Info:
http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/c28621675.mspx

HTH.
REgards,
nass
 
R

Ron Martell

Stevie said:
I recieve a blue screen or critical stop around twice a day with diferent
error codes such as:-
irq-not-equal-or-somthing error code 4a

If that is a STOP 0x0000004A: IRQL_GT_ZERO_AT_SYSTEM_SERVICE then it
is a relatively rare beastie. The following article is for Windows
2000 but the content is probably applicable to Windows XP as well.
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/w2000Msgs/1189.mspx?mfr=true

pfn list corrupt error code 4e

This is somewhat better known, and is most likely associated with a
defective or damaged device driver. The detailed parameter values
that appear on the error message are needed in order to track this
error further. See the following article:
http://msdn2.microsoft.com/en-us/library/ms793247.aspx

and some others, all at very random time although it dose seem to be worse
when the machine is working hard

Look for a common factor between all of these occurrences. It could
be a general hardware related issue such as overheating or low power
voltage that is the cause of all of these errors.

Keep track of the data for these errors, including the complete STOP
code, all 4 parameters, and any file or module names mentioned. These
values are often of considerable assistance in tracking down the cause
of these errors.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
N

NewScience

You can play around this over and over, seconf guessing everything. Try the
Windows Debugging Tools as I mentioned and it will directly pinpoint the
problem.

Believe me ... I've gone thru this for over 4 months.
 
G

Guest

I set the system to do a full memory dump and would you believe it hasn't
crashed since
However i have viewed some mini dumps allhtough im not %100 sure what im doing
Do you have to install the symbols every time you start debug
Anyway mini dump said

Problem caused by:-
Memory corruption (nt!Mmcopytocachedpage+275)
Memory corruption (nt!Mminswapprocess+2c7)
Ntoskrnl exe. (nt!pspreaper+25)

Thank you everyone for any help
Stevie M
 
G

Gerry Cornell

Stevie

Ntoskrnl exe -locate the file in C:\windows\system32 and
right click on it selecting Properties.

On the General tab what is the date modified and on the
Version tab what is the File Version.

You could try Start, Run, type "sfc /scannow" without quotes
and hit Enter.

Description of Windows XP and Windows Server 2003
System File Checker (Sfc.exe)
http://support.microsoft.com/default.aspx?scid=kb;en-us;310747

Check whether this solves the problem of Blue Screen
Stop Errors.

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
N

NewScience

No you do not have to install the Symboils Package each time. However, if
your executable DTG does not match the Symbols File DTG (Date-Time-Group),
then if you have set the Preferences up correctly for WinDBG, then WinDBG
will go to the Windows Symbol Package web-site and automatically download
any symbols that are out-of-date.

I created a Shortcut for Windows Debugger set to the following:

Target: "C:\Program Files\Debugging Tools for Windows\windbg.exe" -v -y
"SRV*C:\Windows\System32\Symbols*http://msdl.microsoft.com/download/symbols"
-i "c:\Windows;c:\Windows\system32;c:\Windows\system32\drivers" -z
"C:\Windows\MEMORY.DMP"

This automatically opens the system crash dump C:\Windows\Memory.DMP file.

I also created a Registry .reg file to create an associated for any .DMP
files

--------------------------COPY AND PASTE TO FILE
..reg -----------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.dmp]
@="dmpfile"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\dmpfile]

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\dmpfile\DefaultIcon]
@="\"C:\\Program Files\\Debugging Tools for Windows\\windbg.exe\",0"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\dmpfile\shell]
@="Debug"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\dmpfile\shell\Debug]
@="&Debug"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\dmpfile\shell\Debug\command]
@="\"C:\\Program Files\\Debugging Tools for Windows\\windbg.exe\" -v -y
\"SRV*C:\\windows\\System32\\Symbols*http://msdl.microsoft.com/download/symbols\"
-i \"c:\\windows;c:\\windows\\system32;c:\\windows\\system32\\drivers\" -z
\"%L\""
------------------------------------------------------------------------------------------------------------

WHen installed in the registry, any .dmp file (when right-clicked), will
have a Debug option that will open the WinDBG program.
So, right-click on any C:\Windows\MiniDump\*.dmp file

By using the shortcut and the registry entry, you assure yourself that you
will always have to most up-to-date symbol.
For example, say MS updates ntdll.dll or ntoskrnl.exe, then next time you
have a crash and need to debug it, WinDbg will automatically retrieve the
new symbol table.

I'd tell you what to look for in the DUMP trace, but since I fixed my
problem, I haven't had one. I know to look for Process (something) after
entering the !analyze -v command
 

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

Top