Computer Hope
Microsoft => Microsoft Windows => Windows Vista and 7 => Topic started by: Diggity on May 09, 2016, 06:49:03 PM
-
Hello all,
I've recently had a string of BSODs (Windows 7) which occur and then afterwards I cannot successfully boot my computer unless it has been switched off for some hours. After such a crash, the computer will power up but fail to move to POST or display anything. The HDD sounds inactive during this, the signs of life are spinning fans. After a successful boot, the computer runs fine for some minutes before crashing again.
Each code is different, and I have no idea how I should proceed. I suspect it might be a driver issue which I could possibly solve by reinstalling windows, but I don't know if it is hardware. I'd imagine if it's hardware related it would fail during Windows reinstall as well.
I built this computer a few years ago, I recently upgraded my graphics card and case fans, but the computer worked fine for at least 2 weeks after.
CPU: AMD Athlon Multi Core Processor AD760KWOHLBOX
Mobo: Gigabyte GA-F2A88X-D3H
GPU: GIGABYTE GeForce GTX 960
RAM: 8Gb
PSU: Rosewill 450W "Capstone"
The latest BSOD has a code of 0x7E . I don't have the Bluescreenview of that one because it just happened. If needed, I can post that next time my PC will boot. The other crashes are listed below from Bluescreenview.
Please let me know if you need any more info, and thanks in advance for the help.
==================================================
Dump File : 050816-22760-01.dmp
Crash Time : 5/6/2016 8:59:57 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`06c7e442
Parameter 3 : fffff880`0e12fdd0
Parameter 4 : 00000000`00000000
Caused By Driver : afd.sys
Caused By Address : afd.sys+49442
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75c00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\050816-22760-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 407,224
Dump File Time : 5/8/2016 7:48:06 PM
==================================================
==================================================
Dump File : 050616-19890-01.dmp
Crash Time : 5/5/2016 12:06:51 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00005002
Parameter 2 : fffff700`01080000
Parameter 3 : 00000000`0000092e
Parameter 4 : 0000ff2d`fffffffe
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75c00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18113 (win7sp1_gdr.130318-1533)
Processor : x64
Crash Address : ntoskrnl.exe+75c00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\050616-19890-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 313,048
Dump File Time : 5/6/2016 8:46:38 PM
==================================================
==================================================
Dump File : 042916-29827-01.dmp
Crash Time : 4/29/2016 2:05:20 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+5e205
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75bd0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\042916-29827-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 392,800
Dump File Time : 4/29/2016 2:09:38 PM
==================================================
==================================================
Dump File : 042316-19624-01.dmp
Crash Time : 4/23/2016 2:46:08 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffff800`034455d3
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000008
Parameter 4 : fffff800`034455d3
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75c00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18113 (win7sp1_gdr.130318-1533)
Processor : x64
Crash Address : ntoskrnl.exe+75c00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\042316-19624-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 272,312
Dump File Time : 4/23/2016 2:51:45 AM
==================================================
==================================================
Dump File : 042316-25303-01.dmp
Crash Time : 4/22/2016 6:50:29 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`03347f7e
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`0000d9f4
Caused By Driver : dxgmms1.sys
Caused By Address : dxgmms1.sys+7f76
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75c00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\042316-25303-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 356,640
Dump File Time : 4/23/2016 2:36:47 AM
==================================================
==================================================
Dump File : 032716-21465-01.dmp
Crash Time : 3/27/2016 8:42:25 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`030cff0f
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75c00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18113 (win7sp1_gdr.130318-1533)
Processor : x64
Crash Address : ntoskrnl.exe+75c00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\032716-21465-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 367,880
Dump File Time : 3/27/2016 8:43:44 PM
==================================================
-
You have a major hardware failure. It is almost certainly either the motherboard, ram or power supply.
-
Start with getting a new PSU. You ought to have a spare PSU on hand anyway.
-
So I finally got a new power supply in yesterday and it crashed once and ran for hours after with no issue, but today it has crashed again and failed to post. I'm guessing it is a Motherboard issue?
The last crash I have the dump for is this one from yesterday (Bluescreenview seems to have not saved the one from this morning correctly and I'm unable to access it at the moment, but I'll update the post if possible).
It was definitely more stable with the new PSU (till now)
==================================================
Dump File : 052116-26598-01.dmp
Crash Time : 5/21/2016 12:41:42 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffff80`0afb05b8
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`0337e42c
Parameter 4 : 00000000`00000005
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75c00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18113 (win7sp1_gdr.130318-1533)
Processor : x64
Crash Address : ntoskrnl.exe+75c00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052116-26598-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 407,640
Dump File Time : 5/21/2016 12:51:24 PM
==================================================
After the crash this morning, upon reboot windows explorer failed to start correctly giving an error of 0xc000007b. Same error given after attempting to start explorer with the task manager.
I also got an error of
STOP: c000007b {Bad Image}
winsrv is either not designed to run on windows or it contains an error
Following this the computer failed to move past post, or allow me to use the F keys to select other options. After a restart the computer didn't display anything.
Thanks again for the help.
-
Try booting the PC with bare configuration. Not graphics card, one stick of RAM no drives or printers. The object is to get into the BIOS and re set the default values.
(A bad GPU can lock a PC, Use the built-tin graphics. And a bad HDD or DVD drive can suck power and stop the PC from booting reliably. And a USB printer prevents the USB stick from booting.)
Also, check the CMOS cell.
You can get Memtest86 to boot from a USB stick.
http://www.memtest86.com/technical.htm
There are many good approaches for testing memory. However, many tests simply throw some patterns at memory without much thought or knowledge of memory architecture or how errors can best be detected. This works fine for hard memory failures but does little to find intermittent errors. BIOS based memory tests are useless for finding intermittent memory errors.
...
Run the test for a long time.
This helps verify the RAM is or is not the problem.
-
Unfortunately I have no integrated graphics, so the graphics card will have to be included. I don't own an internal optical drive or a printer, so those aren't an issue.
I attempted another memtest, the last attempt was with the old power supply, and it again stopped displaying again before the first pass was completed.
However, I swapped RAM with a buddy of mine and it has been working fine in his computer. I borrowed his single stick of RAM and it is unreliable in all 4 of my slots. I did notice a day or two ago that my RAM (2x 4Gb sticks) was not being read properly by my computer. It was showing that I had only 4Gb installed when both sticks were in. Because of that I suspect that if RAM is the issue, it's not in the sticks themselves but in the ports on the Motherboard. The single stick that I am still borrowing is plugged into a slot that was previously not in use.
I was able to set the BIOS to default settings, and since the HDD was disconnected I booted into a Live USB of Ubuntu to see if a crash would happen there as well, which it did after some minutes. The computer continues to boot unreliably.
I'm still assuming that the issue is in the Motherboard, but I am going to look into picking up a new CMOS battery from Walmart or whatever tomorrow if I don't have a spare somewhere in the house.
Is there anything else I should attempt before ordering a new motherboard?
-
Yes, borrow an old reliable graphics card and see if that makes a difference. Let Windows uninstall a simple default driver. The problem just might be the graphics drive and/or the graphics card you have been using.