Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Strange BSOD, W7-64


10 May 2013   #1
oxygen15

Windows 7 Ultimate x64
 
 
Strange BSOD, W7-64

Hi all. Sorry for my English.
I have serious strange problem.
I have two HP DC7800 workstations at home (win7-64bit, e8400, hd6570, 4gb, one 500gb hdd, other 630gb hdd).
So, these computers hard working every day (photoshop, premiere, outlook, etc.).
And..... 5 days ago i have had very bad surprise. In one hour i get 4 BSOD's from one machine!!!
Scenario:
received new email in outlook, answerred. BSOD.
restart automatically, loading windows, login- BSOD.
restart automatically, loading in safe mode- loading stops at classpnp.sys file.
turn computer off- turn computer on- loading normally, but at screen was only mouse cursor in black background.
turn off- turn on- finally loaded, everithing fine to the present. 5 days of work without any problems.
i have tested memory with Memtest for 10 passes. No errors.
i have tested CPU with stress test. No errors.
I have checked HDD for errors, everything is good, no errors in SMART too.

I have downloaded BlueScreenView application:

BSOD N.1:

050413-22120-01.dmp
2013.05.04 01:54:47
CRITICAL_OBJECT_TERMINATION
0x000000f4
00000000`00000003
fffffa80`076c2b30
fffffa80`076c2e10
fffff800`02f9b350
ntoskrnl.exe
ntoskrnl.exe+75c00
NT Kernel & System
Microsoft® Windows® Operating System
Microsoft Corporation 6.1.7601.18113 (win7sp1_gdr.130318-1533)
x64
ntoskrnl.exe+75c00
C:\Windows\Minidump\050413-22120-01.dmp 2 15 7601 275.560

BSOD N.2:

050413-20592-01.dmp
2013.05.04 01:59:16
PAGE_FAULT_IN_NONPAGED_AREA
0x00000050
ffffffff`ffffffe0
00000000`00000001
fffff800`02ccfd9c
00000000`00000000
ntoskrnl.exe
ntoskrnl.exe+75c00
NT Kernel & System
Microsoft® Windows® Operating System
Microsoft Corporation 6.1.7601.18113 (win7sp1_gdr.130318-1533)
x64 ntoskrnl.exe+75c00
C:\Windows\Minidump\050413-20592-01.dmp 2 15 7601 275.560

BSOD N.3:

050413-23259-01.dmp
2013.05.04 02:06:00
SYSTEM_SERVICE_EXCEPTION
0x0000003b
00000000`c0000005
fffff800`02fc0833
fffff880`08fd5f70
00000000`00000000
ntoskrnl.exe
ntoskrnl.exe+75c00
NT Kernel & System
Microsoft® Windows® Operating System
Microsoft Corporation 6.1.7601.18113 (win7sp1_gdr.130318-1533)
x64 ntoskrnl.exe+75c00
C:\Windows\Minidump\050413-23259-01.dmp 2 15 7601 275.560

BSOD N.4:

050413-21247-01.dmp
2013.05.04 02:32:11
MEMORY_MANAGEMENT
0x0000001a
00000000`00000031
fffffa80`03fa2280
fffff880`0845e000
fffff8a0`00ffe0cf
ntoskrnl.exe
ntoskrnl.exe+75c00
NT Kernel & System
Microsoft® Windows® Operating System
Microsoft Corporation 6.1.7601.18113 (win7sp1_gdr.130318-1533)
x64 ntoskrnl.exe+75c00
C:\Windows\Minidump\050413-21247-01.dmp 2 15 7601 271.432



So.... Can this be software problem? Or it seems to be hardware?
Many thanks..


My System SpecsSystem Spec
10 May 2013   #2
cipley

Windows 7
 
 

at least upload the dump files...read this first:
Blue Screen of Death (BSOD) Posting Instructions
then we'll see if we can be any help
My System SpecsSystem Spec
10 May 2013   #3
oxygen15

Windows 7 Ultimate x64
 
 

OK, thank You, there it is:
My System SpecsSystem Spec
10 May 2013   #4
cipley

Windows 7
 
 

I don't see MSINFO file, can you please look it up and upload here also?
My System SpecsSystem Spec
10 May 2013   #5
oxygen15

Windows 7 Ultimate x64
 
 

OK, i will try one more time. Just SF checker stops when should detect Serial ports.
My System SpecsSystem Spec
10 May 2013   #6
cipley

Windows 7
 
 

Uh oh.

STOP 0x000000F4: CRITICAL_OBJECT_TERMINATION
Usual Causes: ? (in my experience, malware/possibly viruses)

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory

STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel

F4 Bugcheck, means something abruptly terminates an essential Windows process, causing the whole system to crash.
in your case, csrss.exe
In my experience, this is mainly caused by malwares. But we need that MSINFO to look for the cause, too

- Scan the computer for viruses and malwares using MSE and Malwarebytes.
Microsoft Security Essentials | Protect against viruses, spyware, and other malware
Malwarebytes : Malwarebytes Anti-Malware removes malware including viruses, spyware, worms and trojans, plus it protects your computer --> DO NOT activate free trial
Install, update, do a full scan.

- Some of the windows components are failing (i.e. lsm.exe from the dump file). Better check Windows System File integrity
from command prompt, do these two commands:
chkdsk /r /f
SFC /scannow --> if the result is other than "no violations detected" run it again 2 more times

I'll go see if the other is available to help

BSOD ANALYSIS
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa80076c2b30, fffffa80076c2e10, fffff80002f9b350}

Probably caused by : csrss.exe

Followup: MachineOwner
---------
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.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffffffffffe0, 1, fffff80002ccfd9c, 0}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4518f )

Followup: MachineOwner
---------
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002fc0833, fffff88008fd5f70, 0}

Probably caused by : ntkrnlmp.exe ( nt!AlpcpDispatchReplyToPort+6f )

Followup: MachineOwner
---------
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {31, fffffa8003fa2280, fffff8800845e000, fffff8a000ffe0cf}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+71d1 )

Followup: MachineOwner
---------
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
My System SpecsSystem Spec
10 May 2013   #7
oxygen15

Windows 7 Ultimate x64
 
 

Here is full SF checker folder:
My System SpecsSystem Spec
10 May 2013   #8
cipley

Windows 7
 
 

well well well, look what you've got in your startup list:
Code:
C:\Windows\system32\V0530Ext.ax	c:\windows\system32\regsvr32.exe /s c:\windows\system32\v0530ext.ax	Public	HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
I am most definitely sure this is a malware
Can you boot to Safe Mode with Networking?
it's best to run the scan from there.
My System SpecsSystem Spec
10 May 2013   #9
oxygen15

Windows 7 Ultimate x64
 
 

OK now i will do that!
My System SpecsSystem Spec
10 May 2013   #10
cipley

Windows 7
 
 

Looking forward to your result
My System SpecsSystem Spec
Reply

 Strange BSOD, W7-64




Thread Tools



Similar help and support threads for2: Strange BSOD, W7-64
Thread Forum
Solved Strange BSOD BSOD Help and Support
Strange BSOD issue BSOD Help and Support
Strange BSoD BSOD Help and Support
BSOD at new Laptop, really strange!?? BSOD Help and Support
Strange BSOD BSOD Help and Support
Strange BSOD crash BSOD Help and Support
strange reacurring BSOD! HELP IF YOU SEE THIS PLZ!!! BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 09:38 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App