BSOD. Possible driver issue?

JoelSCR · 18 May 2011

Hey guys, this is my first post on this awesome forum. I lurk here a lot and can usualy solve any problem by reading posts but this issue has me stumped.

I am trying to fix my friend's dad's laptop, it is an Asus M7V. It actually runs pretty smooth except for a BSOD error they kept getting(the error was PAGE FAULT IN NON PAGED AREA). They just bought windows 7 because they thought it would fix the error (they were using vista) and gave it to me to install. Everything was going well except the drivers were ridiculously hard to find for this system. After installing all the drivers I starting getting BSOD errors like crazy. This time however there was no error message. After reading a post about a similar problem on here, I tried to use driver verifier to locate the issue, but alas, I just don't have the knowledge to correctly identify where the problem exists. I followed the BSOD posting instructions and have attached the files with the dumps and perfmon report. Thanks in advance for all your help guys, I will be eagerly awaiting your reply.

zigzag3143 · 18 May 2011

JoelSCR said:

Hey guys, this is my first post on this awesome forum. I lurk here a lot and can usualy solve any problem by reading posts but this issue has me stumped.

I am trying to fix my friend's dad's laptop, it is an Asus M7V. It actually runs pretty smooth except for a BSOD error they kept getting(the error was PAGE FAULT IN NON PAGED AREA). They just bought windows 7 because they thought it would fix the error (they were using vista) and gave it to me to install. Everything was going well except the drivers were ridiculously hard to find for this system. After installing all the drivers I starting getting BSOD errors like crazy. This time however there was no error message. After reading a post about a similar problem on here, I tried to use driver verifier to locate the issue, but alas, I just don't have the knowledge to correctly identify where the problem exists. I followed the BSOD posting instructions and have attached the files with the dumps and perfmon report. Thanks in advance for all your help guys, I will be eagerly awaiting your reply.

All of these are memory exceptions caused by hardware.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\051311-21125-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0x82810000 PsLoadedModuleList = 0x8294f570
Debug session time: Fri May 13 17:30:34.527 2011 (GMT-4)
System Uptime: 0 days 0:00:49.808
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: c10ff0d2, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 82a2edd7, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000002, (reserved)

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8296f700
Unable to read MiSystemVaType memory at 8294f0c0
 c10ff0d2 

FAULTING_IP: 
nt!ObpAllocateObject+1cc
82a2edd7 108bd1f00fc1    adc     byte ptr [ebx-3EF00F2Fh],cl

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  a848fbf4 -- (.trap 0xffffffffa848fbf4)
ErrCode = 00000002
eax=864aa1d0 ebx=00000001 ecx=0000000c edx=00000000 esi=842a6e38 edi=842aa098
eip=82a2edd7 esp=a848fc68 ebp=a848fc80 iopl=0         ov up ei pl nz na pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010a07
nt!ObpAllocateObject+0x1cc:
82a2edd7 108bd1f00fc1    adc     byte ptr [ebx-3EF00F2Fh],cl ds:0023:c10ff0d2=??
Resetting default scope

MISALIGNED_IP: 
nt!ObpAllocateObject+1cc
82a2edd7 108bd1f00fc1    adc     byte ptr [ebx-3EF00F2Fh],cl

LAST_CONTROL_TRANSFER:  from 82848948 to 8286eba6

STACK_TEXT:  
a848fbdc 82848948 00000001 c10ff0d2 00000000 nt!MmAccessFault+0xbf
a848fbdc 82a2edd7 00000001 c10ff0d2 00000000 nt!KiTrap0E+0xdc
a848fc80 82a63173 a848fc01 a848fca8 00000010 nt!ObpAllocateObject+0x1cc
a848fcb0 82a3c6bc a848fc01 842a6e38 00000000 nt!ObCreateObject+0x128
a848fd18 8284575a 011bf52c 001f0003 00000000 nt!NtCreateEvent+0x93
a848fd18 77646344 011bf52c 001f0003 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
011bf530 00000000 00000000 00000000 00000000 0x77646344


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ObpAllocateObject+1cc
82a2edd7 108bd1f00fc1    adc     byte ptr [ebx-3EF00F2Fh],cl

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!ObpAllocateObject+1cc

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

BUCKET_ID:  IP_MISALIGNED

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

I would start with the following
1-run memtest to test your memory
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86.com - Memory Diagnostic

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.

2-run chkdsk to test the HD
A- CHKDSK /R /F:

Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.

Do this for each hard drive on your system.

When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.

Then reboot and let the test run.

It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.

See "CHKDSK LogFile" below in order to check the results of the test.

B- Elevated Command Prompt:

Go to Start and type in "cmd.exe" (without the quotes)

At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

C-CHKDSK LogFile:

Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter

Expand the Windows logs heading, then select the Application log file entry.

Double click on the Source column header.

Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).

Copy/paste the results into your next post.

3-Furmark to test your video
Try this free video stress test: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

4-Prime 95 to test the cpu
Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Old drivers needing updating

Code:

mdmxsdk.sys    3/17/2004 03:04:10 PM    0x8201de40    0x00002e40    0x4058a12a    0x8201b000                            
HSF_DP.sys    6/17/2004 06:55:00 PM    0x8eff8480    0x000fe480    0x40d22144    0x8eefa000                            
HSF_CNXT.sys    6/17/2004 06:55:36 PM    0x820c8400    0x000a7400    0x40d22168    0x82021000                            
HSFHWICH.sys    6/17/2004 06:57:01 PM    0x8eef9d80    0x00030d80    0x40d221bd    0x8eec9000                            
vinyl97.sys    11/25/2005 02:39:04 AM    0x8ee4cc00    0x00031c00    0x4386b188    0x8ee1b000                            
ATKACPI.sys    12/14/2006 03:11:57 AM    0x82114000    0x00008000    0x4580f93d    0x8210c000                            
igxpmp32.sys    1/13/2007 02:33:17 PM    0x8ed7ac60    0x00568c60    0x45a925ed    0x8e812000                            
NETw2v32.sys    3/6/2007 10:08:44 PM    0x8e76b000    0x00280000    0x45ee1eac    0x8e4eb000                            
Rtnicxp.sys    5/30/2008 11:12:11 AM    0x8ee1b000    0x0000f000    0x4840194b    0x8ee0c000

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

JoelSCR · 18 May 2011

Thank you SO MUCH zigzag, I am currently testing and applying the fixes in your comment. I will update this reply as soon as I am finished.

JoelSCR · 19 May 2011

Ok so Memtest ran fine and encountered 0 errors

ChkDsk seemed to work ok and here are the results

- EventData

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)... 65536 file records processed. File verification completed. 95 large file records processed. 0 bad file records processed. 2 EA records processed. 43 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 90472 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)... 65536 file SDs/SIDs processed. Cleaning up 403 unused index entries from index $SII of file 0x9. Cleaning up 403 unused index entries from index $SDH of file 0x9. Cleaning up 403 unused security descriptors. Security descriptor verification completed. 12469 data files processed. CHKDSK is verifying Usn Journal... 35449304 USN bytes processed. Usn Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... 65520 files processed. File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... 15870846 free clusters processed. Free space verification is complete. Adding 1 bad clusters to the Bad Clusters File. 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. 78046207 KB total disk space. 14357300 KB in 51647 files. 36032 KB in 12470 indexes. 4 KB in bad sectors. 169487 KB in use by the system. 65536 KB occupied by the log file. 63483384 KB available on disk. 4096 bytes in each allocation unit. 19511551 total allocation units on disk. 15870846 allocation units available on disk. Internal Info: 00 00 01 00 80 fa 00 00 98 f0 01 00 00 00 00 00 ................ 85 00 00 00 2b 00 00 00 00 00 00 00 00 00 00 00 ....+........... e0 ed 34 00 50 01 34 00 50 01 34 00 00 00 34 00 ..4.P.4.P.4...4. Windows has finished checking your disk. Please wait while your computer restarts.

Furmark said it will not work on this laptop as it is too old

Prime95 kept encountering errors that it specified were hardware related here are the results:
[May 19 17:10] Worker starting
[May 19 17:10] Beginning a continuous self-test to check your computer.
[May 19 17:10] Please read stress.txt. Choose Test/Stop to end this test.
[May 19 17:10] Test 1, 7800 Lucas-Lehmer iterations of M9961473 using Pentium4 type-0 FFT length 512K, Pass1=512, Pass2=1K.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Possible hardware failure, consult readme.txt file, restarting test.
[May 19 17:11] ERROR: ILLEGAL SUMOUT
[May 19 17:11] Maximum number of warnings exceeded.
[May 19 17:11] Torture Test completed 0 tests in 0 minutes - 0 errors, 100 warnings.
[May 19 17:11] Worker stopped.

The prime95 readme said it could be a driver issue however

I am still working on updating the drivers, though I am having some trouble because they are all meant for XP, but I will update again once I have thoroughly tried all of them.

Thanks again for your help and hope to hear from you soon!