Getting BSOD / Think it might be related to my HDD.

Zephor · 06 May 2012

Just built the computer with all new parts expect for the hard drive (it was a pretty old one.) Everything went completely fine but the hard drive was making some weird sounds like it was dying (grinding and stuff.) I pretty much have an idea that this is the hard drive, I just want to confirm that though because the error I get on the BSOD is 0x0000001A which is apparently RAM/memory related. This makes no sense though because I only have on stick of 4GB RAM installed so my computer shouldn't run in the first place if that was the problem.

This is on Windows 7 Home Premium x64. Also I don't get these BSOD's instantly after start up (they usually take a while.) Also, I only started getting them after the system did one of those disk checks on start up because of "corrupted" files. It's a pretty big coincidence because this is the same hard drive a friend of mine used and if I recall correctly, he had same errors also. Thanks for any help guys, and please be quick so I know if I need to pick up a new hard drive or RMA the ram (before I run out of time) if that is the problem...

Zephor · 06 May 2012

Really... almost to the bottom of the page. Anyway I tried running Memtest86 from a USB but it doesn't want to boot at all. I tried several different flash drives. CD isn't an option because I don't have an optical drive. I'm scared this is going to be more than the hard drive...

usasma · 06 May 2012

Start with these bootable diagnostics (particularly the hard drive tests): Initial Hardware Diagnostics

More to follow when I analyze the memory dumps (gotta get ready for work shortly)......

usasma · 06 May 2012

Only 69 updates since SP1 - please check Windows Update for any available updates (excepting language updates).

MSINFO32 has no information in it. Have you tweaked any services on the system?
Then:

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.

Are you using a wireless USB device? If so, please read my rant:

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.

It looks like you are using a wireless USB device and it's driver is from the Vista era (2008)

Other than that, there's numerous STOP 0x1A's - so I'd suggest running a memory diagnostic. Here's a link to the procedure that I suggest (it's free): Memory Diagnostics

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
How I do it: http://www.carrona.org/howidoit.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


amdxata.sys  Fri Mar 19 12:18:18 2010 (4BA3A3CA)
MpFilter.sys Fri Mar 09 06:05:26 2012 (4F59E3F6)
athrxusb.sys Tue Jul 29 08:47:13 2008 (488F1151)
atikmpag.sys Thu Apr 05 21:10:44 2012 (4F7E4294)
AtihdW76.sys Thu Feb 23 07:30:12 2012 (4F463154)
HECIx64.sys  Tue Oct 19 19:33:43 2010 (4CBE2AD7)
atikmdag.sys Thu Apr 05 21:48:25 2012 (4F7E4B69)
L1C62x64.sys Tue Aug 24 05:14:01 2010 (4C738D59)
EagleX64.sys Fri Jun 17 02:52:11 2011 (4DFAF99B)

http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
http://www.carrona.org/drivers/driver.php?id=athrxusb.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=AtihdW76.sys
http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=L1C62x64.sys

BSOD BUGCHECK SUMMARY

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\050612-16894-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Sun May  6 02:53:53.090 2012 (UTC - 4:00)
System Uptime: 0 days 0:08:57.479
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+355d4 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+355d4
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`008af2d0 00000000`0000ffff 00000000`00000000
BiosVersion = P1.20
BiosReleaseDate = 06/21/2011
CPUID:        "Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\050512-19266-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Sun May  6 02:44:01.090 2012 (UTC - 4:00)
System Uptime: 0 days 0:22:18.479
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13c82 )
BUGCHECK_STR:  0x1a_41201
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  mscorsvw.exe
FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13c82
Bugcheck code 0000001A
Arguments 00000000`00041201 fffff680`0001d7f8 62400000`6215fb67 fffffa80`051f9520
BiosVersion = P1.20
BiosReleaseDate = 06/21/2011
CPUID:        "Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\050512-23166-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Sun May  6 02:20:56.977 2012 (UTC - 4:00)
System Uptime: 0 days 0:06:37.367
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02ac773d fffff880`06e21f70 00000000`00000000
BiosVersion = P1.20
BiosReleaseDate = 06/21/2011
CPUID:        "Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\050312-19078-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Thu May  3 15:31:21.909 2012 (UTC - 4:00)
System Uptime: 0 days 0:38:20.298
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+355d4 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  mscorsvw.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+355d4
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`008af2a0 00000000`0000ffff 00000000`00000000
BiosVersion = P1.20
BiosReleaseDate = 06/21/2011
CPUID:        "Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Zephor · 06 May 2012

Problem is that I can't get Memtest86 to run of a boot-able flash drive. It worked fine when I was installing Windows 7 though. Other than that, I'll get to doing those other things you told me.

So is there a pretty good chance that this could be related to the system deleting corrupt files off the hard drive due to bad sectors? That could screw up drivers and such correct?

I don't understand how it could be the one stick of ram because for the first two days after building the computer I was playing games for hours at a time and didn't get any problems. THEN, after I got that deleting corrupt files screen on boot up I started getting this BSOD. Should I continue to use the wireless USB device? It's the only thing I really have to connect it to the internet. I'm not gonna bother installing any updates at the moment though because today my cousin is going to give me a few hard drives and I'm just going to re-install on those and see if it gives me any more problems.

Zephor · 06 May 2012

Alright got the MSINFO32. Don't know why there was nothing there as I haven't tweaked the system or anything. I ran the HDD check from my specific manufacturer and it passed apparently so I don't know why the deal is. I haven't gotten a BSOD yet today so that's good I guess.

Zephor · 06 May 2012

Still haven't gotten a BSOD yet today (and I've been playing some games.) Could anyone else take a look since usasma is busy?

usasma · 06 May 2012

The wireless USB device is, IMO, the most likely cause of your BSOD's. You need to figure out a way to test to see if it's the cause. You can:
- not use it and see if the BSOD's stop
- use a very long wire (and not use the wireless USB device) and see if the BSOD's stop
- purchase a wireless PCI/PCIe card and install that in your system (and not use the wireless USB device) and see if the BSOD's stop.

Zephor · 06 May 2012

Yeah I haven't had a BSOD all day even though I'm still using the wireless USB. I'm having another problem right now though.. I have it hooked up with the HDMI through my Radeon HD6850 and it's saying I don't have a speaker or anything plugged in. I tried using a audio cable and using the audio straight from the motherboard and it says the same exact thing. I had this problem before but I just did a restore back a couple days and it fixed the problem. What could this be?

EDIT:

usasma said:

The wireless USB device is, IMO, the most likely cause of your BSOD's. You need to figure out a way to test to see if it's the cause. You can:
- not use it and see if the BSOD's stop
- use a very long wire (and not use the wireless USB device) and see if the BSOD's stop
- purchase a wireless PCI/PCIe card and install that in your system (and not use the wireless USB device) and see if the BSOD's stop.

Oh I also want to ad that I'm pretty sure it should be the reason of the BSOD, because why else would I get one while on idle? Anyway I still haven't had one today and about 2 hours ago I switched over to using a long cable to connect straight to the router. Hopefully I don't get any more problems.

usasma · 07 May 2012

Sorry, but I'm not real good with sound problems. I'd suggest posting over in the video forums for help with this: Graphic Cards - Windows 7 Forums