Frequent BSODs

Hi. I'm suffering from many BSODs, and I need help in figuring out the problem. I've attached dump files and other system report files as per the subforum instructions. Below is some information about the computer.

• custom-build computer, built one year ago (August 2010)
• Windows 7 Home Premium x64 with Service Pack 1
• up-to-date on Windows Update
• installed Windows a year ago (August 2010)

I think it's occurring because the computer is running out of memory, perhaps due to a memory leak. The reason is that even if the computer is left idle, the RAM usage keeps skyrocketing, and I come back some time later to a blue screen. This computer does have a page file, so could it be an issue with the hard drive and memory swapping?

Hello Misfortune & Thanks for your post!

First thing to do.

Update your ATI Graphic driver, as it's old.

Code:

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

Code:

2: kd> lmvm atikmdag
start             end                 module name
fffff880`04a5f000 fffff880`05270000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Fri Nov 26 03:46:44 2010 (4CEF1F94)
    CheckSum:         007CA105
    ImageSize:        00811000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Post the new dump (if any), after you done this.

Second thing to do

I noticed a problem with your CPU. Stress test it with Prime95.

https://www.sevenforums.com/tutorials...t-prime95.html

Code:

Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware

!cpuinfo

Code:

1: kd> !cpuinfo
CP  F/M/S Manufacturer  MHz PRCB Signature    MSR 8B Signature Features
 1  6,37,2 GenuineIntel 3600 ffff000800000000                   21193ffe
                      Cached Update Signature ffff000800000000
                     Initial Update Signature ffff000800000000

.. just for the details.

Malwarebyes Scan

I do recommend that you take a full scan of Malwarebytes.

Code:

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  wininit.exe

Best Regards,
FredeGail

Sorry for all this confusion, I also got a little dizzy during analysing due to so many things to think about

Misfortune said:

Thank you so much for the detailed reply, FredeGail! And no need to apologize for any confusion, I understand that this can take time!

Good call on the ATI graphics card driver, and it's now fully up-to-date. I also went ahead and updated the BIOS. But do you think it could be a memory issue? Is there anything in the dump files to indicate that? Just in case, I've burned a copy of memtest86 to a CD and plan to run it tomorrow.

Still, I'll scan with Malwarebytes. And I'll see if I can't get time to run a CPU test with Prime95.

But now, on to more recent news. After I burned memtest86 to a CD I thought I'd play some Crysis 2. Lo and behold, five minutes into the game I get another blue screen! I've attached the dump file.

I'll post again with any updates.

It could be your RAM, but not as far as I can see. To start off with a Prime95 test would be great! :)

Oh and, your latest dump could not be read because it's unloaded. Don't worry about it.

EDIT: When you run the Prime95 test, run both the Blend and SmallFFT tests.

Best Regards,
FredeGail

I ran a CHKDSK /r /f, and the report indicated that some errors in the file system had been corrected. I also ran six passes with memtest86, and no errors were reported.

But I got yet another blue screen just now. I've attached the dump file.

I'll run a test with Prime95 as soon as I get a chance.

Thanks again for the help. I honestly would like to know just what the hell is causing this mess.

Misfortune said:

I ran a CHKDSK /r /f, and the report indicated that some errors in the file system had been corrected. I also ran six passes with memtest86, and no errors were reported.

But I got yet another blue screen just now. I've attached the dump file.

I'll run a test with Prime95 as soon as I get a chance.

Thanks again for the help. I honestly would like to know just what the hell is causing this mess.

Could you please run SFC /SCANNOW? It won't take long. :)

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8005a935d0, fffffa8005a938b0, fffff800031818b0}

Probably caused by : csrss.exe

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8005a935d0, Terminating object
Arg3: fffffa8005a938b0, Process image file name
Arg4: fffff800031818b0, Explanatory message (ascii)

Debugging Details:
------------------


PROCESS_OBJECT: fffffa8005a935d0

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - Instruktionen ved 0x%p refererede hukommelse ved 0x%p. De kr vede data blev ikke skrevet i hukommelsen pga. I/O-fejlstatus 0x%x.

BUGCHECK_STR:  0xF4_IOERR

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`07b9b0e8 fffff800`032085e2 : 00000000`000000f4 00000000`00000003 fffffa80`05a935d0 fffffa80`05a938b0 : nt!KeBugCheckEx
fffff880`07b9b0f0 fffff800`031b599b : ffffffff`ffffffff fffffa80`07185b60 fffffa80`05a935d0 fffffa80`05a935d0 : nt!PspCatchCriticalBreak+0x92
fffff880`07b9b130 fffff800`03135448 : ffffffff`ffffffff 00000000`00000001 fffffa80`05a935d0 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`07b9b180 fffff800`02e7ced3 : fffffa80`05a935d0 fffff800`c0000006 fffffa80`07185b60 00000000`02ea0cb0 : nt!NtTerminateProcess+0xf4
fffff880`07b9b200 fffff800`02e79470 : fffff800`02ec967f fffff880`07b9bb78 fffff880`07b9b8d0 fffff880`07b9bc20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`07b9b398 fffff800`02ec967f : fffff880`07b9bb78 fffff880`07b9b8d0 fffff880`07b9bc20 00000000`77035c44 : nt!KiServiceLinkage
fffff880`07b9b3a0 fffff800`02e7d2c2 : fffff880`07b9bb78 00000000`02ee0000 fffff880`07b9bc20 00000000`77041658 : nt! ?? ::FNODOBFM::`string'+0x49874
fffff880`07b9ba40 fffff800`02e7be3a : 00000000`00000000 00000000`77035c47 fffffa80`05a93501 00000000`02ee0000 : nt!KiExceptionDispatch+0xc2
fffff880`07b9bc20 00000000`77418f36 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`02ea1270 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77418f36


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

Followup: MachineOwner

The csrss.exe is a part of the Win32k kernel, it could be an infection but you said you ran Malwarebytes already. So a sfc /scannow would be great.

Cheers!
FredeGail

Misfortune said:

Thanks for the reply, FredeGail. I ran a file verification scan, and there were no errors found. And still the blue screens keep coming; I've gotten good at reproducing them. It seems every time I run a resource-intensive program (e.g. game), a few minutes later the computer crashes.

But I think I figured out the problem, and unfortunately it's not good . The computer has a SeaGate hard drive installed, and I ran a more thorough test with the vendor's own diagnostic utility (SeaTools for DOS). The utility reported that the hard drive failed two tests, and the drive could not be repaired.

In short, it seems like I have a faulty hard drive. Since the utility indicates that there are no firmware updates available, I'll have to get the hard drive exchanged somehow. So until then, I don't think I'll work on computer. I'll just back up my files and wait for a new hard drive, and hopefully the situation will change for the better.


But still, thank you so much for all your help!

EDIT: I'll mark this thread as solved for the time being, as I don't think there is anything else that needs to be done. Namely, I think that fixing the hard drive is the first priority and until that is done, I could keep running into problems anyway. My next update could be weeks from now, depending on how quickly I can get a new hard drive and if that fixes the problem or not!

I hope this will solve your trouble! :)

Your reputation is most appreciated!

Best Regards,
FredeGail