Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Vista: Blue Screen on new PC (Memdump included)


  • Please log in to reply
No replies to this topic

#1 AlexTheDolphin

AlexTheDolphin

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:03:48 AM

Posted 26 May 2009 - 05:30 PM

Hi,

I have a new computer that is not 2 weeks old. It is a refurbished Packard Bell:

* Intel Core 2 Quad Q6600 Processor
* (2.40GHz, 1066MHz FSB, 8MB Cache)
* Genuine Windows Vista Home Premium
* 3GB Memory
* 460GB Hard Drive

* Multi-Format Dual Layer DVD Re-Writer
* 256MB nVidia GeForce
* 4 USB Connections
* 18-In-1 Card Reader

**AMENDED**

It was crashing lots and going to blue screen so I uninstalled the Norton 360 trial and put on AVG 8.5 free version and Comodo Firewall. It then happened less often.

I then changed to ZoneAlarm instead of Comodo for my firewall and it then only happened when went to to www.flyordie.com to play Go.

I then got rid of AVG Anti virus and i am currently using ZoneAlarm for both firewall and Anti-virus. It still crashes from time to time when using the net but sometimes when using other applications.


I have contacted the company i purchased it from but no reply yet. I just need to know whether it is a hardware fault on my newly purchased machine!

I have run Malwarebytes and it has picked up nothing.

The error message that pops up when it reboots is:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 1000008e
BCP1: C0000005
BCP2: 00000000
BCP3: 99BA1BF8
BCP4: 00000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini052609-02.dmp
C:\Users\Alex\AppData\Local\Temp\WER-33977-0.sysdata.xml
C:\Users\Alex\AppData\Local\Temp\WERB6C0.tmp.version.txt

As per the instructions on a similar post i have run the memory dump through Windows Debugger and got this:

Microsoft Windows Debugger Version 6.11.0001.404 X86
Copyright Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows Vista Kernel Version 6000 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16575.x86fre.vista_gdr.071009-1548
Machine Name:
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Tue May 26 22:42:15.700 2009 (GMT+1)
System Uptime: 0 days 0:14:12.650
Loading Kernel Symbols
...............................................................
................................................................
.....
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 8E, {c0000005, 0, 99ba1bf8, 0}

Page 85211 not present in the dump file. Type ".hh dbgerr004" for details
Page 85211 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details
Probably caused by : win32k.sys ( win32k!xxxInternalInvalidate+b6 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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: c0000005, The exception code that was not handled
Arg2: 00000000, The address that the exception occurred at
Arg3: 99ba1bf8, Trap Frame
Arg4: 00000000

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

Page 85211 not present in the dump file. Type ".hh dbgerr004" for details
Page 85211 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
+69fa952f027bd90c
00000000 ?? ???

TRAP_FRAME: 99ba1bf8 -- (.trap 0xffffffff99ba1bf8)
ErrCode = 00000010
eax=00000000 ebx=00001001 ecx=ff0327a0 edx=0000019c esi=ff032750 edi=99ba1c9c
eip=00000000 esp=99ba1c6c ebp=00000000 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
00000000 ?? ???
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: firefox.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 81c2335e to 81cd8681

STACK_TEXT:
99ba17b8 81c2335e 0000008e c0000005 00000000 nt!KeBugCheckEx+0x1e
99ba1b88 81c8d66a 99ba1ba4 00000000 99ba1bf8 nt!KiDispatchException+0x1a9
99ba1bf0 81c8d61e 00000000 00000000 badb0d00 nt!CommonDispatchException+0x4a
99ba1c70 92acad9f ff024818 99ba1c8c 99ba1d1c nt!KiExceptionExit+0x186
99ba1cb4 92adccae ff024818 01040059 00001001 win32k!xxxInternalInvalidate+0xb6
99ba1ce0 92adddd1 ff024818 99ba1d1c 00000000 win32k!xxxRedrawWindow+0x103
99ba1cf8 92addd5f ff024818 99ba1d1c 00000000 win32k!xxxInvalidateRect+0x32
99ba1d50 81c8caaa 00070310 99ba1d1c 00000000 win32k!NtUserInvalidateRect+0x8f
99ba1d50 77b50f34 00070310 99ba1d1c 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
002cecfc 00000000 00000000 00000000 00000000 0x77b50f34


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!xxxInternalInvalidate+b6
92acad9f 85c0 test eax,eax

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: win32k!xxxInternalInvalidate+b6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 46d4d163

FAILURE_BUCKET_ID: 0x8E_win32k!xxxInternalInvalidate+b6

BUCKET_ID: 0x8E_win32k!xxxInternalInvalidate+b6

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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: c0000005, The exception code that was not handled
Arg2: 00000000, The address that the exception occurred at
Arg3: 99ba1bf8, Trap Frame
Arg4: 00000000

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

Page 85211 not present in the dump file. Type ".hh dbgerr004" for details
Page 85211 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
+69fa952f027bd90c
00000000 ?? ???

TRAP_FRAME: 99ba1bf8 -- (.trap 0xffffffff99ba1bf8)
ErrCode = 00000010
eax=00000000 ebx=00001001 ecx=ff0327a0 edx=0000019c esi=ff032750 edi=99ba1c9c
eip=00000000 esp=99ba1c6c ebp=00000000 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
00000000 ?? ???
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: firefox.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 81c2335e to 81cd8681

STACK_TEXT:
99ba17b8 81c2335e 0000008e c0000005 00000000 nt!KeBugCheckEx+0x1e
99ba1b88 81c8d66a 99ba1ba4 00000000 99ba1bf8 nt!KiDispatchException+0x1a9
99ba1bf0 81c8d61e 00000000 00000000 badb0d00 nt!CommonDispatchException+0x4a
99ba1c70 92acad9f ff024818 99ba1c8c 99ba1d1c nt!KiExceptionExit+0x186
99ba1cb4 92adccae ff024818 01040059 00001001 win32k!xxxInternalInvalidate+0xb6
99ba1ce0 92adddd1 ff024818 99ba1d1c 00000000 win32k!xxxRedrawWindow+0x103
99ba1cf8 92addd5f ff024818 99ba1d1c 00000000 win32k!xxxInvalidateRect+0x32
99ba1d50 81c8caaa 00070310 99ba1d1c 00000000 win32k!NtUserInvalidateRect+0x8f
99ba1d50 77b50f34 00070310 99ba1d1c 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
002cecfc 00000000 00000000 00000000 00000000 0x77b50f34


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!xxxInternalInvalidate+b6
92acad9f 85c0 test eax,eax

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: win32k!xxxInternalInvalidate+b6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 46d4d163

FAILURE_BUCKET_ID: 0x8E_win32k!xxxInternalInvalidate+b6

BUCKET_ID: 0x8E_win32k!xxxInternalInvalidate+b6

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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: c0000005, The exception code that was not handled
Arg2: 00000000, The address that the exception occurred at
Arg3: 99ba1bf8, Trap Frame
Arg4: 00000000

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

Page 85211 not present in the dump file. Type ".hh dbgerr004" for details
Page 85211 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
+69fa952f027bd90c
00000000 ?? ???

TRAP_FRAME: 99ba1bf8 -- (.trap 0xffffffff99ba1bf8)
ErrCode = 00000010
eax=00000000 ebx=00001001 ecx=ff0327a0 edx=0000019c esi=ff032750 edi=99ba1c9c
eip=00000000 esp=99ba1c6c ebp=00000000 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
00000000 ?? ???
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: firefox.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 81c2335e to 81cd8681

STACK_TEXT:
99ba17b8 81c2335e 0000008e c0000005 00000000 nt!KeBugCheckEx+0x1e
99ba1b88 81c8d66a 99ba1ba4 00000000 99ba1bf8 nt!KiDispatchException+0x1a9
99ba1bf0 81c8d61e 00000000 00000000 badb0d00 nt!CommonDispatchException+0x4a
99ba1c70 92acad9f ff024818 99ba1c8c 99ba1d1c nt!KiExceptionExit+0x186
99ba1cb4 92adccae ff024818 01040059 00001001 win32k!xxxInternalInvalidate+0xb6
99ba1ce0 92adddd1 ff024818 99ba1d1c 00000000 win32k!xxxRedrawWindow+0x103
99ba1cf8 92addd5f ff024818 99ba1d1c 00000000 win32k!xxxInvalidateRect+0x32
99ba1d50 81c8caaa 00070310 99ba1d1c 00000000 win32k!NtUserInvalidateRect+0x8f
99ba1d50 77b50f34 00070310 99ba1d1c 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
002cecfc 00000000 00000000 00000000 00000000 0x77b50f34


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!xxxInternalInvalidate+b6
92acad9f 85c0 test eax,eax

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: win32k!xxxInternalInvalidate+b6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 46d4d163

FAILURE_BUCKET_ID: 0x8E_win32k!xxxInternalInvalidate+b6

BUCKET_ID: 0x8E_win32k!xxxInternalInvalidate+b6

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

Any help would be very much appreciated,

Thanks,

Alex

Edited by AlexTheDolphin, 27 May 2009 - 04:01 PM.


BC AdBot (Login to Remove)

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users