Solved hope i can find some help thanks

[clickss]

well windows seems to crash alot on me get the 0x000000f4 screen
also i get kernal page something that comes up i ran a disk check and it fine so i updated all the driver i could and still nothing so hope i can get this fix thanks to every one who reads this
op windows 7 64bit

 

[zigzag3143]

Your crashes are related to a critical process termination.

Lets start by running a system file check

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

 

[clickss]

windows resource protection did not find any integrity violations
so that a good sign kinda so whats next ?
p.s thanks for your time helping me with this

 

[zigzag3143]

windows resource protection did not find any integrity violations
so that a good sign kinda so whats next ?
p.s thanks for your time helping me with this

That means that something other than the OS is making the process crash. Please run these two tests.



Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 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.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html






Driver Verifier

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable 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"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

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.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


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.

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[clickss]

well i got it to crash 2 time but it rebooted from the blue screen tofast to see any thing
ram test pasted no errors

 

[clickss]

that all i got looks like old ones

 

[zigzag3143]

that all i got looks like old ones

Again a critical process has been terminated. It could easily be your AVG

I note you have AVG.
AVG can be a contributing cause of BSOD'S .
Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST

Download tools and utilities | AVG Worldwide


Microsoft Security Essentials - Free Antivirus for Windows

 

[clickss]

ya i did that before i posted i was reading avg does that
and i also used the avg remover i found on here to remove it
soany thing else it could be ?

 

[zigzag3143]

ya i did that before i posted i was reading avg does that
and i also used the avg remover i found on here to remove it
soany thing else it could be ?

Can tell you more when you upload the new DMPS

 

[clickss]

here new ones

 

[zigzag3143]

here new ones

Still a critical object is being terminated. Have you run memtest? what were the results?

And driver verifier? none of the DMPS were verified!!!

 

[clickss]

ram mem test it past it no errors
start the driver verifier and let it run but the crashs rebooted every time and dint get any dump file cuz it rebooted before dump finished
wen i turned verifier off the crashed made dump fire again

 

[zigzag3143]

ram mem test it past it no errors
start the driver verifier and let it run but the crashs rebooted every time and dint get any dump file cuz it rebooted before dump finished
wen i turned verifier off the crashed made dump fire again

How many memtest passes? Did you do each stick individually?

If you cant generate a DMP file with verifier on we cant get any closer to finding out the true cause.


Might be time to start thinking about a clean install.

 

[clickss]

i let it run 7 time all 7 passed
i'll turn verifier back on and try to get a dump file
this is a clean install i just upgrade my computer so i had to install a 64 bit os to get it to see the ram
my old os dint crash

 

[zigzag3143]

i let it run 7 time all 7 passed
i'll turn verifier back on and try to get a dump file
this is a clean install i just upgrade my computer so i had to install a 64 bit os to get it to see the ram
my old os dint crash

Did you upgrade the ram after you had the computer? Did you replace all of it or just add to it?

 

[event3horizon]

to stop your computer from rebooting when BSODing go to control panel > system > advanced system setting > advanced tab > "settings" under startup and recovery and UNCHECK "automatically restart" and switch to 'small memory dump' under debugging information.

 

[zigzag3143]

You mean like this?



If you are overclocking STOP



You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

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.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

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.

 

[clickss]

ya i did a full upgrade cpu - board - ram
the board i have is a asus and if i run a 32bit os it only see 3.2gig of ram
so i had to format and install windows 7 home 64 bit
and not the sys crashs
i put verify back on and changed the dump to small 256kb
i'll upload the dumps soon as it crashes

 

[clickss]

well i got it to crash with verify on and uploading the dump files

 

[zigzag3143]

well i got it to crash with verify on and uploading the dump files

Both NOT verified. Both still pointing to a critical windows file being killed. If SFC really showed no access violations and memtest passed, it is a driver from some third party.

You may be better off doing a clean install rather than trying to diagnose which driver it is.