cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
xSanzo
Blue Screen Again
Posts: 4
Registered: ‎04-30-2015
Location: PH
Views: 1,426
Message 1 of 6

Problems on G40-70 Windows 8.1

I just got my loptop yesterday and when I was booting it up it suddenly had a BSOD error ( Blue screen of Death w/ sad face) I had a bad feeling about it. But I countinued using it for a while at home and after and hour I got really alot of problems many different BSOD error occured may 4-6 diff errors and I don't know how to deal with them, And today I wish to update my loptop and facing update errors... I cant bare with this anymore since it's just a day old loptop im not expecting things like this pls help...

 

BOSD Errors that I've remember

Memory_Management

Kernel_date_inpage

Header something

KMODE_EXCEPTION_NOT_HANDLED

PAGE_FAULT_IN_NONPAGE_AREA

Winsys32 error

 

I've already Updated my bios but still getting Bsod /w sad face errors plus restarts my loptop everytime it shows up and many more... help thank you in Advance!!!

 

Social Support Agent
Social Support Agent
Posts: 5,822
Registered: ‎02-11-2012
Location: PH
Views: 1,416
Message 2 of 6

Re: Problems on G40-70 Windows 8.1

hi xSanzo,

 

Welcome to the Forums.

 

Can you try the following:

1. Download and install all Windows Updates to get the latest patch and bug fixes for the OS.

2. Run a memory and HDD diagnostic scan on the machine using the Lenovo Solutions Center or the Individual Diagnostic Tools.

 

In addition, you could also upload the BSOD dump files for analysis (see locations below):

c:\windows\memory.dmp

c:\windows\minidump\xxx.dmp

 

 

Regards



Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.

Follow us @LenovoSupport on Facebook and Twitter!

xSanzo
Blue Screen Again
Posts: 4
Registered: ‎04-30-2015
Location: PH
Views: 1,410
Message 3 of 6

Re: Problems on G40-70 Windows 8.1

Here is a pic of my another prob

http://i.imgur.com/TLEISsz.png

 

MiniDump Data : https://www.mediafire.com/?m3o3p35oc9n1hjn

Compressed in a zip, Cant upload the memory.dmp file too big its almost 550mb sorry

 

thanks for a fast reply!!

xSanzo
Blue Screen Again
Posts: 4
Registered: ‎04-30-2015
Location: PH
Views: 1,409
Message 4 of 6

Re: Problems on G40-70 Windows 8.1

Just finished updating, updating with the optional updates hope that I will not encounter BSOD again

Scanned the memory diagnostics and got this one : http://i.imgur.com/wAnJ4Bd.png

Social Support Agent
Social Support Agent
Posts: 5,822
Registered: ‎02-11-2012
Location: PH
Views: 1,397
Message 5 of 6

Re: Problems on G40-70 Windows 8.1

hi there,

 

I checked the BSOD dump file and most of the errors are related to the Windows system files (which should be solved by installing all the critical Windows updates).

 

Sample bugcheck analysis using Windows Debugger:

Spoiler

Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\XXX\Downloads\G40-70 DMP\043015-17343-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.16404.amd64fre.winblue_gdr.130913-2141
Machine Name:
Kernel base = 0xfffff802`1ae07000 PsLoadedModuleList = 0xfffff802`1b0cb990
Debug session time: Thu Apr 30 15:55:34.509 2015 (UTC + 8:00)
System Uptime: 0 days 0:19:37.429
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff8021af5b1ea, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!KiIpiInterruptSubDispatch+3a )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8021af5b1ea, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8021b154150
GetUlongFromAddress: unable to read from fffff8021b154208
ffffffffffffffff

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

FAULTING_IP:
nt!KiIpiInterruptSubDispatch+3a
fffff802`1af5b1ea 49014048 add qword ptr [r8+48h],rax

EXCEPTION_PARAMETER2: ffffffffffffffff

BUGCHECK_STR: 0x1E_c0000005_R

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

TRAP_FRAME: ffffd0002705f830 -- (.trap 0xffffd0002705f830)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffffffffffce7 rbx=0000000000000000 rcx=ffffd0002705f982
rdx=ffffd0002705f570 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8021af5b1ea rsp=ffffd0002705fbc0 rbp=ffffd0002705fb80
r8=0200000000000200 r9=000000000000021f r10=fffff78000000208
r11=ffffd0002705fb70 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di ng nz ac po cy
nt!KiIpiInterruptSubDispatch+0x3a:
fffff802`1af5b1ea 49014048 add qword ptr [r8+48h],rax ds:02000000`00000248=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8021af9d45d to fffff8021af54ca0

STACK_TEXT:
ffffd000`2705ef58 fffff802`1af9d45d : 00000000`0000001e ffffffff`c0000005 fffff802`1af5b1ea 00000000`00000000 : nt!KeBugCheckEx
ffffd000`2705ef60 fffff802`1af608c2 : 00000000`01000001 5046504d`00000006 00000200`00080201 0035007b`000002b0 : nt! ?? ::FNODOBFM::`string'+0x382cd
ffffd000`2705f650 fffff802`1af5effe : 00000000`00000000 00000000`00000200 00000001`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
ffffd000`2705f830 00000000`00000200 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x1fe
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x200


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!KiIpiInterruptSubDispatch+3a
fffff802`1af5b1ea 49014048 add qword ptr [r8+48h],rax

SYMBOL_NAME: nt!KiIpiInterruptSubDispatch+3a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 52341cf4

IMAGE_VERSION: 6.3.9600.16404

BUCKET_ID_FUNC_OFFSET: 3a

FAILURE_BUCKET_ID: 0x1E_c0000005_R_nt!KiIpiInterruptSubDispatch

BUCKET_ID: 0x1E_c0000005_R_nt!KiIpiInterruptSubDispatch

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x1e_c0000005_r_nt!kiipiinterruptsubdispatch

FAILURE_ID_HASH: {d1270e15-fab6-00a5-b8c2-9ba6d7d3d4b9}

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

As for the unknown device error in the image, can you follow this guide on how to identify the device and find the correct driver for it.:

 

The memory diagnostics error: http://i.imgur.com/wAnJ4Bd.png seems to be the culprit here. Have you considered contacting lenovo (for service) or the place of purchase (if it's still possible to get a replacement unit) ? It looks like you may need to get a replacement RAM.

 

 

Regards



Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.

Follow us @LenovoSupport on Facebook and Twitter!

xSanzo
Blue Screen Again
Posts: 4
Registered: ‎04-30-2015
Location: PH
Views: 1,389
Message 6 of 6

Re: Problems on G40-70 Windows 8.1

Thanks I've already updated and I'm not experiecing anymore BSOD errors but as you said about the ram error..... I will try to contact them to repair my loptop since it's a gift given to me I really don't know where they bought it.

I will update with this sir!! 

 

Thank you again.

Check out current deals!


Shop current deals

Top Kudoed Authors