Windows 7 blue screen of death fresh install.

[xmorisx]

Hello everyone
So I recently got a gaming mouse that is not compatible with Windows XP. I installed Windows 7 dual boot and did i mention since i am a college student I got Windows 7 from college for free. Not sure if there is anything different with their versions of Win7 but ones i installed it it was going good the key didnt work but I still got through. Then I got blue screen of death and memory was dumping and restarted the computer logged back in and it gave me details of the error. It keep happening every time the computer restarts and goes into Win7.

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: 1000008e
BCP1: C0000420
BCP2: 8285E07B
BCP3: A5C5F988
BCP4: 00000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\112214-4291398478-01.dmp
C:\Users\Hades\AppData\Local\Temp\WER-4291418306-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0...

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



I will be thankful if anyone can help me Because I dont understand this. I also checked my computer if it can run Win7 64 bit or 32 bit and checked out fine! Thank you!

 

[alexoiu]

Hi, Have you updated XP, or fresh installed after formatting the volume?

 

[xmorisx]

I have them dual boot and win xp is not been updated win xp is sp3.
I feel like my computer is old that is why it is happening. And I also checked if I can run Win7 64 bit it checked out fine so It wouldn't be a problem to run 32 bit which is what I installed.


System Information report written at: 11/23/14 12:14:09
System Name: ODIN
[System Summary (C:\DOCUME~1\MORIS\Desktop\INFORM~1.NFO)]

Item Value
OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 3 Build 2600
OS Manufacturer Microsoft Corporation
System Name ODIN
System Manufacturer Gigabyte Technology Co., Ltd.
System Model GA-MA785GM-US2H
System Type X86-based PC
Processor x86 Family 16 Model 2 Stepping 3 AuthenticAMD ~2511 Mhz
BIOS Version/Date Award Software International, Inc. F11, 5/17/2010
SMBIOS Version 2.4
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.5512 (xpsp.080413-2111)"
User Name ODIN\MORIS
Time Zone Pacific Standard Time
Total Physical Memory 4,096.00 MB
Available Physical Memory 2.00 GB
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.95 GB
Page File Space 11.14 GB
Page File C:\pagefile.sys


I also got 8gb ram but it doesnt detect because it is 32 bit same with win7 32 bit

 

[HotPantsHenry]

A quick Google search pulled this up.

This blue screen can have several causes (from most likely to least likely):

Faulty RAM
Faulty hardware
A problem with a device driver
A virus

Seeing as how this is a fresh install, I'd mark of the virus.

So now what you should do is boot into safe mode (F8 at boot) run cmd as admin and run chkdsk /f. It will schedule a chkdsk at next boot. After that, reboot and let it run.

If you can give me more information on when the BSOD'S start to happen (I.e. at boot, when you run a certain program, etc), it will be easier to solve the problem please list all hardware specs as well if you can.

 

[xmorisx]

so it happens at random. Sometime is happens when when I close the error report and sometimes it happens 5 mins later. I dont think it is faulty ram i think it might be incompatibility with hardware in win7. So you want me to restart press f8 then safe mode? How do i know if i am going into win7 safe mode or win XP safe mode? Is the file i have up there not the hardware specs?

 

[HotPantsHenry]

so it happens at random. Sometime is happens when when I close the error report and sometimes it happens 5 mins later. I dont think it is faulty ram i think it might be incompatibility with hardware in win7. So you want me to restart press f8 then safe mode? How do i know if i am going into win7 safe mode or win XP safe mode? Is the file i have up there not the hardware specs?

at OS choice screen, highlight Windows 7 then press f8

 

[HotPantsHenry]

Do you have a 2gb ram stick?

 

[xmorisx]

well i have 2x4 gb ram stick put in there. But the system I have is win7 32 bit i can install win764 bit but i want to make sure i can fix this problem first.

 

[HotPantsHenry]

Gotcha, let me know what the chkdsk /f reports.

 

[xmorisx]

chkdsk /f reported that volume is clean. I am on Win7 right now not sure when blue screen will appear though.
I just remember that this blue screen of death started happening after the installation of avast 2015. And avast is running right now.

 

[xmorisx]

Okay the issue came back. Here is the report not sure how i can open the dmp file so you can read it.

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: 1e
BCP1: C0000420
BCP2: 8F5516F0
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\112314-4291413548-01.dmp
C:\Users\Hades\AppData\Local\Temp\WER-4291512702-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

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

 

[xmorisx]

this is one of the dump files.


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


Loading Dump File [C:\Documents and Settings\MORIS\Desktop\death\112314-4291414374-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
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Checked x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86chk.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x82856000 PsLoadedModuleList = 0x82c9c430
Debug session time: Sun Nov 23 15:21:43.543 2014 (UTC - 8:00)
System Uptime: 49 days 18:15:19.633 (checked kernels begin at 49 days)
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {80000003, 9705eef0, a03d48c8, 0}

Probably caused by : win32k.sys ( win32k!DoRip+53 )

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

0: kd> kd> !analyze -v
Numeric expression missing from '> !analyze -v'
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: 80000003, The exception code that was not handled
Arg2: 9705eef0, The address that the exception occurred at
Arg3: a03d48c8, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

FAULTING_IP:
win32k!DoRip+53
9705eef0 cc int 3

TRAP_FRAME: a03d48c8 -- (.trap 0xffffffffa03d48c8)
ErrCode = 00000000
eax=00000001 ebx=a03d498c ecx=82993c72 edx=00000001 esi=829938a6 edi=00000000
eip=9705eef1 esp=a03d493c ebp=a03d4944 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
win32k!DoRip+0x54:
9705eef1 5e pop esi
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: LolClient.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 9707dd20 to 9705eef1

STACK_TEXT:
a03d4944 9707dd20 00000000 9715f8b0 00000000 win32k!DoRip+0x54
a03d4974 9707fb2b ffbb2728 a03d4c9c 00000000 win32k!RFONTOBJ::bGetDEVICEMETRICS+0x109
a03d4a30 9708021c a03d4c58 a03d4aa0 fe5a8c28 win32k!RFONTOBJ::bRealizeFont+0x27e
a03d4aa4 9703421d a03d4c58 a03d4bb4 00000002 win32k!RFONTOBJ::bSetNewFDX+0x174
a03d4be0 97034c90 a03d4c58 a03d4c9c fe5a8b10 win32k!RESETFCOBJ::RESETFCOBJ+0x24b
a03d4c90 97013b33 fda66cf0 fd4d3210 00000000 win32k!GreGetGlyphOutlineInternal+0x4cb
a03d4d0c 829f2173 96010f08 00000078 00000000 win32k!NtGdiGetGlyphOutline+0xbf
a03d4d0c 76d3a364 96010f08 00000078 00000000 nt!KiFastCallEntry+0x163
WARNING: Frame IP not in any known module. Following frames may be wrong.
0029dacc 00000000 00000000 00000000 00000000 0x76d3a364


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
win32k!DoRip+53
9705eef0 cc int 3

SYMBOL_NAME: win32k!DoRip+53

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7938b

FAILURE_BUCKET_ID: 0x8E_win32k!DoRip+53

BUCKET_ID: 0x8E_win32k!DoRip+53

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

 

[xmorisx]

Can anyone help me or no?

 

[Paul NZ]

Probably this PROCESS_NAME: LolClient.exe

 

[xmorisx]

figured it out I was running Win7 debug that was having issues. so ig ot win7 pro 64bit no problems.