Hi, I've got a studio 1558, core I7, 8 gig ram, 500 gig drive, Win 7 Ultimate. It's around 5 months old or so.

I've got a bad driver that is causing a reboot.  System event logs show it was caused by a bug check.  See below:

 

Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          11/18/2010 9:36:46 PM
Event ID:      1001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      XXXX

Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0xffffffffffffffd0, 0x0000000000000002, 0x0000000000000001, 0xfffff80002c806e0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 111810-15116-01.
Event Xml:
http://schemas.microsoft.com/win/2004/08/events/event">
 
   
    1001
    0
    2
    0
    0
    0x80000000000000
   
    13751
   
   
    System
    DAVELY_STUDIO
   
 
 
    0x0000000a (0xffffffffffffffd0, 0x0000000000000002, 0x0000000000000001, 0xfffff80002c806e0)
    C:\Windows\MEMORY.DMP
    111810-15116-01
 

Anayalsis as follows:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

 

 

Kernel Summary Dump File: Only kernel address space is available

 

WARNING: Whitespace at end of path element

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols

 

Executable search path is:

Windows 7 Kernel Version 7600 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621

Machine Name:

Kernel base = 0xfffff800`02c04000 PsLoadedModuleList = 0xfffff800`02e41e50

Debug session time: Thu Nov 18 21:35:23.923 2010 (UTC - 8:00)

System Uptime: 0 days 3:09:49.094

Loading Kernel Symbols

...............................................................

................................................................

.........................................

Loading User Symbols

 

Loading unloaded module list

....

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck A, {ffffffffffffffd0, 2, 1, fffff80002c806e0}

 

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

 

Followup: MachineOwner

---------

 

2: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

 

IRQL_NOT_LESS_OR_EQUAL (a)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high.  This is usually

caused by drivers using improper addresses.

If a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: ffffffffffffffd0, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000001, bitfield :

bit 0 : value 0 = read operation, 1 = write operation

bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)

Arg4: fffff80002c806e0, address which referenced memory

 

Debugging Details:

------------------

 

 

WRITE_ADDRESS:  ffffffffffffffd0

 

CURRENT_IRQL:  2

 

FAULTING_IP:

nt!ObfReferenceObject+20

fffff800`02c806e0 f0480fc11f      lock xadd qword ptr [rdi],rbx

 

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

 

BUGCHECK_STR:  0xA

 

PROCESS_NAME:  System

 

TRAP_FRAME:  fffff88009380a50 -- (.trap 0xfffff88009380a50)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000

rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff80002c806e0 rsp=fffff88009380be0 rbp=0000000000000001

 r8=0000000000000002  r9=0000000000000000 r10=0000000000000000

r11=0000000000016539 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up ei pl zr na po nc

nt!ObfReferenceObject+0x20:

fffff800`02c806e0 f0480fc11f      lock xadd qword ptr [rdi],rbx ds:8888:0000=????????????????

Resetting default scope

 

LAST_CONTROL_TRANSFER:  from fffff80002c73ca9 to fffff80002c74740

 

STACK_TEXT: 

fffff880`09380908 fffff800`02c73ca9 : 00000000`0000000a ffffffff`ffffffd0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx

fffff880`09380910 fffff800`02c72920 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69

fffff880`09380a50 fffff800`02c806e0 : fffffa80`000000d1 00000000`00000030 00000000`00000030 00000000`0000000b : nt!KiPageFault+0x260

fffff880`09380be0 fffff800`02d5eafc : fffffa80`07398888 fffffa80`07398888 00000000`00000001 00000000`00000000 : nt!ObfReferenceObject+0x20

fffff880`09380c10 fffff800`02edddaf : fffffa80`07398888 00000000`00000001 00000000`00000000 00000000`0001653a : nt!IopDisassociateThreadIrp+0x9c

fffff880`09380c40 fffff800`02f59a2b : 00000000`00000000 ffffffff`fffe7960 00000000`00000000 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x1e7aa

fffff880`09380c70 fffff800`02f5d72d : 00000000`00000000 fffff800`02f18c00 fffffa80`07398400 00000000`00000000 : nt!PspExitThread+0x58b

fffff880`09380d30 fffff800`02c52c26 : fffff880`032f9180 00000000`00000080 fffffa80`073984a0 fffff880`0142f534 : nt!PspTerminateThreadByPointer+0x4d

fffff880`09380d80 00000000`00000000 : fffff880`09381000 fffff880`0937b000 fffff880`093809c0 00000000`00000000 : nt!KxStartSystemThread+0x16

 

 

STACK_COMMAND:  kb

 

FOLLOWUP_IP:

nt!KiPageFault+260

fffff800`02c72920 440f20c0        mov     rax,cr8

 

SYMBOL_STACK_INDEX:  2

 

SYMBOL_NAME:  nt!KiPageFault+260

 

FOLLOWUP_NAME:  MachineOwner

 

MODULE_NAME: nt

 

IMAGE_NAME:  ntkrnlmp.exe

 

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

 

FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260

 

BUCKET_ID:  X64_0xA_nt!KiPageFault+260

 

Followup: MachineOwner

 

Anyone have any way to figure out what driver is causing this problem? I've updated the drivers I could. Bios is not the latest yet.  This has happened several times, but the last time took three weeks to happen.  I have original driver and install disks, but the restore partician is gone.  I ran the original install for only a few days before wiping it clean for an install of Win 7 ultimate.  Any additional info needed? I can supply three memory dump files.