Blue Screen

Tales Of Musica · Nov 1, 2010

Hello i just got a bran new computer, its new just out of the box, i installed windows 7 professional 32 bit and things were ok.
But now every time i try to play Starcraft2 after about 10 mins i blue screen and then on restart get this message.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 2057

Additional information about the problem:
BCCode: 44
BCP1: 925EDBB8
BCP2: 00001D7B
BCP3: 00000000
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\110110-24562-01.dmp
C:\Users\Presley\AppData\Local\Temp\WER-36203-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I know my computer can handle the game and the thing is brand new not even a month old.
Could anyone throw me some insight?
Thanks in advance.

CarlTR6 · Nov 1, 2010

Hi and welcome to the forum. Sorry you are having problems with a new computer. I will look at your dumps but please read this thread, run the tool, and upload the files. This information will help us help you better. It gives us system information the dumps do not show.

http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

Error code 8E, KERNEL_MODE_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory.

Error code 44, MULTIPLE_IRP_COMPLETE_REQUESTS. Usual causes: Device driver(s)

Code:

Windows 7 Kernel Version 7600 MP (8 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x8283a000 PsLoadedModuleList = 0x82979570
Debug session time: Mon Nov  1 17:47:30.974 2010 (GMT-4)
System Uptime: 0 days 7:30:27.974
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 828aa26e, 9d68bb00, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 828aa26e, The address that the exception occurred at
Arg3: 9d68bb00, Trap Frame
Arg4: 00000000

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!EtwpLogKernelEvent+26d
828aa26e 8b8828020000    mov     ecx,dword ptr [eax+228h]

TRAP_FRAME:  9d68bb00 -- (.trap 0xffffffff9d68bb00)
ErrCode = 00000000
eax=00000000 ebx=85259ad0 ecx=85458006 edx=00001402 esi=85458000 edi=00000006
eip=828aa26e esp=9d68bb74 ebp=9d68bba0 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!EtwpLogKernelEvent+0x26d:
828aa26e 8b8828020000    mov     ecx,dword ptr [eax+228h] ds:0023:00000228=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x8E

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 828d9740 to 828aa26e

STACK_TEXT:  
9d68bba0 828d9740 9d68bc0c 00000000 00000002 nt!EtwpLogKernelEvent+0x26d
9d68bbc8 828bfeab 9d68bc0c 00000003 00000004 nt!EtwpTraceKernelEvent+0x6f
9d68bca0 82a70111 000006a0 71970000 ffffffff nt!PerfLogImageUnload+0x173
9d68bd04 82a92b55 8742ea58 71970000 00000000 nt!MiUnmapViewOfSection+0x21b
9d68bd24 8286f79a ffffffff 71970000 020af4c0 nt!NtUnmapViewOfSection+0x55
9d68bd24 775564f4 ffffffff 71970000 020af4c0 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
020af4c0 00000000 00000000 00000000 00000000 0x775564f4


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
3 errors : !nt (828aa248-828aa558)
828aa240  8b  c1  eb  15  8b  5c  24  24 *8f  41  01  8b  f8  8b  c1  f0 .....\$$.A......
...
828aa260  83  c8  ff  83  c6  0c  f0  0f *c3  06  8b  44  24  14  8b  88 ...........D$...
...
828aa550  33  c0  f0  21  03  eb  03  fe *47  ff  8b  4d  f4  33  c0  f0 3..!....G..M.3..

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

5: kd> lmtsmn
start    end        module name
8ba30000 8ba78000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
8c386000 8c3e0000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62)
92954000 92966000   AgileVpn AgileVpn.sys Mon Jul 13 19:55:00 2009 (4A5BC954)
8bb81000 8bb8a000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
9bf6b000 9bf74000   asyncmac asyncmac.sys Mon Jul 13 19:54:46 2009 (4A5BC946)
8bb55000 8bb5e000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
8bb5e000 8bb81000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
8c2f2000 8c2f9000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC)
9288d000 9289b000   blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8)
8b8bc000 8b8c4000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
9bcdc000 9bcf5000   bowser   bowser.sys   Mon Jul 13 19:14:21 2009 (4A5BBFCD)
95b10000 95b2e000   cdd      cdd.dll      unavailable (00000000)
8c2a9000 8c2c8000   cdrom    cdrom.sys    Mon Jul 13 19:11:24 2009 (4A5BBF1C)
8b906000 8b9b1000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
8c252000 8c277000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
8b8c4000 8b906000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
8bd71000 8bdce000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
92947000 92954000   CompositeBus CompositeBus.sys Mon Jul 13 19:45:26 2009 (4A5BC716)
92bed000 92bfa000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
92811000 92875000   csc      csc.sys      Mon Jul 13 19:15:08 2009 (4A5BBFFC)
92875000 9288d000   dfsc     dfsc.sys     Mon Jul 13 19:14:16 2009 (4A5BBFC8)
8bfd8000 8bfe4000   discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214)
8c241000 8c252000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
92b1e000 92b37000   drmk     drmk.sys     Mon Jul 13 20:36:05 2009 (4A5BD2F5)
8c277000 8c280000   dump_atapi dump_atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
92800000 9280b000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:11:16 2009 (4A5BBF14)
8c280000 8c291000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
92b37000 92b41000   Dxapi    Dxapi.sys    Mon Jul 13 19:25:25 2009 (4A5BC265)
942b6000 9436d000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 20:48:33 2009 (4AC54DE1)
9436d000 943a6000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:25:25 2009 (4A5BC265)
9bf74000 9bf9e000   fastfat  fastfat.SYS  Mon Jul 13 19:14:01 2009 (4A5BBFB9)
8bbbe000 8bbcf000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
8bb8a000 8bbbe000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
8bddc000 8bde5000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
8c20f000 8c241000   fvevol   fvevol.sys   Fri Sep 25 22:24:21 2009 (4ABD7B55)
8c149000 8c17a000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
82803000 8283a000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
93800000 9381f000   HDAudBus HDAudBus.sys Mon Jul 13 19:50:55 2009 (4A5BC85F)
92a9f000 92aef000   HdAudio  HdAudio.sys  Mon Jul 13 19:51:46 2009 (4A5BC892)
92bc7000 92bda000   HIDCLASS HIDCLASS.SYS Mon Jul 13 19:51:01 2009 (4A5BC865)
92bda000 92be0480   HIDPARSE HIDPARSE.SYS Mon Jul 13 19:50:59 2009 (4A5BC863)
92bbc000 92bc7000   hidusb   hidusb.sys   Mon Jul 13 19:51:04 2009 (4A5BC868)
9bc57000 9bcdc000   HTTP     HTTP.sys     Mon Jul 13 19:12:53 2009 (4A5BBF75)
8c207000 8c20f000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
92918000 92930000   i8042prt i8042prt.sys Mon Jul 13 19:11:23 2009 (4A5BBF1B)
928bc000 928ce000   intelppm intelppm.sys Mon Jul 13 19:11:03 2009 (4A5BBF07)
9bc16000 9bc34000   irda     irda.sys     Mon Jul 13 19:53:30 2009 (4A5BC8FA)
9382a000 93833000   irenum   irenum.sys   Mon Jul 13 19:53:27 2009 (4A5BC8F7)
9381f000 9382a000   irsir    irsir.sys    Sat Jan 19 00:55:21 2008 (479190C9)
929fb000 92a08000   kbdclass kbdclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
92be1000 92bed000   kbdhid   kbdhid.sys   Mon Jul 13 19:45:09 2009 (4A5BC705)
80b9d000 80ba5000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
92a08000 92a3c000   ks       ks.sys       Wed Mar 03 22:57:52 2010 (4B8F2FC0)
8bd5e000 8bd71000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
8beda000 8beff000   ksecpkg  ksecpkg.sys  Thu Dec 10 23:04:22 2009 (4B21C4C6)
9bc34000 9bc44000   lltdio   lltdio.sys   Mon Jul 13 19:53:18 2009 (4A5BC8EE)
8bbcf000 8bbea000   luafv    luafv.sys    Mon Jul 13 19:15:44 2009 (4A5BC020)
8b833000 8b8ab000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:06:41 2009 (4A5BDA21)
92b9a000 92ba5000   monitor  monitor.sys  Mon Jul 13 19:25:58 2009 (4A5BC286)
92930000 9293d000   mouclass mouclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
9bfcf000 9bfda000   mouhid   mouhid.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
8bb3f000 8bb55000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
8c2c8000 8c2eb000   MpFilter MpFilter.sys Sat Mar 20 00:03:26 2010 (4BA4490E)
9bef8000 9bf00e00   MpNWMon  MpNWMon.sys  Sat Mar 20 00:03:24 2010 (4BA4490C)
9bcf5000 9bd07000   mpsdrv   mpsdrv.sys   Mon Jul 13 19:52:52 2009 (4A5BC8D4)
9bd07000 9bd2a000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:32:02 2010 (4B88CA72)
9bd2a000 9bd65000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:32:21 2010 (4B88CA85)
9bd65000 9bd80000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:32:11 2010 (4B88CA7B)
8c34b000 8c356000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E)
8ba81000 8ba89000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
8bd33000 8bd5e000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
8bfce000 8bfd8000   mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
8c1f7000 8c207000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
8bde5000 8be9c000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
9297e000 92989000   ndistapi ndistapi.sys Mon Jul 13 19:54:24 2009 (4A5BC930)
92989000 929ab000   ndiswan  ndiswan.sys  Mon Jul 13 19:54:34 2009 (4A5BC93A)
92a8e000 92a9f000   NDProxy  NDProxy.SYS  Mon Jul 13 19:54:27 2009 (4A5BC933)
8c3e7000 8c3f5000   netbios  netbios.sys  Mon Jul 13 19:53:54 2009 (4A5BC912)
8beff000 8bf31000   netbt    netbt.sys    Mon Jul 13 19:12:18 2009 (4A5BBF52)
8be9c000 8beda000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
8c356000 8c364000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23)
8c3f5000 8c3ff000   nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48)
8283a000 82c3a000   nt       ntkrnlmp.exe Fri Jun 18 23:55:07 2010 (4C1C3F9B)
8bc04000 8bd33000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
8c2eb000 8c2f2000   Null     Null.SYS     Mon Jul 13 19:11:12 2009 (4A5BBF10)
942b4000 942b5040   nvBridge nvBridge.kmd Fri Jul 09 17:10:11 2010 (4C379033)
93836000 942b3dc0   nvlddmkm nvlddmkm.sys Fri Jul 09 17:15:14 2010 (4C379162)
8bf31000 8bf50000   pacer    pacer.sys    Mon Jul 13 19:53:58 2009 (4A5BC916)
92900000 92918000   parport  parport.sys  Mon Jul 13 19:45:34 2009 (4A5BC71E)
8babe000 8bacf000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
9bd80000 9bd87000   parvdm   parvdm.sys   Mon Jul 13 19:45:29 2009 (4A5BC719)
8ba89000 8bab3000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
8bb2a000 8bb31000   pciide   pciide.sys   Mon Jul 13 19:11:19 2009 (4A5BBF17)
8bb31000 8bb3f000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
8bdce000 8bddc000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
9bd89000 9be20000   peauth   peauth.sys   Mon Jul 13 20:35:44 2009 (4A5BD2E0)
92aef000 92b1e000   portcls  portcls.sys  Mon Jul 13 19:51:00 2009 (4A5BC864)
8b8ab000 8b8bc000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
92966000 9297e000   rasl2tp  rasl2tp.sys  Mon Jul 13 19:54:33 2009 (4A5BC939)
929ab000 929c3000   raspppoe raspppoe.sys Mon Jul 13 19:54:53 2009 (4A5BC94D)
929c3000 929da000   raspptp  raspptp.sys  Mon Jul 13 19:54:47 2009 (4A5BC947)
929da000 929f1000   rassstp  rassstp.sys  Mon Jul 13 19:54:57 2009 (4A5BC951)
8bf8d000 8bfce000   rdbss    rdbss.sys    Mon Jul 13 19:14:26 2009 (4A5BBFD2)
929f1000 929fb000   rdpbus   rdpbus.sys   Mon Jul 13 20:02:40 2009 (4A5BCB20)
8c333000 8c33b000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4)
8c33b000 8c343000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3)
8c343000 8c34b000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5)
8c1ca000 8c1f7000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
9bc44000 9bc57000   rspndr   rspndr.sys   Mon Jul 13 19:53:20 2009 (4A5BC8F0)
928ce000 92900000   Rt86win7 Rt86win7.sys Thu Aug 20 12:04:54 2009 (4A8D7426)
9be20000 9be2a000   secdrv   secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528)
9293d000 92947000   serenum  serenum.sys  Mon Jul 13 19:45:27 2009 (4A5BC717)
8bf50000 8bf6a000   serial   serial.sys   Mon Jul 13 19:45:33 2009 (4A5BC71D)
8c1c2000 8c1ca000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
9bea7000 9bef8000   srv      srv.sys      Thu Aug 26 23:31:26 2010 (4C77318E)
9be58000 9bea7000   srv2     srv2.sys     Thu Aug 26 23:30:45 2010 (4C773165)
9be2a000 9be4b000   srvnet   srvnet.sys   Thu Aug 26 23:30:39 2010 (4C77315F)
93833000 93834380   swenum   swenum.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
9bd87000 9bd882c0   TBPanel  TBPanel.SYS  Fri Jul 26 19:01:04 2002 (3D41D4B0)
8c000000 8c149000   tcpip    tcpip.sys    Sun Jun 13 23:36:59 2010 (4C15A3DB)
9be4b000 9be58000   tcpipreg tcpipreg.sys Mon Jul 13 19:54:14 2009 (4A5BC926)
8c37b000 8c386000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C)
8c364000 8c37b000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A)
8bf7d000 8bf8d000   termdd   termdd.sys   Mon Jul 13 20:01:35 2009 (4A5BCADF)
95ae0000 95ae9000   TSDDD    TSDDD.dll    Mon Jul 13 20:01:40 2009 (4A5BCAE4)
9289b000 928bc000   tunnel   tunnel.sys   Mon Jul 13 19:54:03 2009 (4A5BC91B)
92b5a000 92b9a000   udfs     udfs.sys     Mon Jul 13 19:14:09 2009 (4A5BBFC1)
92a3c000 92a4a000   umbus    umbus.sys    Mon Jul 13 19:51:38 2009 (4A5BC88A)
9bf15000 9bf28b00   usbaudio usbaudio.sys Mon Jul 13 19:51:23 2009 (4A5BC87B)
92ba5000 92bbc000   usbccgp  usbccgp.sys  Mon Jul 13 19:51:31 2009 (4A5BC883)
92b58000 92b59700   USBD     USBD.SYS     Mon Jul 13 19:51:05 2009 (4A5BC869)
943a6000 943b5000   usbehci  usbehci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872)
92a4a000 92a8e000   usbhub   usbhub.sys   Mon Jul 13 19:52:06 2009 (4A5BC8A6)
943b5000 94400000   USBPORT  USBPORT.SYS  Mon Jul 13 19:51:13 2009 (4A5BC871)
92b41000 92b58000   USBSTOR  USBSTOR.SYS  Mon Jul 13 19:51:19 2009 (4A5BC877)
8bab3000 8babe000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
8c2f9000 8c305000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E)
8c305000 8c326000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D)
8c17a000 8c182380   vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C)
8bacf000 8badf000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8badf000 8bb2a000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
8c183000 8c1c2000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
8bf6a000 8bf7d000   wanarp   wanarp.sys   Mon Jul 13 19:55:02 2009 (4A5BC956)
8c326000 8c333000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A)
8b9b1000 8ba22000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
8ba22000 8ba30000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8c3e0000 8c3e7000   wfplwf   wfplwf.sys   Mon Jul 13 19:53:51 2009 (4A5BC90F)
95880000 95acb000   win32k   win32k.sys   Tue Aug 31 22:34:29 2010 (4C7DBBB5)
8ba78000 8ba81000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)
8b800000 8b81a000   WudfPf   WudfPf.sys   Mon Jul 13 19:50:13 2009 (4A5BC835)
9bf29000 9bf3a080   XDva363  XDva363.sys  Fri Sep 03 07:30:43 2010 (4C80DC63)

Unloaded modules:
9bf01000 9bf15000   usbaudio.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
9bf9e000 9bfbf000   WUDFRd.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
9bc00000 9bc14000   usbaudio.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
9bf01000 9bf6b000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
9bfda000 9bfee000   usbaudio.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
9bfc8000 9bfcf000   drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
9bfc4000 9bfc6000   MSTEE.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
9bfc6000 9bfc8000   MSPQM.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
9bfc1000 9bfc4000   MSKSSRV.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
9bfbf000 9bfc1000   MSPCLOCK.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8c291000 8c29c000   mouhid.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8bfe4000 8bff8000   usbaudio.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
9bf01000 9bf6b000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8c277000 8c284000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8c284000 8c28f000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8c28f000 8c298000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8c298000 8c2a9000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

Windows 7 Kernel Version 7600 MP (8 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82812000 PsLoadedModuleList = 0x82951570
Debug session time: Mon Nov  1 18:16:22.183 2010 (GMT-4)
System Uptime: 0 days 0:28:05.324
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....
0: kd> !Analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 44, {925edbb8, 1d7b, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!IopPostProcessIrp+dc )

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

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

MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed.  This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened.  Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it.  The
first actually works, and the second fails.  Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second.  However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: 925edbb8, Address of the IRP
Arg2: 00001d7b
Arg3: 00000000
Arg4: 00000000

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


IRP_ADDRESS:  00df8f68

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x44

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 828a11bb to 828e3574

STACK_TEXT:  
925edb94 828a11bb 00000044 925edbb8 00001d7b nt!KeBugCheckEx+0x1e
925edbbc 828739ac 925edbb8 b71c6d68 00864918 nt!IopFreeIrp+0x22
925edc04 828b89ef 00df8fa8 925edc34 00000000 nt!IopCompleteRequest+0x429
925edc50 82a0f9d0 925edc6c b71c6df8 00000001 nt!IopPostProcessIrp+0xdc
925edc94 82a66213 00000001 925edccc 925edce4 nt!IoRemoveIoCompletion+0xa5
925edd18 8284779a 000004f4 00c9f858 00c9f848 nt!NtRemoveIoCompletion+0x106
925edd18 779a64f4 000004f4 00c9f858 00c9f848 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
00c9f830 00000000 00000000 00000000 00000000 0x779a64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!IopPostProcessIrp+dc
828b89ef 5f              pop     edi

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!IopPostProcessIrp+dc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3f9b

FAILURE_BUCKET_ID:  0x44_nt!IopPostProcessIrp+dc

BUCKET_ID:  0x44_nt!IopPostProcessIrp+dc

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

The dumps indicate hardware or hardware related problems.

You have a couple of obsolete device drivers loading on your system. Out of date drivers can and do cause memory corruption. Update these drivers or uninstall the software they are associated with.

irsir.sys Sat Jan 19 00:55:21 2008 - Serial Infrared Driver, Windows Update.

TBPanel.SYS Fri Jul 26 19:01:04 2002 - Display Control Program belongs to the software Windows (R) 2000 DDK driver by Windows (R) 2000 DDK provider (www.microsoft.com). You can try to update this from Microsoft; but I do not know of an update for it. This is XP software. I recommend that you uninstall this software.

Update these two drivers and reboot. Let's see how your system does. Please upload the rest of the requested files and I will look deeper.

zigzag3143 · Nov 1, 2010

Tales Of Musica said:
Hello i just got a bran new computer, its new just out of the box, i installed windows 7 professional 32 bit and things were ok.
But now every time i try to play Starcraft2 after about 10 mins i blue screen and then on restart get this message.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 2057

Additional information about the problem:
BCCode: 44
BCP1: 925EDBB8
BCP2: 00001D7B
BCP3: 00000000
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\110110-24562-01.dmp
C:\Users\Presley\AppData\Local\Temp\WER-36203-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I know my computer can handle the game and the thing is brand new not even a month old.
Could anyone throw me some insight?
Thanks in advance.

whatever tbpanel.sys is it is 8 years old and should be removed. Also you should update the old drivers, and run driver verifier

Old drivers needing update

Code:

TBPanel.SYS        0x9bd87000    0x9bd882c0    0x000012c0    0x3d41d4b0    7/26/2002 19:01:04                        
irsir.sys        0x9381f000    0x9382a000    0x0000b000    0x479190c9    1/19/2008 01:55:21                        
spldr.sys        0x8c1c2000    0x8c1ca000    0x00008000    0x4a084ebb    5/11/2009 12:13:47                        
amdxata.sys        0x8bb81000    0x8bb8a000    0x00009000    0x4a12f30f    5/19/2009 13:57:35

Run driver verifier

Beyond that, please run Verifier with these settings:

Code:
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 "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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 (an estimate on my part).

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Using Driver Verifier to identify issues with Windows drivers for advanced users

Ken J

Tales Of Musica · Nov 4, 2010

I'm a compleet computer novice when it comes to softwear, how do i find these drivers and update them?
And is there another one, running this driver verifier thing seems like it could just make things worse.

Tales Of Musica · Nov 4, 2010

Sorry for the late reply.
Heres all the info you asked for.
Also how do i find those windows Xp drivers so i can uninstall them?

CarlTR6 · Nov 4, 2010

How to update drivers -

- I have listed links to most of the drivers in the code box above. Please use the links there to see what info I've found about those 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 manufacturer links are on this page: Drivers and Downloads

Running Driver Verifier will not make things worse. It will trigger BSOD's when it finds faulty drivers. Hopefully the resulting mini dumps point to the offending drivers.

Your latest three dumps all indicate memory corruption. We need to eliminate out of date drivers as a problem before we proceed with hardware testing. These are two seriously out of date: irsir.sys Sat Jan 19 00:55:21 2008 and TBPanel.SYS Fri Jul 26 19:01:04 2002. Try renaming them; but keep in mind that renaming them will break whatever program or device they are associated with. Navigate to C:\Windows\System32\Drivers, locate the files and rename them from .sys to .bak. Reboot and the drivers will not load. You can also uninstall the software or hardware to which they belong.

After you rename those two drivers, we will go from there if you have another BSOD.

Tales Of Musica · Nov 9, 2010

And i here i thought that fixed it, then it started up all over again.
got a few days without them tho.
The first BSOD windows said was caused by XDVAnnn.sys which i found was a part of an anti-cheat system called Xtrap used by alot of MMORPG's

But the next one gave no reason like the others and I don't think it was caused by
XDVAnnn.sys but i can't be sure.

Anyway, I'm at a loss I've never had this problem before and so got no clue,

Also i don't know how to update drivers, so i did turn off the two you said were really out of date, but have no clue how to update the other two
I'm hopeless at all this so if you could dumb it down for me I'm not too bad at following step by step.

Heres the dumps again and Thanks again for all your help.

CarlTR6 · Nov 9, 2010

I cannot find the driver, XDVAnnn.sys, anywhere on yours system. Can you give me the location and date of this driver? I did find XDva363.sys in your very first dump. It was not shown as part of the crash and it was up to date. Both of your latest dumps blame memory corruption.

Error code 8E, KERNEL_MODE_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory.

Error code 1A, MEMORY_MANAGEMENT. Usual causes: Device driver, memory, kernel.

Code:

Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82837000 PsLoadedModuleList = 0x82976570
Debug session time: Tue Nov  9 10:55:56.799 2010 (GMT-5)
System Uptime: 0 days 12:15:55.940
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 828aacdb, 9dbbb70c, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 828aacdb, The address that the exception occurred at
Arg3: 9dbbb70c, Trap Frame
Arg4: 00000000

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!MiChargeWsles+3c
828aacdb 66ff8b86000000  dec     word ptr [ebx+86h]

TRAP_FRAME:  9dbbb70c -- (.trap 0xffffffff9dbbb70c)
ErrCode = 00000002
eax=00000040 ebx=00000000 ecx=0000c000 edx=0000c000 esi=00000000 edi=82962c80
eip=828aacdb esp=9dbbb780 ebp=9dbbb7a4 iopl=0         nv up ei ng nz ac pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010297
nt!MiChargeWsles+0x3c:
828aacdb 66ff8b86000000  dec     word ptr [ebx+86h]       ds:0023:00000086=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x8E

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 828d2391 to 828aacdb

STACK_TEXT:  
9dbbb7a4 828d2391 82962c80 00000040 00000000 nt!MiChargeWsles+0x3c
9dbbb880 828db915 82803900 87bbf378 84f6f0b0 nt!MiObtainSystemCacheView+0x76
9dbbb978 828db300 a94e2b78 84f6f0b0 9dbbb9b8 nt!MmMapViewInSystemCache+0xf8
9dbbb9d8 828d0965 00000000 00000000 0ee92400 nt!CcGetVacbMiss+0x165
9dbbba2c 82a99745 87bbf378 0ee92400 00000000 nt!CcGetVirtualAddress+0x1b1
9dbbba74 82a8f872 85384758 0ee92400 00000000 nt!CcMapAndCopyFromCache+0x53
9dbbbab0 8bca25aa 85384758 88188eac 00009c00 nt!CcCopyRead+0x107
9dbbbbd0 8bb64fec 85384758 a464bd78 00009c00 Ntfs!NtfsCopyReadA+0x1d7
9dbbbc04 8bb651bb 00000003 00000000 88188ea4 fltmgr!FltpPerformFastIoCall+0x22e
9dbbbc30 8bb77c37 00bbbc54 8bb77ad4 00000000 fltmgr!FltpPassThroughFastIo+0x7d
9dbbbc74 82a3be7a 85384758 9dbbbcb4 00009c00 fltmgr!FltpFastIoRead+0x163
9dbbbd08 8286c79a 85edb978 00000000 00000000 nt!NtReadFile+0x2d5
9dbbbd08 77c064f4 85edb978 00000000 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
01fdef58 00000000 00000000 00000000 00000000 0x77c064f4


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
3 errors : !nt (828aa058-828aacd8)
828aa050  73  0c  3b  f2  0f  84  9b  03 *02  00  39  55  08  0f  84  8c s.;.......9U....
...
828aa360  ff  75  18  ff  73  10  ff  73 *0e  ff  73  14  ff  73  08  ff .u..s..s..s..s..
...
828aacd0  24  14  eb  64  64  8b  1d  24 *03  00  00  66  ff  8b  86  00 $..dd..$...f....

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

Debug session time: Mon Nov  8 22:34:59.768 2010 (GMT-5)
System Uptime: 0 days 0:46:26.784
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
......
3: kd> !Analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 4c400000, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiTrap0E+dc )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 4c400000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Steam.exe

CURRENT_IRQL:  0

TRAP_FRAME:  a011762c -- (.trap 0xffffffffa011762c)
ErrCode = 00000000
eax=002cd800 ebx=82968c80 ecx=83c00000 edx=8c400000 esi=8c400000 edi=00002546
eip=828aa057 esp=a01176a0 ebp=a01176b4 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nt!MiTerminateWsle+0x3b:
828aa057 8b80000000c0    mov     eax,dword ptr [eax-40000000h] ds:0023:c02cd800=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82875988 to 8289bc46

STACK_TEXT:  
a0117614 82875988 00000000 4c400000 00000000 nt!MmAccessFault+0xbf
a0117614 828aa057 00000000 4c400000 00000000 nt!KiTrap0E+0xdc
a01176b4 828aa284 b3600000 82968c80 00002546 nt!MiTerminateWsle+0x3b
a011781c 82a5e3d7 b3600000 b196ba20 00000000 nt!MmUnmapViewInSystemCache+0x1cd
a0117854 828b9152 84f483b0 8569d008 00000000 nt!CcUnmapVacb+0x185
a0117894 828a460c 0169d008 00000000 00000000 nt!CcUnmapVacbArray+0x292
a0117928 8bcb4f62 853c62c0 00000000 00000000 nt!CcFlushCache+0x140
a011797c 8bcb6ac9 007062e8 a3ff0d78 00000000 Ntfs!NtfsFlushUserStream+0x93
a01179c8 8bcb6046 857062e8 a3ff0d78 2bd63084 Ntfs!NtfsPerformOptimisticFlush+0x7c
a0117a38 8bcb676b 857062e8 85694d50 2bd6301c Ntfs!NtfsCommonFlushBuffers+0x244
a0117aa0 8bc5120c 87d12020 85694d50 2bd63050 Ntfs!NtfsFsdFlushBuffers+0xf7
a0117aec 8bcc164f 00000000 85694d50 00000009 Ntfs!NtfsIoCallSelf+0xdb
a0117ce0 8bc4f456 a5841a24 8566f780 2bd637a0 Ntfs!NtfsCommonCleanup+0x3b59
a0117d1c 8289a056 a58419d4 00000000 ffffffff Ntfs!NtfsCommonCleanupCallout+0x1d
a0117d1c 8289a14d a58419d4 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x15a
a584193c 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTrap0E+dc
82875988 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiTrap0E+dc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3f9b

FAILURE_BUCKET_ID:  0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID:  0x1a_41287_nt!KiTrap0E+dc

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

Please test your RAM with Memtest following the instructions in this tutorial: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html. Run Memtest for at least 7 passes. This will take 6-8 hours. Errors, if any, will show on your screen in red. Post back with your results.

If Memetest shows no errors, enable Driver Verifier. Read the instructions in this tutorial carefully: Driver Verifier - Enable and Disable. Upload any and all dumps generated by Driver Verifier.

Tales Of Musica · Nov 9, 2010

A friend told me a cleen install may help.
So i did and nothing, going to run the RAM tester thing. now and see whats what.
Heres the dump from the cleen install maybe it will help.

Tales Of Musica · Nov 10, 2010

It ran for 11 passes and found no errors.

CarlTR6 · Nov 10, 2010

That is great news about the RAM test. That means your RAM is most likely OK. Thank you for the latest dump. It provides a lot of information.

This latest crash was most like caused by Norton/Symantec, specifically the antitvirus.

Error code A, IRQL_NOT_LESS_OR_EQUAL. Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

The dump shows two unloaded modules which means they were involved in the crash: NAVEX15.SYS and NAVEX15.SYS. Norton is a well known and documented cause of BSOD's on some Win 7 systems. Completely uninstall it using this removal tool: [FONT=&quot]Tool. Do not reinstall this version of Norton; it is way obsolete and not compatible with Win7. I suggest that you download and install Microsoft Security Essentials. Make sure Windows Firewall is turned on. Do not install any third party antivirus or firewall programs until you know your system is stable.

Further, you still have outdated drivers loading on your system. These drivers are quite obsolete. One is definitely an XP driver. XP software is not going to work with Win 7 except in the XP mode.
[/FONT]

BHDrvx86.sys Fri Aug 15 23:24:14 2008 - Symantec Heuristics DriverSymantec - AntiVirus, Anti-Spyware, Endpoint Security, Backup, Storage Solutions
[FONT=&quot]
ccHPx86.sys Mon Aug 25 20:00:37 2008 - [/FONT]Common Client Hash Provider Driver - Symantechttp://www.symantec.com
[FONT=&quot]
IDSVix86.sys Tue Aug 19 13:12:37 2008 - [/FONT]part of Symantec antiviral software
[FONT=&quot]
irsir.sys Sat Jan 19 00:55:21 2008 - [/FONT]Serial Infrared Driver, Windows Update. If you cannot update this driver, uninstall the device.
[FONT=&quot]
SRTSP.SYS Tue Aug 19 14:47:50 2008 - Norton drivers
SRTSPX.SYS Tue Aug 19 14:49:52 2008
SYMDNS.SYS Fri Aug 22 19:47:25 2008
SYMEFA.SYS Thu Aug 28 00:38:44 2008
SYMEVENT.SYS Mon Aug 04 19:28:32 2008
SYMFW.SYS Fri Aug 22 19:47:45 2008
SymIMv.sys Tue Aug 05 21:56:06 2008
SYMNDISV.SYS Fri Aug 22 19:49:58 2008
SYMREDRV.SYS Fri Aug 22 19:47:56 2008
SYMTDI.SYS Fri Aug 22 19:47:22 2008

TBPanel.SYS Fri Jul 26 19:01:04 2002 - [/FONT]Display Control Program belongs to the software Windows (R) 2000 DDK driver by Windows (R) 2000 DDK provider (www.microsoft.com). You can try to update this from Microsoft; but I do not know of an update for it. This is XP software. I recommend that you uninstall this software

Uninstall Norton, install MSE, take care of the other obsolete drivers listed above, reboot, and let's see how your system does. Post back and let us know.

Tales Of Musica · Nov 10, 2010

Ok, removed nortan and sorted out the drivers.
Still BSOD, heres the dump files.
My comp is BSOD'ing more and more now and its running very slow, sometimes even before windows can boot.
I'm really at a loss here..

Tales Of Musica · Nov 10, 2010

Also, my Nan said i should add this.
My dad got me my copy of windows 7, its a disc supposed to be sold with a dell computer for reinstall only, he got it off e-bay unused and assured me it would work fine.
My computer was custome made by the factory i got it from and so is not a dell.
dose this help?

Tales Of Musica · Nov 10, 2010

Ok i ran driver verifier and it crashed my comp instantly and kept doing it over and over, i did a restore and managed to get back on my comp.
Heres the dump files.
My computers in a right state now, not sure how much longer it will be useable like this, the problem seems to be getting worse, soon my comp wont go long enough between BSOD before i can't use it.

CarlTR6 · Nov 11, 2010

Please read this tutorial, Run the tool and upload all of the files. We need to look at your system to try and figure out what is going on.

[FONT=&quot]http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

[/FONT]

Tales Of Musica · Nov 11, 2010

Ok i did it again, heres the files.

CarlTR6 · Nov 11, 2010

Thanks very much.

My dad got me my copy of windows 7, its a disc supposed to be sold with a dell computer for reinstall only, he got it off e-bay unused and assured me it would work fine.
My computer was custome made by the factory i got it from and so is not a dell.
dose this help?

This good well be the problem. Many times, manufacturers, especially of laptops, modify the stock drivers from the component makers to fit their particular system/motherboard. You most definitely have a memory corruption problem. I am going to seek the help of others on the team here.

Tales Of Musica · Nov 11, 2010

Ah, i see. Thank you, i will await your reply.

Tales Of Musica · Nov 11, 2010

I was thinking, i have an OLD OLD copy of Windows, from 2002.
Could i just install that and update it?

Dave76 · Nov 11, 2010

Can you post some information, specs, on your computer?

Brand and model of motherboard, processor, RAM, graphics card, HDD/SSD, monitor if a desktop, etc.

You can use Speccy or SIW to find this information.

It's likely you will need to check for the correct system drivers.

Blue Screen

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

New member

My Computer

Endeavor to Persevere

My Computer