Windows 7 Random BSOD

Very good. Keep us updated.

Both of your most resent dumps are Driver Verifier enabled dumps and both blame wow.exe, World of Warcraft - WoW.exe Windows process - What is it?.

Please turn Driver Verifier off and lets see how your system does: Driver Verifier - Enable and Disable

You are welcome. Please keep us posted. :)

No it isn't fun. Let's see what we can do to end it.

One of the two dumps is error code 19, BAD_POOL_HEADER - usually caused by a device driver. The dump file blames Heroes of Newerth.

The second dump is error code 24, NTFS_FILE_SYSTEM - usual causes are Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure. This dump blames a Windows system file which is most likely not the cause. The dump also points to memory corruption.

Code:

Kernel base = 0xfffff800`02c52000 PsLoadedModuleList = 0xfffff800`02e8fe50
Debug session time: Fri Oct  1 17:45:02.741 2010 (GMT-4)
System Uptime: 0 days 0:31:51.787
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffff900c1f00280, fffff900c1f00830, 255b0004}

Probably caused by : win32k.sys ( win32k!vProcessCursorShape+390 )

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

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff900c1f00280, The pool entry we were looking for within the page.
Arg3: fffff900c1f00830, The next pool entry.
Arg4: 00000000255b0004, (reserved)

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


BUGCHECK_STR:  0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efa0e0
 fffff900c1f00280 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  hon.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002df56d3 to fffff80002cc2740

STACK_TEXT:  
fffff880`08a3a7b8 fffff800`02df56d3 : 00000000`00000019 00000000`00000020 fffff900`c1f00280 fffff900`c1f00830 : nt!KeBugCheckEx
fffff880`08a3a7c0 fffff960`002d2f98 : fffff900`c0170018 fffff960`003c30d0 fffff900`746c7847 fffff900`c1f002b0 : nt!ExDeferredFreePool+0x12c4
fffff880`08a3a870 fffff960`001350de : fffff900`c1e9acd0 00000000`00000000 fffff900`00000001 fffff900`00000020 : win32k!vProcessCursorShape+0x390
fffff880`08a3a980 fffff960`00134c83 : 00000000`00000000 fffffa80`0559fe50 00000000`00000000 fffff900`00000000 : win32k!vSetPointer+0x2d2
fffff880`08a3aab0 fffff960`001a39b6 : fffff900`c00bf010 fffff900`c1eae290 00000000`00000000 00000000`00000000 : win32k!GreSetPointer+0x177
fffff880`08a3ab60 fffff960`00184cc3 : fffff900`c1fd3c30 fffff880`08a3aca0 00000000`0e554ec0 fffff900`c1f3a770 : win32k!zzzUpdateCursorImage+0x28e
fffff880`08a3aba0 fffff960`001cbdeb : 00000000`00000000 fffff880`08a3aca0 00000000`0e554ec0 00000000`fffdb000 : win32k!zzzSetCursor+0x77
fffff880`08a3abf0 fffff800`02cc1993 : fffffa80`0626c930 00000000`0008e270 00000000`00000020 00000000`0008e260 : win32k!NtUserSetCursor+0x4b
fffff880`08a3ac20 00000000`750e2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008ebf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x750e2dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!vProcessCursorShape+390
fffff960`002d2f98 488d0d41130f00  lea     rcx,[win32k!xlateTable (fffff960`003c42e0)]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  win32k!vProcessCursorShape+390

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c483f

FAILURE_BUCKET_ID:  X64_0x19_20_win32k!vProcessCursorShape+390

BUCKET_ID:  X64_0x19_20_win32k!vProcessCursorShape+390

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

Kernel base = 0xfffff800`02c64000 PsLoadedModuleList = 0xfffff800`02ea1e50
Debug session time: Fri Oct  1 18:21:38.002 2010 (GMT-4)
System Uptime: 0 days 0:17:39.937
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff8800861b798, fffff8800861b000, fffff880012bfa91}

Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefix+121 )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff8800861b798
Arg3: fffff8800861b000
Arg4: fffff880012bfa91

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


EXCEPTION_RECORD:  fffff8800861b798 -- (.exr 0xfffff8800861b798)
ExceptionAddress: fffff880012bfa91 (Ntfs!NtfsFindPrefix+0x0000000000000121)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000bde088c0
Attempt to read from address 00000000bde088c0

CONTEXT:  fffff8800861b000 -- (.cxr 0xfffff8800861b000)
rax=fffff8a00c622782 rbx=fffff8a0003814a0 rcx=000000000000b2ae
rdx=0000000000000050 rsi=fffff8a0001f5bc0 rdi=fffff8a000381490
rip=fffff880012bfa91 rsp=fffff8800861b9d0 rbp=fffff8800861bc60
 r8=0000000000000007  r9=00000000bde088c0 r10=fffff8800861ba30
r11=fffff8800861ba10 r12=0000000000000016 r13=0000000000000000
r14=0000000000000000 r15=fffff88007def438
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
Ntfs!NtfsFindPrefix+0x121:
fffff880`012bfa91 410fb709        movzx   ecx,word ptr [r9] ds:002b:00000000`bde088c0=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  spoolsv.exe

CURRENT_IRQL:  1

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

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000bde088c0

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0c0e0
 00000000bde088c0 

FOLLOWUP_IP: 
Ntfs!NtfsFindPrefix+121
fffff880`012bfa91 410fb709        movzx   ecx,word ptr [r9]

FAULTING_IP: 
Ntfs!NtfsFindPrefix+121
fffff880`012bfa91 410fb709        movzx   ecx,word ptr [r9]

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff880012b0f74 to fffff880012bfa91

STACK_TEXT:  
fffff880`0861b9d0 fffff880`012b0f74 : fffffa80`04555360 fffff8a0`001f5bc0 fffff880`07def418 fffff880`0861bc10 : Ntfs!NtfsFindPrefix+0x121
fffff880`0861ba80 fffff880`012ab28d : fffffa80`04555360 fffffa80`04e308f0 fffff880`0861bc60 fffff880`0861bca8 : Ntfs!NtfsFindStartingNode+0x6e4
fffff880`0861bb50 fffff880`01214c0d : fffffa80`04555360 fffffa80`04e308f0 fffff880`07def3b0 00000000`00000000 : Ntfs!NtfsCommonCreate+0x3dd
fffff880`0861bd30 fffff800`02ccc5c7 : fffff880`07def320 00000000`02317250 00000000`77bc4270 00000000`00000000 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`0861bd60 fffff800`02ccc581 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
fffff880`07def1f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsFindPrefix+121

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

STACK_COMMAND:  .cxr 0xfffff8800861b000 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsFindPrefix+121

BUCKET_ID:  X64_0x24_Ntfs!NtfsFindPrefix+121

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

It is time to test hardware. Since one of the dumps is error code 24, start by running Check Disk.

Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please 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.

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"

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 Windows 7) (winlogon for XP).

Copy/paste the results into your next post.

Next run Memtest to test your RAM. Follow the instructions in this tutorial by Jonathan King: RAM - Test with Memtest86+

Errors will show up in red. Post your results.

I still see two outdated drivers on your system:

intelsmb.sys Wed May 13 03:31:00 2009 -

System Management Bus 2.0 (SMBus) Driver is a driver file from Intel Corporation belonging to Intel(R) SMBus Controller. http://downloadcenter.intel.com/Default.aspx. Update this driver

IOCBIOS.SYS Thu Jul 09 13:47:22 2009 - I think this is a thermal monitoring driver. Intel(R) Overclocking Device Driver is a driver file from Intel Corporation belonging to Intel(R) Extreme Tuning Utility Performance Tuning Driver. http://downloadcenter.intel.com/Default.aspx. update this driver.

I should have asked this earlier; are you overclocking? If so, stop and return everything overclocked to default values.

Keep us updated.

Waiting to see your results. The Windows memory test is OK. In my opinion, it does not stress the RAM enough and is not thorough enough.