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 again.. help me please !


28 May 2011   #1

Windoes 7 Ultimate 32 bit
 
 
BSOD again.. help me please !

I have a problem.. again.. with my laptop, it's kinda different than the last problem..

My System Spec :

- Windows 7 Ultimate 32-bit
- the OS is not original
- the age is about 6-8 months
- the age of OS installation is the same 6-8 months, and i'm not re-installed it..

This is the copy :

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 10e
BCP1: 0000001E
BCP2: 00000000
BCP3: 00000000
BCP4: 00000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\052911-22885-01.dmp
C:\Users\Family\AppData\Local\Temp\WER-47439-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


I need some helps here, maybe someone can solve it.. Thank you..


My System SpecsSystem Spec
.

29 May 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by sunemisu75 View Post
I have a problem.. again.. with my laptop, it's kinda different than the last problem..

My System Spec :

- Windows 7 Ultimate 32-bit
- the OS is not original
- the age is about 6-8 months
- the age of OS installation is the same 6-8 months, and i'm not re-installed it..

This is the copy :

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 10e
BCP1: 0000001E
BCP2: 00000000
BCP3: 00000000
BCP4: 00000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\052911-22885-01.dmp
C:\Users\Family\AppData\Local\Temp\WER-47439-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


I need some helps here, maybe someone can solve it.. Thank you..
This was related ot the video memory manager. I aslo would remove sptd.sys which is a huge cause of crash

VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition


I would re-install the video driver and dirextX.

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper


Or Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.


Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp,sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads

when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.


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\052911-22885-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 x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.x86fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0x83253000 PsLoadedModuleList = 0x8339c4d0
Debug session time: Fri May 27 06:48:22.757 2011 (GMT-4)
System Uptime: 0 days 1:58:03.881
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.......
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 0000001e, The subtype of the bugcheck:
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR:  0x10e_1e

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 89022276 to 83331f2c

STACK_TEXT:  
988677c0 89022276 0000010e 0000001e 00000000 nt!KeBugCheckEx+0x1e
988677e8 8fb9a3c9 00000000 8cdc0b78 00001f42 watchdog!WdLogEvent5+0xc6
98867818 8fb8a330 b3e9fcd8 00000000 00010000 dxgmms1!VIDMM_PROCESS_HEAP::MapViewOfAllocation+0x4b
98867834 8fb9ecdd b1eef6a0 00000000 00010000 dxgmms1!VidMmMapViewOfAllocation+0x52
98867888 8fba1f61 b1eef6a0 00000000 00010000 dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+0xa1
988678e8 8fba0d5b b1eef6a0 00000000 00010000 dxgmms1!VIDMM_APERTURE_SEGMENT::LockAllocationRange+0x1db
988679c8 8fb8aac7 b1eef6a0 00000001 89fb2838 dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x52d
988679ec 8fb90dac 89fb2840 00000000 00000000 dxgmms1!VIDMM_GLOBAL::EvictAllAllocationInList+0x2f
98867a10 8fb91cb9 00000000 00000000 00000000 dxgmms1!VIDMM_GLOBAL::EvictAllReclaimedAllocation+0x2a
98867a34 8fb933df 854de488 00000005 89ed99b0 dxgmms1!VIDMM_GLOBAL::PageInOneAllocation+0xbb
98867aa0 8fb93eaa 98867be0 98867b70 98867b9c dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x321
98867ab8 8fba9281 98867b94 89ed99b0 89ed99b0 dxgmms1!VidMmiProcessSystemCommand+0x20
98867ad4 8fbaa15b 89ed9bb0 89ed6788 98867b14 dxgmms1!VidSchiSubmitSystemCommand+0x33
98867ae4 8fb856dc 89ed99b0 89ed99b0 89ed6550 dxgmms1!VidSchiSubmitQueueCommand+0x7b
98867b14 8fbaa32e 89ed8000 98867b38 89ed6550 dxgmms1!VidSchiSubmitQueueCommandDirect+0x1ae
98867b3c 8fba56b9 01ed99b0 89fb2000 bc553148 dxgmms1!VidSchiSubmitCommandPacketToQueue+0x180
98867b54 8fb93f11 89ed6788 8fb93e8a 98867b94 dxgmms1!VidSchSubmitSystemCommand+0xab
98867b80 8fb93f86 98867b94 b8621de0 854de488 dxgmms1!VIDMM_GLOBAL::QueueSystemCommandAndWait+0x41
98867bb8 8fb96df6 98867be0 999e6008 98867cac dxgmms1!VIDMM_GLOBAL::QueueDeferredCommandAndWait+0x3c
98867c14 8fb7943b 01621de0 00000008 0000004d dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+0xa18
98867c34 8fac4329 89fb2000 b8621de0 00000000 dxgmms1!VidMmBeginCPUAccess+0x1f
98867c58 8faec0b2 85f4bfd0 89fb2000 b8621de0 dxgkrnl!VIDMM_EXPORT::VidMmBeginCPUAccess+0x23
98867c90 8faec707 0000004d 172bcedb 01d5ded0 dxgkrnl!DXGDEVICE::Lock+0x24f
98867d28 832911ea 01d5ded0 01d5def8 775170b4 dxgkrnl!DxgkLock+0x17b
98867d28 775170b4 01d5ded0 01d5def8 775170b4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
01d5def8 00000000 00000000 00000000 00000000 0x775170b4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_PROCESS_HEAP::MapViewOfAllocation+4b
8fb9a3c9 c745f4a9f8ffff  mov     dword ptr [ebp-0Ch],0FFFFF8A9h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!VIDMM_PROCESS_HEAP::MapViewOfAllocation+4b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d4a24c1

FAILURE_BUCKET_ID:  0x10e_1e_dxgmms1!VIDMM_PROCESS_HEAP::MapViewOfAllocation+4b

BUCKET_ID:  0x10e_1e_dxgmms1!VIDMM_PROCESS_HEAP::MapViewOfAllocation+4b

Followup: MachineOwner
---------
My System SpecsSystem Spec
29 May 2011   #3

Windoes 7 Ultimate 32 bit
 
 

Where can i get the fresh copy ?

and how can i sweep my old driver ? do you have any tutorials ? which one should i copy ?

thank you..
My System SpecsSystem Spec
.


Reply

 BSOD again.. help me please !




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 03:49 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33