BSOD STOP 0x000000F4
Rien
I get at close intervals (1 to 5 days) a Blue screen (BSOD) without name
of an offending driver, juste STOP 0x000000F4 (0x00000003)
(0x866679D8) (0x86667B4C) (0x805C7478)
I found with several search engines for this Stop and found nothing. I
found nothing either on MS site. How can I do a diagnostic about that ?
My configuration : Dell Inspiron 6000 laptop, with WXP Media center ed.
I didn't intall anything recently, my antivirus is up to date (Avast)
I think about a random hard problem, but before replacing my HDD or
reinstalling all, I'd like to be sure about the diagnostic.
Can anybody help me ?
Thank you
Curious
Dell or the chip manufacturers Websites. You may have installed a driver
from WinUpdate that is out of date or which is incompatible with your
system?
Is there any information in the event logs that might help to determine the
cause?
"Rien" <ri...@rien.com> wrote in message
news:e4NhBfA...@TK2MSFTNGP06.phx.gbl...
Gurpreet Singh
see the first parameter as 0x3 (in you rcase it is 0x3) it indicates a
process termination. In case of a thread termination the first paremeter
would be 0x4. The second parameter would be the terminating object id, in
case it would be a process id. The third parameter is the process image name,
and we do not see this in the bugcheck info provided by you. If you have the
memory.dmp file created in windows folder after this bugcheck, you can use
the windows debugging tools to open the dump file and investigate the cause
of the bugcheck. Download and install the windows debugging tools from
http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi
install it and then open the dump in the windows debugging tools. create a
folder c:\symbols from windows explorer. In windows debugging tools, open the
menu file>>Symbol file path and paste the following
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;
check teh reload button and from the windoes debugging tools main menu type
!analyze -v
This should give you a basic dump analysis.
Alernatively I would suggest you run the following script on the box.
Create a file named processid.vbs and add the following content. Double
click the file to execute the vbs file. This will create a csv file and
everytime you open a process it will update the file with the process
details. Additional run the command at system startup
tasklist >tasks.txt
to dump all the running processes and there process id's. Once the bugcheck
happens and you still do not see any process name in the bugcheck parameter,
use calculator to convert the second parameter from hex to decimal and look
in the tasks.txt file of the file created by the following script.
'========================process.vbs content
strComputer = "."
Const EVENT_SUCCESS = 0
Set objShell = Wscript.CreateObject("Wscript.Shell")
Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")
Set colMonitoredProcesses = objWMIService. _
ExecNotificationQuery("select * from __InstanceCreationEvent " _
& " within 1 where TargetInstance isa 'Win32_process'")
i = 0
Do While i = 0
Set objLatestProcess = colMonitoredProcesses.NextEvent
message = objLatestProcess.TargetInstance.ProcessId & "," &
objLatestProcess.TargetInstance.ExecutablePath & "," &
objLatestProcess.TargetInstance.Name
writetocentrallocation message
Loop
sub writetocentrallocation(message)
filename= replace(date,"/", "-") & ".csv"
Set filesys = CreateObject("Scripting.FileSystemObject")
if filesys.FileExists(filename) then
Set results = filesys.openTextFile(filename , 8)
else
Set results = filesys.CreateTextFile(filename)
results.writeline "Process created"
results.writeline "Process id, Path, Details"
end if
results.writeline message
end sub
--
Regards
Gurpreet Singh
"Rien" wrote:
> .
>
S.Sengupta
was running fine.
Also test your hard drive with manufacturer's diagnostic tool.
regards,
S.Sengupta [MS-MVP]
"Rien" <ri...@rien.com> wrote in message
news:e4NhBfA...@TK2MSFTNGP06.phx.gbl...
> __________ Information from ESET Smart Security, version of virus
> signature database 4566 (20091102) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
>
>
__________ Information from ESET Smart Security, version of virus signature database 4566 (20091102) __________
The message was checked by ESET Smart Security.