BSOD Help

jsparry · 08 Jun 2010

Ahh i was running windows mem tester from the boot menu.

That seems to run a lot faster.

I have the mem tester you asked me to download running now and its taking a lot longer.

will post results when it finish.

zigzag3143 · 08 Jun 2010

jsparry said:

I cant get windows to start with Verifier running.

Should i choose different drivers from the list untill it boots?

Have you been asked to run a system file check yet?

(type cmd in search>right click and run as admin>sfc /scannow)

Ken

jsparry · 08 Jun 2010

Run system file check last time was getting bsod.

It Didn't find any issues.

If it is hardware is the any easy way to find out what device.
All bit in the system are fairly new and should be covered under warranty.

Jonathan_King · 08 Jun 2010

Let us know the results of the Memtest when it's done and we'll go from there.

jsparry · 08 Jun 2010

It it helps at all.

https://www.sevenforums.com/crashes-d...tml#post704785

Was the last post i made. it stopped for about 2 weeks after i took out the sound card.
(its still out..)

I uploaded a few dumps back then.

Not sure if they contain any details.

Jonathan, many thanks for all your help and quick responses.

James

jsparry · 08 Jun 2010

The mem check has just finished its 3rd pass. 0 errors so far. it doesn't look like it ram.

What should i try next. I'll leave it run until it reaches 5 or you post back.

Jonathan_King · 08 Jun 2010

Keep trying to run Driver Verifier, until you can get into Windows.

The fact that it keeps BSODing suggests it found a bad driver. I suggest a selective startup.

jsparry · 08 Jun 2010

Managed to get it to boot into windows.

Just after login as programs load it bluescreen 3 time in around the same place.

Only one mini dump was created. (attached.)

Im about to try the selective startup.

Jonathan_King · 08 Jun 2010

Looks like ASACPI.sys again. Please uninstall the utility and install a fresh copy. In case you haven't seen this: More BSOD - Windows 7 7600 - Tech Support Forum

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_060810-21309-01.zip\060810-21309-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a4c000 PsLoadedModuleList = 0xfffff800`02c89e50
Debug session time: Tue Jun  8 17:34:14.422 2010 (GMT-4)
System Uptime: 0 days 0:01:28.248
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 1a8, fffffa800855c060, fffff88003ec2257}

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

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

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

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: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 00000000000001a8, Handle value being referenced.
Arg3: fffffa800855c060, Address of the current process.
Arg4: fffff88003ec2257, Address inside the driver that is performing the incorrect reference.

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


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  QButton.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f463dc to fffff80002abc600

STACK_TEXT:  
fffff880`09b8e5b8 fffff800`02f463dc : 00000000`000000c4 00000000`000000f6 00000000`000001a8 fffffa80`0855c060 : nt!KeBugCheckEx
fffff880`09b8e5c0 fffff800`02f5bae4 : 00000000`000001a8 fffffa80`0855c060 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`09b8e600 fffff800`02d18580 : 00000000`0000345a fffff880`09b8e830 00000000`00000000 fffffa80`05d52600 : nt!VfCheckUserHandle+0x1b4
fffff880`09b8e6e0 fffff800`02d94425 : 00000000`00000000 fffff880`000f0001 00000000`00000000 fffffa80`00000000 : nt! ?? ::NNGAKEGL::`string'+0x20e1e
fffff880`09b8e7b0 fffff800`02f5b878 : fffffa80`060453a8 fffff800`02f5ebcc fffffa80`05d52550 fffffa80`05d52550 : nt!ObReferenceObjectByHandle+0x25
fffff880`09b8e800 fffff880`03ec2257 : fffff980`1320ccf0 00000000`00000002 fffffa80`05d526a0 00000000`00000000 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`09b8e850 fffff980`1320ccf0 : 00000000`00000002 fffffa80`05d526a0 00000000`00000000 fffffa80`05d526c8 : ASACPI+0x1257
fffff880`09b8e858 00000000`00000002 : fffffa80`05d526a0 00000000`00000000 fffffa80`05d526c8 00000000`00000000 : 0xfffff980`1320ccf0
fffff880`09b8e860 fffffa80`05d526a0 : 00000000`00000000 fffffa80`05d526c8 00000000`00000000 00000000`00000001 : 0x2
fffff880`09b8e868 00000000`00000000 : fffffa80`05d526c8 00000000`00000000 00000000`00000001 00000000`00000000 : 0xfffffa80`05d526a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ASACPI+1257
fffff880`03ec2257 83462001        add     dword ptr [rsi+20h],1

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  ASACPI+1257

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ASACPI

IMAGE_NAME:  ASACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a0b72fd

FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_ASACPI+1257

BUCKET_ID:  X64_0xc4_f6_VRF_ASACPI+1257

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

2: kd> lmvm ASACPI
start             end                 module name
fffff880`03ec1000 fffff880`03ec9000   ASACPI   T (no symbols)           
    Loaded symbol image file: ASACPI.sys
    Image path: \SystemRoot\system32\DRIVERS\ASACPI.sys
    Image name: ASACPI.sys
    Timestamp:        Wed May 13 21:25:17 2009 (4A0B72FD)
    CheckSum:         0000ED7A
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

jsparry · 08 Jun 2010

I've just run the selective startup and it seems to start fine.

And doesn't appear to bluescreen as of yet.

Should i just try adding services and boot stuff one at a time?

untill it blue screens?