Windows Explorer error

[lessthanuthought]

On my older computer I kept getting BSOD and then a couple days ago as soon as windows booted I would get an error than windows explorer has stopped working and would have to be restarted. Then nvstlink.exe - Application error. The windows explorer error repeats infinitely. I formatted and re-installed and after a couple hours I am getting the same windows explorer error. HDD going bad?

Thanks


Phenom x2 965
16GB Mushkin RAM
2TB WD Black (x2)
GTX 9800
GIGABYTE GA-MA790XT-UD4P

 

[lessthanuthought]

no one?

 

[Ketchup]

It would be odd to be a hard drive problem considering the same application is crashing on two separate installs.

If you installed 3DVision with your Nvidia card drivers, uninstall it and see if the problem persists.

 

[Ketchup]

Also, give a decent amount of time before you bump your own thread for an answer. It is Sunday after all.

 

[lessthanuthought]

Also, give a decent amount of time before you bump your own thread for an answer. It is Sunday after all.

K sorry about that, thanks for the reply though. I actually didn't install any drivers. Windows found everything on its own, and I hadn't gotten around to updating to drivers from nvidia's website.

I was installing directx when it crashed the second time. I don't remember what I was doing the first time.

 

[Ketchup]

K sorry, thanks for the reply though. I actually didn't install any drivers. Windows found everything on its own, and I hadn't gotten around to updating to drivers from nvidia's website.

OK, I would go ahead and remove the Windows Nvidia drivers and install the ones from Nvidia's site.

 

[lessthanuthought]

OK, I would go ahead and remove the Windows Nvidia drivers and install the ones from Nvidia's site.

Okay, I'll do a fresh install now, and try that. *Fingers crossed*
At least I have a partition with windows install on it, so the whole thing only takes ~10 minutes.

 

[Ketchup]

Okay, I'll do a fresh install now, and try that. *Fingers crossed*
At least I have a partition with windows install on it, so the whole thing only takes ~10 minutes.

Smart!

 

[lessthanuthought]

Smart!

Well, this may take a while, I'm backing up all the stuff that's on the other partition of the HDD just in case...After that I'll download the other drivers and post on here. Thanks again. see you in a couple hours.

 

[lessthanuthought]

Well, I backed up everything and installed those drivers. No problems yet, wait and see I guess. Thanks for the help ketchup.

 

[Ketchup]

Well, I backed up everything and installed those drivers. No problems yet, wait and see I guess. Thanks for the help ketchup.

Any time. I think I read another thread where Microsoft's suggested drivers weren't what they should have been. Hope this doesn't become a trend.

 

[lessthanuthought]

Eeek, BSOD while installing directX.

 

[lessthanuthought]

And after reboot, Windows Explorer errors again.

And now it is just BSOD as soon as windows loads

 

[Ketchup]

Turn off the auto reboot so that you can see the message on the blue screen. If you already have the minidump files, you can use one of the programs mentioned here to see what they are pointing to:

http://superuser.com/questions/476394/how-to-use-windows-mini-dump-files

 

[lessthanuthought]

K, I turned off the auto-restart.
On Mon 8/26/2013 8:40:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082613-58562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80059A8710, 0xFFFFFA80059A89F0, 0xFFFFF80002B9D510)
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. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 8/26/2013 8:28:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082613-62946-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x7A (0xFFFFF6FC50056B68, 0xFFFFFFFFC0000185, 0xAE393880, 0xFFFFF8A00AD6D000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[lessthanuthought]

I guess there is a hotfix that fixed the same problem for someone else. I will try that.
http://support.microsoft.com/default.aspx/kb/979444

Nope. "Not applicable to your system."

 

[Ketchup]

OK, well you're probably not going to like the answer here, as both are pointing at your hard drive. See here:

http://answers.microsoft.com/en-us/...ror-code/03276fa2-6dcb-44d0-a778-499d5d00b65d

and here:

http://answers.microsoft.com/en-us/...000000f4/57339220-6a1f-41a7-b6b1-3405e499793f

You can run chkdsk, but finding errors on a recently formatted hard drive/partition does not bode well for the drive. I recommend getting anything important off that drive and looking into a new one.

Too bad it wasn't just the drivers, but it was probably just where Windows chose to put them.

Of course, maybe it's your computer telling you it's time for an SSD

 

[denis280]

Of course, maybe it's your computer telling you it's time for an SSD

for sure.just like Ketchup mention you could run chkdsk.but sometime it come out with no errors.A brand new SSD and you will see the big change.

 

[lessthanuthought]

Oh man, that sucks... WD Black is 5 year warranty though I think so just get a new one.

 

[denis280]

WD Black is 5 year warranty though I think so just get a new one.

You Could.i use to.but about a year ago i switched for a samsung SSD.

 

[lessthanuthought]

You Could.i use to.but about a year ago i switched for a samsung SSD.

Yeah I have a 840 pro in my main computer. Love it, and the price and performance on the new EVOs looks awesome but this is just a backup computer, so not worth it to drop ~150 into it when a new WD Black will be free

 

[denis280]

Yeah I have a 840 pro in my main computer. Love it, and the price and performance on the new EVOs looks awesome but this is just a backup computer, so not worth it to drop ~150 into it when a new WD Black will be free

No doubt.and make sure to come back with result.

 

[lessthanuthought]

result of what, chkdsk?

 

[denis280]

result of what, chkdsk?

The result for the new HDD.

 

[lessthanuthought]

The result for the new HDD.

Ah, ok will do. Thanks for the help Denis and Ketchup