HP Laptop BSOD problem

May 28, 2012 at 14:31:35
Specs: Windows 7 Ultimate, Core i5 / 8GB
Does it randomly. Sometimes its fine for a couple of days then the next day it will do it 3 times within 30 minutes.

I have the dmp file but not sure how to read it.

https://skydrive.live.com/redir?res...

HP Laptop G62-149wm
Windows 7 Ultimate
Core i5 2.5GHz
8GB DDR3
120GB Intel 520 ssd


See More: HP Laptop BSOD problem

Report •

#1
May 28, 2012 at 17:42:04
*clicks link*
This item might not exist or is no longer available
This item might have been deleted, expired, or you might not have permission to view it. Contact the owner of this item for more information.

How To Ask Questions The Smart Way


Report •

#2
May 28, 2012 at 23:26:36
Minidump files have to be "translated".

This program does that. It automatacally finds the minidump files.

Search the web for: WhoCrashed
, download it, install it, run it, click on Analyze in the top bar.
.....

If a blue screen appears and stays on the screen.

Copy down the things that are unique in the message and post them here.

E.g.

STOP: 0Xx00000xx (we don't need the stuff in brackets beside that)

A_TEXT_STRING_ALL_IN_CAPITALS

There may be a problem file named at the end of the text.

There may be a link to More info or similar - if so, click on it to see if it names a problem file.


Report •

#3
May 28, 2012 at 23:57:50
Its better to copy the error you are facing and pasting it right here so that we can help you in a better way. There are a lot of Stop Errors so it would be easy to solve your computer's problem by reading the same.

Solving Technical queries is my passion and I just Love it !!


Report •

Related Solutions

#4
June 12, 2012 at 17:19:37
I downloaded WhoCrashed and this is the results it brought up:


On Mon 5/28/2012 11:57:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052812-11341-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 5/28/2012 11:57:49 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheck+0x0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 5/28/2012 8:59:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052812-11076-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002A9D889, 0xFFFFF88006FB7170, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 5/28/2012 6:54:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052812-11590-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002ACE3F0, 0xFFFFF88008536110, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 5/24/2012 12:55:41 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052312-14664-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x34 (0x50853, 0xFFFFF8800337E818, 0xFFFFF8800337E070, 0xFFFFF800029279C3)
Error: CACHE_MANAGER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a problem occurred in the file system's cache manager.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 5/24/2012 12:46:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052312-10530-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800028BAEA7, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 5/24/2012 12:18:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052312-21325-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800028B1D03, 0xFFFFF8800592FDF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

I havent had a BSOD in awhile but i also havent been using this laptop much either. Hope this helps on what may be causing it.

HP Laptop G62-149wm
Windows 7 Ultimate
Core i5 2.5GHz
8GB DDR3
120GB Intel 520 ssd


Report •

#5
June 12, 2012 at 21:35:45
"The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. "

= Windows sometimes can't tell you actually what caused the problem, so it names a file that is affected by the problem instead. That's been the case since Win 95.

You're not likely to find an answer to what is causing the problem unless you make note of under what circumstances you got the error, then search on the web using
e.g. KMODE_EXCEPTION_NOT_HANDLED ntoskrnl.exe
....then look in the "hits" for the same or similar circumstances.


Report •

#6
June 15, 2012 at 04:39:33
This smells like hardware to me. Run a memory tester, and maybe a CPU tester.

How To Ask Questions The Smart Way


Report •

#7
June 15, 2012 at 07:23:50
Razor2.3

If it were a memory problem or a CPU problem he would be getting BSODs frequently.


Report •

#8
June 15, 2012 at 08:38:25
Like, "3 times within 30 minutes?" Also, some of the parameters in the BSOD's he's posted don't make any sense.

How To Ask Questions The Smart Way


Report •

#9
June 15, 2012 at 13:48:22
Razor2.3

When f21403 ran WhoCrashed, he or she had the BSODs that produced a minidump file that was saved in Windows ONLY on Mon 5/28/2012 and Thu 5/24/2012 - not before, or between, or since those dates.

The automatic saving of minidump files in Windows is either enabled (probably the default setting) or disabled - Windows doesn't spontaneously save them, not save them, at random.

Some of, or ALL of, the parameters in the brackets, e.g. (0xC0000005, 0xFFFFF800028B1D03, 0xFFFFF8800592FDF0, 0x0)
are usually unique to the particular computer and useless regarding searching with them on the internet for a cause of the problem.


Report •

#10
June 15, 2012 at 14:34:48
The parameters are there for a reason. Typically the first parameter is the cause of the exception, 2 and 3 are memory pointers (typically pointing to the bad code and/or the exception record), and 4 is generally unused. The meaning and use of the parameters for each BSOD is included in the help file for the Debugging tools for Windows, which is now part of the Win SDK. If you don't want to bother with the SDK just to get at a help file, and I don't blame you, there's always the on-line version at MSDN. It's useful to look at so you can say, "code doesn't live at 0x0, something has gone horribly wrong."

How To Ask Questions The Smart Way


Report •

Ask Question