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: Help me please, BSOD :(


05 Apr 2011   #1

Windows 7 64 bit Ultimate
 
 
Help me please, BSOD :(

Hello guys, im new here, and im really desperate, first ill explain you my situtation, i bought my first comptuer a year ago the complete system SPECS are
Corei7 920 @ Stock
2 CrossFire HD'S 5850 (one is a TOxic Sapphire and the otherone is an XFX Black Edition)
Thermaltake 700 W PSU
Msi pro E Motherboard
Im running windows 7 64 bit i bought it when i bought the computer but separatedly as i built this system, all the pieces were bought at the same time.
for the past year ive got NO problems at all but today i was playing assassins creeds brotherhood and the COMPLETE computer freezed, the image freezed it didnt respond, and it started making a Weird Sound, then i ran who crashed and GOT THIS


On Tue 4/5/2011 7:18:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040511-22687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B2AEC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007FCC038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
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 a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


I DID NOT SEE ANY BSOD

then restarted again and got the SAME ERROR this time with no minidump error
i decided to run unigine heaven bennchmark for 2 hours and i got NO BSODS no errors, i had the rest of the afternoon fine ran a lot of tests videocard stressing tests proccessor tests and got notrhing, i went to verifyer and selected ALL the NON windows drivers, restarted my computer and as soon as it started, the computer crashed witha BSOD .. Who crashed Said This

On Wed 4/6/2011 2:44:48 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040511-26453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0xC4 (0xE3, 0xFFFFFA800926D011, 0x52EF3B4, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver has made a call to a kernel-mode ZwXxx routine with a user-mode address as a parameter. 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 Wed 4/6/2011 2:44:48 AM 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: 0xC4 (0xE3, 0xFFFFFA800926D011, 0x52EF3B4, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver has made a call to a kernel-mode ZwXxx routine with a user-mode address as a parameter. 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 Wed 4/6/2011 2:40:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040511-26140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0xC4 (0xE3, 0xFFFFFA8009250011, 0x51AF3B4, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver has made a call to a kernel-mode ZwXxx routine with a user-mode address as a parameter. 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 Wed 4/6/2011 2:33:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040511-25671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0xC4 (0xE3, 0xFFFFFA80091B9011, 0x51AF3B4, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver has made a call to a kernel-mode ZwXxx routine with a user-mode address as a parameter. 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 4/5/2011 7:18:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040511-22687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B2AEC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007FCC038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
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 a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

The 6 times or idk how many it crashed, everytime 15 seconds afeter startup, when loading some driver i dont know wich one...

i turned verifyer off and everything seems to work fine, as i said this only happened with AC Brotherhood and now im getting this im really confused as this is the first time something like that happens to me, it only happened witht his game, as i said with unigine or other tests no problem, and i got ALL THE OTHER BSODS after i did that weird thing with verifyer.... please help me ill attatch all the needed files as you said in the rules post

PS: I am running allt he diagnose things on a "safe boot" its a normal boot but without audio and a lot of things.
also i have an OLD BSOD from March 25 but that was caused by a driver problem when i was installing CAP.

thanks in advance! i hope you guys can help me!


Edit: maybe the driver verifier bsods dont have somehting to be but i uploaded them do you guys can help me, ill repeat this only happens with acbrotherhood multipleyr it didnt happen in unigine, i hope i provided sufficient info and thanks again in advance!

EDIT 2: i forgot to tell you that 1 week ago my system hanged when executing crysis 2 the screen went black and i had to manually restart after 30 seconds no bsod noe rror log it didnt happen anymore... also when assassins creed breotherhood makes my computer crash i have to manually restart or shut down past 30 or 45 seconds, if not maybe it wouldnt turn off


My System SpecsSystem Spec
.

05 Apr 2011   #2

Windows 7 64 bit Ultimate
 
 

Sorry i couldnt upload the report ad HTML and i found a way to convert from HTML to pdf here it is!
My System SpecsSystem Spec
06 Apr 2011   #3

Windows 7 64 bit Ultimate
 
 

BUMP =D i dont know what does this mean but i saw some guys say this at the forum to get answer n.n sorry for bothering
My System SpecsSystem Spec
.


06 Apr 2011   #4

Windows 8.1 Pro x64
 
 

Your Eset Security Suite/Nod32 triggered the crash, remove it and replace it with MSE
Turn off Driver Verifier
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {e3, fffffa800926d011, 52ef3b4, 0}

Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c )

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000e3, Kernel Zw API called with user-mode address as parameter.
Arg2: fffffa800926d011, Address inside the driver making the incorrect API call.
Arg3: 00000000052ef3b4, User-mode address used as API parameter.
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc4_e3

FAULTING_IP: 
+0
fffffa80`0926d011 3d05000080      cmp     eax,80000005h

FOLLOWUP_IP: 
nt!VerifierBugCheckIfAppropriate+3c
fffff800`039513dc cc              int     3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  ekrn.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800039513dc to fffff800034ca640

STACK_TEXT:  
fffff880`03fde558 fffff800`039513dc : 00000000`000000c4 00000000`000000e3 fffffa80`0926d011 00000000`052ef3b4 : nt!KeBugCheckEx
fffff880`03fde560 fffff800`03951ec5 : fffffa80`0738e600 00000000`00000032 00000000`00000080 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`03fde5a0 fffff800`0395339e : 00000000`00000080 00000000`00000032 00000000`00000000 fffff800`0395339e : nt!ViZwCheckAddress+0x35
fffff880`03fde5e0 fffff800`039565c8 : fffffa80`0926d011 00000000`00000000 fffffa80`0926cedb fffff800`034c5e70 : nt!ViZwCheckUnicodeString+0x2e
fffff880`03fde620 fffffa80`0926d011 : 00000000`052ef3b4 fffff980`2a9b6da0 00000000`052ef3c4 00000000`00000018 : nt!VfZwQueryDirectoryFile+0x88
fffff880`03fde6b0 00000000`052ef3b4 : fffff980`2a9b6da0 00000000`052ef3c4 00000000`00000018 fffff880`03fde778 : 0xfffffa80`0926d011
fffff880`03fde6b8 fffff980`2a9b6da0 : 00000000`052ef3c4 00000000`00000018 fffff880`03fde778 fffff980`2a9b6da0 : 0x52ef3b4
fffff880`03fde6c0 00000000`052ef3c4 : 00000000`00000018 fffff880`03fde778 fffff980`2a9b6da0 fffffa80`00000260 : 0xfffff980`2a9b6da0
fffff880`03fde6c8 00000000`00000018 : fffff880`03fde778 fffff980`2a9b6da0 fffffa80`00000260 fffff800`00000003 : 0x52ef3c4
fffff880`03fde6d0 fffff880`03fde778 : fffff980`2a9b6da0 fffffa80`00000260 fffff800`00000003 fffff880`03fd9001 : 0x18
fffff880`03fde6d8 fffff980`2a9b6da0 : fffffa80`00000260 fffff800`00000003 fffff880`03fd9001 fffff880`03fde728 : 0xfffff880`03fde778
fffff880`03fde6e0 fffffa80`00000260 : fffff800`00000003 fffff880`03fd9001 fffff880`03fde728 00000000`00000001 : 0xfffff980`2a9b6da0
fffff880`03fde6e8 fffff800`00000003 : fffff880`03fd9001 fffff880`03fde728 00000000`00000001 00000000`000101d0 : 0xfffffa80`00000260
fffff880`03fde6f0 fffff880`03fd9001 : fffff880`03fde728 00000000`00000001 00000000`000101d0 fffff980`2a816fc0 : 0xfffff800`00000003
fffff880`03fde6f8 fffff880`03fde728 : 00000000`00000001 00000000`000101d0 fffff980`2a816fc0 00000000`00000000 : 0xfffff880`03fd9001
fffff880`03fde700 00000000`00000001 : 00000000`000101d0 fffff980`2a816fc0 00000000`00000000 ffffffff`80000ef4 : 0xfffff880`03fde728
fffff880`03fde708 00000000`000101d0 : fffff980`2a816fc0 00000000`00000000 ffffffff`80000ef4 00000000`00100010 : 0x1
fffff880`03fde710 fffff980`2a816fc0 : 00000000`00000000 ffffffff`80000ef4 00000000`00100010 00000000`052ef3b4 : 0x101d0
fffff880`03fde718 00000000`00000000 : ffffffff`80000ef4 00000000`00100010 00000000`052ef3b4 00000000`00000260 : 0xfffff980`2a816fc0


STACK_COMMAND:  kb

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!VerifierBugCheckIfAppropriate+3c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

FAILURE_BUCKET_ID:  X64_0xc4_e3_VRF_nt!VerifierBugCheckIfAppropriate+3c

BUCKET_ID:  X64_0xc4_e3_VRF_nt!VerifierBugCheckIfAppropriate+3c

Followup: MachineOwner
---------
My System SpecsSystem Spec
06 Apr 2011   #5

Windows 7 64 bit Ultimate
 
 

And what about the WHEA uncorrectable error? was it caused by assassins creed or my hardware? this hasnt happened to me... only in AC bhood multiplayer, also is the 700 W psu i ahve sufficient for 2 HD 5850 (Oced because their versions) an intrel core i7 920, 3 fan coolers 2 hard drives and 1 cd room? should i change this for a 1000 W psu?
My System SpecsSystem Spec
06 Apr 2011   #6

Windows 8.1 Pro x64
 
 

Quote   Quote: Originally Posted by Dan011093 View Post
And what about the WHEA uncorrectable error? was it caused by assassins creed or my hardware? this hasnt happened to me... only in AC bhood multiplayer, also is the 700 W psu i ahve sufficient for 2 HD 5850 (Oced because their versions) an intrel core i7 920, 3 fan coolers 2 hard drives and 1 cd room? should i change this for a 1000 W psu?
The WHEA error, known as Bugcheck 0x124 is caused by hardware
Stop 0x124 - what it means and what to try

Upgrading to 1000W might help if the cards lack power
My System SpecsSystem Spec
06 Apr 2011   #7

Windows 7 64 bit Ultimate
 
 

is there any way to know wich part of the hardware caused the issue? the computer freezed the speakers made a terrible noise and i ahd to manually restart after 30 seconds with no BSOD, then same thing and i ahd the WHEA report, this ONLY happened at Assassins creed brotherhood multiplayer, it hasnt happened in any other way... any suggestions?

EDIT: attached new repoort
My System SpecsSystem Spec
06 Apr 2011   #8

Windows 8.1 Pro x64
 
 

Quote   Quote: Originally Posted by Dan011093 View Post
is there any way to know wich part of the hardware caused the issue? the computer freezed the speakers made a terrible noise and i ahd to manually restart after 30 seconds with no BSOD, then same thing and i ahd the WHEA report, this ONLY happened at Assassins creed brotherhood multiplayer, it hasnt happened in any other way... any suggestions?

EDIT: attached new repoort
Test each components with OCCT to identify the defective hardware
OCCT (OverClock Checking Tool) 3.0.0 download from Guru3D.com
My System SpecsSystem Spec
06 Apr 2011   #9

Windows 7 64 bit Ultimate
 
 

for how long should i run each test?
My System SpecsSystem Spec
06 Apr 2011   #10

Windows 8.1 Pro x64
 
 

Quote   Quote: Originally Posted by Dan011093 View Post
for how long should i run each test?
1 Hour will be enough
My System SpecsSystem Spec
Reply

 Help me please, BSOD :(




Thread Tools



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 03:50 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33