BSOD driver maybe

Page 2 of 2 FirstFirst 12

  1. teakiie
    Posts : 10
    Windows 7 Professional 64bit
    Thread Starter
       New #11

    So I ran memtest86+ for 9 passes, no errors occured. I got Driver verifier enabled before, except my last uploaded dumps. now i reenabled and generated some BSODs. it wasn't too hard:P
    I tested my hard drive with SeaTools and ran some video, sound, network related stress tests too. fortunately no errors occured. just the regular bsods: 109, 50 and 3B, but the last seems to occure just after an another bsod.
      My Computer
    Quote Quote

  3. CarlTR6
    Posts : 11,990
    Windows 7 Ultimate 32 bit
       New #12

    I only see two Driver Verifier enabled dumps and they both blame the Windows system core file, which is highly unlikely to be the cause. For the time being, you can keep Driver Verifier turned off. Your latest dumps either directly blame or reference memory corruption. I suggest that you run Memtest again from a cold boot after your computer has been off for a while. Again, run it for at least seven passes.

    If you get no errors with Memtest, run Prime95 to test your CPU and your RAM. Follow the instructions in this tutorial: https://www.sevenforums.com/tutorials...t-prime95.html. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with the results.
    Code:
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02255000 PsLoadedModuleList = 0xfffff800`02492e50
Debug session time: Sun Dec  5 15:54:49.826 2010 (GMT-5)
System Uptime: 0 days 0:05:14.326
Loading Kernel Symbols
...............................................................
.....................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1, {742bffaa, 0, 100ff, fffff88009cf1ca0}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

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

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

APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->KernelApcDisable field. A negative value indicates that a driver
has disabled APC calls without re-enabling them.  A positive value indicates
that the reverse is true. This check is made on exit from a system call.
Arguments:
Arg1: 00000000742bffaa, address of system function (system call)
Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 00000000000100ff, Thread->KernelApcDisable
Arg4: fffff88009cf1ca0, Previous KernelApcDisable

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


FAULTING_IP: 
+59cd952f01b1dbb4
00000000`742bffaa ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1

PROCESS_NAME:  WmiPrvSE.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800022c4ca9 to fffff800022c5740

STACK_TEXT:  
fffff880`09cf1ad8 fffff800`022c4ca9 : 00000000`00000001 00000000`742bffaa 00000000`00000000 00000000`000100ff : nt!KeBugCheckEx
fffff880`09cf1ae0 fffff800`022c4be0 : fffffa80`05323060 00000000`001ddfe0 00000000`7efdb001 00000000`00000004 : nt!KiBugCheckDispatch+0x69
fffff880`09cf1c20 00000000`742bffaa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`001ddfa8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x742bffaa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSystemServiceExit+245
fffff800`022c4be0 4883ec50        sub     rsp,50h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiSystemServiceExit+245

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1_nt!KiSystemServiceExit+245

BUCKET_ID:  X64_0x1_nt!KiSystemServiceExit+245

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

Debug session time: Sun Dec  5 15:38:07.982 2010 (GMT-5)
System Uptime: 0 days 0:00:22.325
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800033a3a87, fffff88003be2f90, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

3: 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: fffff800033a3a87, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88003be2f90, 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!SepAccessCheckAndAuditAlarm+96e
fffff800`033a3a87 cf              iretd

CONTEXT:  fffff88003be2f90 -- (.cxr 0xfffff88003be2f90)
rax=fffffa8005c4eb20 rbx=00000000002e9301 rcx=fffff88003be3960
rdx=fffff8a0023cf150 rsi=0000000000000001 rdi=0000000000000000
rip=fffff800033a3a87 rsp=fffff88003be3960 rbp=fffff88003be3ca0
 r8=0000000000000000  r9=fffff8a0023cf150 r10=fffff8a0023cf150
r11=00000000000006bf r12=fffff88003be3a14 r13=fffff88003be3a01
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!SepAccessCheckAndAuditAlarm+0x96e:
fffff800`033a3a87 cf              iretd
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  services.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800033a3a87

STACK_TEXT:  
fffff880`03be3960 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SepAccessCheckAndAuditAlarm+0x96e


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff800033a3a7f - nt!SepAccessCheckAndAuditAlarm+966
    [ 8c:cc ]
1 error : !nt (fffff800033a3a7f)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

STACK_COMMAND:  .cxr 0xfffff88003be2f90 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

Debug session time: Sun Dec  5 15:39:24.780 2010 (GMT-5)
System Uptime: 0 days 0:00:39.655
Loading Kernel Symbols
...............................................................
.....................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8800a165c38, 1, fffff800025bb11d, 2}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

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.
Arguments:
Arg1: fffff8800a165c38, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff800025bb11d, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800025000e0
 fffff8800a165c38 

FAULTING_IP: 
nt!RtlLookupAtomInAtomTable+bd
fffff800`025bb11d 6641890424      mov     word ptr [r12],ax

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x50

PROCESS_NAME:  HelpPane.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88009d657e0 -- (.trap 0xfffff88009d657e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000c001 rbx=0000000000000000 rcx=fffff8a000a00440
rdx=fffff8a000a00410 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800025bb11d rsp=fffff88009d65970 rbp=fffff88009d65ca0
 r8=fffff8a000a03000  r9=0000000000000004 r10=0000000000000780
r11=fffff8a000a00020 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!RtlLookupAtomInAtomTable+0xbd:
fffff800`025bb11d 6641890424      mov     word ptr [r12],ax ds:0004:00000000`00000000=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800023478f2 to fffff800022c8740

STACK_TEXT:  
fffff880`09d65678 fffff800`023478f2 : 00000000`00000050 fffff880`0a165c38 00000000`00000001 fffff880`09d657e0 : nt!KeBugCheckEx
fffff880`09d65680 fffff800`022c682e : 00000000`00000001 ffffffff`ffffffff fffff700`01080400 000007fe`fe79b000 : nt! ?? ::FNODOBFM::`string'+0x40ec0
fffff880`09d657e0 fffff800`025bb11d : 00000000`00000004 ffffffff`ffffffff fffff8a0`00a00020 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`09d65970 fffff800`025bb88c : fffff8a0`00a00020 00000000`00000007 00000000`001bf600 00000000`001bf600 : nt!RtlLookupAtomInAtomTable+0xbd
fffff880`09d659c0 fffff800`022c7993 : fffffa80`05a2d760 00000000`001bf598 00000000`ffffff01 fffffa80`05a227c0 : nt!NtFindAtom+0xe7
fffff880`09d65c20 00000000`76dcfe9a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001bf558 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76dcfe9a


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff800025bb87f - nt!NtFindAtom+da
    [ 00:40 ]
1 error : !nt (fffff800025bb87f)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------
      My Computer
    Quote Quote

  4. teakiie
    Posts : 10
    Windows 7 Professional 64bit
    Thread Starter
       New #13

    I've found a(!) cause of the BSODs. I disabled in the BIOS PME event wakeup and the system stabilized. I tested to reenable, it run fine for a while then BSODs started again. actually WOL is not a cardinal service for me but it's annoying a bit.

    I ran prime95 and OCCT too. OCCT is quite fast so I ran several test with that, all of them ended with an error or a BSOD But actually I couldn't find any log of the error or error codes, so now I'm running Prime95.
    I got an error during the first run: 'FATAL ERROR: Rounding was 0.4943237305, expected less than 0.4', but I ran it without "Round off checkin". Is that change something? Now I'm running it again.

    The CPU voltage is default, all CPU settings in bios are default. In bios CPU freq. is set to normal (1.325V), measured 1.408V in health status.

    I've got some BSODs since I disabled PME, but it has an impact on the crashes that's for sure. 2 dumps are attached.
    I attach the OCCT graphs and a CPU-Z screen too.

    I'm really confused of the results. After I've found the PME thing I thought that this should be some bios/motherboard/lan adapter error. But CPU results really says that the CPU is unstable or bad. That would explain the wrong memory addresses, but not the PME issue. So I hope you have some ideas:)

    thanks
      My Computer
    Quote Quote

  6. teakiie
    Posts : 10
    Windows 7 Professional 64bit
    Thread Starter
       New #14

    could someone suggest a forum where I can post my hw issues, pls?
      My Computer
    Quote Quote

  7. CarlTR6
    Posts : 11,990
    Windows 7 Ultimate 32 bit
       New #15

    Sure. Start a thread here: Hardware & Devices - Windows 7 Forums
      My Computer
    Quote Quote

 
Page 2 of 2 FirstFirst 12

  Related Discussions
Hello, I would appreciate any help with the following problem: the pc sometimes seemingly randomly shows BSOD with errors named in the title, I also attach corresponding screenshots. The problem wont happen if the PC power is supplied from the adapter AND there is some content running on the...
I have had BSOD for a while and being super busy I did not have time to look at it and get it fixed. Well Being a computer guy I assumed I could fix it myself. But with tons of research and trying to use every guide I can find I decided to try here(probably should have came here first). Today I...
Hi, and thanks in advance... Much of this is a repeat to other threads, until the graphic driver problem at the end... (I also have an Ubuntu partition.) I'd left my mp3 player plugged in overnight + an Asus Xonar DAC in a usb hub, when Windows wanted to do an update and conflict over...
Hi, I've recently been using drivermax to update my drivers. After my updates, I've been randomly getting BSODs then and now. I looked into the minidump with bluescreenviewer but cannot find a fix to the problem. I've uploaded the minidump. Please help! I'm using a shared a computer so I don't know...
Hello, After many many hours of searching forums for solutions I have been unable to find a solution to my problem - so I decided to open a topic of my own and hope someone can help me with my problem specifically. My problem is similar to this topic, although the solutions posted there...
Our Sites
Site Links
About 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 19:01.
Find Us