BSOD ,Lenovo Laptop G460

[rOnnyJustrOn]

Hi,currently my laptop keep BSOD after startup and its happen randomly.

Mode: Laptop Lenovo G460
Windows: OEM Windows 7 Home Premium 64BIT
Buying this laptop last year so its new.
Never formated.
Using Malwarebytes and AVG free.

Help me pls. i need this laptop to do my assignment.
Thanks very much all specialist.

 

[zigzag3143]

Hi,currently my laptop keep BSOD after startup and its happen randomly.

Mode: Laptop Lenovo G460
Windows: OEM Windows 7 Home Premium 64BIT
Buying this laptop last year so its new.
Never formated.
Using Malwarebytes and AVG free.

Help me pls. i need this laptop to do my assignment.
Thanks very much all specialist.

Most of these were memory corruption caused by a driver. There seem to be a few drivers that are suspect.


Please run memtest for you ram

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86.com - Memory Diagnostic

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



Also Please run driver verifier to find out which driver is at fault.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[rOnnyJustrOn]

Sorry. I'm really noob in Computer stuff.. Can anyone explain step by step.

 

[kuki]

Download memtest iso from the link above, then using "burn disc from ISO image" function in a burning software like Nero or Alcohol 120%, burn the disc.

Reboot your computer and boot from CD, run memory test, 5 or 6 passes.

Repeat the procedure changing the memory stick to another SODIMM slot. Your memory is located in the bottom of your laptop. There should be some screws holding cover of your memory sticks. Here is the tutorial for changing/replacing SODIMM (laptop) memory:
http://www.helpwithpcs.com/upgrading/install-laptop-memory.htm

Then you should change the stick from the slot it was during the first test to the second (Free) one. If you have two memory sticks, remove one of them, run the test, then switch the slot, and then do the same with the second stick. That will give you the answer - either one of the RAM modules or the motherboard is damaged.

 

[rOnnyJustrOn]

My laptop keep crushing now. cant enter windows normaly but no problem on safemode. I'm online using safemode with network. i will buy new ram tonight and put in for test.

 

[rOnnyJustrOn]

Here the latest 3 crash i got together old one.

 

[rOnnyJustrOn]

,...... Problem still,even i change ram

 

[zigzag3143]

Here the latest 3 crash i got together old one.

These were Related to idmwfp.sys Internet Download Manager WFP Driver from Tonec Inc.

I would remove it.

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\051811-72212-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`03453000 PsLoadedModuleList = 0xfffff800`03690e50
Debug session time: Wed May 18 08:25:59.456 2011 (GMT-4)
System Uptime: 0 days 0:01:27.063
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D6, {fffff9802612b000, 0, fffff88006b82081, 0}

Unable to load image idmwfp.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for idmwfp.sys
*** ERROR: Module load completed but symbols could not be loaded for idmwfp.sys

Could not read faulting driver name
Probably caused by : idmwfp.sys ( idmwfp+e081 )

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

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

DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION (d6)
N bytes of memory was allocated and more than N bytes are being referenced.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff9802612b000, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff88006b82081, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036fb0e0
 fffff9802612b000 

FAULTING_IP: 
idmwfp+e081
fffff880`06b82081 668b040a        mov     ax,word ptr [rdx+rcx]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD6

PROCESS_NAME:  DCService.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88002a1ac70 -- (.trap 0xfffff88002a1ac70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8007d81001 rbx=0000000000000000 rcx=fffffa8007d81090
rdx=ffffff001e3a9f70 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88006b82081 rsp=fffff88002a1ae08 rbp=fffff9802612afa0
 r8=0000000000000062  r9=0000000000000016 r10=fffff80003652888
r11=fffffa8007d81030 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
idmwfp+0xe081:
fffff880`06b82081 668b040a        mov     ax,word ptr [rdx+rcx] ds:aeb8:fffff980`2612b000=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003544024 to fffff800034c3700

STACK_TEXT:  
fffff880`02a1ab08 fffff800`03544024 : 00000000`00000050 fffff980`2612b000 00000000`00000000 fffff880`02a1ac70 : nt!KeBugCheckEx
fffff880`02a1ab10 fffff800`034c17ee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000020 : nt! ?? ::FNODOBFM::`string'+0x427f7
fffff880`02a1ac70 fffff880`06b82081 : fffff880`06b7fc29 00000000`00000000 fffff980`2612afa0 fffff880`02a1aeb8 : nt!KiPageFault+0x16e
fffff880`02a1ae08 fffff880`06b7fc29 : 00000000`00000000 fffff980`2612afa0 fffff880`02a1aeb8 fffff980`26cdab30 : idmwfp+0xe081
fffff880`02a1ae10 00000000`00000000 : fffff980`2612afa0 fffff880`02a1aeb8 fffff980`26cdab30 fffff980`26cdab30 : idmwfp+0xbc29


STACK_COMMAND:  kb

FOLLOWUP_IP: 
idmwfp+e081
fffff880`06b82081 668b040a        mov     ax,word ptr [rdx+rcx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  idmwfp+e081

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: idmwfp

IMAGE_NAME:  idmwfp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c45b8d1

FAILURE_BUCKET_ID:  X64_0xD6_VRFK_idmwfp+e081

BUCKET_ID:  X64_0xD6_VRFK_idmwfp+e081

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

 

[rOnnyJustrOn]

Thanks for reply. I remove all the application included IDM. And know what,it fix the BSOD. Gonna used my laptop for 24hour to see if any bsod happen. Thanks very much for your time.

 

[zigzag3143]

Thanks for reply. I remove all the application included IDM. And know what,it fix the BSOD. Gonna used my laptop for 24hour to see if any bsod happen. Thanks very much for your time.

My pleasure keep us in the loop

 

[rOnnyJustrOn]

another bsod