Windows Vista BSOD few minutes after Bootup

Josephur said:

I would first start by removing Norton completely using Symantec's Uninstall Tool which you can find here. Boot in to safe mode and launch the tool, be aware it may uninstall Symantec and Live Update components if they are still used by other Symantec programs on your computer!

Click to expand...

kemical said:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904aa, fffffa600cc37678, fffffa600cc37050, fffffa60014e7309}

Probably caused by : Ntfs.sys ( Ntfs!NtfsExpandHashTable+79 )

Followup: MachineOwner

Hi,
this is your most common dump file out of those sent. The above and other dump files suggest you may have issues with either the Hard drive or RAM.
Please run a chkdsk:
Link Removed

I see that your machine is a NV80Vm Notebook and as such drivers and updates are supplied by the manufacturer. I also notice you have several Bios updates available:
Link Removed

Check your RAM
If after making the above changes you still get the bsod then you need to test your RAM.
Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:
http://www.memtest.org/

To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
Try and run the test overnight if possible unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.

Post any new dump files.

Click to expand...

kemical said:

Hi Ken,
re the Bios updates, it's usual to just install the latest version as that should contain everything that came before. You can update drivers after the bios update and just go through each driver as it comes. Something I forgot to mention last time is after removing Norton install MSE as it's extremely stable:
Link Removed

Also please download and run Malwarebytes:
https://www.malwarebytes.org/

Click to expand...

Josephur said:

My favorite way to get BIOS version at an Administrative command prompt:

wmic bios list brief

Also gives you serial number for the machine

Click to expand...

kemical said:

Sorry I forgot about your question. If you download this app it should tell you which bios you currently have:
http://www.cpuid.com/softwares/cpu-z.html
Look under 'mainboard' which is a tab along the top.

Click to expand...

kemical said:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904aa, fffffa600cc09708, fffffa600cc090e0, fffffa60012e71a2}

Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+202 )

Followup: MachineOwner

Hi,
using third party apps to update your drivers is a real no no and possibly why you still have a bsod issue. It's a pain I know but you have to use the drivers supplied by the manufacturer and I would go back and re-install the drivers posted on the support section of your machines webpage:
Link Removed

{9edd0ea8-2819-47c2-8320-b007d5996f8a}Gt64.sys Fri Jan 31 00:46:41 2014: The file {9edd0ea8-2819-47c2-8320-b007d5996f8a}gt64.sys by webget has been detected as adware by 10 anti-malware scanners. It runs as a Windows 64-bit kernel mode device driver named “{9edd0ea8-2819-47c2-8320-b007d5996f8a}Gt64”. It is part of the Yontoo branded browser-extension.
Please run Malwarebytes:
https://www.malwarebytes.org/

When you ran the chkdsk did you check the boxes to repair sectors? If not run chkdsk again but this time make it chkdsk /f /r C: or if your doing it the GUI way make sure both boxes are ticked.
Another thing to check is the SMART data on the drive itself. You might have to enable it in the Bios. This web page has more info:
http://superuser.com/questions/29240/how-can-i-read-my-hard-drives-smart-status-in-windows-7

Click to expand...

kemical said:

Hi Ken,
that's great to hear and as for Norton... Well I guess ultimately it's up to you but Norton nowadays isn't well liked by the enthusiast community as it really takes over your machine and more often than not causes issues. I used to run Norton back in 2002 when it was still a great anti-virus app but over the years it's become ever more complex and invades the machine on such a scale a driver stack with norton included has to be seen to be believed. It has it's tentacles into everything which is probably why it ends up causing issues but anyway I'm starting to ramble..
I currently use Defender (same as MSE but a windows 8.1 version) and Malwarebytes as neither conflicts nor causes issues.

Click to expand...