BSOD windows 7 ulti x64 stop 0x000000F4

[woootnesss]

Since i built my computer back in august of 2010 I've been getting random BSOD's i was wondering if anyone could shed some light on my issue.View attachment 128371

 

[zigzag3143]

Since i built my computer back in august of 2010 I've been getting random BSOD's i was wondering if anyone could shed some light on my issue.View attachment 128371

There are many problem here. I cannot get to the underlying cause untill you resolve these.

1-sptd.sys a huge cause of BSOD's

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

2-AVG. remove and replace with Microsoft security essentials

AVG - Download tools

http://www.microsoft.com/security_essentials/

3-old drivers

 Lycosa.sys    1/18/2008 3:51:42    0x4790689e    fffff880`0546a000    fffff880`0546e980        0x00004980                    
dump_JRAID.sys    10/1/2008 1:30:44    0x48e31914    fffff880`0468b000    fffff880`046a6000        0x0001b000                    
jraid.sys    10/1/2008 1:30:44    0x48e31914    fffff880`0122a000    fffff880`01245000        0x0001b000                    
iaStorV.sys    4/8/2009 11:57:17    0x49dcd76d    fffff880`012ba000    fffff880`013d8000        0x0011e000

especially the raid drivers.

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 Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

4-NDIS (your miniport driver) Run SFC to verify and repair

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html?ltr=S

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\121710-33789-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03253000 PsLoadedModuleList = 0xfffff800`03490e50
Debug session time: Fri Dec 17 18:06:57.726 2010 (GMT-5)
System Uptime: 0 days 4:56:24.881
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa800732c040, fffff80004a7b510}

Probably caused by : ndis.sys ( ndis!ndisPnPRemoveDeviceEx+112 )

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa800732c040, The thread currently holding on to the Pnp lock.
Arg4: fffff80004a7b510

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


DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  fffffa800732c040

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800032ca992 to fffff800032c95da

STACK_TEXT:  
fffff880`035853d0 fffff800`032ca992 : fffffa80`0732c040 fffffa80`0732c040 00000000`00000000 00000000`0000000d : nt!KiSwapContext+0x7a
fffff880`03585510 fffff800`032cccff : fffffa80`0855b1a0 fffffa80`0855b000 fffff880`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
fffff880`035855a0 fffff880`017046f2 : fffffa80`0855b100 00000000`00000000 fffffa80`07ef9b00 fffffa80`07c9f400 : nt!KeWaitForSingleObject+0x19f
fffff880`03585640 fffff880`0175f0c2 : 00000000`00000000 fffffa80`0855b1a0 fffffa80`07ef9bd0 00000000`00000002 : ndis!ndisPnPRemoveDeviceEx+0x112
fffff880`035856a0 fffff880`00e8093c : 00000000`00000001 fffffa80`07ef9dc0 fffffa80`07ca38c0 00000000`00000000 : ndis! ?? ::LNCPHCLB::`string'+0x73a3
fffff880`03585740 fffff880`00e792ce : 00000000`00000001 fffff880`03585850 fffff880`03585800 fffffa80`07ca3800 : Wdf01000!FxPkgFdo::ProcessRemoveDeviceOverload+0x74
fffff880`03585770 fffff880`00e77dd6 : fffffa80`0c425c02 00000000`c00000bb 00000000`00000000 fffffa80`07ca38c0 : Wdf01000!FxPkgPnp::_PnpRemoveDevice+0x126
fffff880`035857e0 fffff880`00e47245 : fffffa80`07ef9bd0 fffffa80`07ef9bd0 fffffa80`0bb2f9c0 fffffa80`0bb2f9c0 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
fffff880`03585850 fffff880`00e4714b : 00000000`00000006 fffffa80`07ef9bd0 00000000`c00000bb fffffa80`0bb2f9c0 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`03585880 fffff800`0352f519 : fffffa80`0bb2f9c0 00000000`c00000bb fffff880`03585978 fffffa80`07ef9bd0 : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff880`035858c0 fffff800`036ad831 : fffffa80`07c9f440 00000000`00000000 fffffa80`07981480 00000000`00000801 : nt!IopSynchronousCall+0xc5
fffff880`03585930 fffff800`033c4bf3 : fffff8a0`04ba68a0 fffff8a0`04ba68a0 00000000`0000000a 00000000`00000000 : nt!IopRemoveDevice+0x101
fffff880`035859f0 fffff800`036ad384 : fffffa80`07981480 00000000`00000000 00000000`00000002 fffffa80`07c9f440 : nt!PnpRemoveLockedDeviceNode+0x1a3
fffff880`03585a40 fffff800`036ad490 : 00000000`00000000 fffff8a0`04be0300 fffff8a0`0b82d2c0 ffffe611`4878b634 : nt!PnpDeleteLockedDeviceNode+0x44
fffff880`03585a70 fffff800`0373d984 : 00000000`00000002 00000000`00000000 fffffa80`07981480 fffff8a0`04be03d0 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff880`03585ae0 fffff800`0373dfdc : fffff880`03585cb8 fffffa80`07820100 fffffa80`0732c000 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0xc34
fffff880`03585c20 fffff800`036290dc : 00000000`00000000 fffffa80`07820110 fffff8a0`04be03d0 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`03585c50 fffff800`032d0961 : fffff800`0352f008 fffff8a0`04be03d0 fffff800`034685f8 fffff800`034685f8 : nt! ?? ::NNGAKEGL::`string'+0x58ffb
fffff880`03585cb0 fffff800`03567c06 : 53005300`e1cce1cc fffffa80`0732c040 00000000`00000080 fffffa80`0730f990 : nt!ExpWorkerThread+0x111
fffff880`03585d40 fffff800`032a1c26 : fffff880`0336a180 fffffa80`0732c040 fffff880`033750c0 825d825d`03b603b6 : nt!PspSystemThreadStartup+0x5a
fffff880`03585d80 00000000`00000000 : fffff880`03586000 fffff880`03580000 fffff880`035855c0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .thread 0xfffffa800732c040 ; kb

FOLLOWUP_IP: 
ndis!ndisPnPRemoveDeviceEx+112
fffff880`017046f2 4883a3f805000000 and     qword ptr [rbx+5F8h],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  ndis!ndisPnPRemoveDeviceEx+112

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ndis

IMAGE_NAME:  ndis.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc184

FAILURE_BUCKET_ID:  X64_0x9F_ndis!ndisPnPRemoveDeviceEx+112

BUCKET_ID:  X64_0x9F_ndis!ndisPnPRemoveDeviceEx+112

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

There are more that will only become apparent when these have been eliminated

 

[woootnesss]

Step 3

So I've reached the driver portion of attempting to fix my errors and i have a few questions about the RAID drivers. I went to the website you gave me and searched for jmicron and downloaded a zip named JMB36X_WinDrv_R1.17.62_WHQL.zip which is think is the file i need. How do i install them? will i need to create a boot-able flash inorder to install them or..? I'm going to do some more searching on the matter but i would much appreciate the already exuberant help.

 

[CarlTR6]

Unzip the file to a folder on your desktop. Open the folder. If there is an .exe file, click on it and it will install the driver.

 

[woootnesss]

did everything

i did everything you told me but im still getting the bsod =/. maybe i got the wrong raid driver?

 

[CarlTR6]

Please upload your latest BSOD's.

 

[woootnesss]

heres the updated reports

 

[CarlTR6]

There are no dump files included. Look in C:\Windows\Minidump. Copy your most recently dated dumps to your desktop, zip them and upload them.

 

[woootnesss]

says its empty

 

[woootnesss]

what now

what should i do at this point?

 

[CarlTR6]

1. Make sure your computer is set for mini dump[s and not memory dumps. Read the last part of the first post in this tutorial: http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

2. If you are running any type of cleaning program, such as Ccleaner, make sure that it is not set to clean dump files.

Then we wait for the next BSOD and dump file.