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: Help BSOD

25 Oct 2010   #1
IhateBSOD

Windows 7 Home Premium 32bit.
 
 
Help BSOD

Having a problem with my pc. I keep getting the blue screen of death. Windows 7 32bit Retail Version computer is 2 years old aprox I just installed Windows 7. It had the same problems with Windows Vista. Mostly happens running Windows explorer/ Firefox and windows media player. Can be have lots of windows open or just one or two and it happens.

I hope one of you can shed some light on this.


My System SpecsSystem Spec
.
25 Oct 2010   #2
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Hi, IhateBSOD (me, too); and welcome to the forum. Your dumps indicate hardware or hardware related problems.
Quote:
Error code 19, BAD_POOL_HEADER. Usual causes: Device driver

Error code 24, NTFS_FILE_SYSTEM. Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

Error code 1A (2X), MEMORY_MANAGEMENT. Usual causes: Device driver, memory, kernel
Code:
Windows 7 Kernel Version 7600 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82847000 PsLoadedModuleList = 0x8298f810
Debug session time: Mon Oct 25 08:48:37.745 2010 (GMT-4)
System Uptime: 0 days 2:20:51.571
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
.......
kd> !Analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, 85253488, 95253488, 85253488}

Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetInfo+109 )

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

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000003, the pool freelist is corrupt.
Arg2: 85253488, the pool entry being checked.
Arg3: 95253488, the read back flink freelist value (should be the same as 2).
Arg4: 85253488, the read back blink freelist value (should be the same as 2).

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


BUGCHECK_STR:  0x19_3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82fe1e7e to 82967232

STACK_TEXT:  
a54a381c 82fe1e7e 00000001 00000400 6e664d46 nt!ExAllocatePoolWithTag+0x682
a54a3850 82fe2df4 00720df8 00000000 85720df8 fltmgr!FltpExpandShortNames+0x100
a54a386c 82fe3505 85720000 00000000 868f84e4 fltmgr!FltpGetNormalizedFileNameWorker+0xae
a54a3884 82fe0765 85720df8 00000000 85720df8 fltmgr!FltpGetNormalizedFileName+0x19
a54a389c 82fcab21 85720df8 00000000 00000000 fltmgr!FltpCreateFileNameInformation+0x81
a54a38cc 82fcafa3 8554210c 00000000 a54a3964 fltmgr!FltpGetFileNameInformation+0x321
a54a38f4 8bde9c87 003d0258 00000401 a54a3928 fltmgr!FltGetFileNameInformation+0x12b
a54a3944 8bde9edd 853d0258 a54a3964 00036ddf fileinfo!FIStreamGetInfo+0x109
a54a3980 82fc4324 853d0258 a54a39a4 50f2e5b7 fileinfo!FIPostCreateCallback+0x171
a54a39e8 82fc7512 003d01f8 853d01f8 1000000c fltmgr!FltpPerformPostCallbacks+0x24a
a54a39fc 82fc7b46 853d01f8 85f2c5d0 a54a3a3c fltmgr!FltpProcessIoCompletion+0x10
a54a3a0c 82fc829c 86187cd0 85f2c5d0 853d01f8 fltmgr!FltpPassThroughCompletion+0x98
a54a3a3c 82fdb8c9 a54a3a5c 00000000 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x33a
a54a3a88 828834bc 86187cd0 8618a3e0 85f1e854 fltmgr!FltpCreate+0x2db
a54a3aa0 82a8762d 8e3c6a3b a54a3c48 00000000 nt!IofCallDriver+0x63
a54a3b78 82a681d7 852c08c0 852daf78 8574f008 nt!IopParseDevice+0xed7
a54a3bf4 82a8e24d 00000000 a54a3c48 00000040 nt!ObpLookupObjectName+0x4fa
a54a3c50 82a865ab 069be81c 852daf78 00000001 nt!ObOpenObjectByName+0x159
a54a3ccc 82ac15ee 069be868 00100001 069be81c nt!IopCreateFile+0x673
a54a3d14 8288a42a 069be868 00100001 069be81c nt!NtOpenFile+0x2a
a54a3d14 76fc64f4 069be868 00100001 069be81c nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
069beae8 00000000 00000000 00000000 00000000 0x76fc64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
fileinfo!FIStreamGetInfo+109
8bde9c87 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  fileinfo!FIStreamGetInfo+109

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fileinfo

IMAGE_NAME:  fileinfo.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc18f

FAILURE_BUCKET_ID:  0x19_3_fileinfo!FIStreamGetInfo+109

BUCKET_ID:  0x19_3_fileinfo!FIStreamGetInfo+109

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

kd> lmtsmn
start    end        module name
8bc1c000 8bc64000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
9085e000 908b8000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62)
90f20000 90f32000   AgileVpn AgileVpn.sys Mon Jul 13 19:55:00 2009 (4A5BC954)
909e9000 909fb000   amdk8    amdk8.sys    Mon Jul 13 19:11:03 2009 (4A5BBF07)
8bdd9000 8bde2000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
8bd41000 8bd4a000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
8bd4a000 8bd6d000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
8be30000 8be37000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC)
909ba000 909c8000   blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8)
82e4e000 82e56000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
8d383000 8d39c000   bowser   bowser.sys   Mon Jul 13 19:14:21 2009 (4A5BBFCD)
92ad0000 92aee000   cdd      cdd.dll      unavailable (00000000)
8be11000 8be30000   cdrom    cdrom.sys    Mon Jul 13 19:11:24 2009 (4A5BBF1C)
82e98000 82f43000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
8bfa7000 8bfcc000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
82e56000 82e98000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
8c017000 8c074000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
90f13000 90f20000   CompositeBus CompositeBus.sys Mon Jul 13 19:45:26 2009 (4A5BC716)
8d259000 8d266000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
909a2000 909ba000   dfsc     dfsc.sys     Mon Jul 13 19:14:16 2009 (4A5BBFC8)
90996000 909a2000   discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214)
8c1df000 8c1f0000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
90e00000 90e19000   drmk     drmk.sys     Mon Jul 13 20:36:05 2009 (4A5BD2F5)
8d266000 8d270000   dump_diskdump dump_diskdump.sys Mon Jul 13 19:45:49 2009 (4A5BC72D)
8d295000 8d2a6000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
8d270000 8d295000   dump_nvstor dump_nvstor.sys Wed May 20 02:44:09 2009 (4A13A6B9)
8d244000 8d24e000   Dxapi    Dxapi.sys    Mon Jul 13 19:25:25 2009 (4A5BC265)
90e23000 90eda000   dxgkrnl  dxgkrnl.sys  Mon Jul 13 19:26:15 2009 (4A5BC297)
90eda000 90f13000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:25:25 2009 (4A5BC265)
8d21a000 8d244000   fastfat  fastfat.SYS  Mon Jul 13 19:14:01 2009 (4A5BBFB9)
8bde2000 8bdf3000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
82fc2000 82ff6000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
8c082000 8c08b000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
8c1ad000 8c1df000   fvevol   fvevol.sys   Mon Jul 13 19:13:01 2009 (4A5BBF7D)
8c34b000 8c37c000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
82810000 82847000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
90ce5000 90d04000   HDAudBus HDAudBus.sys Mon Jul 13 19:50:55 2009 (4A5BC85F)
91daf000 91dff000   HdAudio  HdAudio.sys  Mon Jul 13 19:51:46 2009 (4A5BC892)
90daa000 90dbd000   HIDCLASS HIDCLASS.SYS Mon Jul 13 19:51:01 2009 (4A5BC865)
90e1b000 90e21480   HIDPARSE HIDPARSE.SYS Mon Jul 13 19:50:59 2009 (4A5BC863)
90d9f000 90daa000   hidusb   hidusb.sys   Mon Jul 13 19:51:04 2009 (4A5BC868)
8d2fe000 8d383000   HTTP     HTTP.sys     Mon Jul 13 19:12:53 2009 (4A5BBF75)
8c1a5000 8c1ad000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
90fbd000 90fca000   kbdclass kbdclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
90dbd000 90dc9000   kbdhid   kbdhid.sys   Mon Jul 13 19:45:09 2009 (4A5BC705)
80bbc000 80bc4000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
90ac8000 90afc000   ks       ks.sys       Mon Jul 13 19:45:13 2009 (4A5BC709)
8bf94000 8bfa7000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
8c180000 8c1a5000   ksecpkg  ksecpkg.sys  Mon Jul 13 19:34:00 2009 (4A5BC468)
8d2db000 8d2eb000   lltdio   lltdio.sys   Mon Jul 13 19:53:18 2009 (4A5BC8EE)
8d2a6000 8d2c1000   luafv    luafv.sys    Mon Jul 13 19:15:44 2009 (4A5BC020)
82e32000 82e3d000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 19:13:13 2009 (4A5BBF89)
90cd8000 90ce5000   modem    modem.sys    Mon Jul 13 19:55:24 2009 (4A5BC96C)
8d24e000 8d259000   monitor  monitor.sys  Mon Jul 13 19:25:58 2009 (4A5BC286)
90fca000 90fd7000   mouclass mouclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
90de0000 90deb000   mouhid   mouhid.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
8bd2b000 8bd41000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
8d39c000 8d3ae000   mpsdrv   mpsdrv.sys   Mon Jul 13 19:52:52 2009 (4A5BC8D4)
8d3ae000 8d3d1000   mrxsmb   mrxsmb.sys   Mon Jul 13 19:14:24 2009 (4A5BBFD0)
99e18000 99e53000   mrxsmb10 mrxsmb10.sys Mon Jul 13 19:14:34 2009 (4A5BBFDA)
99e53000 99e6e000   mrxsmb20 mrxsmb20.sys Mon Jul 13 19:14:29 2009 (4A5BBFD5)
82e21000 82e2c000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E)
8bc6d000 8bc75000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
8bf69000 8bf94000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
9098c000 90996000   mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
8c3f0000 8c400000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
8c08b000 8c142000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
90f4a000 90f55000   ndistapi ndistapi.sys Mon Jul 13 19:54:24 2009 (4A5BC930)
90f55000 90f77000   ndiswan  ndiswan.sys  Mon Jul 13 19:54:34 2009 (4A5BC93A)
90fe7000 90ff8000   NDProxy  NDProxy.SYS  Mon Jul 13 19:54:27 2009 (4A5BC933)
90910000 9091e000   netbios  netbios.sys  Mon Jul 13 19:53:54 2009 (4A5BC912)
908b8000 908ea000   netbt    netbt.sys    Mon Jul 13 19:12:18 2009 (4A5BBF52)
8c142000 8c180000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
9082e000 9083c000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23)
90982000 9098c000   nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48)
82847000 82c57000   nt       ntkrpamp.exe Mon Jul 13 19:15:19 2009 (4A5BC007)
8be3a000 8bf69000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
8c00a000 8c011000   Null     Null.SYS     Mon Jul 13 19:11:12 2009 (4A5BBF10)
91405000 91d6a940   nvlddmkm nvlddmkm.sys Thu May 14 16:32:27 2009 (4A0C7FDB)
90d04000 90d58c80   nvm62x32 nvm62x32.sys Fri Oct 17 17:00:39 2008 (48F8FCF7)
8bd6d000 8bd92000   nvstor   nvstor.sys   Wed May 20 02:44:09 2009 (4A13A6B9)
908f1000 90910000   pacer    pacer.sys    Mon Jul 13 19:53:58 2009 (4A5BC916)
8bcaa000 8bcbb000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
8bc75000 8bc9f000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
8bd16000 8bd1d000   pciide   pciide.sys   Mon Jul 13 19:11:19 2009 (4A5BBF17)
8bd1d000 8bd2b000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
8c074000 8c082000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
99e86000 99f1d000   peauth   peauth.sys   Mon Jul 13 20:35:44 2009 (4A5BD2E0)
90d59000 90d88000   portcls  portcls.sys  Mon Jul 13 19:51:00 2009 (4A5BC864)
82e3d000 82e4e000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
90f32000 90f4a000   rasl2tp  rasl2tp.sys  Mon Jul 13 19:54:33 2009 (4A5BC939)
90f77000 90f8f000   raspppoe raspppoe.sys Mon Jul 13 19:54:53 2009 (4A5BC94D)
90f8f000 90fa6000   raspptp  raspptp.sys  Mon Jul 13 19:54:47 2009 (4A5BC947)
90fa6000 90fbd000   rassstp  rassstp.sys  Mon Jul 13 19:54:57 2009 (4A5BC951)
90941000 90982000   rdbss    rdbss.sys    Mon Jul 13 19:14:26 2009 (4A5BBFD2)
8bc00000 8bc08000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4)
8bc08000 8bc10000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3)
8bc10000 8bc18000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5)
8c3c3000 8c3f0000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
8d2eb000 8d2fe000   rspndr   rspndr.sys   Mon Jul 13 19:53:20 2009 (4A5BC8F0)
99f1d000 99f27000   secdrv   secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528)
8c3bb000 8c3c3000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
99fa4000 99ff5000   srv      srv.sys      Mon Jul 13 19:15:10 2009 (4A5BBFFE)
99f55000 99fa4000   srv2     srv2.sys     Mon Jul 13 19:14:52 2009 (4A5BBFEC)
99f27000 99f48000   srvnet   srvnet.sys   Mon Jul 13 19:14:45 2009 (4A5BBFE5)
8bd92000 8bdd9000   storport storport.sys Mon Jul 13 19:45:58 2009 (4A5BC736)
90fd7000 90fd8380   swenum   swenum.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
8c202000 8c34b000   tcpip    tcpip.sys    Mon Jul 13 19:13:18 2009 (4A5BBF8E)
99f48000 99f55000   tcpipreg tcpipreg.sys Mon Jul 13 19:54:14 2009 (4A5BC926)
90853000 9085e000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C)
9083c000 90853000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A)
90931000 90941000   termdd   termdd.sys   Mon Jul 13 20:01:35 2009 (4A5BCADF)
92aa0000 92aa9000   TSDDD    TSDDD.dll    Mon Jul 13 20:01:40 2009 (4A5BCAE4)
909c8000 909e9000   tunnel   tunnel.sys   Mon Jul 13 19:54:03 2009 (4A5BC91B)
90fd9000 90fe7000   umbus    umbus.sys    Mon Jul 13 19:51:38 2009 (4A5BC88A)
90d88000 90d9f000   usbccgp  usbccgp.sys  Mon Jul 13 19:51:31 2009 (4A5BC883)
90e19000 90e1a700   USBD     USBD.SYS     Mon Jul 13 19:51:05 2009 (4A5BC869)
90a6d000 90a7c000   usbehci  usbehci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872)
91d6b000 91daf000   usbhub   usbhub.sys   Mon Jul 13 19:52:06 2009 (4A5BC8A6)
90800000 9080a000   usbohci  usbohci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872)
90a22000 90a6d000   USBPORT  USBPORT.SYS  Mon Jul 13 19:51:13 2009 (4A5BC871)
90dc9000 90de0000   USBSTOR  USBSTOR.SYS  Mon Jul 13 19:51:19 2009 (4A5BC877)
8bc9f000 8bcaa000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
8bff1000 8bffd000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E)
82e00000 82e21000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D)
8bcbb000 8bccb000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8bccb000 8bd16000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
8c37c000 8c3bb000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
90a7c000 90ac8000   VSTBS23  VSTBS23.SYS  Wed Oct 15 20:30:15 2008 (48F68B17)
90c23000 90cd8000   VSTCNXT3 VSTCNXT3.SYS Wed Oct 15 20:29:13 2008 (48F68AD9)
90afc000 90bfe000   VSTDPV3  VSTDPV3.SYS  Wed Oct 15 20:32:04 2008 (48F68B84)
9091e000 90931000   wanarp   wanarp.sys   Mon Jul 13 19:55:02 2009 (4A5BC956)
8bdf3000 8be00000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A)
82f43000 82fb4000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
82fb4000 82fc2000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
908ea000 908f1000   wfplwf   wfplwf.sys   Mon Jul 13 19:53:51 2009 (4A5BC90F)
92840000 92a8a000   win32k   win32k.sys   Mon Jul 13 19:26:26 2009 (4A5BC2A2)
8bc64000 8bc6d000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)
8d2c1000 8d2db000   WudfPf   WudfPf.sys   Mon Jul 13 19:50:13 2009 (4A5BC835)
8d3d1000 8d3f1480   WUDFRd   WUDFRd.sys   Mon Jul 13 19:50:44 2009 (4A5BC854)

Unloaded modules:
a1601000 a166b000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
9e23b000 9e2a5000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
99e6e000 99e86000   parport.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8c1f0000 8c1fd000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8c000000 8c00a000   dump_storpor
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8bfcc000 8bff1000   dump_nvstor.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8be00000 8be11000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

Kernel base = 0x82837000 PsLoadedModuleList = 0x8297f810
Debug session time: Mon Oct 25 09:07:51.961 2010 (GMT-4)
System Uptime: 0 days 0:01:52.787
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
.....
kd> !Analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {c08a2, 0, 0, 0}

Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+138 )

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

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

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

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x24

PROCESS_NAME:  plugin-contain

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8be2697c to 82913d10

STACK_TEXT:  
9e043a58 8be2697c 00000024 000c08a2 00000000 nt!KeBugCheckEx+0x1e
9e043b14 8be259e1 00001000 869f7168 15e08113 Ntfs!NtfsPagingFileIo+0x138
9e043b84 828734bc 86198020 85397e00 85397e00 Ntfs!NtfsFsdRead+0xac
9e043b9c 8bd9e20c 861785b0 85397e00 00000000 nt!IofCallDriver+0x63
9e043bc0 8bd9e3cb 9e043be0 861785b0 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa
9e043bf8 828734bc 861785b0 85397e00 85397e00 fltmgr!FltpDispatch+0xc5
9e043c10 828dc000 86501038 85369410 86501008 nt!IofCallDriver+0x63
9e043c2c 828e2fad 86a076a0 85369410 86501040 nt!IoPageRead+0x1f5
9e043c94 828bf428 85354918 06005010 86501009 nt!MiIssueHardFault+0x28c
9e043d1c 8287d5f8 00000001 06005010 00000001 nt!MmAccessFault+0x2c3a
9e043d1c 6adc11eb 00000001 06005010 00000001 nt!KiTrap0E+0xdc
WARNING: Frame IP not in any known module. Following frames may be wrong.
6afe2da8 00000000 00000000 00000000 00000000 0x6adc11eb


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Ntfs!NtfsPagingFileIo+138
8be2697c 0fbe8720010000  movsx   eax,byte ptr [edi+120h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  Ntfs!NtfsPagingFileIo+138

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf45

FAILURE_BUCKET_ID:  0x24_Ntfs!NtfsPagingFileIo+138

BUCKET_ID:  0x24_Ntfs!NtfsPagingFileIo+138

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

Kernel base = 0x82845000 PsLoadedModuleList = 0x8298d810
Debug session time: Mon Oct 25 05:18:20.489 2010 (GMT-4)
System Uptime: 0 days 0:13:29.315
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
......
kd> !Analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, c0802110, ffff, 0}

Probably caused by : win32k.sys ( win32k!SURFACE::Map+ae )

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

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

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

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 828f83fe to 828feb1d

STACK_TEXT:  
9b2ec9e0 828f83fe 0c200002 0c8a3fff 8622f310 nt!MiDeleteVirtualAddresses+0x41a
9b2ecab0 828ec708 8622f310 872cb0c8 8726c030 nt!MiRemoveMappedView+0x325
9b2ecad8 82abf4c8 8726c030 00000000 00000000 nt!MiRemoveVadAndView+0xe5
9b2ecb3c 82ac2da2 8622f310 0c200000 00000000 nt!MiUnmapViewOfSection+0x265
9b2ecb50 9558ccc9 8622f310 0c200000 fe71a248 nt!MmUnmapViewOfSection+0x12
9b2ecb78 9558ce95 9b2ecbe4 fe7401d0 9b2ecbf4 win32k!SURFACE::Map+0xae
9b2ecb98 9558d53c fe528008 9b2ecbe4 9b2ecce8 win32k!DEVLOCKOBJ::bMapTrgSurfaceView+0x30
9b2ecbac 9558c95d 9b2ecce8 01900010 9b2ecce8 win32k!DEVLOCKOBJ::bPrepareTrgDco+0x79
9b2ecbc4 9559124b ffb8f748 00000001 0e43ad42 win32k!DEVLOCKOBJ::bLock+0x332
9b2ecc54 95591594 9b2ecce8 0000f0f0 00dbf218 win32k!GrePolyPatBltInternal+0x91
9b2ecd18 8288842a 29010803 00f00021 00dbf218 win32k!NtGdiPolyPatBlt+0x1bc
9b2ecd18 772764f4 29010803 00f00021 00dbf218 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
00dbf1f4 00000000 00000000 00000000 00000000 0x772764f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!SURFACE::Map+ae
9558ccc9 8b464c          mov     eax,dword ptr [esi+4Ch]

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  win32k!SURFACE::Map+ae

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc2a2

FAILURE_BUCKET_ID:  0x1a_41790_win32k!SURFACE::Map+ae

BUCKET_ID:  0x1a_41790_win32k!SURFACE::Map+ae

Followup: MachineOwner
---------
You have some out of date drivers loading on your system. Some are quite obsolete. Third party outed drivers can and do cause memory corruption and crashes. Update these drivers, especailly those in red font.
Quote:
nvlddmkm.sys Thu May 14 16:32:27 2009 - nVidia Video drivers Drivers - Download NVIDIA Drivers

nvm62x32.sys Fri Oct 17 17:00:39 2008 - nVidia Ethernet Networking Driver (nForce chipset driver) Drivers - Download NVIDIA Drivers

nvstor.sys Wed May 20 02:44:09 2009 - nVidia Storage Drivers Drivers - Download NVIDIA Drivers

VSTBS23.SYS Wed Oct 15 20:30:15 2008
- Conexant HSF_HWB2 WDM driverConexant: Support

VSTCNXT3.SYS Wed Oct 15 20:29:13 2008
- Conexant SoftK56 Modem Driver Conexant: Support

VSTDPV3.SYS Wed Oct 15 20:32:04 2008 - Conexant SoftK56 Modem Driver Conexant: Support
How to find drivers -
Quote:
- I have listed links to most of the drivers in the code box below. 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
If you need help with the drivers, let us know. You may not find updated drivers for the modem. If you cannot and if you do not use the modem, navigate to C:\Windows\System32\Drivers and rename each of the modem drivers listed above from .sys to .bak. Reboot and these drivers will not load.

Since you received an error 24, I suggest you run Check Disk.
Quote:

Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP).

Copy/paste the results into your next post.


After you have taken care of the drivers, run your system and see how it does. Upload any new BSOD's you get. Keep us updated.
My System SpecsSystem Spec
25 Oct 2010   #3
IhateBSOD

Windows 7 Home Premium 32bit.
 
 

I tried updating the drivers i changed the modem files like you suggested as i dont use it anyways

here is what the check disk results were

Checking file system on C: The type of the file system is NTFS. A disk check has been scheduled. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 3)... 49408 file records processed. File verification completed. 63 large file records processed. 0 bad file records processed. 0 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)... 69486 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)... 49408 file SDs/SIDs processed. Cleaning up 64 unused index entries from index $SII of file 0x9. Cleaning up 64 unused index entries from index $SDH of file 0x9. Cleaning up 64 unused security descriptors. Security descriptor verification completed. 10040 data files processed. CHKDSK is verifying Usn Journal... 36770600 USN bytes processed. Usn Journal verification completed. Windows has checked the file system and found no problems. 233596927 KB total disk space. 15536552 KB in 37963 files. 28868 KB in 10041 indexes. 0 KB in bad sectors. 158675 KB in use by the system. 65536 KB occupied by the log file. 217872832 KB available on disk. 4096 bytes in each allocation unit. 58399231 total allocation units on disk. 54468208 allocation units available on disk. Internal Info: 00 c1 00 00 90 bb 00 00 3f 7a 01 00 00 00 00 00 ........?z...... 3b 00 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ;...,........... 88 ee 25 00 50 01 25 00 f8 17 25 00 00 00 25 00 ..%.P.%...%...%. Windows has finished checking your disk. Please wait while your computer restarts.

The BSOD happend twice today even happened once right after it restarted. Could this be a Memory issue?

*Last BSOD*
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 1000008e
BCP1: C0000005
BCP2: 82AB1FD6
BCP3: 8F9D1BF0
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
My System SpecsSystem Spec
.

25 Oct 2010   #4
goguta

Windows 7 ultimate 32
 
 

Why don't u just format & reinstall windows. It seems to me the easiest way to solve your problem.
My System SpecsSystem Spec
25 Oct 2010   #5
IhateBSOD

Windows 7 Home Premium 32bit.
 
 

Quote   Quote: Originally Posted by goguta View Post
Why don't u just format & reinstall windows. It seems to me the easiest way to solve your problem.
did that yesterday
My System SpecsSystem Spec
25 Oct 2010   #6
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Looks like your hard drive is OK and Check Disk successfully repaired file system errors. Very good. Sorry you had another BSOD. Can you upload it to us? We need the actual dump. To answer your question, yes, memory is a possibility. But obsolete drivers are also a possibility. Were you able to update nvm62x32.sys Fri Oct 17 2008?

You can certainly test your RAM with Memtest. Follow the instructions in this tutorial:
RAM - Test with Memtest86+. Run the test for at least 7 passes. This will take 7 to 8 hours. Errors, if any, will show on your screen in red. Post your results.



My System SpecsSystem Spec
25 Oct 2010   #7
IhateBSOD

Windows 7 Home Premium 32bit.
 
 

I updated the driver but it doesnt seem to be any newer than oct 17 2008. Updated files

Quote   Quote: Originally Posted by CarlTR6 View Post
Looks like your hard drive is OK and Check Disk successfully repaired file system errors. Very good. Sorry you had another BSOD. Can you upload it to us? We need the actual dump. To answer your question, yes, memory is a possibility. But obsolete drivers are also a possibility. Were you able to update nvm62x32.sys Fri Oct 17 2008?

You can certainly test your RAM with Memtest. Follow the instructions in this tutorial: RAM - Test with Memtest86+. Run the test for at least 7 passes. This will take 7 to 8 hours. Errors, if any, will show on your screen in red. Post your results.


My System SpecsSystem Spec
26 Oct 2010   #8
IhateBSOD

Windows 7 Home Premium 32bit.
 
 

Been running the memory test it all shows red on pass Number 5 right now
My System SpecsSystem Spec
26 Oct 2010   #9
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Once you see red, you can stop Memtest. You have identified that you have a RAM problem. Keep in mind that Memtest errors can mean several things: one or more RAM sticks are bad, the RAM sticks are mismatched, The RAM is not compatible with the mother board, or there is a bad RAM slot.

Remove all sticks except the one in the first slot. Test that stick with Memtest. If it passes, test the next stick and so on. If it fails, test the next stick in the same slot. If the second stick passes, you will know the first stick is bad. If the second stick fails, test both sticks separately in another slot. Post your results.

If you cannot update nvm62x32.sys to a date later than 2008, you are going to have to get a new LAN adapter, one that is compatible with Win 7.

After we sort out your RAM problem, we will again look a dumps.
My System SpecsSystem Spec
26 Oct 2010   #10
IhateBSOD

Windows 7 Home Premium 32bit.
 
 

Ok I went threw all the 4 sticks of ram one was bad. im running on three right now and no BSOD so far.

Tested all four sticks in each slot one was bad. All slots worked fine
My System SpecsSystem Spec
Reply

 Help BSOD




Thread Tools



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 17:20.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App