Random BSOD problems, unknown causes.

[phosphorus2500]

Ok, for the past week or so now (Sorry for inaccurate timing that I'll be giving) I've been getting a lot of BSoD problems. These have included PFN list corrupt, System Service Exception, Page fault in non page area, and multiple memory management errors.

Two days ago (18th March 2012) I did a fresh install on an old hard drive I have in my computer, but which I have always used to install and run windows from. The BSoDs continued after this, some friends who are better with computers than myself (and I consider myself good with computers having studied it at uni and pursuing a job in IT) suggested it was an old HD issue, as I have run windows memory diagnostic tool and memtest and both reported no issues.

Yesterday I removed the old hard drive, made a 50gb partition in my 1tb hard drive and installed windows 7 professional x64 (which I have used for a long time now) and I still get blue screen errors.

All components of my computer were replaced with newer components midway through last year (as far as I can remember) including motherboard, RAM, graphics card, etc. I have been using Windows 7 x64 all this time. Drivers are up to date as far as I can tell.

Attached are the recommended files from the important post in this forum, the dump files and system health report.

Thank you reading and any help received. I will go to bed now and check the forums when I wake up.

 

[JMH]

1. Asacpi.sys

The pre 2009 version of this driver is a known BSOD cause. Yours is dated 2005.

Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).

Download and install it.

Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (not before).

2. I note you have AVG.

AVG can be a contributing cause of BSOD'S .
Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST

Download tools and utilities | AVG Worldwide

Microsoft Security Essentials - Free Antivirus for Windows

 

[zigzag3143]

In addition to followings JMH'S suggestions there are two issues you should address. If you are still crashing I would first update to Service pack 1 and then run these two tests.

Please run the System Update Readiness Tool (SURT) and then update to SP-1


32 Bit

Download: System Update Readiness Tool for Windows 7 (KB947821) [February 2012] - Microsoft Download Center - Download Details

64 Bit

Download: System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [February 2012] - Microsoft Download Center - Download Details


Now update to SP-1

Learn how to install Windows 7 Service Pack 1 (SP1)



These crashes were caused by memory corruption/exception (`c0000005) (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[phosphorus2500]

Ok, I updated the drivers stated above. I removed AVG, and I'm in the process of updating to Service Pack 1. So far no blue screens after AVG and the driver update but its early in the day yet. I will post back at the end of the day or if I have another blue screen to keep you updated.

Many thanks for the helpful and prompt replies

 

[zigzag3143]

Ok, I updated the drivers stated above. I removed AVG, and I'm in the process of updating to Service Pack 1. So far no blue screens after AVG and the driver update but its early in the day yet. I will post back at the end of the day or if I have another blue screen to keep you updated.

Many thanks for the helpful and prompt replies

Our pleasure and good luck

 

[phosphorus2500]

Ok, I just had another blue screen about ten minutes ago with no error message. I was talking on ventrilo, steam, and running the battlelog web service for battlefield 3. I forgot to mention previously that I have already run memtest before and it found no problems but I guess it wouldnt hurt to run it again. Im uploading the new dump files with this post.

 

[zigzag3143]

Ok, I just had another blue screen about ten minutes ago with no error message. I was talking on ventrilo, steam, and running the battlelog web service for battlefield 3. I forgot to mention previously that I have already run memtest before and it found no problems but I guess it wouldnt hurt to run it again. Im uploading the new dump files with this post.

SP=1 not installed.

 

[phosphorus2500]

Ok, think I've had two blue screens today, the first one I didnt see because I went AFK, came back and everything had restarted. The second one I had about ten minutes ago with a Driver IRQL not less or equal error message.

Service Pack 1 should be installed as I've let windows install all of its updates and everything. New dump files attached. Thanks for the help so far

 

[zigzag3143]

Ok, think I've had two blue screens today, the first one I didnt see because I went AFK, came back and everything had restarted. The second one I had about ten minutes ago with a Driver IRQL not less or equal error message.

Service Pack 1 should be installed as I've let windows install all of its updates and everything. New dump files attached. Thanks for the help so far

Sp-1 is still not installed.

 

[phosphorus2500]

Ok, windows service pack 1 is DEFINITELY 100% installed, and I have blue screened twice in the past 40 minutes although I suspect my participating in the Firefall beta may have aggravated whatever the problem is. New dump files are attached as always, I really hope with your help we can get this problem fixed cause I want my working computer back

 

[writhziden]

Problem Devices:

Belkin High-Speed Mode Wireless G USB Network Adapter	USB\VID_050D&PID_7051\8057	The drivers for this device are not installed.

Security Software:

msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	844	8	200	1380	22/03/2012 00:36	3.0.8402.0	12.48 KB (12,784 bytes)	27/04/2011 17:21
nissrv.exe	c:\program files\microsoft security client\antimalware\nissrv.exe	1200	8	200	1380	22/03/2012 00:37	3.0.8402.0	281.52 KB (288,272 bytes)	27/04/2011 17:21
msseces.exe	c:\program files\microsoft security client\msseces.exe	2392	8	200	1380	22/03/2012 00:37	2.1.1116.0	1.37 MB (1,436,736 bytes)	15/06/2011 14:35

Possible out of date driver:

ssadadb	fffff880`04e08000	fffff880`04e17000	Wed Jan 14 14:27:20 2009 (496e58b8)	0000debb		ssadadb.sys

ssadadb.sys

[list=1]
[*]Loading Dump File [D:\Kingston\BSODDmpFiles\phosphorus2500\Windows_NT6_BSOD_jcgriff2\032212-26254-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c1a000 PsLoadedModuleList = 0xfffff800`02e5e650
Debug session time: Thu Mar 22 01:31:55.648 2012 (UTC - 6:00)
System Uptime: 0 days 0:17:39.256
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002f8c3b1, fffff88008096ab0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObpWaitForMultipleObjects+186 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002f8c3b1, Address of the instruction which caused the bugcheck
Arg3: fffff88008096ab0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ObpWaitForMultipleObjects+186
fffff800`02f8c3b1 488b4a20        mov     rcx,qword ptr [rdx+20h]

CONTEXT:  fffff88008096ab0 -- (.cxr 0xfffff88008096ab0)
rax=00000000000000a8 rbx=fffff8a0020295c0 rcx=fffff80002c1a000
rdx=0000000000000000 rsi=000000000000000e rdi=fffffa800a12eb90
rip=fffff80002f8c3b1 rsp=fffff88008097490 rbp=fffff88008097ca0
 r8=0000000000000008  r9=fffff8a003b84000 r10=fffffa800a135060
r11=fffffffffffffd80 r12=fffff88008097a08 r13=fffff8a0039ebbd0
r14=000000000000000d r15=0000000000000010
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!ObpWaitForMultipleObjects+0x186:
fffff800`02f8c3b1 488b4a20        mov     rcx,qword ptr [rdx+20h] ds:002b:00000000`00000020=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Ventrilo.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002f8c3b1

STACK_TEXT:  
fffff880`08097490 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpWaitForMultipleObjects+0x186


FOLLOWUP_IP: 
nt!ObpWaitForMultipleObjects+186
fffff800`02f8c3b1 488b4a20        mov     rcx,qword ptr [rdx+20h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ObpWaitForMultipleObjects+186

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

STACK_COMMAND:  .cxr 0xfffff88008096ab0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ObpWaitForMultipleObjects+186

BUCKET_ID:  X64_0x3B_nt!ObpWaitForMultipleObjects+186

Followup: MachineOwner
---------
[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\phosphorus2500\Windows_NT6_BSOD_jcgriff2\032212-29421-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c0a000 PsLoadedModuleList = 0xfffff800`02e4e650
Debug session time: Thu Mar 22 01:13:10.897 2012 (UTC - 6:00)
System Uptime: 0 days 1:27:42.504
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8800fd9cd42, fffff8800a6349e0, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+26 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8800fd9cd42, Address of the instruction which caused the bugcheck
Arg3: fffff8800a6349e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+26
fffff880`0fd9cd42 488b5b08        mov     rbx,qword ptr [rbx+8]

CONTEXT:  fffff8800a6349e0 -- (.cxr 0xfffff8800a6349e0)
rax=fffffa8003e2e108 rbx=0000000000000000 rcx=fffffa80091a8f00
rdx=ffffffffffffffd0 rsi=fffff8a00a8a5500 rdi=fffffa80068e49a0
rip=fffff8800fd9cd42 rsp=fffff8800a6353c8 rbp=fffffa80091a8f00
 r8=fffff8800a635438  r9=fffff8800a635440 r10=fffffa8003fe6d48
r11=fffffa80091a8f40 r12=0000000000000000 r13=fffff8a002fbfbd0
r14=0000000000000000 r15=fffff8a0024aec90
iopl=0         nv up ei pl nz ac po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010216
dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+0x26:
fffff880`0fd9cd42 488b5b08        mov     rbx,qword ptr [rbx+8] ds:002b:00000000`00000008=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  FirefallClient

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800fd9cd42

STACK_TEXT:  
fffff880`0a6353c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+0x26


FOLLOWUP_IP: 
dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+26
fffff880`0fd9cd42 488b5b08        mov     rbx,qword ptr [rbx+8]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+26

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

STACK_COMMAND:  .cxr 0xfffff8800a6349e0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+26

BUCKET_ID:  X64_0x3B_dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+26

Followup: MachineOwner
---------

[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\phosphorus2500\Windows_NT6_BSOD_jcgriff2\032112-18844-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c06000 PsLoadedModuleList = 0xfffff800`02e42e70
Debug session time: Wed Mar 21 18:11:30.482 2012 (UTC - 6:00)
System Uptime: 0 days 0:00:12.370
Loading Kernel Symbols
..................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 6B, {ffffffffc0000428, 3, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!PspLocateSystemDll+13e )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PROCESS1_INITIALIZATION_FAILED (6b)
Arguments:
Arg1: ffffffffc0000428, Indicates the NT status code that caused the failure.
Arg2: 0000000000000003, (reserved)
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x6B

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800030bab2e to fffff80002c76540

STACK_TEXT:  
fffff880`009a9928 fffff800`030bab2e : 00000000`0000006b ffffffff`c0000428 00000000`00000003 00000000`00000000 : nt!KeBugCheckEx
fffff880`009a9930 fffff800`030bae09 : 00000000`002a0028 00000000`00000001 00000000`00000001 fffff8a0`001edc60 : nt!PspLocateSystemDll+0x13e
fffff880`009a9a00 fffff800`031a3abd : fffff800`008127f0 00000000`00000002 00000000`00000000 fffff800`02defe80 : nt!PsLocateSystemDlls+0x69
fffff880`009a9a40 fffff800`031a6c6c : 00000000`00000000 00000000`00000010 ffffffff`80000028 fffff800`008127f0 : nt!IoInitSystem+0x85d
fffff880`009a9b40 fffff800`030f7f59 : 00000000`00000000 fffffa80`039e5b60 00000000`00000080 fffffa80`039e5040 : nt!Phase1InitializationDiscard+0x129c
fffff880`009a9d10 fffff800`02f15726 : 00000000`00000000 00000000`00000080 00000000`00000000 fffff800`02c54ab9 : nt!Phase1Initialization+0x9
fffff880`009a9d40 fffff800`02c54ac6 : fffff800`02defe80 fffffa80`039e5b60 fffff800`02dfdc40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PspLocateSystemDll+13e
fffff800`030bab2e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!PspLocateSystemDll+13e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec7a284

FAILURE_BUCKET_ID:  X64_0x6B_nt!PspLocateSystemDll+13e

BUCKET_ID:  X64_0x6B_nt!PspLocateSystemDll+13e

Followup: MachineOwner
---------


[/list]

1. Possible caused by Ventrilo.exe.
2. DirectX/Graphics Card problems...

3. Any part of the disk subsystem can cause the PROCESS1_INITIALIZATION_FAILED bug check, including bad disks, bad or incorrect cables, mixing different ATA-type devices on the same chain, or drives that are not available becuase of hardware regeneration.
   This bug check can also be caused by a missing file from the boot partition or by a driver file that a user accidentally disabled in the Drivers tab.

   from Bug Check 0x6B: PROCESS1_INITIALIZATION_FAILED

Thanks to Dave76 for help understanding possible causes.


We will start with the common problems first (see bold possible causes). Do the following steps and test by doing your normal routine after each step to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

If you can do your normal routine for a few weeks without a crash, and your crashes are usually more frequent than that, then the problem is likely solved.

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run the short and long tests of SeaTools.
  
  
• Try re-installing DirectX using the Download: DirectX Redist (June 2010) - Microsoft Download Center - Download Details and see how the system responds.
  
  Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.
  
  1. Download the latest drivers for your display card(s)
  2. Click Start Menu
  3. Right Click My Computer/Computer
  4. Click Manage
  5. Click Device Manager from the list on the left
  6. Expand Display adapters
  7. Do the following for each adapter (in case you have multiple display cards)
     • Right click the adapter
     • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
     • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  8. Restart your computer after uninstalling drivers for all display cards
  9. Install the latest driver for the display cards once Windows starts
  
  Alternatively:
  1. Login as an adminstrative user
  2. Download the latest drivers for your display card(s)
  3. Click Start Menu
  4. Click Control Panel
  5. Click Hardware and Sound
  6. Click Device Manager (the last link under Devices and Printers)
  7. Expand Display adapters
  8. Do the following for each adapter (in case you have multiple display cards)
     • Right click the adapter
     • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
     • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  9. Restart your computer after uninstalling drivers for all display cards
  10. Install the latest driver for the display cards once Windows starts
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • 
    Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

 

[phosphorus2500]

Thank you all for the help you've given me so far but after yesterday and today I have removed a stick of RAM and done further testing and it appears that one of the sticks may be faulty which was the cause of the BSoD's as I have had none since yesterday now. I will do further testing to see, but thank you all

 

[writhziden]

No problem. Keep us updated on how the system responds over the next few days. Good troubleshooting step!

 

[phosphorus2500]

Sorry for the late reply, and I dont know if we should mark it as solved or not yet.

Over the past couple of days I've been moving around the RAM to see if its a faulty stick or slot I have, I've ran the computer for a substantial amount of time in the suspected good slot with both RAM sticks and its been fine, anytime I put something in the bad slot, it bluescreens after running for a while... BUT since then I've also had random blackouts from my computer, freezing crashes and all sorts. I know its not a BSoD but my computer definitely seems to be going the way of the dodo and I dont know why =/

 

[writhziden]

It's possible if you have a bad slot, you may also have a bad board...

Just to make sure I understand, you say you get these other strange occurrences when you have the RAM in the suspected good slot? Does it matter which module is in the slot, or do both cause the same erratic behavior?

 

[phosphorus2500]

I have looked into new motherboards to upgrade to but I dont have enough money and wont have for a while to make the suspected fix to the problems I'm having.

But the problems do seem to be incredibly random and tempermental so its difficult to try and gauge when they happen as over the past couple of days I've been switching the RAM about a lot to keep testing things and seeing what works, but yes the erratic behaviour and crashes seem to happen with either stick in the suspected good slot.

 

[writhziden]

You might consider the option to http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html and see if it is indeed hardware and not Windows related. I suspect there is a bad slot since the tests indicate it, but the erratic behavior could possibly be Windows related.

Backup any important files before doing the clean install if you go that route.