Another BSOD...

rx791 · 12 Jan 2010

My issues are similar to many here, however after trying quite a few suggestions, I haven't quite put my finger on the problem.

The system:
Gateway MT3705
Intel Dual Core Processor 1.6Ghz
2GB Ram
100GB HD Fujitsu
Graphics = ATI Radeon Xpress 200M
OS = Windows 7 Home Premium
Sound = ?
Chipset = AMD
Bios = Phoenix Ver 83.04

Basically clean installed the OS after wiping out Vista. Worked well for a couple of hours then started throwing BSOD's. Didn't have any under the Vista install.

BSOD:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

BCCode: 1000008e
BCP1: C000001D
BCP2: 90F5D3FD
BCP3: 97EE3BFC
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Latest .dmp file attached...

The only thing I haven't done is flash the BIOS, though attempted. Each time I run the utility it tells me that it can't proceed due to Himem.sys, or memory manger-something like that-running. This occurring while running in safe mode command prompt. Don't know how to keep that memory manager from loading.

Of note is that the system runs with no problems under safe mode with networking so I'm reasonably sure it's something that loads under normal boot. Initially I thought it might be the graphics driver, but after updating it as well as running the standard VGA, I'm not so sure because it still throws the BSOD.

The most intense programs I run are Adobe Master Suite CS4 and I don't open more than one at a time unless it's Bridge.

The BSOD's are truly random; sometimes when browsing the web, other times in PS, others when downloading or installing .

As a side not I use COMODO antivirus/firewall. BSOD's still occur even when disabled.

Has anyone gotten win 7 to run on this laptop?

So for the guys smarter than me I could use a little tutelage

zigzag3143 · 12 Jan 2010

rx791 said:

My issues are similar to many here, however after trying quite a few suggestions, I haven't quite put my finger on the problem.

The system:
Gateway MT3705
Intel Dual Core Processor 1.6Ghz
2GB Ram
100GB HD Fujitsu
Graphics = ATI Radeon Xpress 200M
OS = Windows 7 Home Premium
Sound = ?
Chipset = AMD
Bios = Phoenix Ver 83.04

Basically clean installed the OS after wiping out Vista. Worked well for a couple of hours then started throwing BSOD's. Didn't have any under the Vista install.

Code:

BSOD:
 Problem Event Name:    BlueScreen
 OS Version:    6.1.7600.2.0.0.768.3
 Locale ID:    1033

  BCCode:    1000008e
  BCP1:    C000001D
  BCP2:    90F5D3FD
  BCP3:    97EE3BFC
  BCP4:    00000000
  OS Version:    6_1_7600
  Service Pack:    0_0
  Product:    768_1

Latest .dmp file attached...

The only thing I haven't done is flash the BIOS, though attempted. Each time I run the utility it tells me that it can't proceed due to Himem.sys, or memory manger-something like that-running. This occurring while running in safe mode command prompt. Don't know how to keep that memory manager from loading.
use msconifig for prevent himem, memory mgr from loading. use services.msc to stop services

Of note is that the system runs with no problems under safe mode with networking so I'm reasonably sure it's something that loads under normal boot. Initially I thought it might be the graphics driver, but after updating it as well as running the standard VGA, I'm not so sure because it still throws the BSOD.

The most intense programs I run are Adobe Master Suite CS4 and I don't open more than one at a time unless it's Bridge.

The BSOD's are truly random; sometimes when browsing the web, other times in PS, others when downloading or installing .

As a side not I use COMODO antivirus/firewall. BSOD's still occur even when disabled.

Has anyone gotten win 7 to run on this laptop?

So for the guys smarter than me I could use a little tutelage

Hi and welcome

This crash was caused by hardware. Usually it is either incompatible or a corrupt driver
use these to help you isolate exactly which. https://www.sevenforums.com/crash-loc...-what-try.html

Also if you are overclocking stop. If you have a raid update its driver.
run system file check sfc /scannow

If this happens again download memtestx86 and run it for 5 passes

Ken J+

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\011210-23859-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a06000 PsLoadedModuleList = 0x82b4e810
Debug session time: Tue Jan 12 08:20:40.011 2010 (GMT-5)
System Uptime: 0 days 0:34:45.933
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c000001d, 8204d3fd, 97c9baa4, 0}

Probably caused by : hardware ( win32k!MulFillPath+8d )

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

0: 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: c000001d, The exception code that was not handled
Arg2: 8204d3fd, The address that the exception occurred at
Arg3: 97c9baa4, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
win32k!MulFillPath+8d
8204d3fd f08b45e4        lock mov eax,dword ptr [ebp-1Ch]

TRAP_FRAME:  97c9baa4 -- (.trap 0xffffffff97c9baa4)
ErrCode = 00000000
eax=0000008a ebx=00000000 ecx=ffab1730 edx=00000000 esi=97c9bbac edi=97c9bc18
eip=8204d3fd esp=97c9bb18 ebp=97c9bc71 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
win32k!MulFillPath+0x8d:
8204d3fd f08b45e4        lock mov eax,dword ptr [ebp-1Ch] ss:0010:97c9bc55=00000000
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  Photoshop.exe

CURRENT_IRQL:  0

MISALIGNED_IP: 
win32k!MulFillPath+8d
8204d3fd f08b45e4        lock mov eax,dword ptr [ebp-1Ch]

LAST_CONTROL_TRANSFER:  from 0181f081 to 8204d3fd

FAILED_INSTRUCTION_ADDRESS: 
win32k!MulFillPath+8d
8204d3fd f08b45e4        lock mov eax,dword ptr [ebp-1Ch]

STACK_TEXT:  
97c9bc71 0181f081 70000000 00ffa8e1 08000000 win32k!MulFillPath+0x8d
WARNING: Frame IP not in any known module. Following frames may be wrong.
97c9bc91 15000000 28000000 000a4800 70000000 0x181f081
00000000 00000000 00000000 00000000 00000000 0x15000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!MulFillPath+8d
8204d3fd f08b45e4        lock mov eax,dword ptr [ebp-1Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!MulFillPath+8d

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

BUCKET_ID:  IP_MISALIGNED

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