Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD analysis - Help needed - Thanks in advance

14 Jan 2011   #1
renren

Windws 7 ultimate 64bit
 
 
BSOD analysis - Help needed - Thanks in advance

Windows 7 Ultimate x86
Original OS: XP Pro 32bit SP3
System: 2008-2009 parts (Just check my comp parts in my profile for more details)
OS age: 1 week

Notes: Been crashing a few days after the install - whocrashed notified me that its OS drivers that are crashing my PC. What can i do? Or is there another driver behind the crashing


My System SpecsSystem Spec
.
15 Jan 2011   #2
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Hi Renren. I looked at your six most recent dumps; the latest two are corrupted and contain no information. Start with turning Driver Veririfer off. Each of the four dumps is a Driver Verifier enabled dump and all four blame hardware.

I do find two out of date drivers on your system; one is way obsolete. Outdated drivers can and do cause conflicts and BSOD's.
Quote:
giveio.sys Wed Apr 03 22:33:25 1996 - ADC Analyzer/SwiftForth/Disspy - ?SpeedFan?. Info only ( way down page) - I/O Port Programming with Delphi and NT. Using Windows Explorer, navigate to C:\Windows\system 32. Look for giveio.sys and rename it from .sys to .old. Reboot and the driver will not load. This will break the program it is associated with.

Rt86win7.sys Thu Feb 26 04:04:22 2009 - Realtek NIC. Realtek. Update this driver through the link provided.
Turn Driver Verifier off, update Rt86win7.sys and rename giveio.sys. Reboot and let's see how your system does. Post back and let us know. If you get another BSOD after following these suggestions, upload it and we will go from there.
Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c3b000 PsLoadedModuleList = 0x82d83810
Debug session time: Fri Jan 14 22:01:19.582 2011 (GMT-5)
System Uptime: 0 days 0:10:52.894
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ddc776ca, 2, 8, ddc776ca}

Probably caused by : hardware

Followup: MachineOwner
---------
 *** Possible invalid call from 82f76555 ( nt!VerifierKeAcquireInStackQueuedSpinLock+0xa7 )
 *** Expected target 82c776ca ( nt!KeGetCurrentProcessorNumberEx+0x0 )

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: ddc776ca, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: ddc776ca, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82da3718
Unable to read MiSystemVaType memory at 82d83160
 ddc776ca 

CURRENT_IRQL:  2

FAULTING_IP: 
+52ea952f00e0ddac
ddc776ca ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  887c2c40 -- (.trap 0xffffffff887c2c40)
ErrCode = 00000010
eax=887c2d24 ebx=8553d320 ecx=82d708c4 edx=00000000 esi=82d708c4 edi=887c2d24
eip=ddc776ca esp=887c2cb4 ebp=887c2cd0 iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
ddc776ca ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82f7655a to ddc776ca

FAILED_INSTRUCTION_ADDRESS: 
+52ea952f00e0ddac
ddc776ca ??              ???

POSSIBLE_INVALID_CONTROL_TRANSFER:  from 82f76555 to 82c776ca

STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
887c2cb0 82f7655a 00000000 8fa37de0 000001ff 0xddc776ca
887c2cd0 82d5a903 00000000 82d7ac10 8fa7f338 nt!VerifierKeAcquireInStackQueuedSpinLock+0xac
887c2d30 82f745c0 8fa37de8 00000000 00000000 nt!ExFreePoolWithTag+0x8fd
887c2d50 82e496d3 82d7ac10 cbf83cc3 00000000 nt!ViPoolDelayFreeTrimThreadRoutine+0x35
887c2d90 82cfb0f9 82f7458b 82d7ac10 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .trap 0xffffffff887c2c40 ; kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CPU_CALL_ERROR

Followup: MachineOwner
---------
 *** Possible invalid call from 82f76555 ( nt!VerifierKeAcquireInStackQueuedSpinLock+0xa7 )
 *** Expected target 82c776ca ( nt!KeGetCurrentProcessorNumberEx+0x0 )

2: kd> lmtsmn
start    end        module name
9bcca000 9bcf6000   1394ohci 1394ohci.sys Mon Jul 13 19:51:59 2009 (4A5BC89F)
858a1000 858e9000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
95666000 956c0000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62)
9bd62000 9bd74000   AgileVpn AgileVpn.sys Mon Jul 13 19:55:00 2009 (4A5BC954)
859f2000 859fb000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
859c6000 859cf000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
859cf000 859f2000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
85c00000 85c07000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC)
95eb0000 95ebe000   blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8)
856b5000 856bd000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
99557000 99570000   bowser   bowser.sys   Mon Jul 13 19:14:21 2009 (4A5BBFCD)
a79e0000 a79fe000   cdd      cdd.dll      unavailable (00000000)
85ddd000 85dfc000   cdrom    cdrom.sys    Mon Jul 13 19:11:24 2009 (4A5BBF1C)
856ff000 857aa000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
85d86000 85dab000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
856bd000 856ff000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
85b9e000 85bfb000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
9bd55000 9bd62000   CompositeBus CompositeBus.sys Mon Jul 13 19:45:26 2009 (4A5BC716)
99400000 99409000   cpuz133_x32 cpuz133_x32.sys Tue Mar 30 17:38:01 2010 (4BB26F39)
827e1000 827ee000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
95e34000 95e98000   csc      csc.sys      Mon Jul 13 19:15:08 2009 (4A5BBFFC)
95e98000 95eb0000   dfsc     dfsc.sys     Mon Jul 13 19:14:16 2009 (4A5BBFC8)
957b8000 957c4000   discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214)
85e00000 85e11000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
82775000 8278e000   drmk     drmk.sys     Mon Jul 13 20:36:05 2009 (4A5BD2F5)
82400000 82409000   dump_atapi dump_atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
827ee000 827f9000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:11:16 2009 (4A5BBF14)
82409000 8241a000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
827be000 827c8000   Dxapi    Dxapi.sys    Mon Jul 13 19:25:25 2009 (4A5BC265)
95ef1000 95fa8000   dxgkrnl  dxgkrnl.sys  Mon Nov 01 22:37:53 2010 (4CCF7981)
95fa8000 95fe1000   dxgmms1  dxgmms1.sys  Mon Nov 01 22:37:04 2010 (4CCF7950)
9bcf6000 9bd01000   fdc      fdc.sys      Mon Jul 13 19:45:45 2009 (4A5BC729)
85800000 85811000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
9946f000 99479000   flpydisk flpydisk.sys Mon Jul 13 19:45:45 2009 (4A5BC729)
857aa000 857de000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
85a0e000 85a17000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
85d54000 85d86000   fvevol   fvevol.sys   Fri Sep 25 22:24:21 2009 (4ABD7B55)
85f61000 85f92000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
85ffc000 85ffc680   giveio   giveio.sys   Wed Apr 03 22:33:25 1996 (316334F5)
82c04000 82c3b000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
9bc86000 9bca5000   HDAudBus HDAudBus.sys Mon Jul 13 19:50:55 2009 (4A5BC85F)
994d2000 99557000   HTTP     HTTP.sys     Mon Jul 13 19:12:53 2009 (4A5BBF75)
85ff4000 85ffc000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
9bd23000 9bd3b000   i8042prt i8042prt.sys Mon Jul 13 19:11:23 2009 (4A5BBF1B)
95edf000 95ef1000   intelppm intelppm.sys Mon Jul 13 19:11:03 2009 (4A5BBF07)
9bd48000 9bd55000   kbdclass kbdclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
80ba9000 80bb1000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
95e00000 95e34000   ks       ks.sys       Wed Mar 03 22:57:52 2010 (4B8F2FC0)
85b8b000 85b9e000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
85d02000 85d27000   ksecpkg  ksecpkg.sys  Thu Dec 10 23:04:22 2009 (4B21C4C6)
82425000 82435000   lltdio   lltdio.sys   Mon Jul 13 19:53:18 2009 (4A5BC8EE)
9948a000 994a5000   luafv    luafv.sys    Mon Jul 13 19:15:44 2009 (4A5BC020)
8562c000 856a4000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:06:41 2009 (4A5BDA21)
8241a000 82425000   monitor  monitor.sys  Mon Jul 13 19:25:58 2009 (4A5BC286)
9bd3b000 9bd48000   mouclass mouclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
859b0000 859c6000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
85600000 85626680   MpFilter MpFilter.sys Tue Sep 14 17:23:59 2010 (4C8FE7EF)
99570000 99582000   mpsdrv   mpsdrv.sys   Mon Jul 13 19:52:52 2009 (4A5BC8D4)
99582000 995a5000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:32:02 2010 (4B88CA72)
995a5000 995e0000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:32:21 2010 (4B88CA85)
995e0000 995fb000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:32:11 2010 (4B88CA7B)
9562b000 95636000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E)
858f2000 858fa000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
85b60000 85b8b000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
957ae000 957b8000   mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
85fe4000 85ff4000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
85c0d000 85cc4000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
9bd8c000 9bd97000   ndistapi ndistapi.sys Mon Jul 13 19:54:24 2009 (4A5BC930)
9bd97000 9bdb9000   ndiswan  ndiswan.sys  Mon Jul 13 19:54:34 2009 (4A5BC93A)
99479000 9948a000   NDProxy  NDProxy.SYS  Mon Jul 13 19:54:27 2009 (4A5BC933)
95718000 95726000   netbios  netbios.sys  Mon Jul 13 19:53:54 2009 (4A5BC912)
956c0000 956f2000   netbt    netbt.sys    Mon Jul 13 19:12:18 2009 (4A5BBF52)
85cc4000 85d02000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
95636000 95644000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23)
957a4000 957ae000   nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48)
82c3b000 8304b000   nt       ntkrpamp.exe Fri Jun 18 23:55:24 2010 (4C1C3FAC)
85a31000 85b60000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
85e11000 85e18000   Null     Null.SYS     Mon Jul 13 19:11:12 2009 (4A5BBF10)
97bfc000 97bfd040   nvBridge nvBridge.kmd Tue Dec 21 18:21:05 2010 (4D113661)
97202000 97bfba00   nvlddmkm nvlddmkm.sys Tue Dec 21 18:29:24 2010 (4D113854)
956f9000 95718000   pacer    pacer.sys    Mon Jul 13 19:53:58 2009 (4A5BC916)
9bd0b000 9bd23000   parport  parport.sys  Mon Jul 13 19:45:34 2009 (4A5BC71E)
8592f000 85940000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
82435000 8243c000   parvdm   parvdm.sys   Mon Jul 13 19:45:29 2009 (4A5BC719)
858fa000 85924000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
8599b000 859a2000   pciide   pciide.sys   Mon Jul 13 19:11:19 2009 (4A5BBF17)
859a2000 859b0000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
85a00000 85a0e000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
bac11000 baca8000   peauth   peauth.sys   Mon Jul 13 20:35:44 2009 (4A5BD2E0)
82746000 82775000   portcls  portcls.sys  Mon Jul 13 19:51:00 2009 (4A5BC864)
856a4000 856b5000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
9bd74000 9bd8c000   rasl2tp  rasl2tp.sys  Mon Jul 13 19:54:33 2009 (4A5BC939)
9bdb9000 9bdd1000   raspppoe raspppoe.sys Mon Jul 13 19:54:53 2009 (4A5BC94D)
9bdd1000 9bde8000   raspptp  raspptp.sys  Mon Jul 13 19:54:47 2009 (4A5BC947)
9bde8000 9bdff000   rassstp  rassstp.sys  Mon Jul 13 19:54:57 2009 (4A5BC951)
95763000 957a4000   rdbss    rdbss.sys    Mon Jul 13 19:14:26 2009 (4A5BBFD2)
9bc00000 9bc0a000   rdpbus   rdpbus.sys   Mon Jul 13 20:02:40 2009 (4A5BCB20)
85811000 85819000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4)
85819000 85821000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3)
95623000 9562b000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5)
85d27000 85d54000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
994bf000 994d2000   rspndr   rspndr.sys   Mon Jul 13 19:53:20 2009 (4A5BC8F0)
9bca5000 9bcca000   Rt86win7 Rt86win7.sys Thu Feb 26 04:04:22 2009 (49A65B16)
8243d000 82745180   RTKVHDA  RTKVHDA.sys  Fri Sep 03 04:00:20 2010 (4C80AB14)
baca8000 bacb2000   secdrv   secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528)
9bd01000 9bd0b000   serenum  serenum.sys  Mon Jul 13 19:45:27 2009 (4A5BC717)
95726000 95740000   serial   serial.sys   Mon Jul 13 19:45:33 2009 (4A5BC71D)
85fe2000 85fe3480   speedfan speedfan.sys Sun Sep 24 09:28:47 2006 (4516880F)
85fda000 85fe2000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
bad2f000 bad80000   srv      srv.sys      Thu Aug 26 23:31:26 2010 (4C77318E)
bace0000 bad2f000   srv2     srv2.sys     Thu Aug 26 23:30:45 2010 (4C773165)
bacb2000 bacd3000   srvnet   srvnet.sys   Thu Aug 26 23:30:39 2010 (4C77315F)
9bc0a000 9bc0b380   swenum   swenum.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
85e18000 85f61000   tcpip    tcpip.sys    Sun Jun 13 23:36:59 2010 (4C15A3DB)
bacd3000 bace0000   tcpipreg tcpipreg.sys Mon Jul 13 19:54:14 2009 (4A5BC926)
9565b000 95666000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C)
95644000 9565b000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A)
95753000 95763000   termdd   termdd.sys   Mon Jul 13 20:01:35 2009 (4A5BCADF)
a79b0000 a79b9000   TSDDD    TSDDD.dll    unavailable (00000000)
95ebe000 95edf000   tunnel   tunnel.sys   Mon Jul 13 19:54:03 2009 (4A5BC91B)
9bc0c000 9bc1a000   umbus    umbus.sys    Mon Jul 13 19:51:38 2009 (4A5BC88A)
8278e000 827a5000   usbccgp  usbccgp.sys  Mon Jul 13 19:51:31 2009 (4A5BC883)
827a5000 827a6700   USBD     USBD.SYS     Mon Jul 13 19:51:05 2009 (4A5BC869)
9bc77000 9bc86000   usbehci  usbehci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872)
9942b000 9946f000   usbhub   usbhub.sys   Mon Jul 13 19:52:06 2009 (4A5BC8A6)
9bc2c000 9bc77000   USBPORT  USBPORT.SYS  Mon Jul 13 19:51:13 2009 (4A5BC871)
827c8000 827d3000   usbprint usbprint.sys Mon Jul 13 20:17:06 2009 (4A5BCE82)
827d3000 827e1000   usbscan  usbscan.sys  Mon Jul 13 20:14:44 2009 (4A5BCDF4)
827a7000 827be000   USBSTOR  USBSTOR.SYS  Mon Jul 13 19:51:19 2009 (4A5BC877)
95fe1000 95fec000   usbuhci  usbuhci.sys  Mon Jul 13 19:51:10 2009 (4A5BC86E)
85924000 8592f000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
85a17000 85a23000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E)
857de000 857ff000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D)
85f92000 85f9a380   vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C)
85940000 85950000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
85950000 8599b000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
85f9b000 85fda000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
95740000 95753000   wanarp   wanarp.sys   Mon Jul 13 19:55:02 2009 (4A5BC956)
85a23000 85a30000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A)
85822000 85893000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
85893000 858a1000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
956f2000 956f9000   wfplwf   wfplwf.sys   Mon Jul 13 19:53:51 2009 (4A5BC90F)
a7750000 a799b000   win32k   win32k.sys   unavailable (00000000)
858e9000 858f2000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)
994a5000 994bf000   WudfPf   WudfPf.sys   Mon Jul 13 19:50:13 2009 (4A5BC835)
bad80000 bada0480   WUDFRd   WUDFRd.sys   Mon Jul 13 19:50:44 2009 (4A5BC854)

Unloaded modules:
c4428000 c4492000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
85dab000 85db8000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
85db8000 85dc3000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
85dc3000 85dcc000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
85dcc000 85ddd000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
My System SpecsSystem Spec
15 Jan 2011   #3
renren

Windws 7 ultimate 64bit
 
 

Dear carl,

Thanks for the reply i got worried that my case wouldve been buried in everyone elses BSOD posts.

To the point, Driver verifier is now off, giveio.sys is now a .old extension and the NIC driver is now updated. I will get back to you after i collect a couple more BSOD dumps and i will compile it via jcgriff exe.

Thanks for your help so far <3.
My System SpecsSystem Spec
.

16 Jan 2011   #4
renren

Windws 7 ultimate 64bit
 
 

I had a BSOD about 3 times or so. I hope its enough to make out a reason why.

I also did a memtest on my sticks. It came out negative.
My System SpecsSystem Spec
16 Jan 2011   #5
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Quote   Quote: Originally Posted by renren View Post
Dear carl,

Thanks for the reply i got worried that my case wouldve been buried in everyone elses BSOD posts.

To the point, Driver verifier is now off, giveio.sys is now a .old extension and the NIC driver is now updated. I will get back to you after i collect a couple more BSOD dumps and i will compile it via jcgriff exe.

Thanks for your help so far <3.
You are welcome for the help. Sometimes, it get busy and it takes us a while to get to a new thread. Good job of taking care of giveo.sys and updating Rt86win7.sys. All of your drivers look up to date.

Quote   Quote: Originally Posted by renren View Post
I had a BSOD about 3 times or so. I hope its enough to make out a reason why.

I also did a memtest on my sticks. It came out negative.
Tell me about Memtest; how many passes did you let it make? Did you run it from a cold boot? I ask because I suspect a hardware problem.

Both dumps are bugcheck 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.

One dump blames ntkrpamp.exe, a Windows system core file, and indicates memory corruption. The other dump blames hardware and indicates a bad CPU call.

I recommend that you stop overclocking your CPU and return to default values. If you are over clocking RAM or your GPU, return those to default values also.
Quote:
Processor may be overclocked!
Expected Frequency: 2660
Actual Frequency: 3200
Overclock Ratio: 1.20
If you have not already done so, please run Memtest86 from a cold boot after your computer has been off for an hour or two. Let it run for a minimum of 7 passes. This will take 6-8 hours. If you see any errors, you can stop the test. Post back with your results. RAM - Test with Memtest86+


If and only if you get no errors with Memtest, test your RAM and your CPU with Prime95 closely following the instructions in this tutorial: https://www.sevenforums.com/tutorials...t-prime95.html. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with the results.

Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c45000 PsLoadedModuleList = 0x82d8d810
Debug session time: Sun Jan 16 05:11:32.560 2011 (GMT-5)
System Uptime: 0 days 1:45:47.230
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 82e7cb4b, a19a6958, 0}

Probably caused by : ntkrpamp.exe ( nt!CmpParseCacheLookup+24 )

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

1: 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: 82e7cb4b, The address that the exception occurred at
Arg3: a19a6958, 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!CmpParseCacheLookup+24
82e7cb4b 8b7304          mov     esi,dword ptr [ebx+4]

TRAP_FRAME:  a19a6958 -- (.trap 0xffffffffa19a6958)
ErrCode = 00000000
eax=82771f08 ebx=00000000 ecx=00000000 edx=00000001 esi=c0000034 edi=00000000
eip=82e7cb4b esp=a19a69cc ebp=a19a6b48 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!CmpParseCacheLookup+0x24:
82e7cb4b 8b7304          mov     esi,dword ptr [ebx+4] ds:0023:00000004=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  sidebar.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82e6626b to 82e7cb4b

STACK_TEXT:  
a19a6b48 82e6626b 8c00ad50 85476980 889c1d20 nt!CmpParseCacheLookup+0x24
a19a6bc4 82e8c2d9 00000000 a19a6c18 00000040 nt!ObpLookupObjectName+0x4fa
a19a6c20 82e83a24 020ae060 85476980 ffffff01 nt!ObOpenObjectByName+0x165
a19a6d00 82e7e777 020ae5c4 00000001 020ae060 nt!CmOpenKey+0x1f4
a19a6d1c 82c8844a 020ae5c4 00000001 020ae060 nt!NtOpenKeyEx+0x18
a19a6d1c 771264f4 020ae5c4 00000001 020ae060 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
020ae294 00000000 00000000 00000000 00000000 0x771264f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!CmpParseCacheLookup+24
82e7cb4b 8b7304          mov     esi,dword ptr [ebx+4]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!CmpParseCacheLookup+24

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

FAILURE_BUCKET_ID:  0x8E_nt!CmpParseCacheLookup+24

BUCKET_ID:  0x8E_nt!CmpParseCacheLookup+24

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

Debug session time: Sun Jan 16 05:16:07.596 2011 (GMT-5)
System Uptime: 0 days 0:00:19.266
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 62e20bfe, 9e3f99ec, 0}

Probably caused by : hardware

Followup: MachineOwner
---------
 *** Possible invalid call from 82e2feda ( nt!ObCheckObjectAccess+0x62 )
 *** Expected target 82e20bfe ( nt!SeLockSubjectContext+0x0 )

1: 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: 62e20bfe, The address that the exception occurred at
Arg3: 9e3f99ec, 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: 
+5e62952f017fdd60
62e20bfe ??              ???

TRAP_FRAME:  9e3f99ec -- (.trap 0xffffffff9e3f99ec)
ErrCode = 00000010
eax=00000000 ebx=85349b98 ecx=00000004 edx=9128c018 esi=9e3f9b48 edi=9e3f9b64
eip=62e20bfe esp=9e3f9a60 ebp=9e3f9a84 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
62e20bfe ??              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82e2fedf to 62e20bfe

POSSIBLE_INVALID_CONTROL_TRANSFER:  from 82e2feda to 82e20bfe

STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
9e3f9a5c 82e2fedf 9e3f9b64 9e3f9b48 9e3f9cec 0x62e20bfe
9e3f9a84 82e2fe6a 91200598 9e3f9b48 00000001 nt!ObCheckObjectAccess+0x67
9e3f9aa8 82e227ac 00000001 9e3f9b01 00000000 nt!ObpGrantAccess+0x5f
9e3f9b08 82e7b06e 00000001 91200598 00000000 nt!ObpCreateHandle+0x8b
9e3f9c88 82e7b0d3 91200598 00000000 00000000 nt!ObOpenObjectByPointerWithTag+0xc1
9e3f9cb0 82e3c172 91200598 00000000 00000000 nt!ObOpenObjectByPointer+0x24
9e3f9d1c 82c4344a ffffffff 00000008 00000000 nt!NtOpenProcessTokenEx+0xb4
9e3f9d1c 772b64f4 ffffffff 00000008 00000000 nt!KiFastCallEntry+0x12a
001cec40 00000000 00000000 00000000 00000000 0x772b64f4


STACK_COMMAND:  .trap 0xffffffff9e3f99ec ; kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CPU_CALL_ERROR

Followup: MachineOwner
---------
 *** Possible invalid call from 82e2feda ( nt!ObCheckObjectAccess+0x62 )
 *** Expected target 82e20bfe ( nt!SeLockSubjectContext+0x0 )
My System SpecsSystem Spec
16 Jan 2011   #6
renren

Windws 7 ultimate 64bit
 
 

Insufficient disk space, i got plenty of room in the HDD
Device driver,
Video card, not OCed
BIOS, Shall i update my bios?
, Breakpoint in startup without having a debugger attached
, Hardware incompatibility
, Faulty system service i also ran sfc /scannow twice and it came out clear
, 3rd party remote control
, Memory. i ran the windows version of memtest and ran it under extended for 2 passes. Should i do a memtest using your link? ill do a cold boot one after i run prime95 for a while.

Thanks for your help so far ill get back to you once i finish testing
My System SpecsSystem Spec
16 Jan 2011   #7
CarlTR6

Windows 7 Ultimate 32 bit
 
 

YOu are very welcome for the help. Those above are the usual causes. They may or may not apply. Stop your overclocking until you get your system stable. You need to eliminate that possible cause of crashes.
My System SpecsSystem Spec
Reply

 BSOD analysis - Help needed - Thanks in advance




Thread Tools




Similar help and support threads
Thread Forum
BSOD Analysis Needed
Hey, title says it all. Was gone for about a week, when I came home, my computer ran for about 2-3 hours and then the blue screens started. Have been getting them upon reboot and within 5-10 min of reboot. Here is my analysis... ...
BSOD Help and Support
Win7 startup delay... xperfview analysis needed.
Several weeks ago, my startup time went from about 30 seconds to about 3 minutes. Can't remember any specific event. LOOOONG black screen after Win7 login, with only the pointer on screen, for at least 90-120 seconds. Clearly, the attached xperfview shows a lot of nothing from about 38 seconds...
Performance & Maintenance
BSOD analysis needed 0x0000003d
Hi All, i keep getting this random BSOD, your help analyzing what's wrong will be greatly appreciated! thanks! My Spec - Ultimate x64 - self built system - What is the age of system (hardware). 9 month old
BSOD Help and Support
BSOD Analysis
Windows 7 is - x86 (32-bit) - not original installation, it is windows 7 ultimate - full retail version - Not sure age of software bought comp last year January - OS installation just recently to clean it up. need all the help i can get wasnt going to worry about it but its getting on...
BSOD Help and Support
Another BSOD Dump file analysis needed please
Hey guys I just got a BSOD and was wondering if anyone could tell me the cause thanks in advance if anyone knows a good dump analysis program could you also give me a link .
BSOD Help and Support
Crash Dump Analysis Needed
Hi guys, can you please help me on finding a solution for the BSOD i received several times a day? The BSOD appears while i try to shutdown or restart windows. By the way i am using ultimate edition of windows 7. thanks in advance.
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 04:58.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App