Author Topic: Windows 7 Home Premium after Windows XP crashing (Read 14851 times)

aleemhasham · « **on:** February 20, 2012, 04:54:27 PM »

So I go back in time to 2 years running an HP with Windows XP. Sometime ago, my HD crashed and I replaced it with a new one. Convinced by HP and BB, I also purchases a Windows 7 Home Premium CD (since I never had back up software).

So after a successful installation of the CD, the following errors occurred every day

On Wed 7/20/2011 9:20:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072011-17425-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8004908B30, 0xFFFFFA8004908E10, 0xFFFFF80002BD9F40)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time

In talking to both HP and MS, both cannot fix the issue and recommend that I purchase a new PC or send that out for repair.

Any ideas ?

PcWinTech.com Forums · « **on:** February 20, 2012, 04:54:27 PM »

Shane · « **Reply #1 on:** February 20, 2012, 08:20:39 PM »

First thing is to check the memory.

Have you ran any memory test on it yet?

Shane

aleemhasham · « **Reply #2 on:** February 20, 2012, 08:26:39 PM »

no i have not run any memory test ... how would i do this ?

Shane · « **Reply #3 on:** February 20, 2012, 08:27:39 PM »

http://oca.microsoft.com/en/windiag.asp

Shane

aleemhasham · « **Reply #4 on:** February 20, 2012, 08:32:31 PM »

thanks, will test is and revert the findings ..

aleemhasham · « **Reply #5 on:** February 20, 2012, 09:36:59 PM »

Just did a "Windows MEmory Diagnostics Tool" test, results are "No problems have been detected yet". Test completed successfully ....

Shane · « **Reply #6 on:** February 20, 2012, 09:57:52 PM »

Next thing to do is a bad sector test on the hard drive with the windows chkdsk.

Also we need to make sure you have the current drivers for everything.

How often does this bluescreen happen?

Shane

aleemhasham · « **Reply #7 on:** February 21, 2012, 05:01:21 PM »

Thanks for the post ... I did a chkdsk and reported no errors on that ... Earlier on I started the computer in safe mode with networking, and it seems to work .... to early to tell though .. as to the other question as to how often it crashes .... it crashed every day without fail ...

I do not know how to update all drivers at one go, when I checked the drivers they all (just the ones I randomly checked) stated they were working fine ...

Shane · « **Reply #8 on:** February 22, 2012, 11:42:34 AM »

Do windows update and see if it offers any drivers.

IS there a point when it crashes? Such as sleep mode? Drivers can cause a lot of crashes.

So check for video, chipset and sound drivers.

Shane

aleemhasham · « **Reply #9 on:** February 22, 2012, 05:28:21 PM »

In safe mode it does not crash. Seems it crashes in sleep mode when booted normally. Checked all drivers chipset audio and video. All show driver is up to date.

aleemhasham · « **Reply #10 on:** February 22, 2012, 05:30:53 PM »

Also doing an automatic update now. Will take a while to complete

Shane · « **Reply #11 on:** February 22, 2012, 05:39:34 PM »

Safe mode runs with the minimum need to run windows including the minimum drivers.

Shane

aleemhasham · « **Reply #12 on:** February 22, 2012, 05:43:37 PM »

So in deducing that a driver is what's the issue. The million dollar question is identifying that driver. Is there a way to scan em all in one go and update change or bypass the missing driver ?

Shane · « **Reply #13 on:** February 22, 2012, 05:46:39 PM »

Not easily. I normally just go and manually hunt them all down. Video chipset and sounds are the most common.

The chipset is the driver for the hard drive and such. So hunt those down.

Also did windows update list any driver updates?

Shane

aleemhasham · « **Reply #14 on:** February 22, 2012, 05:56:55 PM »

Windows update did list a couple of drivers didn't really read them. But checked video and hard drive drivers and tried to do an update on them. Said driver was updated ... Since I've done the windows auto update let me wait till morning to see if it still crashes and revert

PcWinTech.com Forums · « **Reply #14 on:** February 22, 2012, 05:56:55 PM »

PcWinTech.com Forums

News: