Frequent BSODs last month, then stopped, now re-occuring

[mcutugno]

About a month ago I had this thread going:
http://www.sevenforums.com/crashes-debugging/154039-irql_not_less_or_equal-2.html

Then the system stabilized. Now I am receiving daily blue screens again. The most frequent is 0x000001a Memory Management. Info attached.

Please help.

 

[zigzag3143]

About a month ago I had this thread going:
http://www.sevenforums.com/crashes-debugging/154039-irql_not_less_or_equal-2.html

Then the system stabilized. Now I am receiving daily blue screens again. The most frequent is 0x000001a Memory Management. Info attached.

Please help.

Caused by your wlite.exe (xp webcam driver) and some really old drivers

Update these

SiWinAcc.sys    11/1/2004 3:23:29 PM        fffff880`01345000    fffff880`0134f000    0x0000a000    0x41868d31                        
secdrv.SYS    9/13/2006 9:18:38 AM        fffff880`057a8000    fffff880`057b3000    0x0000b000    0x4508052e                        
SiRemFil.sys    10/18/2006 6:20:39 PM        fffff880`01b9c000    fffff880`01ba4000    0x00008000    0x4536a8b7                        
LVUSBS64.sys    5/11/2007 8:01:20 PM        fffff880`04871000    fffff880`0487b900    0x0000a900    0x464503d0                        
Si3114r5.sys    4/24/2008 2:20:08 AM        fffff880`01000000    fffff880`01052000    0x00052000    0x48102698

How To Find 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 Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\060111-56753-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`0304b000 PsLoadedModuleList = 0xfffff800`03290650
Debug session time: Wed Jun  1 18:39:08.025 2011 (GMT-4)
System Uptime: 3 days 4:54:20.763
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
...........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {411, fffff680000357e8, 9a900000a8266886, fffff680000357f9}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6061 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000411, The subtype of the bugcheck.
Arg2: fffff680000357e8
Arg3: 9a900000a8266886
Arg4: fffff680000357f9

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


BUGCHECK_STR:  0x1a_411

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  wLite.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800030a79ad to fffff800030cad00

STACK_TEXT:  
fffff880`02bb28c8 fffff800`030a79ad : 00000000`0000001a 00000000`00000411 fffff680`000357e8 9a900000`a8266886 : nt!KeBugCheckEx
fffff880`02bb28d0 fffff800`030fc071 : 00000000`00000000 fffff680`000357e8 0000007f`fffffff8 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x6061
fffff880`02bb2920 fffff800`030e884f : 00000000`00000001 00000000`00000000 00000000`00000000 fffffa80`15a51ab8 : nt!MiResolveTransitionFault+0x381
fffff880`02bb29b0 fffff800`030d7f69 : 00000000`00000202 ffffffff`ffffffff 00000000`00000000 00000000`00000000 : nt!MiDispatchFault+0x95f
fffff880`02bb2ac0 fffff800`030c8e2e : 00000000`00000001 00000000`06afd170 00000000`00000001 00000000`06afc1d0 : nt!MmAccessFault+0x359
fffff880`02bb2c20 00000000`6ab6a043 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0a01ebd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6ab6a043


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+6061
fffff800`030a79ad cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+6061

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

FAILURE_BUCKET_ID:  X64_0x1a_411_nt!_??_::FNODOBFM::_string_+6061

BUCKET_ID:  X64_0x1a_411_nt!_??_::FNODOBFM::_string_+6061

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

 

[mcutugno]

wLite.exe is gone. It still appears to be happening. This time it was BAD_POOL_HEADER 0x00000019.

 

[zigzag3143]

wLite.exe is gone. It still appears to be happening. This time it was BAD_POOL_HEADER 0x00000019.

No DMP file included in upload try this method




To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

 

[mcutugno]

Latest blue screens attached.