
Quote: Originally Posted by
brodiewf
this happened when i was using my anti-virus program please assist
- windows 7 professional x64
- windows vista 32 bit, however the computer is made for 64 bit
MSI gx 700
laptop
- hardware is not even a year old yet
- installed windows 7 about 6 months ago
Old drivers. these are from as far back as 2005. They need updating
Code:
tosrfcom.sys 8/1/2005 2:45:42 0x42edd326 fffff880`02dc3000 fffff880`02ddbe80 0x00018e80
tosporte.sys 10/11/2006 2:31:08 0x452c9dbc fffff880`04957000 fffff880`04969000 0x00012000
agrsm64.sys 11/28/2006 15:46:57 0x456ca041 fffff880`068a1000 fffff880`069d4000 0x00133000
SandBox64.sys 3/12/2008 4:31:32 0x47d7a2f4 fffff880`01950000 fffff880`019bb380 0x0006b380
o2sdx64.sys 6/10/2008 6:26:44 0x484e64f4 fffff880`03c3e000 fffff880`03c49300 0x0000b300
adfs.SYS 6/26/2008 15:52:37 0x48640195 fffff880`06e8d000 fffff880`06ea5000 0x00018000
o2mdx64.sys 7/14/2008 22:21:08 0x487c17a4 fffff880`03c4a000 fffff880`03c57c00 0x0000dc00
spldr.sys 5/11/2009 11:56:27 0x4a0858bb fffff880`015ca000 fffff880`015d2000 0x00008000
GEARAspiWDM.sys 5/18/2009 7:17:04 0x4a1151c0 fffff880`02c4c000 fffff880`02c59000 0x0000d000
How To Find Drivers:
Quote:
- 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
Though blamed on win32.sys it is a memory exception probably again caused by one of the above drivers. Update the drivers and run memtest. If the problems continue let us know
Download a copy of
Memtest86 and burn the ISO to a CD using
Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.
Code:
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\021811-24492-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0405c000 PsLoadedModuleList = 0xfffff800`04299e50
Debug session time: Fri Feb 18 21:05:40.540 2011 (GMT-5)
System Uptime: 0 days 12:35:07.021
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff960000c5314, fffff8800b120920, 0}
Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+264 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960000c5314, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800b120920, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
win32k!SURFACE::bDeleteSurface+264
fffff960`000c5314 396908 cmp dword ptr [rcx+8],ebp
CONTEXT: fffff8800b120920 -- (.cxr 0xfffff8800b120920)
rax=fffff900c0200000 rbx=518ae30051a5d800 rcx=0000000000000000
rdx=0000000000000000 rsi=fffff900c2b4e000 rdi=0000000000000000
rip=fffff960000c5314 rsp=fffff8800b1212f0 rbp=0000000000000001
r8=0000000000000001 r9=0000000000000000 r10=5195060051800000
r11=fffff8800b1212d0 r12=0000000000000000 r13=000000000000518c
r14=0000000000000000 r15=5181d7005186ef00
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
win32k!SURFACE::bDeleteSurface+0x264:
fffff960`000c5314 396908 cmp dword ptr [rcx+8],ebp ds:002b:00000000`00000008=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: explorer.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff960000c5314
STACK_TEXT:
fffff880`0b1212f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SURFACE::bDeleteSurface+0x264
FOLLOWUP_IP:
win32k!SURFACE::bDeleteSurface+264
fffff960`000c5314 396908 cmp dword ptr [rcx+8],ebp
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!SURFACE::bDeleteSurface+264
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d23ecb0
STACK_COMMAND: .cxr 0xfffff8800b120920 ; kb
FAILURE_BUCKET_ID: X64_0x3B_win32k!SURFACE::bDeleteSurface+264
BUCKET_ID: X64_0x3B_win32k!SURFACE::bDeleteSurface+264
Followup: MachineOwner
---------
1: kd> lmvm win32k
start end module name
fffff960`00000000 fffff960`00310000 win32k (pdb symbols) c:\symbols\win32k.pdb\37B842136414455F88E0369BAAB0B7962\win32k.pdb
Loaded symbol image file: win32k.sys
Mapped memory image file: C:\Symbols\win32k.sys\4D23ECB0310000\win32k.sys
Image path: \SystemRoot\System32\win32k.sys
Image name: win32k.sys
Timestamp: Tue Jan 04 22:59:44 2011 (4D23ECB0)
CheckSum: 00309E24
ImageSize: 00310000
File version: 6.1.7600.16732
Product version: 6.1.7600.16732
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: win32k.sys
OriginalFilename: win32k.sys
ProductVersion: 6.1.7600.16732
FileVersion: 6.1.7600.16732 (win7_gdr.110104-1502)
FileDescription: Multi-User Win32 Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.