Sign in with
Sign up | Sign in
Your question

Random Crashes/BSoD

Last response: in Systems
Share
March 29, 2011 10:17:21 PM

I recently built a computer and any game I would run would randomly crash at some point in time. On top of that I would get random BSoD's.

I figured it was my nvidia card conflicting with my ATI motherboard so I got an ATI card but same thing happened after that. I even reformatted windows thinking old nvidia drivers were causing conflicts.

Here are my specs.
Processor:
2.80 gigahertz AMD Phenom II X6 1055T
256 kilobyte primary memory cache
512 kilobyte tertiary memory cache
64-bit ready
Multi-core (6 total)
Not hyper-threaded

Memory: OCZ Reaper HPC
8190 Megabytes Usable Installed Memory

Slot 'A0' has 4096 MB
Slot 'A1' has 4096 MB
Slot 'A2' is Empty
Slot 'A3' is Empty

Hard Drive: WDC WD1501FASS-00W2B0 ATA
c: (NTFS on drive 0) 1500.19 GB 1298.32 GB free
WDC WD1501FASS-00W2B0 ATA Device [Hard drive] (1500.30 GB) -- drive 0, s/n WD-WMAY00357424

Video Card:
ATI Radeon HD 5800 Series [Display adapter]

Sound Card:
Realtek High Definition Audio

Network Adapter:
Microsoft ISATAP Adapter
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)

Operating System:
Windows 7 Home Premium 64-bit (6.1, Build 7600) (7600.win7_gdr.101026-1503)

Motherboard: Gigabyte GA-89OGPA-UD3H
Board: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H
Bus Clock: 200 megahertz
BIOS: Award Software International, Inc. FD 07/23/2010

My DxDiag
http://www.privatepaste.com/c0fd7bcb81

Blue screen errors:

==================================================
Dump File : 032711-16738-01.dmp
Crash Time : 3/27/2011 5:23:18 PM
Bug Check String : ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Bug Check Code : 0x000000fc
Parameter 1 : 00000000`00010128
Parameter 2 : e6f00000`32a0d867
Parameter 3 : fffff880`02ed3600
Parameter 4 : 00000000`00000000
Caused By Driver : dxgmms1.sys
Caused By Address : dxgmms1.sys+c74d
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\032711-16738-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 7600
Dump File Size : 276,200
==================================================

==================================================
Dump File : 032711-19936-01.dmp
Crash Time : 3/27/2011 4:01:20 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00005003
Parameter 2 : fffff780`c0000000
Parameter 3 : 00000000`0000e5cf
Parameter 4 : 0001e80f`0001ca9e
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.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\032711-19936-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 7600
Dump File Size : 276,248
==================================================

==================================================
Dump File : 032711-19032-01.dmp
Crash Time : 3/27/2011 1:17:52 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`043e85c9
Parameter 3 : fffff880`01f61db0
Parameter 4 : 00000000`00000000
Caused By Driver : dxgmms1.sys
Caused By Address : dxgmms1.sys+355c9
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\032711-19032-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 7600
Dump File Size : 276,200
==================================================

==================================================
Dump File : 032711-20092-01.dmp
Crash Time : 3/27/2011 12:45:58 AM
Bug Check String : ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug Check Code : 0x000000be
Parameter 1 : fffff880`02a16758
Parameter 2 : 80000002`20acd121
Parameter 3 : fffff880`027f4850
Parameter 4 : 00000000`0000000b
Caused By Driver : afd.sys
Caused By Address : afd.sys+16758
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\032711-20092-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 7600
Dump File Size : 276,200
==================================================



Games I play:
San Andreas Multiplayer
Fallout: New Vegas
Metro 2033
APB: Reloaded
Splinter Cell: Convictions

More about : random crashes bsod

March 30, 2011 1:36:48 AM

First I'd recommend to get into the BIOS and do a Load Optimized Defaults (or Load Defaults, depending on your BIOS). Once that is done, manually configure your RAM to the specs on the stickers on your RAM modules. After doing this, try playing one of your games, to check for stability. If you get BSOD, continue diagnosing with the following suggestsion.

Load Windows. Download and install the following free software:

1. FurMark - GPU tester
2. CPU-Z - Use this to check what your CPU and RAM are operating at
3. Prime95 - CPU/RAM tester
4. HW Monitor - Displays what your hardware temps and voltages are at
5. GPU-Z - like CPU-Z and HW Monitor, but for your GPU
6. SpeedFan - use this to get a second opinion on what CPU-Z shows.
7. MemTest86+ - A RAM tester

MT86+ is software that needs to be burned to cd (or made bootable on a flash drive) and is used independently of Windows. To use it, put the bootable media into your computer and reset the computer. The test will run automatically. Note that this test may take awhile; 8-10 hours, unless errors are found. Also note that it is best to test one RAM stick at a time.

Since BSOD are most commonly related to RAM, it is best to start your diagnosing with MT86+. If no errors are found, proceed.


Ideally, what you should do is pull you system apart and rebuild it outside of the case; this is called breadboarding. Breadboarding will rule out any case shorts as the reason for failure(s). Granted, most electrical shorts cause a "no boot/no display" issue, but still, it's good to be 100% sure.

Run both CPU-Z and HW Monitor and check your temps/voltages, make sure they're where they should/need to be. If not, shut down and verify you've installed the questionable components.

After verifying temps and voltages are correct, move on to GPU-Z. Again, check temps, make sure your GPU isn't getting too hot. If all is well, proceed. If card is running too hot, check to see if the fan is spinning and check the aux power cable to the card.

Now its time to run a stress test on the GPU. Run FurMark. Using this software will open a window in fullscreen mode and will cause your GPU temps to rise, significantly. Don't be alarmed if you see GPU temps in the mid 80's. If your system crashes while this is running, chances are the GPU is the cause. If you don't experience any difficulties, you can stop running this after about 20-30 minutes.

Next, use Prime95. This tests stability under 100% load on the CPU. Naturally, 100% load on the CPU means that you'll be testing RAM along with it, but keep in mind the focus is on the CPU. If any errors are detected, you will see a message instructing you to look at a log file created by Prime95.

m
0
l
!