It looks like it's the sound driver. Uninstall it, and run the system for a long period, stress it and try to force it to BSOD again. If it doesn't fail, then maybe you should look into getting a cheap PCI sound card that is newer and supported by Windows 7. Good job, and good luck. Let us know how it goes.
Well unfortunately still haven't solved problem. I uninstalled the sound but still got BSOD last night whilst running virus check, then twice this morning just booting up & trying to go into emails. Below is results from "whocrashed" software;
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 09/05/2012 08:56:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050912-39718-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5B68)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880066CD028, 0xFFFFF880066CC880, 0xFFFFF80002AEFA11)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 Wed 09/05/2012 08:56:05 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5B68)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880066CD028, 0xFFFFF880066CC880, 0xFFFFF80002AEFA11)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 Wed 09/05/2012 08:50:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050912-43281-01.dmp
This was probably caused by the following module: hal.dll (hal+0xDBC6)
Bugcheck code: 0xA (0x200, 0x2, 0x1, 0xFFFFF80002ACCF39)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 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 Wed 09/05/2012 08:44:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050912-44906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0x200, 0x2, 0x1, 0xFFFFF80002AD8F39)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 08/05/2012 19:31:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050812-50171-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5B68)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88003834EE8, 0xFFFFF88003834740, 0xFFFFF80002AF0A11)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 08/05/2012 18:51:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050812-40625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002AE1B6C)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 Intel CPU generated a trap and the kernel failed to catch this trap.
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 08/05/2012 18:06:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050812-58421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0x200, 0x2, 0x1, 0xFFFFF80002A8DF39)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.
It appears that the last supported OS is Microsoft Windows 2000 Pro. Looking at this page, there are a large amount of updates and drivers that you could install and run in compatibility mode when installing them to try. It also seems that there are firmware updates for your GPU, and HDDs. There is also a BIOS update. If none of these resolve your issues, move to the next steps.
First, please remove all peripherals and non essentials from the system. Then please open up your PC and unplug and re-seat all connections. If necessary, replace any cables running to your HDD. Also, please remove your RAM, blast the slots with canned air and re-seat them, ensuring that they are seated properly and locked in with the retaining tabs. Please follow these ESD prevention measeures while doing so;
1. It is a good idea to buy an anti-static wristband, and follow the instructions for use.(They are sold at most electronics stores.) If you are going to do quite a lot of bench work, you might do well to invest in an anti-static mat.
2. If you don't have a wristband, you are not necessarily out of luck. Assuming that your PC is grounded, you can ground yourself by just keeping one hand in contact with the bare metal frame (not a painted or coated surface) of the computer case. Keep the PC power cord plugged in to a (3-prong) grounded outlet and turn off the rocker switch on the back of the power supply. If the power supply does not have a switch on the back, this won't work, however. Never work on a PC with the power on. In that case, you should buy an anti-static band or try another method of grounding.
3. As an alternative, alter a standard 3-conductor power cord by snipping off the two flat blades, leaving only the grounding portion of the plug. Or simply purchase a cord like this from an electronics supply house. This accomplishes the same thing as turning off the rocker switch.
4. You can employ an LCD Static Discharger. As a simple measure, you can hang it on your key ring and just dangle it. This is less reliable, but when it touches a ground, it should discharge the static electricity. Procedure：①Lightly touch the oval button with a finger. ②Make sure that the end of the conductive material touches a grounded conductor. (such as vehicle, human body, computer, metal or other) to release static electricity, and observe the LCD display.
5. Some people claim that damage can be reduced by wearing little or no clothing, it is said that the less cloth that is in contact with your body, the less static is produced, though these claims remain unproven.
The average person can carry up to 25,000 volts of static energy at any given time. This sounds like a lot, but because the current level is low, you usually won't notice it. Follow safe ESD procedures any time you open a computer.
If the equipment is cold, wait until it has reached room temperature. ESD builds up much faster when it's cold and dry (low humidity).
If you don't take steps to prevent ESD, you may regret it. Your computer can sustain serious damage without you knowing it. CPUs and memory chips of any kind are highly vulnerable to ESD. If you fry your PC with static electricity, you may soon start to notice random memory errors, blue screens, and lock-ups. Normally, you can't see (or even feel) ESD, but it is almost always there, so be sure to do the right thing. Your PC will thank you!
Try not to open up computers while on thick carpets, petting long-haired pets, dressing, emptying the dryer, etc. Use common sense; don't do anything that would cause you to get a shock from touching something made of metal.
Second, I know you said that you ran Memtest86, please do so again. This time, wait for the BSOD to occur and then upon reboot, run Memtest86. Leave it running for as long as you can. We find, very often, that memory does not always show as bad in Memtest86. There have been instances where an OP has had to run Memtest86 numerous times before the offending memory errors are caught.
Third, please run a disk check. You may have already done so, but please do it again.
Another thing. The memory you are using may not be compatible with your processor.
This is from the HP Specs; The Intel E7525 chipset supports ECC Registered 400 MHz (PC2-3200) DDR2 memory only.
This is from your system report;
DIMM # 1
SMBus address 0x50
Memory type DDR2
Module format Regular RDIMM
Manufacturer (ID) Hyundai Electronics (AD00000000000000)
Size 1024 MBytes
Max bandwidth PC2-3200 (200 MHz)
Part number HYMP512R72BP4-E3
Serial number 04008044
Manufacturing date Week 24/Year 06
Number of banks 1
Data width 72 bits
Correction ECC
Nominal Voltage 1.80 Volts
EPP no
XMP no
JEDEC timings table CL-tRCD-tRP-tRAS-tRC @ frequency
JEDEC #1 3.0-3-3-8-11 @ 200 MHz
JEDEC #2 4.0-3-3-8-11 @ 200 MHz
JEDEC #3 5.0-3-3-8-11 @ 200 MHz
DIMM # 2
SMBus address 0x51
Memory type DDR2
Module format Regular RDIMM
Manufacturer (ID) Hyundai Electronics (AD00000000000000)
Size 1024 MBytes
Max bandwidth PC2-3200 (200 MHz)
Part number HYMP512R72BP4-E3
Serial number 00006024
Manufacturing date Week 24/Year 06
Number of banks 1
Data width 72 bits
Correction ECC
Nominal Voltage 1.80 Volts
EPP no
XMP no
JEDEC timings table CL-tRCD-tRP-tRAS-tRC @ frequency
JEDEC #1 3.0-3-3-8-11 @ 200 MHz
JEDEC #2 4.0-3-3-8-11 @ 200 MHz
JEDEC #3 5.0-3-3-8-11 @ 200 MHz
DIMM # 3
SMBus address 0x52
Memory type DDR2
Module format Regular RDIMM
Manufacturer (ID) Hyundai Electronics (AD00000000000000)
Size 1024 MBytes
Max bandwidth PC2-3200 (200 MHz)
Part number HYMP512R72BP4-E3
Serial number 00007053
Manufacturing date Week 24/Year 06
Number of banks 1
Data width 72 bits
Correction ECC
Nominal Voltage 1.80 Volts
EPP no
XMP no
JEDEC timings table CL-tRCD-tRP-tRAS-tRC @ frequency
JEDEC #1 3.0-3-3-8-11 @ 200 MHz
JEDEC #2 4.0-3-3-8-11 @ 200 MHz
JEDEC #3 5.0-3-3-8-11 @ 200 MHz
DIMM # 4
SMBus address 0x53
Memory type DDR2
Module format Regular RDIMM
Manufacturer (ID) Hyundai Electronics (AD00000000000000)
Size 1024 MBytes
Max bandwidth PC2-3200 (200 MHz)
Part number HYMP512R72BP4-E3
Serial number 00006114
Manufacturing date Week 24/Year 06
Number of banks 1
Data width 72 bits
Correction ECC
Nominal Voltage 1.80 Volts
EPP no
XMP no
JEDEC timings table CL-tRCD-tRP-tRAS-tRC @ frequency
JEDEC #1 3.0-3-3-8-11 @ 200 MHz
JEDEC #2 4.0-3-3-8-11 @ 200 MHz
JEDEC #3 5.0-3-3-8-11 @ 200 MHz
If you are unable to change the timings and frequency in the BIOS, do you have another set that matches the requirements that you could test?
I know this is a lot of info. Please do them one step at a time and test for stability after doing each. Be sure to note any changes in stability as a result of each step and post back with the results.
Happy hunting.
Yes the HP site doesn't have any specific drivers for my model & win7. I have searched around & updated various drivers & the system is more stable - only a handful of BSOD a day now, still unacceptable, but better. I've disabled the on-board sound & installed a soundcard today. Next I'm going to change the RAM.
Sounds like you are making progress. Keep at it and let us know how it goes. Uploading the .dmps would still be helpful.
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 11/05/2012 09:34:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051112-49812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1 (0x76DAFC0A, 0x0, 0x10000, 0xFFFFF88007043CA0)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 11/05/2012 09:34:27 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1 (0x76DAFC0A, 0x0, 0x10000, 0xFFFFF88007043CA0)
Error: APC_INDEX_MISMATCH
Bug check description: This indicates that there has been a mismatch in the APC state index.
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 11/05/2012 08:53:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051112-39171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1 (0xFFFFF80002D80762, 0x0, 0x10000, 0x0)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 10/05/2012 15:41:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051012-53359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002A7A171, 0xFFFFF880021EA240, 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 10/05/2012 11:51:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051012-45750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1 (0x77C7FC0A, 0x0, 0x1, 0xFFFFF8800638DCA0)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 10/05/2012 11:14:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051012-39390-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5B68)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880068D3F08, 0xFFFFF880068D3760, 0xFFFFF80002AAEA11)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 Thu 10/05/2012 09:30:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051012-38953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002A8D17C, 0xFFFFF8800658E150, 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 10/05/2012 09:00:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051012-39984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1 (0x775B018A, 0x0, 0x1, 0xFFFFF880064A7CA0)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
Thanks macca747, but we do need the full pkg, please follow these instructions.
One more thing. I asked previously about your CPU temps. Before you proceed, please download and install Hardware Monitor and run Prime95 for a bit to see what your temps reach and if any errors occur while running Prime95. Please post screenies for both.
Running the full pkg has crashed my system twice now, just when it was finishing both times.
I looked into the RAMtest software you said you used. It appears that it is not widely supported because it only tests the RAM that is not in use by Windows. Please run Memtest86+ to test all of the RAM.
- If you are overclocking any hardware, please stop.
WARNING: The steps that follow can void your warranty!!!
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
- Shut down and turn off your computer.
- Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
- Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
- Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
Once these steps have been followed, it is safe to remove and replace components within your computer.
I would also recommend checking Windows for corruption.
- Check Windows for corruption. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.
Quote