BSoD on Vista x86 (0xF4,parameters)

Status
Not open for further replies.
Everytime I try to open games such as special force and exteel, I get BSoD. Me and my friend have the same system and both using Vista Home Premium but i'm the only one getting BSoD and he says maybe my RAM is faulty or maybe BIOS. At first I reformatted my Pc to x64 Home Premium but got a lot of BSoD's even at idle, so I reformatted back to x86 Home Premium. Hope someone can help me. :)
 
You will get a lot more responses if you re-set the .dmp to issue as a txt file or other than a .dmp.
And tell us the brand, model, and configuration of the computers in question.
 
How will I make that into a .txt?

AMD Athlon 64 X2 4200+
Inno3D GeForce 8500GT 512Mb
2GB Kingston 667Mhz
Seagate 160GB + 500GB SATA
Sony DVD Burner 20x
Corsair 450VX
 
Hello and welcome, Freedom44 .

Code:
On Sun 8/2/2009 6:43:41 AM your computer crashed
This was likely caused by the following module: [URL="http://www.google.com/search?q=csrss.exe"][B]csrss.exe[/B][/URL]
Bugcheck code: [B]0xF4[/B] (0x3, 0x86615418, 0x86615564, 0x82248400)
Error: [B][URL="http://www.google.com/search?q=bugcheck+CRITICAL_OBJECT_TERMINATION"]CRITICAL_OBJECT_TERMINATION[/URL][/B]
file path: C:\Windows\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

Code:
On Sun 8/2/2009 6:43:39 AM your computer crashed
This was likely caused by the following module: [URL="http://www.google.com/search?q=csrss.exe"][B]csrss.exe[/B][/URL]
Bugcheck code: [B]0xF4[/B] (0x3, 0x91E03190, 0x91E032DC, 0x8227F400)
Error: [URL="http://www.google.com/search?q=bugcheck+CRITICAL_OBJECT_TERMINATION"][B]CRITICAL_OBJECT_TERMINATION[/B][/URL]
file path: C:\Windows\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

Windows Debugger thought the main threat was csrss (.exe).

2 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

PLEASE, do as follows:

Step 1: Press "Windows Key" + "R", this will show you the 'run' dialog.
Step 2: Enter "dxdiag", this will show you the 'directx diagnostics panel'.
Step 3: Wait for it to load, COMPLETELY.
Step 4: Near the bottom left, you'll see "Save all information . . ." Please click this.
Step 5: NOW, upload it as an attachment next post, Thank you.
 
Status
Not open for further replies.
Back