BSOD help

[julianbraso]

Hi, i'm on Windows 7 ultimate 32 bit full retail, i'm having bsods while playing games, this started 2 weeks ago i reinstalled 7 formatting c: and it didn't helped at all it kept happening and i'm so frustrated because i can't seem to know what it's actually wrong on my rig or os, i tried switching the ram modules, running the system with each one and it's the always the same i play for like 5 minutes and then it crashes, sometimes showing bsod others by keeping the screen like blurry or distortioned (crash) and then it restarts,please if someone could help me it'd be so cool because i'm very frustrated, thanks in advance

Is Windows 7 Ultimate 32 bits
- x86 (32-bit) or x64 ? x86
- the original installed OS on the system? none, i put the rig together
- an OEM or full retail version? full retail
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? motherboard is less than a year everything else 1 year and a half
- What is the age of OS installation (have you re-installed the OS?) i reinstalled 3 days ago

Edit: i'm attaching the most recent minidump, hope this helps
Edit 2: i've just finished installing win 7 home edition pro 64bits and at first it didn't gave me any bsods but after one there are randomly appearing, it could be at login or at 5 hours, i'm attaching the minidump i'm so sick about this i want my computer back to normal (the minidump.rar it's the last uploaded)
Edit 3: Ok, now i've updated the jcgriff 2 full report

 

[wish]

Follow this:
Blue Screen of Death (BSOD) Posting Instructions

 

[julianbraso]

Oh, you're right, i'm sorry it's just that i'm so pissed off that i forgot to follow the rules, so sorry i'm editing now

 

[julianbraso]

Done, thanks for pointing it Wish, hope someone helps me now

 

[wish]

I have checked your single dump. Do you use Release Candidate version?
Your windows:
Built by: 7100.0.x86fre.winmain_win7rc --> It should be build 7600 winRTM

No wonder if you get BSOD maybe that version not stable yet, so it's better for you to use the RTM version of windows.

 

[julianbraso]

Oh okay i'll update then, btw this happened to me aswell on the 7600 version i had before

 

[wish]

Yes you need to update it.
If 7600 version still BSOD, you may post the data here.

-wish

 

[julianbraso]

The BSOD error code is 0x000008E or something like that, now the bsod doesn't tell me the problem it only says that a problem has been found etc

 

[zigzag3143]

Hi, i'm on Windows 7 ultimate 32 bit full retail, i'm having bsods while playing games, this started 2 weeks ago i reinstalled 7 formatting c: and it didn't helped at all it kept happening and i'm so frustrated because i can't seem to know what it's actually wrong on my rig or os, i tried switching the ram modules, running the system with each one and it's the always the same i play for like 5 minutes and then it crashes, sometimes showing bsod others by keeping the screen like blurry or distortioned (crash) and then it restarts,please if someone could help me it'd be so cool because i'm very frustrated, thanks in advance

Is Windows 7 Ultimate 32 bits
- x86 (32-bit) or x64 ? x86
- the original installed OS on the system? none, i put the rig together
- an OEM or full retail version? full retail
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? motherboard is less than a year everything else 1 year and a half
- What is the age of OS installation (have you re-installed the OS?) i reinstalled 3 days ago

Edit: i'm attaching the most recent minidump, hope this helps

Wish is of course correct and either that version is hacked or you have your system clock out of sync. Which??

It is making it difficult to troubleshoot your problem so you do need to update with a valid key




Ken

 

[julianbraso]

why my system clock out of sync ken?

 

[zigzag3143]

The BSOD error code is 0x000008E or something like that, now the bsod doesn't tell me the problem it only says that a problem has been found etc

After you update we can help you. The current problem is relatively easy to fix

 

[zigzag3143]

why my system clock out of sync ken?

I suspect it is more than your system clock. If you want to sync your clock go to the time and say update now.

If there is a modded OS it will tell you



See picture

 

[julianbraso]

Ok, tomorrow i'm updating and i'll be back with news, meanwhile i updated the clock and at first it timed out, but after that it updated succesfully

 

[zigzag3143]

Ok, tomorrow i'm updating and i'll be back with news, meanwhile i updated the clock and at first it timed out, but after that it updated succesfully

You may want to remove the virtual HD software (daemon tools/alcohol 120). It is involved in your BSOD

 

[julianbraso]

i just have removed it by now, i'm going to play some cs in order to see if the pc crashes

 

[julianbraso]

ok i'm back, the pc is still firing bsod's at me

 

[Tews]

Julian, please upload your latest .dmp file..

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[julianbraso]

done, please help me

 

[wish]

Hi,
Your dumps bugcheck:
- 0x1E = KMODE_EXCEPTION_NOT_HANDLED probably cause by driver or RAM
- 0x3B = SYSTEM_SERVICE_EXCEPTION

Msmpeng.exe was involved in the both dumps, It relates to your Windows Defender or MSE.
So I would recommend you to reinstall that applications.

Then these drivers need to be update:

ASACPI.sys   Wed May 13 18:25:17 2009 --> [URL="http://support.asus.com/download/download.aspx"]Asus ATK0110 ACPI Utility[/URL]
AsIO.sys     Mon Apr 06 00:21:08 2009 --> [URL="http://support.asus.com/download/download.aspx"]Asus PCProbe Utility[/URL]

[URL="http://www.nvidia.com/page/drivers.html"]Nvdia chipset drivers: [/URL]
nvmf6264.sys Thu Apr 30 12:45:59 2009
nvstor.sys   Tue May 19 23:45:37 2009
nvstor64.sys Wed Apr 29 18:57:30 2009

Make sure to do the update, and if the problem persist then test your RAM with memtest86 for at least 7 passes.
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

BugCheck 1E, {ffffffffc0000005, fffff800028f1065, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+265 )

Log

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800028ffc22, fffff88004239a70, 0}

Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800028ffc22, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88004239a70, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP: 
nt!KxWaitForLockOwnerShip+12
fffff800`028ffc22 48890a          mov     qword ptr [rdx],rcx

CONTEXT:  fffff88004239a70 -- (.cxr 0xfffff88004239a70)
rax=000000000000003e rbx=fffff80002a37e80 rcx=fffff80002a385e0
rdx=0040000000000000 rsi=0000000000000001 rdi=fffff80002a385e0
rip=fffff800028ffc22 rsp=fffff8800423a450 rbp=fffff8800423a4c0
 r8=4000000000000000  r9=0000000000000000 r10=00000000000002fe
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=fffffa80029bfb30 r15=0000000000812df0
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!KxWaitForLockOwnerShip+0x12:
fffff800`028ffc22 48890a          mov     qword ptr [rdx],rcx ds:002b:00400000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800028ffc22

STACK_TEXT:  
fffff880`0423a450 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxWaitForLockOwnerShip+0x12


FOLLOWUP_IP: 
nt!KxWaitForLockOwnerShip+12
fffff800`028ffc22 48890a          mov     qword ptr [rdx],rcx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KxWaitForLockOwnerShip+12

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

STACK_COMMAND:  .cxr 0xfffff88004239a70 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!KxWaitForLockOwnerShip+12

BUCKET_ID:  X64_0x3B_nt!KxWaitForLockOwnerShip+12

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

 

[CarlTR6]

MSE should be OK; you can leave it for now. It is probably a victim of the crash rather than a cause. I think you have other problems. Please update the drivers that Wish listed above.