[PSYCHOBOY_666]

I am currently working on a Averatec 6240 Laptop with Windows XP Home SP2 & I get a BSOD Stop: 0x000000F4 error message when I try to boot the comp. I can't boot into safe mode either the computer just keeps rebooting.
I used Windows Debugger but I can't figure out which driver is causing a fault in csrss.exe
I can supply the last Dump File.....I will attach it.

I hope somebody can help me or my last resort will be to due a repair installation (I really don't want to do that).


Thanx Scott

Attached File(s)

•  DUMP52b4.zip (19.77K)
  Number of downloads: 2

[cluberti]

Unfortunately, you've given us only a minidump - so your dump is missing lots of info (like, potentially the memory information regarding the driver crashing the box). However, since this is a csrss dump and the parameter that's being passed is invalid, I'd suspect a memory dump without any further checking would just lead to a bigger file without any more data that would be useful. Also, most of the time I see this, it's one of three things - a processor problem relating to the BIOS (more with Intel microcode than AMD, but AMD processors do have their BIOS issues), a failing hard disk, or a potential antivirus interference issue (and seeing how old your symevent and symtdi files are, I wouldn't be shocked).

So, assuming you run a chkdsk /r /f on your drive and it comes back clean, I'll tackle the other two:

//1. You're running an AMD Athlon 64 3000+ processor, and I don't see anything odd
// regarding the CPU itself, or the SMBIOS info - I'd say it's likely not a bad processor,
// however you are running a REALLY old BIOS that you should consider touching:
kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 2000
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ x86 Family 15 Model 28 Stepping 0
ProcessorNameString = REG_SZ Mobile AMD Athlon(tm) 64 Processor 3000+
Update Status = REG_DWORD 1
VendorIdentifier = REG_SZ AuthenticAMD

kd> !sysinfo smbios
[SMBIOS Data Tables v2.3]
[DMI Version - 35]
[2.0 Calling Convention - No]
[Table Size - 732 bytes]

[BIOS Information (Type 0) - Length 20 - Handle 0000h]
  Vendor						American Megatrends Inc.
  BIOS Version				  A1011SMS V0.90 11/22/04
  BIOS Starting Address Segment f000
  BIOS Release Date			 11/22/2004
  BIOS ROM Size				 80000


//2. Your symevent and symtdi files are both quite old, and known to be somewhat buggy:
kd> lmvm symevent
start	end		module name
f3ae0000 f3afcdc0   SYMEVENT   (deferred)			 
	Image path: SYMEVENT.SYS
	Image name: SYMEVENT.SYS
	Timestamp:		Sat Sep 16 01:48:19 2006 (450B9023)
	CheckSum:		 000209CF
	ImageSize:		0001CDC0
	Translations:	 0000.04b0 0000.04e4 0409.04b0 0409.04e4
kd> lmvm symtdi
start	end		module name
f3b1e000 f3b5dda0   SYMTDI	 (deferred)			 
	Image path: SYMTDI.SYS
	Image name: SYMTDI.SYS
	Timestamp:		Sat Jan 22 00:55:40 2005 (41F1EADC)
	CheckSum:		 000500F3
	ImageSize:		0003FDA0
	Translations:	 0000.04b0 0000.04e4 0409.04b0 0409.04e4

One last thing to note, which I found odd - both processr.sys and tosrfcom.sys were in the unloaded modules list when the machine crashed, meaning it's also possible that the tosrfcom.sys file is the culprit. It's either the Toshiba Bluetooth stack driver, or a virus, so I hope you have the Toshiba software installed.

Noting that this is not a Toshiba, I'm actually leaning on removing the Bluetooth software and driver entirely as well, as it's very suspicious to be unloaded along with processr.sys.