Frequent BSODs

[Regnak]

I've suddenly been getting a lot of BSODs at apparently random times lately. They've occurred while I wasn't running any particular applications and lately they have been occurring during start up as well.

My PC is running Windows Home Premium x64 with service pack 2. I think the motherboard is an an Asus P5QPL Pro motherboard (sorry, I'll have to check that again soon) with an Intel Core 2 Duo CPU and an Asus HD4850 512mb PCI Express Graphics Card.

I suspect that there is a problem with my graphics card but I wanted to be sure it wasn't something else. I have updated the graphics driver but am still having problems.

Below is the crash dump analysis from WhoCrashed:
---------------------------------

On Tue 5/4/2010 1:08:41 AM your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFA60046196AC, 0xFFFFFA60005AEC68, 0xFFFFFA60005AE640)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\Mini050410-01.dmp

On Mon 5/3/2010 6:57:26 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0xB3E33, 0x2, 0xB3DF2)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\Mini050310-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
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 5/2/2010 5:35:16 AM your computer crashed
This was likely caused by the following module: atikmdag.sys
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFA600257FC66, 0xFFFFFA60039D7A08, 0xFFFFFA60039D73E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\Mini050210-02.dmp
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver

On Sun 5/2/2010 5:20:24 AM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0xD3 (0xFFFFF960002E4D43, 0x2, 0x0, 0xFFFFF800026D3F35)
Error: DRIVER_PORTION_MUST_BE_NONPAGED
Dump file: C:\Windows\Minidump\Mini050210-01.dmp
file path: C:\Windows\system32\win32k.sys
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 Thu 4/29/2010 12:22:59 PM your computer crashed
This was likely caused by the following module: watchdog.sys
Bugcheck code: 0x50 (0xFFFFFA60AE83CC00, 0x1, 0xFFFFFA6002B571AC, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\Mini042910-01.dmp
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog 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 Thu 4/22/2010 7:19:04 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800026BA3E8, 0x0, 0x492DCD0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\Mini042210-02.dmp
file path: C:\Windows\system32\ntoskrnl.exe
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/22/2010 7:14:14 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000269EA4E, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\Mini042210-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
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.

---------------------------------

Thanks.

 

[stoneys-nutz]

Hello Regnak,
I think i would start by removing all but one stick of ram and trying it, see if you get a BSOD with just one stick at a time, if all goes well swap the stick over and try another one, this will eliminate the ram one way or the other.
Check the temps of the MB and your graphics card too.
Do you have another card you could try if you think that is the problem ?.

Read this article through and see if there are any drivers that may be causing this.

How to identify a buggy device driver on Windows Vista | Vista Rewired

Just to make sure your system files are OK open a command prompt as administrator and type sfc/scannow press enter and let it scan, if errors are found you may need to scan more than once.
Also, go to your HDD makers site and download the diagnostic software for your HDD, run this and check for errors.

Try this and post your results, good luck.

 

[Ragscot]

Hello Regnak,

I read with sympathy your problems with the old BSOD. This happened to me
early last year. My basic setup is Windows Home Premium 32bit, Intel Core
Duo in a Zoostorm Desktop PC.

For the first time in many years I took out extended warranty on this machine
which, in this instance saved me a packet. The BSOD appeared randomly but mostly
whilst running Microsoft FSX. After a couple of hours the BSOD appeared. The
frequency of crashes increased until I had to do something about it. Looked for
inspiration on the Internet and found HUNDREDS of answers with many suggestions
making it difficult to sort out what to do. All drivers were checked and updated,
still the crashes. Did Mem Checks and found they failed. Contacted the repair
centre who collected the machine. Two weeks later it was returned OK. Within a
few days BSOD again. Crash dumps suggested Graphics problem. Machine went back
to repair centre and new graphics card fitted, another two weeks. Once again
BSOD appeared a few days later. Machine back to repair centre. Informed that
CPU has failed, another 3 weeks, wrong CPU fitted, another two weeks, machine
returned OK. Ran for a week the BSOD again. I had talked several times to the
Manufacturer who went through my crash dumps and said it's the motherboard.
Phoned the repair centre and told them it's probably the motherboard. Engineer
arrived next day and fitted new motherboard. Touch wood - all has been running
smoothly for six months now.

It took nearly six months to get it fixed. I also found out that my expensive
PC had some VERY average priced parts inside so they got a good profit from my
purchase. The extended warranty was very helpful though in this instance.

You can send all your dumps to various forums or help sites and you will get
many different answers. Mem Test said graphics and did the same after new
memory and graphics card fitted. I'm not able to give you any real answers,
just a tale of woe that eventually worked out OK.

Good Luck

Roger