BSOD HELP (files included)

jugy3 · Jul 13, 2011

Hey i really need help with this issue. My computer keeps crashing and giving me the blue screen irql not less or equal. I searched everywhere but cannpt find a method to fix it. Here is what windows tells me when i restart my computer if it was shut down by the blue screen.

My computer gave me these results when i restarted it:
Problem signature:
[COLOR=#3676a2 !important][FONT=inherit !important][COLOR=#3676a2 !important][FONT=inherit !important]Problem [/FONT][COLOR=#3676a2 !important][FONT=inherit !important]Event[/FONT][/COLOR][/FONT][/COLOR][/COLOR] Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 4105

Additional information about the problem:
BCCode: a
BCP1: 03CBD308
BCP2: 00000002
BCP3: 00000001
BCP4: 81EE9123
OS Version: 6_0_6002
[COLOR=#3676a2 !important][FONT=inherit !important][COLOR=#3676a2 !important][FONT=inherit !important]Service [/FONT][COLOR=#3676a2 !important][FONT=inherit !important]Pack[/FONT][/COLOR][/FONT][/COLOR][/COLOR]: 2_0
Product: 768_1

Files that help describe the problem:
C:\WINDOWS\Minidump\Mini071211-01.dmp
C:\Users\Family\AppData\Local\Temp\WER-2…
C:\Users\Family\AppData\Local\Temp\WERB3…

Here is some information:
It's 32-bit. Originally installed on the computer OEM hardware and OS 4-5 years old
I attached the jcgriff zipped folder with the html report inside.

richc46 · Jul 13, 2011

Welcome
The check code A generally means
Typically due to a bad driver, or faulty or incompatible hardware or software. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.)
Your second report mentioned hardware. I would start with a memory test and lets see how that goes.
Guide to using Memtest86+ - Geeks to Go Forums

The reports that you have submittedreveal clues to the cause of your problem. They do not give a definitive answer. The more reports that we receivethe more clues are made available improving our chances of finding a solutionto your problem. Each remedy suggested must be performed regardless ofplacement in this report or other variables. You may have to experience severalmore BSODs until the final answer is discovered.

jugy3 · Jul 13, 2011

So after every crash i should run a report? Also i do not know much about computers :/

richc46 · Jul 13, 2011

What you can do is take the test. If it passes I need as many reports as crashes. If the test fails, fix the memory and then give me any new reports.

jugy3 · Jul 14, 2011

richc46 said:
What you can do is take the test. If it passes I need as many reports as crashes. If the test fails, fix the memory and then give me any new reports.

There were no errors with ram :/
I'll run another report when the crash happens.

richc46 · Jul 14, 2011

The more the better. Each one gives just little hints

jugy3 · Jul 17, 2011

Hey so i haven't got the blue screen in a while (don't know why) but today, instead of the computer crashing and the blue screen popping up, i got some next error. My computer crashed while watching a video and this popped up, "Not Optimum Mode
Recommended Mode: 1680 x 1050 60Hz

richc46 · Jul 17, 2011

Just adjust the resolution.
This has nothing to do with your BSOD, though
http://www.vistax64.com/tutorials/84291-screen-resolution.html

jugy3 · Jul 21, 2011

Ugh.. Blue screen is back. This time however, it's a different error called Bad_Pool_CALLER. I'll attach the files and here is some additional information.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 4105

Additional information about the problem:
BCCode: c2
BCP1: 00000099
BCP2: 86FED000
BCP3: 00000000
BCP4: 00000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

Files that help describe the problem:
C:\WINDOWS\Minidump\Mini072111-02.dmp
C:\Users\Family\AppData\Local\Temp\WER-174533-0.sysdata.xml
C:\Users\Family\AppData\Local\Temp\WERA949.tmp.version.txt

richc46 · Jul 21, 2011

IM away and cannot read the files. Another member will open them for me and/or offer help.

jugy3 · Jul 21, 2011

Ok thanks

Btw I got another blue screen, this time Driver_IRQL_NOT_LESS_OR_EQUAL

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 4105

Additional information about the problem:
BCCode: d1
BCP1: 0000DEC8
BCP2: 00000002
BCP3: 00000001
BCP4: 87760FE0
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

Files that help describe the problem:
C:\WINDOWS\Minidump\Mini072111-03.dmp
C:\Users\Family\AppData\Local\Temp\WER-204439-0.sysdata.xml
C:\Users\Family\AppData\Local\Temp\WERC7C1.tmp.version.txt

And the attachment is included.

Also i don't know if this will help but the blue screen usually comes when i try to watch a video.

americancritic · Jul 21, 2011

Hello I looked at your bsod files and you have 5, which are as follows.

1. 1000008E
2. A
3. D1
4. C2
5. C2

Sense Rich is out of town I will be working with him long distance by posting what he needs to help you in repairing your system...

americancritic · Jul 21, 2011

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\Tom\AppData\Local\Temp\Temp1_Windows_NT6_BSOD_jcgriff2.zip\Windows_NT6_BSOD_jcgriff2\Mini071111-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
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18327.x86fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0x81e46000 PsLoadedModuleList = 0x81f5dc70
Debug session time: Mon Jul 11 10:36:48.668 2011 (GMT-7)
System Uptime: 1 days 0:02:53.596
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 81ede5b0, b28b696c, 0}
Probably caused by : hardware ( nt!KiTrap0E+dc )
Followup: MachineOwner
---------
0: 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: 81ede5b0, The address that the exception occurred at
Arg3: b28b696c, 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!MmAccessFault+341
81ede5b0 6a00            push    0
TRAP_FRAME:  b28b6a54 -- (.trap 0xffffffffb28b6a54)
ErrCode = 00000002
eax=00000001 ebx=0019f04d ecx=869b0700 edx=00000000 esi=869b0788 edi=00000004
eip=81e6c086 esp=b28b6ac8 ebp=b28b6ad8 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
nt!KeGetExecuteOptions+0x37:
81e6c086 c804f6c3        enter   0F604h,0C3h
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x8E
PROCESS_NAME:  chrome.exe
CURRENT_IRQL:  0
MISALIGNED_IP: 
nt!KeGetExecuteOptions+37
81e6c086 c804f6c3        enter   0F604h,0C3h
LAST_CONTROL_TRANSFER:  from 81e93dd4 to 81ede5b0
STACK_TEXT:  
b28b6a3c 81e93dd4 00000001 b28a74b4 00000000 nt!MmAccessFault+0x341
b28b6a3c 81e6c086 00000001 b28a74b4 00000000 nt!KiTrap0E+0xdc
b28b6ad8 82055024 b28b6c4c e97575a7 ffffffff nt!KeGetExecuteOptions+0x37
b28b6d48 81e90c7a ffffffff 00000022 0019f038 nt!NtQueryInformationProcess+0xfde
b28b6d48 77505ca4 ffffffff 00000022 0019f038 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0019f048 00000000 00000000 00000000 00000000 0x77505ca4
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!KiTrap0E+dc
81e93dd4 85c0            test    eax,eax
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt!KiTrap0E+dc
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
---------
0: kd> lmvm hardware
start    end        module name
0: kd> Lmntsm
start    end        module name
8b6d3000 8b6e0080   1394BUS  1394BUS.SYS  Fri Jan 18 21:53:27 2008 (47919057)
87207000 8724d000   acpi     acpi.sys     Fri Apr 10 21:19:03 2009 (49E01A37)
8d202000 8d24a000   afd      afd.sys      Thu Apr 21 06:58:25 2011 (4DB03801)
87726000 87736000   amdk8    amdk8.sys    Fri Jan 18 21:27:20 2008 (47918A38)
9bfbb000 9bfc4000   asyncmac asyncmac.sys Fri Jan 18 21:56:29 2008 (4791910D)
87312000 8731a000   atapi    atapi.sys    Fri Apr 10 21:39:09 2009 (49E01EED)
8731a000 87338000   ataport  ataport.SYS  Fri Apr 10 21:39:10 2009 (49E01EEE)
8b588000 8b599000   avgfwd6x avgfwd6x.sys Sun Jul 11 18:37:25 2010 (4C3A71D5)
9bf85000 9bfa4300   AVGIDSDriver AVGIDSDriver.Sys Thu Apr 14 10:09:45 2011 (4DA72A59)
879d5000 879d8f80   AVGIDSEH AVGIDSEH.Sys Mon Feb 21 21:21:35 2011 (4D6347DF)
9bf80000 9bf84400   AVGIDSFilter AVGIDSFilter.Sys Wed Feb 09 20:58:08 2011 (4D537060)
9be53000 9be58580   AVGIDSShim AVGIDSShim.Sys Wed Feb 09 20:58:11 2011 (4D537063)
8d2ea000 8d325100   avgldx86 avgldx86.sys Thu Jan 06 20:35:29 2011 (4D269811)
8cbed000 8cbf9000   avgmfx86 avgmfx86.sys Tue Mar 01 04:23:55 2011 (4D6CE55B)
879ce000 879d4500   avgrkx86 avgrkx86.sys Wed Mar 16 07:05:26 2011 (4D80C3A6)
877b6000 877fce80   avgtdix  avgtdix.sys  Mon Apr 04 14:53:24 2011 (4D9A3DD4)
8b9e2000 8b9e9000   Beep     Beep.SYS     Fri Jan 18 21:49:10 2008 (47918F56)
8061f000 80627000   BOOTVID  BOOTVID.dll  Fri Jan 18 23:27:15 2008 (4791A653)
9af68000 9af81000   bowser   bowser.sys   Tue Feb 22 05:23:54 2011 (4D63B8EA)
92d70000 92d7e000   cdd      cdd.dll      Fri Apr 10 23:22:03 2009 (49E0370B)
9bfa5000 9bfbb000   cdfs     cdfs.sys     Fri Jan 18 21:28:02 2008 (47918A62)
8b90e000 8b926000   cdrom    cdrom.sys    Fri Apr 10 21:39:17 2009 (49E01EF5)
80668000 80748000   CI       CI.dll       Fri Apr 10 23:25:22 2009 (49E037D2)
879a4000 879c5000   CLASSPNP CLASSPNP.SYS Fri Apr 10 21:39:05 2009 (49E01EE9)
80627000 80668000   CLFS     CLFS.SYS     Fri Apr 10 21:13:51 2009 (49E018FF)
9bfd7000 9bfe4000   crashdmp crashdmp.sys Fri Apr 10 21:39:12 2009 (49E01EF0)
879c5000 879ce000   crcdisk  crcdisk.sys  Thu Nov 02 01:52:27 2006 (4549B1CB)
8d2c7000 8d2de000   dfsc     dfsc.sys     Thu Apr 14 07:59:03 2011 (4DA70BB7)
87993000 879a4000   disk     disk.sys     Fri Apr 10 21:39:14 2009 (49E01EF2)
8b7a3000 8b7c8000   drmk     drmk.sys     Fri Jan 18 22:53:02 2008 (47919E4E)
9bfe4000 9bfee000   dump_diskdump dump_diskdump.sys Fri Apr 10 21:39:11 2009 (49E01EEF)
8d33b000 8d358000   dump_nvstor32 dump_nvstor32.sys Mon Jul 02 17:35:28 2007 (468999D0)
8d36f000 8d379000   Dxapi    Dxapi.sys    Fri Jan 18 21:36:12 2008 (47918C4C)
8c717000 8c7b6000   dxgkrnl  dxgkrnl.sys  Fri Apr 10 21:23:43 2009 (49E01B4F)
8796c000 87993000   ecache   ecache.sys   Fri Apr 10 21:40:12 2009 (49E01F2C)
8c6c0000 8c6e8000   fastfat  fastfat.SYS  Fri Apr 10 21:13:52 2009 (49E01900)
873c8000 873d8000   fileinfo fileinfo.sys Fri Jan 18 21:34:27 2008 (47918BE3)
87396000 873c8000   fltmgr   fltmgr.sys   Fri Apr 10 21:13:59 2009 (49E01907)
8ca00000 8ca09000   Fs_Rec   Fs_Rec.SYS   unavailable (00000000)
876ee000 87709000   fwpkclnt fwpkclnt.sys Fri Apr 10 21:45:42 2009 (49E02076)
81e13000 81e46000   hal      halmacpi.dll Fri Apr 10 21:13:13 2009 (49E018D9)
8b6e1000 8b76e000   HDAudBus HDAudBus.sys Fri Apr 10 21:42:41 2009 (49E01FC1)
8b601000 8b6b6000   HSX_CNXT HSX_CNXT.sys Thu May 08 13:04:13 2008 (48235CBD)
8b478000 8b57a000   HSX_DP   HSX_DP.sys   Thu May 08 13:03:14 2008 (48235C82)
8b402000 8b44e000   HSXHWBS2 HSXHWBS2.sys Thu May 08 13:05:16 2008 (48235CFC)
9aede000 9af4b000   HTTP     HTTP.sys     Sat Feb 20 12:53:31 2010 (4B804BCB)
87736000 87749000   i8042prt i8042prt.sys Fri Jan 18 21:49:17 2008 (47918F5D)
87754000 8775f000   kbdclass kbdclass.sys Fri Jan 18 21:49:14 2008 (47918F5A)
80607000 8060e000   kdcom    kdcom.dll    Fri Apr 10 23:25:29 2009 (49E037D9)
8b44e000 8b478000   ks       ks.sys       Fri Apr 10 21:38:47 2009 (49E01ED7)
87404000 87475000   ksecdd   ksecdd.sys   Mon Jun 15 05:48:53 2009 (4A364335)
9aebb000 9aecb000   lltdio   lltdio.sys   Fri Jan 18 21:55:03 2008 (479190B7)
8d388000 8d3a3000   luafv    luafv.sys    Fri Jan 18 21:30:35 2008 (47918AFB)
9be59000 9be5c180   mdmxsdk  mdmxsdk.sys  Mon Jun 19 14:26:59 2006 (449716A3)
8b6b6000 8b6c3000   modem    modem.sys    Fri Jan 18 21:57:16 2008 (4791913C)
9bfc4000 9bfd3000   monitor  monitor.sys  Fri Jan 18 21:52:19 2008 (47919013)
87749000 87754000   mouclass mouclass.sys Fri Jan 18 21:49:14 2008 (47918F5A)
87302000 87312000   mountmgr mountmgr.sys Fri Jan 18 21:49:13 2008 (47918F59)
9af81000 9af96000   mpsdrv   mpsdrv.sys   Fri Jan 18 21:54:45 2008 (479190A5)
9af96000 9afb7000   mrxdav   mrxdav.sys   Fri Apr 10 21:14:39 2009 (49E0192F)
9afb7000 9afd6000   mrxsmb   mrxsmb.sys   Fri Apr 29 06:24:39 2011 (4DBABC17)
8d3ab000 8d3e4000   mrxsmb10 mrxsmb10.sys Fri Apr 29 06:24:48 2011 (4DBABC20)
9afd6000 9afee000   mrxsmb20 mrxsmb20.sys Fri Apr 29 06:24:41 2011 (4DBABC19)
8b7e9000 8b7f4000   Msfs     Msfs.SYS     unavailable (00000000)
87256000 8725e000   msisadrv msisadrv.sys Fri Jan 18 21:32:51 2008 (47918B83)
8c7c2000 8c7f1000   msiscsi  msiscsi.sys  Fri Apr 10 21:40:07 2009 (49E01F27)
87580000 875ab000   msrpc    msrpc.sys    unavailable (00000000)
8b9ba000 8b9c4000   mssmbios mssmbios.sys Fri Jan 18 21:32:55 2008 (47918B87)
8795d000 8796c000   mup      mup.sys      Fri Apr 10 21:14:12 2009 (49E01914)
87475000 87580000   ndis     ndis.sys     Fri Apr 10 21:45:52 2009 (49E02080)
8b93d000 8b948000   ndistapi ndistapi.sys Fri Jan 18 21:56:24 2008 (47919108)
8b948000 8b96b000   ndiswan  ndiswan.sys  Fri Apr 10 21:46:31 2009 (49E020A7)
8b9d1000 8b9e2000   NDProxy  NDProxy.SYS  Fri Jan 18 21:56:28 2008 (4791910C)
8d260000 8d26e000   netbios  netbios.sys  Fri Jan 18 21:55:45 2008 (479190E1)
8b5c3000 8b5f5000   netbt    netbt.sys    Fri Apr 10 21:45:35 2009 (49E0206F)
875ab000 875e6000   NETIO    NETIO.SYS    Fri Apr 10 21:46:21 2009 (49E0209D)
8b57a000 8b588000   Npfs     Npfs.SYS     Fri Apr 10 21:14:01 2009 (49E01909)
8d2bd000 8d2c7000   nsiproxy nsiproxy.sys Fri Jan 18 21:55:50 2008 (479190E6)
81e46000 82200000   nt       ntkrpamp.exe Thu Oct 14 07:16:54 2010 (4CB710D6)
8780c000 8791c000   Ntfs     Ntfs.sys     Fri Apr 10 21:14:34 2009 (49E0192A)
8cbf9000 8cc00000   Null     Null.SYS     unavailable (00000000)
8c715000 8c716040   nvBridge nvBridge.kmd Tue Mar 16 00:57:16 2010 (4B9F39DC)
8bc0a000 8c561c60   nvlddmkm nvlddmkm.sys Fri Oct 30 13:00:35 2009 (4AEB45E3)
8c562000 8c661600   nvmfdx32 nvmfdx32.sys Fri Aug 01 11:37:49 2008 (489357FD)
87338000 87355000   nvstor32 nvstor32.sys Mon Jul 02 17:35:28 2007 (468999D0)
8b6c3000 8b6d2300   ohci1394 ohci1394.sys Fri Apr 10 21:43:04 2009 (49E01FD8)
8d24a000 8d260000   pacer    pacer.sys    Fri Apr 10 21:45:51 2009 (49E0207F)
87285000 87294000   partmgr  partmgr.sys  Fri Apr 10 21:39:19 2009 (49E01EF7)
8725e000 87285000   pci      pci.sys      Fri Apr 10 21:19:16 2009 (49E01A44)
872ed000 872f4000   pciide   pciide.sys   Fri Apr 10 21:39:10 2009 (49E01EEE)
872f4000 87302000   PCIIDEX  PCIIDEX.SYS  Fri Apr 10 21:39:09 2009 (49E01EED)
9be5d000 9bf3b000   peauth   peauth.sys   Mon Oct 23 01:55:32 2006 (453C8384)
8cbc0000 8cbed000   portcls  portcls.sys  Fri Apr 10 21:42:48 2009 (49E01FC8)
879fb000 879ffa80   PS2      PS2.sys      Mon Dec 12 17:26:59 2005 (439E2363)
8060e000 8061f000   PSHED    PSHED.dll    Fri Apr 10 23:25:32 2009 (49E037DC)
873d8000 873e0b80   PxHelp20 PxHelp20.sys Fri Feb 02 13:23:57 2007 (45C3ABED)
8b7f4000 8b7fd000   rasacd   rasacd.sys   Fri Jan 18 21:56:31 2008 (4791910F)
8b926000 8b93d000   rasl2tp  rasl2tp.sys  Fri Jan 18 21:56:33 2008 (47919111)
8b96b000 8b97a000   raspppoe raspppoe.sys Fri Apr 10 21:46:30 2009 (49E020A6)
8b97a000 8b98e000   raspptp  raspptp.sys  Fri Jan 18 21:56:34 2008 (47919112)
8b98e000 8b9a3000   rassstp  rassstp.sys  Fri Apr 10 21:46:40 2009 (49E020B0)
8d281000 8d2bd000   rdbss    rdbss.sys    Fri Apr 10 21:14:26 2009 (49E01922)
8b9f5000 8b9fd000   RDPCDD   RDPCDD.sys   Fri Jan 18 22:01:08 2008 (47919224)
8b800000 8b808000   rdpencdd rdpencdd.sys Fri Jan 18 22:01:09 2008 (47919225)
8b9a3000 8b9a9a00   RimSerial RimSerial.sys Mon Nov 24 09:02:13 2008 (492ADE15)
8bc00000 8bc08000   RootMdm  RootMdm.sys  Fri Jan 18 21:57:14 2008 (4791913A)
9aecb000 9aede000   rspndr   rspndr.sys   Fri Jan 18 21:55:03 2008 (479190B7)
8ca0b000 8cbbfa40   RTKVHDA  RTKVHDA.sys  Tue Jul 10 19:20:43 2007 (46943E7B)
9bf3b000 9bf45000   secdrv   secdrv.SYS   Wed Sep 13 06:18:32 2006 (45080528)
8b5af000 8b5c3000   smb      smb.sys      Fri Apr 10 21:45:22 2009 (49E02062)
87955000 8795d000   spldr    spldr.sys    Thu Jun 21 17:29:17 2007 (467B17DD)
9ae0b000 9aebb000   spsys    spsys.sys    Tue Mar 10 10:10:28 2009 (49B69F04)
9be04000 9be53000   srv      srv.sys      Fri Feb 18 06:03:28 2011 (4D5E7C30)
807c7000 807ef000   srv2     srv2.sys     Fri Apr 29 06:25:09 2011 (4DBABC35)
9af4b000 9af68000   srvnet   srvnet.sys   Fri Apr 29 06:25:08 2011 (4DBABC34)
87355000 87396000   storport storport.sys Fri Apr 10 21:39:19 2009 (49E01EF7)
8bc08000 8bc09380   swenum   swenum.sys   Fri Jan 18 21:49:20 2008 (47918F60)
87604000 876ee000   tcpip    tcpip.sys    Wed Jun 16 06:45:41 2010 (4C18D585)
9bf45000 9bf51000   tcpipreg tcpipreg.sys Tue Dec 08 09:26:18 2009 (4B1E8C3A)
8c7f1000 8c7fc000   TDI      TDI.SYS      Fri Jan 18 21:57:10 2008 (47919136)
8b599000 8b5af000   tdx      tdx.sys      Fri Apr 10 21:45:56 2009 (49E02084)
8b9aa000 8b9ba000   termdd   termdd.sys   Fri Apr 10 21:51:14 2009 (49E021C2)
92cb0000 92cb9000   TSDDD    TSDDD.dll    unavailable (00000000)
87800000 87809000   tunmp    tunmp.sys    Fri Jan 18 21:55:40 2008 (479190DC)
879f0000 879fb000   tunnel   tunnel.sys   Thu Feb 18 03:28:13 2010 (4B7D244D)
8b9c4000 8b9d1000   umbus    umbus.sys    Fri Jan 18 21:53:40 2008 (47919064)
8d2e8000 8d2e9700   USBD     USBD.SYS     Fri Jan 18 21:53:17 2008 (4791904D)
877a7000 877b6000   usbehci  usbehci.sys  Fri Apr 10 21:42:52 2009 (49E01FCC)
8b76e000 8b7a3000   usbhub   usbhub.sys   Fri Apr 10 21:43:14 2009 (49E01FE2)
8775f000 87769000   usbohci  usbohci.sys  Fri Apr 10 21:42:52 2009 (49E01FCC)
87769000 877a7000   USBPORT  USBPORT.SYS  Fri Apr 10 21:42:55 2009 (49E01FCF)
9bfee000 9bff8000   usbprint usbprint.sys Fri Jan 18 22:14:40 2008 (47919550)
8d326000 8d33b000   USBSTOR  USBSTOR.SYS  Fri Apr 10 21:42:55 2009 (49E01FCF)
8b9e9000 8b9f5000   vga      vga.sys      Fri Jan 18 21:52:06 2008 (47919006)
8b7c8000 8b7e9000   VIDEOPRT VIDEOPRT.SYS Fri Jan 18 21:52:10 2008 (4791900A)
87294000 872a3000   volmgr   volmgr.sys   Fri Jan 18 21:49:51 2008 (47918F7F)
872a3000 872ed000   volmgrx  volmgrx.sys  Fri Apr 10 21:39:25 2009 (49E01EFD)
8791c000 87955000   volsnap  volsnap.sys  Fri Apr 10 21:39:37 2009 (49E01F09)
8d26e000 8d281000   wanarp   wanarp.sys   Fri Jan 18 21:56:31 2008 (4791910F)
8c7b6000 8c7c2000   watchdog watchdog.sys Fri Apr 10 21:22:43 2009 (49E01B13)
80748000 807b9000   Wdf01000 Wdf01000.sys Mon Jul 13 16:11:36 2009 (4A5BBF28)
807b9000 807c7000   WDFLDR   WDFLDR.SYS   Mon Jul 13 16:11:25 2009 (4A5BBF1D)
92a90000 92c94000   win32k   win32k.sys   Thu Mar 03 05:24:58 2011 (4D6F96AA)
8724d000 87256000   WMILIB   WMILIB.SYS   Fri Jan 18 21:53:08 2008 (47919044)
9bf66000 9bf78000   WUDFPf   WUDFPf.sys   Fri Jan 18 21:52:49 2008 (47919031)
9bf51000 9bf65580   WUDFRd   WUDFRd.sys   Fri Jan 18 21:53:04 2008 (47919040)
9bf78000 9bf80000   xaudio   xaudio.sys   Thu Oct 18 15:36:53 2007 (4717E005)
Unloaded modules:
9bfee000 9bff8000   usbprint.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8c662000 8c6c0000   eeCtrl.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8b80b000 8b90e000   nvmfdx32.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8d33b000 8d348000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8d348000 8d352000   dump_storpor
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8d352000 8d36f000   dump_nvstor3
    Timestamp: unavailable (00000000)
    Checksum:  00000000
9bfd3000 9bfd7000   cpuz134_x32.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8bc0d000 8c715000   nvlddmkm.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8d379000 8d388000   monitor.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8d2de000 8d2e8000   usbprint.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8d3a3000 8d3ab000   drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
879d9000 879e6000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
879e6000 879f0000   dump_storpor
    Timestamp: unavailable (00000000)
    Checksum:  00000000
87709000 87726000   dump_nvstor3
    Timestamp: unavailable (00000000)
    Checksum:  00000000

Sorry Rich I forgot to include this info, if you need anything let me know.

jugy3 · Jul 23, 2011

Here's another report

americancritic · Jul 23, 2011

Hello jugy3

Right off the bat the first stop code is coming back to a hardware problem. Please redo the whole memtest86, if it turns out not to be your ram them we need to look at some of the other things that can go wrong...

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [_jcgriff2\Mini071111-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
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18327.x86fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0x81e46000 PsLoadedModuleList = 0x81f5dc70
Debug session time: Mon Jul 11 10:36:48.668 2011 (GMT-7)
System Uptime: 1 days 0:02:53.596
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
[COLOR=blue]BugCheck 1000008E[/COLOR], {c0000005, 81ede5b0, b28b696c, 0}
[COLOR=blue]Probably caused by : hardware[/COLOR] ( nt!KiTrap0E+dc )
Followup: MachineOwner
---------
0: 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: 81ede5b0, The address that the exception occurred at
Arg3: b28b696c, 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!MmAccessFault+341
81ede5b0 6a00            push    0
TRAP_FRAME:  b28b6a54 -- (.trap 0xffffffffb28b6a54)
ErrCode = 00000002
eax=00000001 ebx=0019f04d ecx=869b0700 edx=00000000 esi=869b0788 edi=00000004
eip=81e6c086 esp=b28b6ac8 ebp=b28b6ad8 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
nt!KeGetExecuteOptions+0x37:
81e6c086 c804f6c3        enter   0F604h,0C3h
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x8E
PROCESS_NAME:  chrome.exe
CURRENT_IRQL:  0
MISALIGNED_IP: 
nt!KeGetExecuteOptions+37
81e6c086 c804f6c3        enter   0F604h,0C3h
LAST_CONTROL_TRANSFER:  from 81e93dd4 to 81ede5b0
STACK_TEXT:  
b28b6a3c 81e93dd4 00000001 b28a74b4 00000000 nt!MmAccessFault+0x341
b28b6a3c 81e6c086 00000001 b28a74b4 00000000 nt!KiTrap0E+0xdc
b28b6ad8 82055024 b28b6c4c e97575a7 ffffffff nt!KeGetExecuteOptions+0x37
b28b6d48 81e90c7a ffffffff 00000022 0019f038 nt!NtQueryInformationProcess+0xfde
b28b6d48 77505ca4 ffffffff 00000022 0019f038 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0019f048 00000000 00000000 00000000 00000000 0x77505ca4
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!KiTrap0E+dc
81e93dd4 85c0            test    eax,eax
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt!KiTrap0E+dc
FOLLOWUP_NAME:  MachineOwner
[COLOR=blue]IMAGE_NAME:  hardware[/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP:  0
MODULE_NAME: hardware
FAILURE_BUCKET_ID:  IP_MISALIGNED
BUCKET_ID:  IP_MISALIGNED
Followup: MachineOwner
---------

You can see for your self that this report along with the other I uploaded for you to see says hard ware but we will keep looking for some answers and hopefully we will find them soon.

jugy3 · Jul 24, 2011

Thanks so much for the help :D and i'll run another ram test soon.
Here's two more reports.
The first one was a irql not less or equal error
and the second one is bad pool caller.

Ran the memtest and it says everything is good.

americancritic · Jul 24, 2011

Hello

These last 2 reports are the same they are as follows.

1. A probably caused by: ntkrpamp.exe

2. C2 - Nvlddmkm.sys

americancritic · Jul 24, 2011

Here is one of the lastest reports...

Code:

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

Loading Dump File (2ndreport).zip\Windows_NT6_BSOD_jcgriff2(2ndreport)\Mini072411-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
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18327.x86fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0x81e17000 PsLoadedModuleList = 0x81f2ec70
Debug session time: Sun Jul 24 09:15:24.260 2011 (GMT-7)
System Uptime: 0 days 22:58:38.299
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
[COLOR=blue]BugCheck A[/COLOR], {8059e004, 1b, 1, 81e5bcae}
[COLOR=red]Probably caused by : ntkrpamp.exe[/COLOR] ( nt!KiQueueReadyThread+40 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 8059e004, memory referenced
Arg2: 0000001b, IRQL
Arg3: 00000001, bitfield :
 bit 0 : value 0 = read operation, 1 = write operation
 bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 81e5bcae, address which referenced memory
Debugging Details:
------------------

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81f4e868
Unable to read MiSystemVaType memory at 81f2e420
 8059e004 
CURRENT_IRQL:  1b
FAULTING_IP: 
nt!KiQueueReadyThread+40
81e5bcae 894704          mov     dword ptr [edi+4],eax
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  plugin-containe
TRAP_FRAME:  ae426b9c -- (.trap 0xffffffffae426b9c)
ErrCode = 00000002
eax=854380a0 ebx=81f0f800 ecx=81f11328 edx=81f0f920 esi=00000009 edi=8059e000
eip=81e5bcae esp=ae426c10 ebp=ae426c3c iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
nt!KiQueueReadyThread+0x40:
81e5bcae 894704          mov     dword ptr [edi+4],eax ds:0023:8059e004=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from 81e5bcae to 81e64fd9
STACK_TEXT:  
ae426b9c 81e5bcae badb0d00 81f0f920 00000004 nt!KiTrap0E+0x2e1
ae426c14 81ebf3a2 ae426c3c 00000102 00000200 nt!KiQueueReadyThread+0x40
ae426c28 821d8468 00000000 00000000 00000206 nt!KiDispatchInterrupt+0xf2
ae426c3c 821d8668 00000002 00000000 821d86a8 hal!HalpDispatchSoftwareInterrupt+0x5e
ae426c58 821d870c 00000000 00000000 ae426cac hal!HalpCheckForSoftwareInterrupt+0x64
ae426c68 81ec339a 85438030 854380b8 81f0f920 hal!KfLowerIrql+0x64
ae426cac 81ec0a4e 85438030 00000000 0435fe78 nt!KiSwapThread+0x477
ae426d08 8204aeee 805d1001 00000000 ae426d2c nt!KeDelayExecutionThread+0x472
ae426d54 81e61c7a 00000000 0435feac 0435fed0 nt!NtDelayExecution+0x8d
ae426d54 77af5ca4 00000000 0435feac 0435fed0 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0435fed0 00000000 00000000 00000000 00000000 0x77af5ca4

STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!KiQueueReadyThread+40
81e5bcae 894704          mov     dword ptr [edi+4],eax
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt!KiQueueReadyThread+40
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4cb710d6
FAILURE_BUCKET_ID:  0xA_nt!KiQueueReadyThread+40
BUCKET_ID:  0xA_nt!KiQueueReadyThread+40
Followup: MachineOwner
---------

jugy3 · Jul 24, 2011

How would i go upon fixing this? :confused:

americancritic · Jul 24, 2011

Hello

Can you tell me if you have replaced the ram in your system within the last year, any new hardware at all, any new software etc.

When is the last time you ran a full Virus check and do you have malwarebytes installed...

Have you rerun the memtest yet....Very Important...

BSOD HELP (files included)

Attachments

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

Attachments

My Computer

My Computer

Attachments

My Computer

My Computer

My Computer

Attachments

My Computer

My Computer

Attachments

My Computer

My Computer

My Computer

My Computer

My Computer