icsbudapest
asked on
Multiple BSOD in Windows 7
I am getting multiple BSOD on this computer. (It is a client's computer) I have attached a table showing the multiple minidumps. Crashes seem random. I am unsure where to start on this one. The OS was fresh install. Files were moved via microsoft's easy file transfer stuff.I have done a diskcheck and a memory check without any problems.
Here is the configuration:
Windows 7 Pro, fully updated
Gigabyte P55M-UD2 (newest bios)
Intel i3 540
Ati Raedon HD 4500, 1Gb (CCC v. 10.2)
Giel Value 4GB RAM
Sata Running in ide mode
HP Officejet V45
report.html
Here is the configuration:
Windows 7 Pro, fully updated
Gigabyte P55M-UD2 (newest bios)
Intel i3 540
Ati Raedon HD 4500, 1Gb (CCC v. 10.2)
Giel Value 4GB RAM
Sata Running in ide mode
HP Officejet V45
report.html
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I ran Memtest86+ already, but only 1 pass. I am running it again and will let it go for a few hours. I will then run a lower level diagnostic on the hdd as suggested. May play with the ram swap as well. Based on the posts above, if the RAM and HDD don't show problems then it will probably be a motherboard issue?
It could be one of many possibilities including drivers, hardware, disk errors, corruption etc. The motherboard may be one of the causes. But of course, tests should be runned first to accurately diagnose the problem.
ASKER
I let memtest86+ run all night and it is showing 1027 errors in 27 passes. Is there any way to save the error reports in memtest86+? Anything I should look for in particular in the results before shutting down? (I don't have much experience with memtest86+.) If nothing else I'll take a digital photo of the screen.
"I let memtest86+ run all night and it is showing 1027 errors in 27 passes"
did you try using another RAM? yours RAM might be bad buy new RAM
there can be one last test for RAM
boot system with Linux live CD and see if it can take you till its desktop or not
did you try using another RAM? yours RAM might be bad buy new RAM
there can be one last test for RAM
boot system with Linux live CD and see if it can take you till its desktop or not
I haven't heard of any methods to capture the screenshot of Memtest86+, but it is okay to post the screenshot if it isn't so blur. As for the RAM,try testing it 1 at a time. For the faulty RAM, take it out and wipe the gold platings with dry tissues or anything equivalent and try testing it again. Sometimes, it may because the RAM is dirty (physically).
ASKER
Now I am doing a test of the memory one at a time, using the same slot. Meanwhile here is a screenshot. The errors seem to happen during test 7.
2010-04-14-11.15.54.jpg
2010-04-14-11.15.54.jpg
ASKER
With single stick memtest86+ Ram test, Stick A had 6 clean passes, Stick B (In same slot) had multiple errors in tests 5 and 7. Looks like we have the culprit! I will return the faulty RAM. I will get some new RAM and once things are running, I will come back and confirm that this solved the problem.
Kudos to you for finding the problem!
ASKER
Bad memory replaced. Running stable now. Thanks for the help.
ASKER
On Tue 4/13/2010 8:30:48 AM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xC2 (0x7, 0x1097, 0x0, 0x829BDDC8)
Error: BAD_POOL_CALLER
Dump file: C:\Windows\Minidump\041310
file path: C:\Windows\system32\ntkrnl
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 4/11/2010 6:53:30 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x82CA78FB, 0x8DB8E884, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_
Dump file: C:\Windows\Minidump\041110
file path: C:\Windows\system32\ntkrnl
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 4/11/2010 4:01:49 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1A (0x41790, 0xC080204C, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\041110
file path: C:\Windows\system32\ntkrnl
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Thu 4/8/2010 5:14:03 PM your computer crashed
This was likely caused by the following module: hardware_ram
Bugcheck code: 0x1A (0x8887, 0x84AF9234, 0x84B01DC4, 0x205)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\040810
On Thu 4/8/2010 5:06:27 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1A (0x31, 0x85762B20, 0x8E0FB000, 0x97238DC7)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\040810
file path: C:\Windows\system32\ntkrnl
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 4/4/2010 7:11:26 PM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0xC08A2, 0x0, 0x0, 0x0)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\040410
file path: C:\Windows\system32\driver
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 4/4/2010 6:31:48 PM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0xC08A2, 0x0, 0x0, 0x0)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\040410
file path: C:\Windows\system32\driver
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 4/4/2010 6:30:08 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xBE (0x93FFCCB0, 0x7D002121, 0x8E56FAE8, 0xB)
Error: ATTEMPTED_WRITE_TO_READONL
Dump file: C:\Windows\Minidump\040410
file path: C:\Windows\system32\ntkrnl
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 4/4/2010 6:27:12 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xA (0xFFFFFFFF, 0x2, 0x1, 0x82C13839)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\040410
file path: C:\Windows\system32\ntkrnl
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 4/4/2010 7:31:06 AM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1A (0x3452, 0x7600F000, 0xC0804DC4, 0x6430A424)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\040410
file path: C:\Windows\system32\ntkrnl
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 4/4/2010 7:21:10 AM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xC2 (0x7, 0x1097, 0x0, 0xA1A3BDC8)
Error: BAD_POOL_CALLER
Dump file: C:\Windows\Minidump\040410
file path: C:\Windows\system32\ntkrnl
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 4/4/2010 7:19:02 AM your computer crashed
This was likely caused by the following module: dxgkrnl.sys
Bugcheck code: 0x50 (0xC2C95BC3, 0x1, 0x91F58DC6, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_ARE
Dump file: C:\Windows\Minidump\040410
file path: C:\Windows\system32\driver
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 4/4/2010 7:17:57 AM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xA (0xC0DB8F44, 0x0, 0x1, 0x82C86358)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\040410
file path: C:\Windows\system32\ntkrnl
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Fri 4/2/2010 3:27:29 PM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1A (0x41284, 0xFC593001, 0x361, 0x82230000)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\040210
file path: C:\Windows\system32\win32k
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Wed 3/31/2010 6:26:41 AM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x50 (0xC041D950, 0x0, 0x82CCD9B5, 0x9)
Error: PAGE_FAULT_IN_NONPAGED_ARE
Dump file: C:\Windows\Minidump\033110
file path: C:\Windows\system32\ntkrnl
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.