bsod's

derkaderka

New member
Local time
5:22 PM
Messages
20
Windows 7 64bit, purchased from newegg 3 months ago, installed myself.
I build my pc's myself. Hardware is maybe 2 years old. Hard drive is 3 months old. This was my switch from XP to 7.

I've had bsod's for the entire 3 months. XP never gave me bsod's for 2 years previous on the same hardware. Last month I posted here because BSOD's were very frequent. After narrowing it down to an incompatible webcam/driver, BSOD's seemed to stop. But the BSOD's are back again and becoming frequent again over the last 2 weeks or so.
 
Last edited:

My Computer

OS
windows 7 64
Did I post correctly? I'm suprised I haven't gotten a reply.

Attached is a new BSOD from today.
 

My Computer

OS
windows 7 64
Did I post correctly? I'm suprised I haven't gotten a reply.

Attached is a new BSOD from today.



This one was caused by memory management and old driver.

I would
1- run memtest
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

2-Update the drivers listed below
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Let us know if you need further assistance

Ken J



Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\102010-18470-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;srv*e:\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 Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02809000 PsLoadedModuleList = 0xfffff800`02a46e50
Debug session time: Wed Oct 20 13:10:09.983 2010 (GMT-4)
System Uptime: 0 days 18:23:06.058
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {8884, fffffa800015b220, fffffa800015b910, 503}

Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+c6 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000008884, The subtype of the bugcheck.
Arg2: fffffa800015b220
Arg3: fffffa800015b910
Arg4: 0000000000000503

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


BUGCHECK_STR:  0x1a_8884

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002927e56 to fffff80002879740

STACK_TEXT:  
fffff880`05c6b8b8 fffff800`02927e56 : 00000000`0000001a 00000000`00008884 fffffa80`0015b220 fffffa80`0015b910 : nt!KeBugCheckEx
fffff880`05c6b8c0 fffff800`02986675 : fffffa80`0490d498 fffffa80`049ac000 00000000`00000000 00000000`00000000 : nt!MiRelinkStandbyPage+0xc6
fffff880`05c6b930 fffff800`02c8b504 : fffffa80`0490c000 fffff880`05c6bca0 fffff880`05c6ba08 00000000`00000001 : nt!MmSetPfnListPriorities+0x175
fffff880`05c6b980 fffff800`02cec22a : 00000000`00000020 00000000`00000000 fffffa80`0490c000 00000000`00000001 : nt!PfpPfnPrioRequest+0x84
fffff880`05c6b9d0 fffff800`02cf096e : 00000000`00000000 00000000`0169b808 00000000`0000004f fffff880`03f5a701 : nt!PfSetSuperfetchInformation+0x199
fffff880`05c6bab0 fffff800`02878993 : fffffa80`062d6760 00000000`0312b770 fffffa80`0411f600 00000000`00008a34 : nt!NtSetSystemInformation+0xb91
fffff880`05c6bc20 00000000`7733144a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0169b758 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7733144a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiRelinkStandbyPage+c6
fffff800`02927e56 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiRelinkStandbyPage+c6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1a_8884_nt!MiRelinkStandbyPage+c6

BUCKET_ID:  X64_0x1a_8884_nt!MiRelinkStandbyPage+c6

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000008884, The subtype of the bugcheck.
Arg2: fffffa800015b220
Arg3: fffffa800015b910
Arg4: 0000000000000503

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


BUGCHECK_STR:  0x1a_8884

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002927e56 to fffff80002879740

STACK_TEXT:  
fffff880`05c6b8b8 fffff800`02927e56 : 00000000`0000001a 00000000`00008884 fffffa80`0015b220 fffffa80`0015b910 : nt!KeBugCheckEx
fffff880`05c6b8c0 fffff800`02986675 : fffffa80`0490d498 fffffa80`049ac000 00000000`00000000 00000000`00000000 : nt!MiRelinkStandbyPage+0xc6
fffff880`05c6b930 fffff800`02c8b504 : fffffa80`0490c000 fffff880`05c6bca0 fffff880`05c6ba08 00000000`00000001 : nt!MmSetPfnListPriorities+0x175
fffff880`05c6b980 fffff800`02cec22a : 00000000`00000020 00000000`00000000 fffffa80`0490c000 00000000`00000001 : nt!PfpPfnPrioRequest+0x84
fffff880`05c6b9d0 fffff800`02cf096e : 00000000`00000000 00000000`0169b808 00000000`0000004f fffff880`03f5a701 : nt!PfSetSuperfetchInformation+0x199
fffff880`05c6bab0 fffff800`02878993 : fffffa80`062d6760 00000000`0312b770 fffffa80`0411f600 00000000`00008a34 : nt!NtSetSystemInformation+0xb91
fffff880`05c6bc20 00000000`7733144a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0169b758 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7733144a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiRelinkStandbyPage+c6
fffff800`02927e56 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiRelinkStandbyPage+c6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1a_8884_nt!MiRelinkStandbyPage+c6

BUCKET_ID:  X64_0x1a_8884_nt!MiRelinkStandbyPage+c6

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000008884, The subtype of the bugcheck.
Arg2: fffffa800015b220
Arg3: fffffa800015b910
Arg4: 0000000000000503

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


BUGCHECK_STR:  0x1a_8884

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002927e56 to fffff80002879740

STACK_TEXT:  
fffff880`05c6b8b8 fffff800`02927e56 : 00000000`0000001a 00000000`00008884 fffffa80`0015b220 fffffa80`0015b910 : nt!KeBugCheckEx
fffff880`05c6b8c0 fffff800`02986675 : fffffa80`0490d498 fffffa80`049ac000 00000000`00000000 00000000`00000000 : nt!MiRelinkStandbyPage+0xc6
fffff880`05c6b930 fffff800`02c8b504 : fffffa80`0490c000 fffff880`05c6bca0 fffff880`05c6ba08 00000000`00000001 : nt!MmSetPfnListPriorities+0x175
fffff880`05c6b980 fffff800`02cec22a : 00000000`00000020 00000000`00000000 fffffa80`0490c000 00000000`00000001 : nt!PfpPfnPrioRequest+0x84
fffff880`05c6b9d0 fffff800`02cf096e : 00000000`00000000 00000000`0169b808 00000000`0000004f fffff880`03f5a701 : nt!PfSetSuperfetchInformation+0x199
fffff880`05c6bab0 fffff800`02878993 : fffffa80`062d6760 00000000`0312b770 fffffa80`0411f600 00000000`00008a34 : nt!NtSetSystemInformation+0xb91
fffff880`05c6bc20 00000000`7733144a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0169b758 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7733144a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiRelinkStandbyPage+c6
fffff800`02927e56 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiRelinkStandbyPage+c6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1a_8884_nt!MiRelinkStandbyPage+c6

BUCKET_ID:  X64_0x1a_8884_nt!MiRelinkStandbyPage+c6

Followup: MachineOwner
---------
Old drivers
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\102010-18470-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;srv*e:\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 Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02809000 PsLoadedModuleList = 0xfffff800`02a46e50
Debug session time: Wed Oct 20 13:10:09.983 2010 (GMT-4)
System Uptime: 0 days 18:23:06.058
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {8884, fffffa800015b220, fffffa800015b910, 503}

Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+c6 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000008884, The subtype of the bugcheck.
Arg2: fffffa800015b220
Arg3: fffffa800015b910
Arg4: 0000000000000503

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


BUGCHECK_STR:  0x1a_8884

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002927e56 to fffff80002879740

STACK_TEXT:  
fffff880`05c6b8b8 fffff800`02927e56 : 00000000`0000001a 00000000`00008884 fffffa80`0015b220 fffffa80`0015b910 : nt!KeBugCheckEx
fffff880`05c6b8c0 fffff800`02986675 : fffffa80`0490d498 fffffa80`049ac000 00000000`00000000 00000000`00000000 : nt!MiRelinkStandbyPage+0xc6
fffff880`05c6b930 fffff800`02c8b504 : fffffa80`0490c000 fffff880`05c6bca0 fffff880`05c6ba08 00000000`00000001 : nt!MmSetPfnListPriorities+0x175
fffff880`05c6b980 fffff800`02cec22a : 00000000`00000020 00000000`00000000 fffffa80`0490c000 00000000`00000001 : nt!PfpPfnPrioRequest+0x84
fffff880`05c6b9d0 fffff800`02cf096e : 00000000`00000000 00000000`0169b808 00000000`0000004f fffff880`03f5a701 : nt!PfSetSuperfetchInformation+0x199
fffff880`05c6bab0 fffff800`02878993 : fffffa80`062d6760 00000000`0312b770 fffffa80`0411f600 00000000`00008a34 : nt!NtSetSystemInformation+0xb91
fffff880`05c6bc20 00000000`7733144a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0169b758 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7733144a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiRelinkStandbyPage+c6
fffff800`02927e56 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiRelinkStandbyPage+c6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1a_8884_nt!MiRelinkStandbyPage+c6

BUCKET_ID:  X64_0x1a_8884_nt!MiRelinkStandbyPage+c6

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000008884, The subtype of the bugcheck.
Arg2: fffffa800015b220
Arg3: fffffa800015b910
Arg4: 0000000000000503

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


BUGCHECK_STR:  0x1a_8884

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002927e56 to fffff80002879740

STACK_TEXT:  
fffff880`05c6b8b8 fffff800`02927e56 : 00000000`0000001a 00000000`00008884 fffffa80`0015b220 fffffa80`0015b910 : nt!KeBugCheckEx
fffff880`05c6b8c0 fffff800`02986675 : fffffa80`0490d498 fffffa80`049ac000 00000000`00000000 00000000`00000000 : nt!MiRelinkStandbyPage+0xc6
fffff880`05c6b930 fffff800`02c8b504 : fffffa80`0490c000 fffff880`05c6bca0 fffff880`05c6ba08 00000000`00000001 : nt!MmSetPfnListPriorities+0x175
fffff880`05c6b980 fffff800`02cec22a : 00000000`00000020 00000000`00000000 fffffa80`0490c000 00000000`00000001 : nt!PfpPfnPrioRequest+0x84
fffff880`05c6b9d0 fffff800`02cf096e : 00000000`00000000 00000000`0169b808 00000000`0000004f fffff880`03f5a701 : nt!PfSetSuperfetchInformation+0x199
fffff880`05c6bab0 fffff800`02878993 : fffffa80`062d6760 00000000`0312b770 fffffa80`0411f600 00000000`00008a34 : nt!NtSetSystemInformation+0xb91
fffff880`05c6bc20 00000000`7733144a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0169b758 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7733144a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiRelinkStandbyPage+c6
fffff800`02927e56 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiRelinkStandbyPage+c6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1a_8884_nt!MiRelinkStandbyPage+c6

BUCKET_ID:  X64_0x1a_8884_nt!MiRelinkStandbyPage+c6

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000008884, The subtype of the bugcheck.
Arg2: fffffa800015b220
Arg3: fffffa800015b910
Arg4: 0000000000000503

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


BUGCHECK_STR:  0x1a_8884

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002927e56 to fffff80002879740

STACK_TEXT:  
fffff880`05c6b8b8 fffff800`02927e56 : 00000000`0000001a 00000000`00008884 fffffa80`0015b220 fffffa80`0015b910 : nt!KeBugCheckEx
fffff880`05c6b8c0 fffff800`02986675 : fffffa80`0490d498 fffffa80`049ac000 00000000`00000000 00000000`00000000 : nt!MiRelinkStandbyPage+0xc6
fffff880`05c6b930 fffff800`02c8b504 : fffffa80`0490c000 fffff880`05c6bca0 fffff880`05c6ba08 00000000`00000001 : nt!MmSetPfnListPriorities+0x175
fffff880`05c6b980 fffff800`02cec22a : 00000000`00000020 00000000`00000000 fffffa80`0490c000 00000000`00000001 : nt!PfpPfnPrioRequest+0x84
fffff880`05c6b9d0 fffff800`02cf096e : 00000000`00000000 00000000`0169b808 00000000`0000004f fffff880`03f5a701 : nt!PfSetSuperfetchInformation+0x199
fffff880`05c6bab0 fffff800`02878993 : fffffa80`062d6760 00000000`0312b770 fffffa80`0411f600 00000000`00008a34 : nt!NtSetSystemInformation+0xb91
fffff880`05c6bc20 00000000`7733144a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0169b758 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7733144a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiRelinkStandbyPage+c6
fffff800`02927e56 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiRelinkStandbyPage+c6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1a_8884_nt!MiRelinkStandbyPage+c6

BUCKET_ID:  X64_0x1a_8884_nt!MiRelinkStandbyPage+c6

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

My Computer

Computer Manufacturer/Model Number
HP Pavillion dv-7 1005 Tx
OS
Win 8 Release candidate 8400
CPU
[email protected]
Memory
4 gigs
Graphics Card(s)
Nvidia 9600M
Sound Card
HD built-in
Monitor(s) Displays
17" Wxga
Screen Resolution
1440x900
Cooling
none
Internet Speed
45Mb down 5Mb up
I don't see any names of "old drivers" in the above post. Both of those copies of code seem to be identical.
 

My Computer

OS
windows 7 64
I have no idea what drivers I should be trying to update, since the above post didn't mention a speciic driver. And no driver verifier didn't raise any flags.

I have been getting a barrage of new BSOD's with different errors this week, at least 4 today. So I tested the memory - 2 sticks of 2 gigs each, in dual channel. Test failed and I got BSOD on reboot. Then I tested 1 stick at a time, both in same slot - 1 failed, 1 passed.

So now I'm running the one 1 stick of 2 gigs that passed. (My PC is sluggish w/o the full 4 gigs). But... a new BSOD just 20 minutes later... attached.
 

My Computer

OS
windows 7 64
Minutes later, another BSOD, seems exactly the same as the previous. Something about stopping a driver that was trying to corrupt ? idk.
 

My Computer

OS
windows 7 64
Can someone please read the last 2 dumps I posted and tell me the name/type of driver that is giving me these BSOD's please please please?
 

My Computer

OS
windows 7 64
just got a new bsod yet again... invalid kernel handle 0x00000093
 

My Computer

OS
windows 7 64
2 seconds later, i get another bsod while trying to install new cpu drivers...

0x000000c9 DRIVER_VERIFIER_IOMANAGER_VIOLATION
 

My Computer

OS
windows 7 64
the last bsod (0xc9) seems to be reproduceable. i get it when trying to update my cpu drivers. which means i can't update my drivers. can anyone indentify whats wrong here? seriously, it seems i have hardware failures, but not just one.

since i already removed failing ram yesterday, but since then i have gotten tons of new bsod's, so now i'm looking at a bad mobo or cpu/memory controller? idk i'm just guessing and i know very little about failures.

right now i'm just about to hit up newegg and buy a whole fricken new pc. i can't believe i have been posting here all week and haven't gotten but one reply and no follow up whatsoever. any insight would help. my pc is running like dogcrap and i can't go 30 minutes w/o a blue screen. its ridiculous. i can't get any work done.
 

My Computer

OS
windows 7 64
So, out of desparation, I decided to go back to windows Xp on my old harddrive... everything else is the same hardware += no bsod's.

so i guess i need to reformat the windows 7 drive and hope the bsod's don't come back.

still, i'd like to know why it has come to having to reformat due to a bombardment of bsod's that went unanswered here. and why was it causing windows 7 to claim my hardware was bad.
 

My Computer

OS
windows 7 64
I have no idea what drivers I should be trying to update, since the above post didn't mention a speciic driver. And no driver verifier didn't raise any flags.

I have been getting a barrage of new BSOD's with different errors this week, at least 4 today. So I tested the memory - 2 sticks of 2 gigs each, in dual channel. Test failed and I got BSOD on reboot. Then I tested 1 stick at a time, both in same slot - 1 failed, 1 passed.

So now I'm running the one 1 stick of 2 gigs that passed. (My PC is sluggish w/o the full 4 gigs). But... a new BSOD just 20 minutes later... attached.

This last one was caused by your adaware driver KernExplorer64.sys. It should be removed to test


Ken

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\102810-35521-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;srv*e:\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 Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0281a000 PsLoadedModuleList = 0xfffff800`02a57e50
Debug session time: Thu Oct 28 17:34:48.772 2010 (GMT-4)
System Uptime: 0 days 0:28:46.411
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 4, fffffa8003615b30, fffff8800747d273}

Unable to load image \??\C:\Program Files (x86)\Lavasoft\Ad-Aware\KernExplorer64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for KernExplorer64.sys
*** ERROR: Module load completed but symbols could not be loaded for KernExplorer64.sys
Probably caused by : KernExplorer64.sys ( KernExplorer64+1273 )

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: 0000000000000004, Handle value being referenced.
Arg3: fffffa8003615b30, Address of the current process.
Arg4: fffff8800747d273, 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:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002d143dc to fffff8000288a740

STACK_TEXT:  
fffff880`09bbd658 fffff800`02d143dc : 00000000`000000c4 00000000`000000f6 00000000`00000004 fffffa80`03615b30 : nt!KeBugCheckEx
fffff880`09bbd660 fffff800`02d29ae4 : 00000000`00000004 fffffa80`03615b30 00000000`00000002 fffffa80`04a82060 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`09bbd6a0 fffff800`02ae5b40 : fffff800`02a19880 fffff880`09bbd8d0 00000000`00000000 fffffa80`03493e00 : nt!VfCheckUserHandle+0x1b4
fffff880`09bbd780 fffff800`02b615f5 : 00000000`00000300 fffff800`00000000 00000000`00000000 fffffa80`03fdb000 : nt! ?? ::NNGAKEGL::`string'+0x20e2e
fffff880`09bbd850 fffff800`02d29878 : 00000000`00000348 fffffa80`03493e40 fffff880`09bbd930 fffff880`0747db52 : nt!ObReferenceObjectByHandle+0x25
fffff880`09bbd8a0 fffff880`0747d273 : 00000000`00000000 fffffa80`02909000 fffffa80`03493e40 00000000`00000000 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`09bbd8f0 00000000`00000000 : fffffa80`02909000 fffffa80`03493e40 00000000`00000000 fffff880`09bbd9b0 : KernExplorer64+0x1273


STACK_COMMAND:  kb

FOLLOWUP_IP: 
KernExplorer64+1273
fffff880`0747d273 807c244001      cmp     byte ptr [rsp+40h],1

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  KernExplorer64+1273

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: KernExplorer64

IMAGE_NAME:  KernExplorer64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4be3e1d3

FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_KernExplorer64+1273

BUCKET_ID:  X64_0xc4_f6_VRF_KernExplorer64+1273

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

My Computer

Computer Manufacturer/Model Number
HP Pavillion dv-7 1005 Tx
OS
Win 8 Release candidate 8400
CPU
[email protected]
Memory
4 gigs
Graphics Card(s)
Nvidia 9600M
Sound Card
HD built-in
Monitor(s) Displays
17" Wxga
Screen Resolution
1440x900
Cooling
none
Internet Speed
45Mb down 5Mb up
Back
Top