Windows 7 Ultimate (x64) Service Pack 1 (build 7601)
Install Language: English (United States)
System Locale: English (United Kingdom)
Installed: 27/05/2017 13:59:45
Boot Mode: BIOS
3.20 gigahertz AMD Athlon 64 X2 Dual Core 6400+
256 kilobyte primary memory cache
1024 kilobyte secondary memory cache
Multi-core (2 total)
479.99 Gigabytes Usable Hard Drive Capacity
188.96 Gigabytes Hard Drive Free Space
PIONEER DVD-RW DVR-111D ATA Device [Optical drive]
3.5" format removeable media [Floppy drive]
Mass Storage Device USB Device [Hard drive] (320.07 GB) -- drive 1
WDC WD1600AAJS-08L7A0 [Hard drive] (160.04 GB) -- drive 0, s/n WD-WMAV3K088278, rev 03.03E03, SMART Status: Healthy
Gigabyte Technology Co., Ltd. M56S-S3
Enclosure Type: Desktop
Board: Gigabyte Technology Co., Ltd. GA-M56S-S3
Bus Clock: 200 megahertz
BIOS: Award Software International, Inc. F5 01/22/2009
5120 Megabytes Usable Installed Memory
Slot 'A0' has 1024 MB
Slot 'A1' has 2048 MB
Slot 'A2' has 1024 MB
Slot 'A3' has 1024 MB
Im new to all this so hope thats not to much info above, I keep getting a BOSD when watching youtube,playing games or converting video. I have installed speccy system temps are fine.its not over clocked,cleaned inside,run loads of driver software and up dated any drivers i can. Its driving me mad, here is a report of who crashed.
On Mon 25/09/2017 09:34:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092517-16567-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpHpetClockInterrupt+0x8D)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009E7180, 0x1)
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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 that cannot be identified at this time.
Thank you for any help.