0x000000F4 error

[eldanieloxx]

i've been looking for this error and it says that there should be something wrong with my hardware but i checked everything and it's fine... I can't even get in to the safe mode, always get the BSoD 1 or 2 seconds after the mouse appears on the screen, also all the tools that came with the Windows CD couldn't find errors and the only way i got the report or the error was with the command prompt from the CD tools

I have a Dell Inspiron 1720 with Windows 7 Ultimate 32 bits (retail), 2Gb of Ram, 1,73 Ghz intel dual core and a 120 Gb HD

The laptop came with Windows Vista Basic but i change it afer like a month and has been almost 4 years with the same windows 7

I would really like to avoid lossing all my data and just fix the problem

 

[zigzag3143]

i've been looking for this error and it says that there should be something wrong with my hardware but i checked everything and it's fine... I can't even get in to the safe mode, always get the BSoD 1 or 2 seconds after the mouse appears on the screen, also all the tools that came with the Windows CD couldn't find errors and the only way i got the report or the error was with the command prompt from the CD tools

I have a Dell Inspiron 1720 with Windows 7 Ultimate 32 bits (retail), 2Gb of Ram, 1,73 Ghz intel dual core and a 120 Gb HD

The laptop came with Windows Vista Basic but i change it afer like a month and has been almost 4 years with the same windows 7

I would really like to avoid lossing all my data and just fix the problem

NO DMP files included in the upload try this method.




To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

 

[eldanieloxx]

Sorry, here is the minidump

 

[zigzag3143]

Sorry, here is the minidump

These crashes were related to memory management probably caused by a driver (as yet un-named).

I would


1-Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



2-Driver verifier

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

3-Update the old driver listed below

bcm4sbxp.sys    11/21/2006 8:25:43 AM        0x8f825000    0x8f836000    0x00011000    0x4562f047                        
OEM02Vfx.sys    3/5/2007 6:45:03 AM        0x8fd18000    0x8fd19d00    0x00001d00    0x45ebf4af                        
Apfiltr.sys    6/25/2007 5:53:10 AM        0x8f90a000    0x8f936000    0x0002c000    0x467f9086                        
OEM02Dev.sys    10/10/2007 10:29:05 PM        0x8fcde000    0x8fd17880    0x00039880    0x470d8a71                        
ifsmount.sys    8/28/2008 4:47:56 PM        0x88dd2000    0x88de3000    0x00011000    0x48b70efc                        
ext2fs.sys    9/25/2008 11:37:25 AM        0x8cce0000    0x8cd11000    0x00031000    0x48dbb035                        
VSTCNXT3.SYS    10/15/2008 8:29:13 PM        0x8fc03000    0x8fcb8000    0x000b5000    0x48f68ad9                        
VSTAZL3.SYS    10/15/2008 8:30:03 PM        0x8f010000    0x8f04d000    0x0003d000    0x48f68b0b                        
VSTDPV3.SYS    10/15/2008 8:32:04 PM        0x8f04d000    0x8f14f000    0x00102000    0x48f68b84                        
hamachi.sys    2/19/2009 6:36:27 AM        0x8f9f6000    0x8f9fac00    0x00004c00    0x499d362b                        
netw5v32.sys    3/26/2009 12:10:37 PM        0x8f412000    0x8f825000    0x00413000    0x49cba8fd                        
spldr.sys    5/11/2009 12:13:47 PM        0x88fcc000    0x88fd4000    0x00008000    0x4a084ebb                        
GEARAspiWDM.sys    5/18/2009 8:16:53 AM        0x8f950000    0x8f955280    0x00005280    0x4a1151b5                        
amdxata.sys    5/19/2009 1:57:35 PM        0x889b8000    0x889c1000    0x00009000    0x4a12f30f                        
rimsptsk.sys    6/25/2009 3:10:46 AM        0x8f88c000    0x8f8a0000    0x00014000    0x4a4322f6                        
rixdptsk.sys    6/25/2009 3:25:57 AM        0x8f8a0000    0x8f8f2000    0x00052000    0x4a432685                        
rimmptsk.sys    6/25/2009 3:58:09 AM        0x8f87b000    0x8f88c000    0x00011000    0x4a432e11

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

 

[eldanieloxx]

i'll try the memtest, but the problem with the others solutions is that i can't boot windows, even in safe mode crashes before the desktop appears (i only get to see the mouse pointer for 2 seconds)

 

[zigzag3143]

i'll try the memtest, but the problem with the others solutions is that i can't boot windows, even in safe mode crashes before the desktop appears (i only get to see the mouse pointer for 2 seconds)

Do you have the win 7 dvd to boot from? If so you can attempt a repair install.

 

[eldanieloxx]

Do you have the win 7 dvd to boot from? If so you can attempt a repair install.

Yes, I do have it... but the only option to install (the other is upgrade) is deleting everything and also and I just have 4 GB free HD and ask me for 5 GB of free space to install the "new" windows and leave a copy of "old" windows

Just finnished to run memtest 10 times and didn't find any errors...