Quantcast
Channel: Notebook Boot and Lockup topics
Viewing all articles
Browse latest Browse all 62223

HP DV3 Pavilion Laptop experiencing frequent 'unexpected shutdowns'

$
0
0

Greetings - Please advise if I should be on another board; I am not having lockups per se, but actual shutdowns (without restarting).  I would appreciate your help.  I have run dskchk twice and some bad sectors have been found.  I cannot actually pinpoint what may have happened before the stint of shutdowns; no particular major updates are on the list.  Eventviewer shows a few events in Feb, then up again in May and steady since June, with two just in the past two hours.  I have checked for updated drivers, and apparently they are all up to date.  I run a fan under the computer, and it does not appear to overheat; average temps are in the low-mid 50's F.

 

Please let me know anything I can do to help you to help me.

 

System Info:

 

More details about my computer
ComponentDetailsSubscoreBase scoreProcessorIntel(R) Core(TM)2 Duo CPU T6400 @ 2.00GHz5.53.9Determined by lowest subscoreMemory (RAM)4.00 GB5.5GraphicsNVIDIA GeForce G 105M3.9Gaming graphics2287 MB Total available graphics memory5.4Primary hard disk234GB Free (452GB Total)5.6Windows 7 Home Premium
System


  ManufacturerHewlett-Packard  ModelHP Pavilion dv3 Notebook PC  Total amount of system memory4.00 GB RAM  System type64-bit operating system  Number of processor cores2Storage


  Total size of hard disk(s)466 GB  Disk partition (C:smileyhappy:234 GB Free (452 GB Total)  Disk partition (D:smileyhappy:2 GB Free (14 GB Total)  Media drive (E:smileyhappy:CD/DVDGraphics


  Display adapter typeNVIDIA GeForce G 105M  Total available graphics memory2287 MB  Dedicated graphics memory512 MB  Dedicated system memory0 MB  Shared system memory1775 MB  Display adapter driver version9.18.13.3165  Primary monitor resolution1920x1200  Secondary monitor resolution1366x768  DirectX versionDirectX 10Network


  Network AdapterRealtek PCIe GBE Family Controller  Network AdapterBroadcom 802.11b/g WLAN  Network AdapterBluetooth Device (Personal Area Network)  Network AdapterMicrosoft Virtual WiFi Miniport AdapterNotes


 

EVENT VIEWER

Log Name:      System
Source:        EventLog
Date:          8/12/2014 6:15:20 PM
Event ID:      6008
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DV3T-2000
Description:
The previous system shutdown at 5:47:10 PM on ‎8/‎12/‎2014 was unexpected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="EventLog" />
    <EventID Qualifiers="32768">6008</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-08-12T22:15:20.000000000Z" />
    <EventRecordID>374015</EventRecordID>
    <Channel>System</Channel>
    <Computer>DV3T-2000</Computer>
    <Security />
  </System>
  <EventData>
    <Data>5:47:10 PM</Data>
    <Data>‎8/‎12/‎2014</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>4756</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Binary>DE07080002000C0011002F000A00AB01DE07080002000C0015002F000A00AB01600900003C000000010000006009000000000000B00400000100000000000000</Binary>
  </EventData>
</Event>

+++++++++++++++++++++++++++++++++++++++++
Log Name:      System
Source:        EventLog
Date:          8/12/2014 4:28:24 PM
Event ID:      6008
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DV3T-2000
Description:
The previous system shutdown at 4:14:08 PM on ‎8/‎12/‎2014 was unexpected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="EventLog" />
    <EventID Qualifiers="32768">6008</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-08-12T20:28:24.000000000Z" />
    <EventRecordID>373846</EventRecordID>
    <Channel>System</Channel>
    <Computer>DV3T-2000</Computer>
    <Security />
  </System>
  <EventData>
    <Data>4:14:08 PM</Data>
    <Data>‎8/‎12/‎2014</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>8593</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Binary>DE07080002000C0010000E0008003C03DE07080002000C0014000E0008003C03600900003C000000010000006009000000000000B004000001000000C12C0000</Binary>
  </EventData>
</Event>

++++++++++++++++++++++++++++++++++++++

Error    8/12/2014 6:15:20 PM    EventLog    6008    None
Error    8/12/2014 
4:14:08 PM    EventLog    6008    None
Error    8/6/2014 4:07:06 PM    EventLog    6008    None
Error    7/30/2014 8:50:19 AM    EventLog    6008    None
Error    7/28/2014 8:36:14 AM    EventLog    6008    None
Error    7/27/2014 7:50:03 PM    EventLog    6008    None
Error    7/23/2014 11:26:45 PM    EventLog    6008    None
Error    7/22/2014 4:22:36 PM    EventLog    6008    None
Error    7/21/2014 8:15:26 PM    EventLog    6008    None
Error    7/18/2014 4:11:03 PM    EventLog    6008    None
Error    7/17/2014 1:55:11 PM    EventLog    6008    None
Error    7/16/2014 7:12:19 AM    EventLog    6008    None
Error    7/13/2014 5:27:24 PM    EventLog    6008    None
Error    7/9/2014 7:53:17 AM    EventLog    6008    None
Error    7/8/2014 4:21:16 PM    EventLog    6008    None
Error    7/5/2014 7:48:32 AM    EventLog    6008    None
Error    6/28/2014 7:32:31 AM    EventLog    6008    None
Error    6/25/2014 12:16:18 PM    EventLog    6008    None
Error    6/23/2014 10:48:36 PM    EventLog    6008    None
Error    6/21/2014 1:29:57 PM    EventLog    6008    None
Error    6/18/2014 5:53:24 PM    EventLog    6008    None
Error    6/16/2014 8:27:04 PM    EventLog    6008    None
Error    6/11/2014 8:00:30 PM    EventLog    6008    None
Error    6/2/2014 8:32:33 PM    EventLog    6008    None
Error    6/1/2014 9:54:27 AM    EventLog    6008    None
Error    6/1/2014 8:03:20 AM    EventLog    6008    None
Error    5/31/2014 6:20:25 PM    EventLog    6008    None
Error    5/20/2014 7:25:04 PM    EventLog    6008    None
Error    5/10/2014 12:44:48 PM    EventLog    6008    None
Error    2/11/2014 11:35:46 AM    EventLog    6008    None
Error    2/11/2014 11:21:01 AM    EventLog    6008    None
Error    2/7/2014 8:54:00 PM    EventLog    6008    None
Error    2/7/2014 6:15:31 PM    EventLog    6008    None
Error    12/12/2013 10:43:47 PM    EventLog    6008    None

++++++++++++++++++++++++++++++++++++++++

 

 


System Information (local)



computer name: DV3T-2000
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: HP Pavilion dv3 Notebook PC, Hewlett-Packard, Compal, 306D
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU T6400 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4260323328 total
VM: 2147352576, free: 1939087360




"Who-Crashed" Crash Dump Analysis



Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 7/28/2014 12:35:14 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072814-26457-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0xFFFFF6FC50070078, 0xFFFFFFFFC0000185, 0x108147880, 0xFFFFF8A00E00F000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Fri 7/18/2014 8:09:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071814-31075-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0xFFFFF6FB41FFBF68, 0xFFFFFFFFC0000185, 0x71E01884, 0xFFFFF683FF7ED788)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 7/9/2014 11:52:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070914-46207-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0xFFFFF6FC500018B0, 0xFFFFFFFFC0000185, 0x47E35880, 0xFFFFF8A000316000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 7/8/2014 8:19:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070814-27378-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0xFFFFF6FC5002F3F0, 0xFFFFFFFFC0000185, 0x10D83F880, 0xFFFFF8A005E7E000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 6/28/2014 11:31:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062814-28064-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0xFFFFF6FC50005DF8, 0xFFFFFFFFC0000185, 0x127D4E820, 0xFFFFF8A000BBF008)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 6/25/2014 1:02:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062514-24507-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0xFFFFF6FC50045E70, 0xFFFFFFFFC0000185, 0x133BCD820, 0xFFFFF8A008BCE29C)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 6/21/2014 5:28:58 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062114-30544-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0xFFFFF6FC5001F030, 0xFFFFFFFFC0000185, 0x78B8B880, 0xFFFFF8A003E06034)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 6/18/2014 9:52:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061814-26660-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0xFFFFF6FB41FFBFC0, 0xFFFFFFFFC0000185, 0x11D105884, 0xFFFFF683FF7F8000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


Conclusion


8 crash dumps have been found and analyzed. No offending third party drivers have been found.

 

 

---------THANK YOU IN ADVANCE FOR YOUR TIME AND ASSISTANCE!---------


Viewing all articles
Browse latest Browse all 62223

Trending Articles