Computer Keeps Restarting

My computer kept restarting randomly, so I turned off the "automatically restart" feature to see what was wrong. I got this error:



What's wrong with my computer? What do I need to do to fix it??

BTW, I'm running Windows XP.

 

Run a RAM test (we use Memtest 86+) and let it go through a few passes. If that's fine I'd test the hard drive (Seatools or Hitachi). My bet is on the RAM.

 

The blue screen indicates an attempt to write to an invalid memory location, most likely caused by either the thread dispatcher or timer interrupt handler. If you have a crash dump, you might want to take a look at which module/function resides at 0x80502ccc; I bet its somewhere within NTOSKRNL.

Did you upgrade your hardware or device drivers recently, or did you change some BIOS settings? Unfortunately, this is one of the most generic blue screens ever, so there is no easy way to point to the root cause of your problem. A misbehaving driver can cause this error, besides other things.

As Taemos said, give MEMTEST86 a try.

 

Check this thread:

http://pressf1.pcworld.co.nz/showthread.php?t=53947

 

i got similar problems out of grafic card and power supply... so run the mem test and if everything seems ok try other options

 

I second the Power Supply.

What PSU are you using?

 

I haven't tried memtest yet, so I'll try that. I forget which PSU I'm using. I can look it up. I ran WhoCrashed and it gave me a huge list, which I can't make any sense of. Can anybody help me out?

On Mon 5/18/2009 3:34:26 AM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1902FE, 0xF7A1390C, 0xF7A13608, 0xF72159EF)
Error: NTFS_FILE_SYSTEM
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 4/20/2009 11:02:03 PM your computer crashed
This was likely caused by the following module: symevent.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x0, 0xEEEB0A9C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\symevent.sys
product: SYMEVENT
company: Symantec Corporation
description: Symantec Event Library



On Mon 4/20/2009 10:45:57 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE0F7B428, 0x0, 0x8050A7C2, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 4/20/2009 3:03:31 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xDE (0x2, 0xE2F1A990, 0xE0F1A990, 0x3195F8C0)
Error: POOL_CORRUPTION_IN_FILE_AREA
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 4/20/2009 3:02:10 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xB81F5FFC, 0xFF, 0x0, 0x80545B0F)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 4/20/2009 2:59:03 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0x0, 0x1C, 0x1, 0x80502CCC)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 4/15/2009 5:37:53 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xB8726FFC, 0xFF, 0x0, 0x80545B0F)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 4/15/2009 5:22:00 AM your computer crashed
This was likely caused by the following module: nv4_disp.dll
Bugcheck code: 0x1000000A (0x10, 0x2, 0x1, 0x805172D6)
Error: Unknown
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 182.50
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 182.50



On Wed 4/15/2009 5:03:14 AM your computer crashed
This was likely caused by the following module: nv4_mini.sys
Bugcheck code: 0x100000D1 (0xC0, 0x2, 0x0, 0xF5858966)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\nv4_mini.sys
product: NVIDIA Compatible Windows 2000 Miniport Driver, Version 182.50
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Miniport Driver, Version 182.50



On Thu 4/2/2009 9:57:13 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0x8745768C, 0x2, 0x0, 0x80515C32)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 3/21/2009 1:56:50 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007F (0x8, 0x80042000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 3/21/2009 1:49:24 AM your computer crashed
This was likely caused by the following module: navex15.sys
Bugcheck code: 0x1000000A (0xED30CF30, 0x2, 0x1, 0x804E8955)
Error: Unknown
file path: \??\C:\Documents and Settings\All Users\Application Data\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\Norton\Definitions\VirusDefs\20090420.002\NAVEX15.SYS
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on navex15.sys





On Sat 10/18/2008 1:53:15 AM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xBF802A90, 0xBAD07C60, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 1/13/2008 10:08:35 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x19 (0x20, 0xE5D24BA0, 0xE5D24EE0, 0xC68051A)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 8/13/2007 5:57:05 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000012 (0x1, 0x85B8A520, 0x0, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 7/27/2007 5:16:46 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xDFF40F8C, 0x2, 0x0, 0x8050E252)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 5/5/2007 5:37:39 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFC (0xF7A67B80, 0x6DCE963, 0xF7A67AE8, 0x1)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 5/5/2007 5:24:40 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFC (0xF7A6FB80, 0x6D54963, 0xF7A6FAE8, 0x1)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 5/5/2007 5:19:03 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFC (0xF7A6FB80, 0x6D54963, 0xF7A6FAE8, 0x1)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 5/5/2007 5:14:44 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFC (0xF7A5FB80, 0x6E06963, 0xF7A5FAE8, 0x1)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 4/25/2007 8:27:06 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFC (0xF7A63B80, 0x6DCB963, 0xF7A63AE8, 0x1)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 4/24/2007 5:36:28 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFC (0xF7A6FB80, 0x6D54963, 0xF7A6FAE8, 0x1)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Mon 5/18/2009 3:34:26 AM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1902FE, 0xF7A1390C, 0xF7A13608, 0xF72159EF)
Error: NTFS_FILE_SYSTEM
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 4/20/2009 11:02:03 PM your computer crashed
This was likely caused by the following module: symevent.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x0, 0xEEEB0A9C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\symevent.sys
product: SYMEVENT
company: Symantec Corporation
description: Symantec Event Library



On Mon 4/20/2009 10:45:57 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE0F7B428, 0x0, 0x8050A7C2, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 4/20/2009 3:03:31 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xDE (0x2, 0xE2F1A990, 0xE0F1A990, 0x3195F8C0)
Error: POOL_CORRUPTION_IN_FILE_AREA
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 4/20/2009 3:02:10 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xB81F5FFC, 0xFF, 0x0, 0x80545B0F)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 4/20/2009 2:59:03 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0x0, 0x1C, 0x1, 0x80502CCC)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 4/15/2009 5:37:53 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xB8726FFC, 0xFF, 0x0, 0x80545B0F)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 4/15/2009 5:22:00 AM your computer crashed
This was likely caused by the following module: nv4_disp.dll
Bugcheck code: 0x1000000A (0x10, 0x2, 0x1, 0x805172D6)
Error: Unknown
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 182.50
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 182.50



On Wed 4/15/2009 5:03:14 AM your computer crashed
This was likely caused by the following module: nv4_mini.sys
Bugcheck code: 0x100000D1 (0xC0, 0x2, 0x0, 0xF5858966)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\nv4_mini.sys
product: NVIDIA Compatible Windows 2000 Miniport Driver, Version 182.50
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Miniport Driver, Version 182.50



On Thu 4/2/2009 9:57:13 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0x8745768C, 0x2, 0x0, 0x80515C32)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 3/21/2009 1:56:50 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007F (0x8, 0x80042000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 3/21/2009 1:49:24 AM your computer crashed
This was likely caused by the following module: navex15.sys
Bugcheck code: 0x1000000A (0xED30CF30, 0x2, 0x1, 0x804E8955)
Error: Unknown
file path: \??\C:\Documents and Settings\All Users\Application Data\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\Norton\Definitions\VirusDefs\20090420.002\NAVEX15.SYS
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on navex15.sys





On Sat 10/18/2008 1:53:15 AM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xBF802A90, 0xBAD07C60, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 1/13/2008 10:08:35 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x19 (0x20, 0xE5D24BA0, 0xE5D24EE0, 0xC68051A)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 8/13/2007 5:57:05 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000012 (0x1, 0x85B8A520, 0x0, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 7/27/2007 5:16:46 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xDFF40F8C, 0x2, 0x0, 0x8050E252)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 5/5/2007 5:37:39 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFC (0xF7A67B80, 0x6DCE963, 0xF7A67AE8, 0x1)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 5/5/2007 5:24:40 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFC (0xF7A6FB80, 0x6D54963, 0xF7A6FAE8, 0x1)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 5/5/2007 5:19:03 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFC (0xF7A6FB80, 0x6D54963, 0xF7A6FAE8, 0x1)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 5/5/2007 5:14:44 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFC (0xF7A5FB80, 0x6E06963, 0xF7A5FAE8, 0x1)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 4/25/2007 8:27:06 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFC (0xF7A63B80, 0x6DCB963, 0xF7A63AE8, 0x1)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 4/24/2007 5:36:28 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFC (0xF7A6FB80, 0x6D54963, 0xF7A6FAE8, 0x1)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

 

Also, I tried memtest86 and it found a few bad sectors. How many, I'm not sure because I don't know how to scroll down the list. What does this mean? Do I need to get new memory, and how do I know for sure that this is what's causing me problems?

 

Looks like kernel memory corruption, probably caused by a bad device driver. Unfortunately, there is no simple way to find the culprit; if an error occurs, the faulting component is most likely not the one responsible for the corruption.

Run memtest to rule out bad RAM. If it doesn't find anything, try to update the applications that installed the following drivers:

Evil Symantec/Norton Utilities or something like that. I'd recommend to get rid of these completely; their drivers were once known to do really horrible things :evil:.

NVidia display drivers.

Another idea: did you notice that all ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY errors at the end of your list refer to nearly identical addresses (0xF7A5FB80, 0xF7A6FB80)? I'd expect these to be somewhere within either Symantec's or NVidia's drivers. Could you run DriverView (http://www.nirsoft.net/utils/driverview.html) and check whether any driver has been loaded there?

 

It means you have a ticking time bomb in your RAM slot(s).

Indeed, you absolutely need to install new memory; after installing it, re-run memcheck to make sure it doesn't display any further errors.

You can't be sure that defect RAM was causing your original problems, but it is very likely. Anyway, you really don't want to run your system on bad memory, as it can slowly destroy your data.

 

I would agree with the ram voltage being too low as a possible culprit, check what your ram is rated for and what it's set at in the bios. Check the actual voltage reading as well, either in the bios of with a utility like Hardware monitor. You could try upping it by 0.1V in the bios see if that helps at least before buying new ram. Don't go nuts though you may just fry it altogether, make sure it's not running too hot. (Heat could also be a factor in the instability at the moment, how good is your airflow?)

Personally I'm a believer in 'you get what you pay for'. If your ram (or other components for that matter) is cheap or unbranded, it may just be worth biting the bullet and getting some new stuff. I would recommend OCZ and Corsair form first-hand experience.

I wouldn't rule out the PSU though, if the RAM voltage is unstable...

 

^I know my "mileage may vary," but I've bought Corsair RAM twice and both times it's been bad. Granted, this was one of their cheaper lines, but it should work regardless as I wasn't planning on doing anything like overclocking. Most people I know have had similar experiences.

I had some cheap brand in my desktop ("Wintex" or something like that), but it was quite stable and I almost never had crashes. I'm using Mushkin DDR3 in my Macbook and it's been pretty stable, as well.

My recommendation to the OP is to avoid Corsair as my [anecdotal] experience has been that it is of generally poor quality. I'd go with either G.Skill or Kingston, as their cheap RAM is quite good if you don't plan on overclocking.

 

If the motherboard is not supplying enough voltage, then the motherboard is simply deteriorating. Might be a capacitor or mosfet simply not working as it has in the past.

 

This thread is interesting reading. I have the same problem with my PC. Random BSOD all the time. It mostly seems to happen when encoding video or runing a lot of apps. So I'm under the impression that I have a memory problem too. I think I'll try that extra power boost to see if that solves the problem.

By the way, how can I find out the exact type of memory in my PC without taking it out?

yakumo

 

Nice software. Told me everything about my PC except the type of memory :lol: I was told How much memory I had in each slot which I already knew.

Yakumo

 

try to take off one RAM stick at a time and run tests to check the broken one... else check if your PSU is underdimensioned... in the first year a PSU loses up to 20% power and this might turn a perfectly running pc in a nightmare....

here you can run a check:

http://www.antec.outervision.com/

 

Look up CPU-Z. Tells you exactly who makes your RAM, the speed, etc. as well as CPU information, too.