HP 4310s Problems
 

look sorry if this is not meant to be on this website but im struggling here

i got a hp probook 4310s the problem is:

Blue Screen/Black screen of death (and random crashes)

so i done fresh re install 15 with windows 7 still no luck

wat happens is i boot up computer i get blue screen then a reboot happens 3 times and then it works fine then when im done i shut the lid on the lap top and when i open it to use it the display comes up and 2mins later it blue screen of death/black screen/freeze i put ubuntu on it it works fine no crashes nothing like that i can shut the lid and open it no problem but im not a big fan of ubuntu 11.04 i was just running tests

i have done:

Change hard drive
Change Ram Striped it down took dust out
reinstalled it 15 times for different windows 7 discs Ultimate/Basic/Premium
Updated all drivers

And Nothing

This Laptop has no warranty all this laptop is doing is costing me money

Ive tried everything wondering what you ps3hax members can help

The BSOD gives a 0x......... error code, can you post it?

Example:
http://social.microsoft.com/Forums/getfile/2535/

In this BSOD the error code is: 0x0000007B

You can set to not restart after BSOD with the F8 option at startup, where you also set to boot in save mode.

Did you also check/update the Bios?

ive updated bios and i went to crash dump folder theres about 50 DMP files i dont know what to do im sick of it crashing its got to be a driver problem but i updated evrey driver ubuntu works fine but when i was using it it wasent the same as windows

what is the stop code?
you can download bluescreenview and run it.
it will show your dump files, stop code, plus the most likely driver causing the issue.

http://www.nirsoft.net/utils/bluescreenview.zip

i downloaded bluescreen viewer and heres what i get

http://img4.imageshack.us/img4/5718/crashes.jpg

can you try the program Whocrashed?
http://www.resplendence.com/whocrashed

yh i got


Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 15/12/2011 13:26:53 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 23:05:01
This was probably caused by the following module: atikmdag.sys (atikmdag+0x24420)
Bugcheck code: 0xEA (0xFFFFFFFF87517538, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. THREAD_STUCK_IN_DEVICE_DRIVER




On Wed 14/12/2011 14:21:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121411-19063-01.dmp
uptime: 00:00:31
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
Bugcheck code: 0xD4 (0xFFFFFFFF8EFC4CC8, 0x2, 0x1, 0xFFFFFFFF82AB0C1E)
Error: SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver did not cancel pending operations before unloading.
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 Tue 13/12/2011 14:09:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121311-20607-01.dmp
uptime: 1 day, 04:29:09
This was probably caused by the following module: atikmdag.sys (atikmdag+0x24420)
Bugcheck code: 0x100000EA (0xFFFFFFFF877D4848, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. THREAD_STUCK_IN_DEVICE_DRIVER_M




On Mon 12/12/2011 09:39:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121211-19718-01.dmp
uptime: 00:02:52
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
Bugcheck code: 0xD4 (0xFFFFFFFF8EFC1CC8, 0x2, 0x1, 0xFFFFFFFF82A85C1E)
Error: SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver did not cancel pending operations before unloading.
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 12/12/2011 09:36:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121211-19032-01.dmp
uptime: 17:28:44
This was probably caused by the following module: atikmdag.sys (atikmdag+0x24420)
Bugcheck code: 0x100000EA (0xFFFFFFFF85972710, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. THREAD_STUCK_IN_DEVICE_DRIVER_M




On Sun 11/12/2011 12:24:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121111-18829-01.dmp
uptime: 18:24:33
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
Bugcheck code: 0xD4 (0xFFFFFFFF8E3F4CC8, 0x2, 0x1, 0xFFFFFFFF82A81C1E)
Error: SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver did not cancel pending operations before unloading.
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 Sat 10/12/2011 17:59:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121011-22370-01.dmp
uptime: 11:36:03
This was probably caused by the following module: atikmdag.sys (atikmdag+0x24420)
Bugcheck code: 0x100000EA (0xFFFFFFFF85A7E438, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. THREAD_STUCK_IN_DEVICE_DRIVER_M




On Sat 10/12/2011 06:22:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121011-27502-01.dmp
uptime: 14:34:57
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
Bugcheck code: 0xD4 (0xFFFFFFFF8EFE2CC8, 0x2, 0x1, 0xFFFFFFFF82A70C1E)
Error: SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver did not cancel pending operations before unloading.
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 Fri 09/12/2011 15:47:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120911-39608-01.dmp
uptime: 21:05:47
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
Bugcheck code: 0xD4 (0xFFFFFFFF8EFE2CC8, 0x2, 0x1, 0xFFFFFFFF82A82C1E)
Error: SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver did not cancel pending operations before unloading.
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 08/12/2011 18:41:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120811-18907-01.dmp
uptime: 1 day, 05:54:14
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
Bugcheck code: 0xD4 (0xFFFFFFFF8EFD5CC8, 0x2, 0x1, 0xFFFFFFFF82A86C1E)
Error: SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver did not cancel pending operations before unloading.
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 Wed 07/12/2011 12:44:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120711-21949-01.dmp
uptime: 23:28:58
This was probably caused by the following module: watchdog.sys (watchdog+0x1276)
Bugcheck code: 0x113 (0x6, 0xFFFFFFFF87709000, 0x0, 0x0)
Error: VIDEO_DXGKRNL_FATAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the dxg kernel has detected a violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Tue 06/12/2011 13:09:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120611-26083-01.dmp
uptime: 1 day, 00:31:31
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
Bugcheck code: 0xD4 (0xFFFFFFFF8E3E8CC8, 0x2, 0x1, 0xFFFFFFFF82A79C1E)
Error: SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver did not cancel pending operations before unloading.
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 05/12/2011 10:58:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120511-31980-01.dmp
uptime: 23:36:15
This was probably caused by the following module: atikmdag.sys (atikmdag+0x24420)
Bugcheck code: 0x100000EA (0xFFFFFFFF877EB030, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. THREAD_STUCK_IN_DEVICE_DRIVER_M




On Sun 04/12/2011 11:21:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120411-16910-01.dmp
uptime: 00:00:39
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
Bugcheck code: 0xD4 (0xFFFFFFFF8E5E1CC8, 0x2, 0x1, 0xFFFFFFFF82AA9C1E)
Error: SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver did not cancel pending operations before unloading.
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 Sun 04/12/2011 11:20:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120411-18439-01.dmp
uptime: 00:00:30
This was probably caused by the following module: watchdog.sys (watchdog+0x1276)
Bugcheck code: 0x113 (0x6, 0xFFFFFFFF859A1000, 0x0, 0x0)
Error: VIDEO_DXGKRNL_FATAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the dxg kernel has detected a violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

15 crash dumps have been found and analyzed. 5 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Sounds like a GPU problem...

have you cleaned all fans inside the laptop, especially the GPU fan?

If they are clean, is it possible to login to Win7 (after a few reboots maybe) and run this:
http://freestone-group.com/video-car...ility-test.htm

Do you know if the laptop has a MXM or MXM-II/III slot for the ATI graphic card?
If not and the GPU is faulty, maybe a reflow will help?

erm i not sure about the MXM or MXM-II ect
************* [ - Post Merged - ] *************
i dont get it coz it dose not crash on ubuntu 11.04 by i pefer windows

I'm not familiar with ATI, maybe Ubuntu uses the framebuffer (more CPU) and Windows doesn't?

Did you install the standard Windows ATI driver or the driver from the HP site?