|
Answer» hi im new to this specific forum but i do love to try new stuff and this semed like a nice comunity so i thought id try and post my problem here.
My problem is that my pc started to give me a few BSOD. At the start i thougt i damaged one of the ram blocks when instaling the new CPU cooler, but im now starting to think i was wrong on that since i keep geting different BSOD all tha time but at the same time still unsure becos a defected ram dosent neceseraly cause the same BSOD all the time.
I then re instaled windows (needed to do that anyhow for a long time and this gave me the exuse to get of me *censored* and do it ) but after the reinstal and the lovely BSOD just keeps haunting me. And now i suspect it being my aging hard drive or the cheep motherebord i got my hands on (il EXPLANE the thinking behind the motherebord further down) now il edmit that im lazy when it comes to my pc seing as a make my living on pc maintenence and selling custom build pc's but can never realy be to bothered with my own
here are the specs on my pc il post it as detailed as i can
OS: Windows 7 Ultimate 64 bit
CPU: AMD FX-9590 8 core runing at a standard 4.0 GHz (old one was a AMD Phenom2 965)
CPU Fan: Noctua DH-D14
RAM: 1x 8GB block (in ram dock 1) 2x 4GB blocks
HD 1: Hitachi HD103SJ 500GB (its bin with me for about 4 years and for some reson i still have OS on this one so this might be problem)
HD 2: SAMSUNG LaCie 2TB (use to be a usb drive but now internal )
HD 3: SAMSUNG 1TB
CD Roms: TSST corp TS-H653L(second one is TS-H653N)
GPU: Nvidia Geforce GTX 590 using driver version 9.18.13.3523
Power supply: corsair cmpsu-850TX
Motherbord: Gigabyte 990FXA-UD3 (the reson i suspect this is that i got a hold of few of there for next to nothing becos there old REV 1.0 and there fore have no official support for my curent CPU but i was told by a colleague that he was runing that motherebord and CPU together without any problems so i decided to save a few bucks for myself and nick one of the ones i got for myself which might have bin a blunder in hinsight )
and now on to the fun stuff
i used bluescreenview to compile the BSOD dumps into a text file and il post them here (these are just the ones i got the last 24 hours after re installing windows)
PS. so sorry for the bad spelling but im sleepy and dyslektik and i just dont feal like staring at the text for an hour
==================================================
Dump File : 051714-36551-01.dmp
Crash Time : 2014-05-17 16:46:29
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000004
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`034dcb54
CAUSED By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f880
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.17273 (win7_gdr.130318-1532)
Processor : x64
Crash Address : ntoskrnl.exe+6f880
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\051714-36551-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 291 776
Dump File Time : 2014-05-17 16:51:15
==================================================
==================================================
Dump File : 051614-38360-01.dmp
Crash Time : 2014-05-16 20:58:22
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`0e102028
Parameter 3 : 00000000`b0800000
Parameter 4 : 00000000`00040151
Caused By Driver : hal.dll
Caused By Address : hal.dll+12903
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+6f880
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\051614-38360-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 293 488
Dump File Time : 2014-05-16 21:00:20
==================================================
==================================================
Dump File : 051614-41246-01.dmp
Crash Time : 2014-05-16 00:06:31
Bug Check String :
Bug Check Code : 0x00000101
Parameter 1 : 00000000`00000019
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`02fd5180
Parameter 4 : 00000000`00000003
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+3e206
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+71f00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\051614-41246-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 288 424
Dump File Time : 2014-05-16 00:09:27
==================================================
==================================================
Dump File : 051514-21450-01.dmp
Crash Time : 2014-05-15 22:36:23
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`03315c22
Parameter 3 : fffff880`0a464980
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.17273 (win7_gdr.130318-1532)
Processor : x64
Crash Address : ntoskrnl.exe+71f00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\051514-21450-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 292 944
Dump File Time : 2014-05-15 22:39:23
==================================================
Well they are quite varied in cause and all over the place...
3 most common causes of this would be HDD issues ...a weak/flakey PSU...or Windows corruption.
1st think i would do tonite after your done with the PC is open a Command prompt and run chkdsk /r.....let it run to completion...you don't have to watch it so it can be done while you sleep.
For the PSU if it's a cheapo model or off name brand try and borrow one for a day and swap it in there to see if they go away...if they do replace it with a quality unit.
For the OS since it's Win7 you can run a Repair Install...which if done properly will retain all your Apps and Data.
Let us know the chkdsk results 1st and we'll go from there...
Note: There is a space between the command and the/switch.sorry for late reply bin upp for 32 hours and had to sleep alittle
And now i cinda feal stubid here becos i forgot to say what iv alredy done so far
i alredy ran 10 ram test with the Windows Memory Diagnostic and that gave me no ansers as no problems were encountered and i did run a chkdsk and didint say much there ithere but i dug it upp in EVENT viewer for ya and il post it here and as far as the PSU goes its a good brand (corsair 850w) so i wasent to worried about that one but i did change it for the one in my stream pc and didint make any diference. The window being corupt is a possibilaty but not likely since i just instaled it about 48 hours agou that is whie i leening towars the botherbord being the problem becos of it being a rev 1.0 with no offical support for this processor but like i sead earlyer my colleague did say he had the same motherbord/pross setup but im thinking he was wrong and had a later rev bord in his settup
anyhow heres the chkdsk log
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 5)...
224768 file records processed. File verification completed.
270 large file records processed. 0 bad file records processed. 2 EA records processed. 60 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
291714 index entries processed. Index verification completed.
0 unindexed files SCANNED. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
224768 file SDs/SIDs processed. Cleaning up 205 unused index entries from index $SII of file 0x9.
Cleaning up 205 unused index entries from index $SDH of file 0x9.
Cleaning up 205 unused security descriptors.
Security descriptor verification completed.
33474 data files processed. CHKDSK is verifying Usn Journal...
37623776 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
224752 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
15335985 free clusters processed. Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.
128303090 KB total disk space.
66519404 KB in 161523 files.
106972 KB in 33475 indexes.
0 KB in bad sectors.
332770 KB in use by the system.
65536 KB occupied by the log file.
61343944 KB available on disk.
4096 bytes in each allocation unit.
32075772 total allocation units on disk.
15335986 allocation units available on disk.
Internal Info:
00 6e 03 00 c1 f9 02 00 0e 8d 05 00 00 00 00 00 .n..............
33 01 00 00 3c 00 00 00 00 00 00 00 00 00 00 00 3...<...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Windows has finished checking your disk.
Please wait while your computer restarts.
and heres anothere fresh one ran on the command prompt
Chkdsk was executed in read-only mode on a volume snapshot.
Checking file system on C:
The type of the file system is NTFS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
224768 file records processed. File verification completed.
270 large file records processed. 0 bad file records processed. 2 EA records processed. 60 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
291718 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
224768 file SDs/SIDs processed. Cleaning up 203 unused index entries from index $SII of file 0x9.
Cleaning up 203 unused index entries from index $SDH of file 0x9.
Cleaning up 203 unused security descriptors.
Security descriptor verification completed.
33476 data files processed. CHKDSK is verifying Usn Journal...
37523360 USN bytes processed. Usn Journal verification completed.
Windows has checked the file system and found no problems.
128303090 KB total disk space.
67080016 KB in 161557 files.
106976 KB in 33477 indexes.
0 KB in bad sectors.
332198 KB in use by the system.
65536 KB occupied by the log file.
60783900 KB available on disk.
4096 bytes in each allocation unit.
32075772 total allocation units on disk.
15195975 allocation units available on disk.
i should also mentsion that my primary disk is partisioned 350GB and the system is on the 122GB part of it just had this one when loading a webbpage tab in firefox
==================================================
Dump File : 051714-23899-01.dmp
Crash Time : 2014-05-17 23:02:30
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffff800`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`0350c6f2
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f880
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.17273 (win7_gdr.130318-1532)
Processor : x64
Crash Address : ntoskrnl.exe+6f880
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\051714-23899-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 293 456
Dump File Time : 2014-05-17 23:04:19
==================================================
Quote The window being corupt is a possibilaty but not likely since i just instaled it about 48 hours agou that is whie i leening towars the botherbord being the problem becos of it being a rev 1.0 with no offical support for this processor
This jumps out at me...i don't care if your colleague got it to work it's not a good way to run a PC.
Replace the MBoard with one that supports the CPU.
Quote from: patio on May 17, 2014, 03:17:34 PMThis jumps out at me...i don't care if your colleague got it to work it's not a good way to run a PC.
Replace the MBoard with one that supports the CPU.
well i wouldent say that neceseraly a bad way to run a pc becos if it had worked then there woudent have bin a problem but i think you are right though so il try with anothere motherebord i think i have a REV 4 of the same bord lying around so il try with that and se what hapeneds
the reson i trusted my colleague is that he works with computers just as i do so i thought he would be right but like i did say that might have bin a blunder on my part espesialy since it was he who had the 8 motherebords in stock that i bought of him cheap Having a dig into your BSOD codes...
I too have run that CPU and Board in combination with no issues.
0x0A is usually caused by bad RAM. You have done the tests to rule that out.
0x124 is a general hardware error. I used to get these on Win 7 Enterprise 64-bit until I unplugged my DVD-R/W drive, I had 0x0A codes occasionally because of this too. Unplug your optical drives and see if the issues persist. My CCNA tutor also had the same problems with his optical drive too.
0x101 I have never seen before, but giving it a Google it tells me it is a CLOCK_WATCHDOG_TIMEOUT error, combined with the driver at fault being tcpip.sys, sounds like an issue with the network adapter communi Again this could be caused by the buses being busy or locked by the optical drives. See here for more info on this BCC:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff557211(v=vs.85).aspx
0x3b is generally caused by bad data being swapped back and forth from the page file to RAM, or from the graphics adapter to RAM. Again this is a very seldom seen code. Again I have a good feeling about your optical drives causing these issues, and is definitely worth unplugging them for a day or two to see if the issues go away.
After I was given Windows 8.1 for free via Dreamspark (being an academic student!) I plugged my optical drive back in, no issues for over a month. It appears to be an issue with Win 7 64-bit.
hmmm i have seen optical drive cause some weird things before so it woudent suprise me
for fun and becos it was aging anyhow i changed my system hard drive the othere day to a ADATA 128 GB SSD
after that i dont seme to get the same blue screens anymore but instead i have had 3 of the and thay all came upp just as im installing windows uppdates and then dont come agen at all
and it was kinda funny you shoud post this idea becos one of the blue screens is caused by cdrom.sys
here see for urself
==================================================
Dump File : 052414-14476-01.dmp
Crash Time : 2014-05-24 16:25:04
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`034c66f2
Parameter 3 : fffff880`036a7120
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f880
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.17273 (win7_gdr.130318-1532)
Processor : x64
Crash Address : ntoskrnl.exe+6f880
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052414-14476-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 293 464
Dump File Time : 2014-05-24 18:37:59
==================================================
==================================================
Dump File : 052314-15600-01.dmp
Crash Time : 2014-05-23 22:10:55
Bug Check String :
Bug Check Code : 0x00000101
Parameter 1 : 00000000`00000019
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`02fd5180
Parameter 4 : 00000000`00000003
Caused By Driver : cdrom.sys
Caused By Address : cdrom.sys+3e8b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+71f00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052314-15600-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 291 936
Dump File Time : 2014-05-23 22:11:59
==================================================
==================================================
Dump File : 052114-12776-01.dmp
Crash Time : 2014-05-21 03:23:13
Bug Check String :
Bug Check Code : 0x00000101
Parameter 1 : 00000000`00000019
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`02f6a180
Parameter 4 : 00000000`00000007
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.17273 (win7_gdr.130318-1532)
Processor : x64
Crash Address : ntoskrnl.exe+71f00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052114-12776-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 293 416
Dump File Time : 2014-05-21 03:24:13
==================================================
also i did look it upp and there are a few ppl out there using this MB+CPU combo and it is sopostu work aparantly
|
