Tech Support Forum banner
Status
Not open for further replies.

New build PC BSOD win7 64bit

4K views 20 replies 5 participants last post by  reventon  
#1 · (Edited)
Hi, i've read the posting instructions so hopefully i've go this right

Intel Core i7 870 Lynnfield 2.93GHz 8MB LGA1156
ASUS P7P55D-E LX Intel P55 Core i7/
OCZ Intel Extreme Series 2x2GB DDR3-1600 CL8
Prolimatech Megahalems Rev. B CPU Cooler LGA1366/LGA1156/LGA775
Samsung Spinpoint F3 1TB 32MB 7200rpm SATAII
EVGA nVidia GeForce GTS450 1GB GDDR5 PCI-E
Silverstone Strider Essential ST50F-ES 500W PSU 80 PLUS
AOC IF23 23IPS 16:9 Monitor
Microsoft Windows 7 OEM Home Premium 64Bit

Ive run memtest, re installed the OS 3 times, updated all drivers, removed a second HDD and i'm still getting BSOD.

I have noticed that internet explorer stops lots! and when I get the BDOS I have to login to all of my pages that I am normaly auto logged in to.

Sometimes it crashed after hours of use but today less than 5 minutes with only internet explorer and canon digital photo professional open.

Am I supposed to attach the while windows folder (zip)?



Cheers
Jason
 

Attachments

#2 ·
Evening from earthquake-central. I was up your way two years ago, Bay of Islands etc. - very nice place.

The only 3rd party driver mentioned directly in your BSODs = aswMonFlt.sys

This is part of Avast, and explains the networking related (Internet Explorer) BSODs.

So, remove Avast and hopefully the problem should go away
Download the Avast Removal Tool (ART) from here -> save to desktop.

Boot into SAFEMODE - NO Networking. Then go to desktop, RIGHT-click on the ART icon and select Run as Administrator.

When complete - re-boot.

Install MS Security Essentials --> http://www.microsoft.com/Security_Essentials/

Then reset the Windows Firewall to its default settings -
START -> type cmd.exe -> right-click -> run as administrator -> type netsh advfirewall reset press enter
If it doesn't, then the next step is to test the hard drive. Storage drivers were mentioned in a few BSODs, and I don't like the look of that.
Hard Drive Testing

First run chkdsk

START -> type cmd.exe -> Right-click -> run as admin -> type chkdsk /f -> Press Y at prompt -> restart computer.

Also to check the drive's physical state run SeaTools

Download SeaTools for DOS from here: http://www.seagate.com/ww/v/index.j...p?locale=en-US&name=SeaTools&vgnextoid=720bd20cacdec010VgnVCM100000dd04090aRCRD

Follow the instructions to run it. After it has detected the drive, select Basic Tests, then Long Test and let it run.
Regards,
Ben

BUGCHECK SUMMARY
Code:
[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov 25 16:58:05.510 2010 (GMT+13)
System Uptime: 0 days 0:03:23.447
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29f57 )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Safari.exe
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff700`01080000 00000000`00004414 00004412`0000882c
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov 25 07:19:57.929 2010 (GMT+13)
System Uptime: 0 days 0:26:36.866
*** WARNING: Unable to verify timestamp for aswMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
Probably caused by : aswMonFlt.sys ( aswMonFlt+52db )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`054ef2db fffff880`05fcca98 fffff880`05fcc300
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Nov 21 18:02:17.877 2010 (GMT+13)
System Uptime: 0 days 0:13:07.814
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+1fe )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`07e10cc8 fffff880`07e10530 fffff880`012b7c27
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov 13 20:49:54.904 2010 (GMT+13)
System Uptime: 0 days 0:49:48.730
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteScb+108 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`033545d8 fffff880`03353e40 fffff800`0306dcbf
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov 13 19:59:10.414 2010 (GMT+13)
System Uptime: 0 days 0:57:03.351
*** WARNING: Unable to verify timestamp for aswMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
Probably caused by : aswMonFlt.sys ( aswMonFlt+1135 )
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  fsx.exe
Bugcheck code 00000019
Arguments 00000000`00000020 fffff8a0`056f5850 fffff8a0`056f5920 00000000`050d021a
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/font]
 
#5 · (Edited by Moderator)
I've removed Avast, installed Microsoft Security Essentials, I just ran chkdsk, do I have to watch it or do I now look for a Log file or somthing? Also, will run seatools once I find a blank cd to burn it to.

Thanks
Jason

I have run seatools short and long test, both times the test finished with a pass, now what?
 
#9 ·
When it happened this time I was importing photo's from a SD card through my HP printer. I havn't tried a second HDD but I did have a secondary HDD installed initialy, it is a WD Caviar Green 500GB which is formatted in FAT32 because I use it to backup files for my PS3.
I hope that answers your question. I am begining to think it is my HDD - Samsung Spinpoint F3 1TB 32MB 7200rpm SATAII

Thanks again
Jason
 
#10 ·
I suspect it is your hd as well. More specifically it could be just as simple as some bad clusters. I would try using your other hd and that will at the very least solve your issue or rule off one possible cause of it. Don't immediately toss out the other hd though, as it could be fixable. You say seatools tests passed, try a few other pieces of software. It is rare but once in a while a single piece of software might overlook a small problem.FJDT (Fujitsu ATA Diagnostic Tool) is a tool I have used with success before. Let us know and good luck.
 
#12 ·
Still having this issue, :upset: I want to move my OS and all of my files to another HDD and disconnect the suspected faulty Samsung drive and run it like that for a few days.

Could someone tell me of an easy way to cary out this task.


TIA Jason
 
#13 ·
Norton Ghost is a good tool to do just what your wanting to do.

[url]http://lmgtfy.com/?q=Norton+Ghost[/URL]

If it is the HDD that is the problem, and you have finished doing your OS and file move, try formatting the whole HDD you had previously and see if you can't get it back up and running :D.

Hope this helps!
 
#14 ·
#18 ·
WOW!! i'm gettin so sick of this thing!!!!

on the 31st I was running from the WD 500gb and had the Samsung 1TB installed to transfer files across and another Bluescreen, I unplugged the Samsung and decided it was time to go and party for New Years, just switched the computer on for the first time this morning with only the WD 500gb installed and yet another BSOD and when I re booted I couldn't open internet explorer and everything was going very slow, so I powered off and am running back on the Samsung OS again. are there any memory test utilitys other than MEMTEST?
 
#20 ·
Thanks guys

It worked 100% on 1 stick of RAM doing all of the things I usualy do, Internet Explorer, Photoshop Elements & Lightroom, I powered down and swaped ram sticks, booted up and opened internet explorer, it failed to respond imediatly and lightroom wouldn't open, within 2 minute of logging in BSOD, and after that it wouldn't even boot, straight to "startup repair" which wouldn't work and then another BSOD, I then re fitted the ram that worked fine for 10+ hours of computing and back to normal.

I am 99.9% certain that I have a faulty stick of RAM, memtest or Prime 95 showed no faults but under normal working conditions there is a problem.
 
Status
Not open for further replies.
You have insufficient privileges to reply here.