Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Multiple BSODs

28 May 2011   #41
Ran

Windows 7 Profesional 64 bit
 
 

Turned verifier on, sfc was error free, I had already run a short hard drive test before you posted, and the long one will probably take a while, so I figured I would just let you know right now.

Edit: Long tests passed as well


My System SpecsSystem Spec
.
29 May 2011   #42
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

Change the CPU/NB voltage to 1.30v, default setting should be 1.100v.
Change the Dram voltage to 1.60v.

Run Prime95 torture test.
First open Core Temp to monitor CPU temperatures, don't go over 71°C.
Open Prime95 and stop the test if it is running, in Advanced tab select 'Round off checking', in the Options tab select 'Torture Test...', in the window that opens select 'Blend', after 'Number of torture test threads to run' enter 4, then click OK to start the test.
My System SpecsSystem Spec
29 May 2011   #43
Ran

Windows 7 Profesional 64 bit
 
 

Got another bsod. Driver verifier wasn't on at the time because I hadn't restarted my computer after the hard drive test. I'll edit this post with the results of prime and will change the voltages now.

EDIT: Prime passed fine after 3 hours.
My System SpecsSystem Spec
.

29 May 2011   #44
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

The stop code is STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a very common bug check, the debugger doesn't give a lot of information on the cause.

Code:
 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
 
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP: 
+6333373330386364
00000000`00000000 ??              ???
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR:  0x1E_0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  2
EXCEPTION_RECORD:  fffff88002f8b328 -- (.exr 0xfffff88002f8b328)
ExceptionAddress: fffff80002c947a5 (nt!KiTimerWaitTest+0x00000000000002a5)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: ffffffffffffffff
   Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000
TRAP_FRAME:  fffff88002f8b3d0 -- (.trap 0xfffff88002f8b3d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000009 rbx=0000000000000000 rcx=0000000000000000
rdx=effffa8003fb80d0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c947a5 rsp=fffff88002f8b560 rbp=effffa8003fb80d0
 r8=fffff88002f65301  r9=0000000000000002 r10=0000000000000002
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe cy
nt!KiTimerWaitTest+0x2a5:
fffff800`02c947a5 488b6d00        mov     rbp,qword ptr [rbp] ss:0018:effffa80`03fb80d0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002c836be to fffff80002c8bcd0
STACK_TEXT:  
fffff880`02f8a408 fffff800`02c836be : 00000000`00000002 fffff800`031f7e08 fffff880`02f8ab80 fffff800`02cb7890 : nt!KeBugCheck
fffff880`02f8a410 fffff800`02cb755d : fffff800`02e92968 fffff800`02dcfcbc fffff800`02c0c000 fffff880`02f8b328 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f8a440 fffff800`02cb6335 : fffff800`02dd30fc fffff880`02f8a4b8 fffff880`02f8b328 fffff800`02c0c000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f8a470 fffff800`02cc73b1 : fffff880`02f8b328 fffff880`02f8ab80 fffff880`00000000 fffffa80`03d7bcc0 : nt!RtlDispatchException+0x415
fffff880`02f8ab50 fffff800`02c8b382 : fffff880`02f8b328 fffffa80`03d7bcc8 fffff880`02f8b3d0 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`02f8b1f0 fffff800`02c89b52 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02f8b3d0 fffff800`02c947a5 : fffff800`02dfee80 fffffa80`05ac4b60 00000000`00000000 fffffa80`03d7bcc0 : nt!KiStackFault+0x112
fffff880`02f8b560 fffff800`02c9749d : fffffa80`03d7bcc0 fffffa80`040cc298 fffffa80`040cc298 00000000`00000000 : nt!KiTimerWaitTest+0x2a5
fffff880`02f8b5e0 fffff800`02c973de : 000000ab`50432319 fffff880`02f8bc58 00000000`0047f802 fffff880`02f655c8 : nt!KiProcessExpiredTimerList+0x6d
fffff880`02f8bc30 fffff800`02c971c7 : 00000032`5c823bc1 00000032`0047f802 00000032`5c823b95 00000000`00000002 : nt!KiTimerExpiration+0x1be
fffff880`02f8bcd0 fffff800`02c83a2a : fffff880`02f63180 fffff880`02f6dfc0 00000000`00000000 fffff880`04855480 : nt!KiRetireDpcList+0x277
fffff880`02f8bd80 00000000`00000000 : fffff880`02f8c000 fffff880`02f86000 fffff880`02f8bd40 00000000`00000000 : nt!KiIdleLoop+0x5a
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`02c836be 90              nop
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Followup: MachineOwner
---------
Check for newer drivers, 2009+, or uninstall the programs for testing purposes.

Code:
AsIO AsIO.sys Mon Dec 17 17:11:49 2007 - Asus PCProbe Utility - http://support.asus.com/download/download.aspx
Uninstall all the Asus utility programs, they are known to cause crashes.
You can re-install later, one by one, if you want to keep them.

You have a lot of these errors, as well as app hangs.
Since sfc scannow didn't repair it, rebuild the index.
How to Rebuild the Windows 7 Index
Code:
 
Event[190]:
  Log Name: Application
  Source: Microsoft-Windows-Search
  Date: 2011-05-27T16:58:48.000
  Event ID: 3028
  Task: Gatherer
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Ryan-PC
  Description: 
The gatherer object cannot be initialized.
Context: Windows Application, SystemIndex Catalog
Details:
 The content index catalog is corrupt.  (HRESULT : 0xc0041801) (0xc0041801)
 
Event[193]:
  Log Name: Application
  Source: Microsoft-Windows-Search
  Date: 2011-05-27T16:58:47.000
  Event ID: 9002
  Task: Search service
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Ryan-PC
  Description: 
The Windows Search Service cannot load the property store information.
Context: Windows Application, SystemIndex Catalog
Details:
 The content index server cannot find a description of the content index in its database. Search will automatically attempt to recreate the content index description.  If this problem persists, stop and restart the search service and, if necessary, delete  and recreate the content index.  (HRESULT : 0x80041181) (0x80041181)
Update MSE, this is indicating that the latest definitions have not been updated.
Code:
Event[3618]:
  Log Name: System
  Source: Microsoft Antimalware
  Date: 2011-05-28T18:43:28.000
  Event ID: 3002
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Ryan-PC
  Description: 
Microsoft Antimalware Real-Time Protection feature has encountered an error and failed.
  Feature: Behavior Monitoring
  Error Code: 0x80004005
  Error description: Unspecified error 
  Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection.
Update, reinstall the mouse driver.
Code:
Event[5331]:
  Log Name: System
  Source: XMouseButton Launcher
  Date: 2011-05-28T07:59:31.000
  Event ID: 0
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Ryan-PC
  Description: N/A
Which Graphics Card driver do you have installed?
AODDriver.sys - this is reported as >AMD Overdrive; also in EasyTune6 for Gigabyte motherboard
I am assuming you have an Asus mobo, add to your system specs.
Post the current perfmon report in your next post.
Code:
Event[6025]:
  Log Name: System
  Source: Service Control Manager
  Date: 2011-05-27T18:33:06.155
  Event ID: 7000
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Ryan-PC
  Description: 
The AODDriver4.0 service failed to start due to the following error: 
The system cannot find the path specified.
There are many errors per day, let's do a malware check.
Download and run Malwarebytes, be sure to update it before running.


If this doesen't fix the problem, then you need to look at hardware.

You have the latest BIOS version for your motherboard.

You have done a lot of testing, your next step may be to do a Repair Install or Clean Install.
Let's eliminate all the hardware possible causes first.

Replace your keyboard and mouse for testing purposes, if you have a spare or borrow them, I have seen these cause this type of crash.

At this stage it is best to try and eliminate all variables as possible.

Disconnect all peripherals not required to run your system, all external drives, any USB hubs or connected devices, CD ROM if not needed, sound card and speakers, etc., everything.

If the crashes stop, then re-install them one at a time and test for stability.
If they don't stop then you need to look at the main internal components.
My System SpecsSystem Spec
30 May 2011   #45
Ran

Windows 7 Profesional 64 bit
 
 

-I uninstalled asus probe, never used it anyway.
-The Index is being rebuilt.
-I updated MSE.
-Uninstalled, and then reinstalled xmousebutton.
-I am not really sure how to answer your graphics driver question, but I installed the Catalyst Software Suite from http://sites.amd.com/us/game/downloads/Pages/radeon_win7-64.aspx.
-I do have an asus mobo, specific model number : M4A78T-E
-Things plugged into my computer: Speakers : Headset/Mic : mouse : keyboard : TV used as a second monitor. Those are the only unnecessary things, so I will unplug all that and use an old mouse + keyboard.
-I got another bsod, right after I uninstalled pc probe, and reset the index.
-I will attach the bsod and perfmon report, update the post with the results of the malware scan, and let you know if I have any more problems.

EDIT: Malwarebytes found 4 potential threats which I had it remove after a full computer scan.
c:\$Recycle.Bin\s-1-5-21-1105035022-2918786625-2477223559-1000\$RB0KDPP.exe (PUP.SmsPay.PGen)
c:\$Recycle.Bin\s-1-5-21-1105035022-2918786625-2477223559-1000\$RK81WFF.exe (PUP.SmsPay.PGen)
c:\program files (x86)\teamviewer\Version6\teamviewer_desktop.exe (Trojan.Agent)
c:\Users\Ryan\Dropbox\Version6\teamviewer_desktop.exe (Trojan.Agent)

Two random exes in the recycle bin, and from teamviewer, which I doubt is really a trojan.
My System SpecsSystem Spec
31 May 2011   #46
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

The AMD Radeon drivers from that site are version 11.5.

Good work on the trouble shooting steps.

Keep posting the results and any new dump files.


This dump indicates STOP 0x000000C1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
Usual causes: Device driver, ?Memory

Cause: A driver has written to an invalid section of the special pool.

Did you change the voltages mentioned above?
Quote:
Change the CPU/NB voltage to 1.30v.
Change the Dram voltage to 1.60v.
Run memtest86+, again, I know you have ran this several times. I have seen memtest86+ find errors after several clean runs. It is just the way electronics are. Run it overnight.

RAM - Test with Memtest86+

The best way to test if the RAM is causing the crashes is to get another set of RAM that are known to be working and run them in your system.
You mentioned before that you had some that you could try, but never confirmed if you tried them.

Code:
 
 *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption.  Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: fffff98053ad4fe0, address trying to free
Arg2: fffff98053ad4f87, address where bits are corrupted
Arg3: 0000000000710016, (reserved)
Arg4: 0000000000000023, caller is freeing an address where nearby bytes within the same page have been corrupted
Debugging Details:
------------------
 
BUGCHECK_STR:  0xC1_23
SPECIAL_POOL_CORRUPTION_TYPE:  23
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  SearchProtocol
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff80002d06ffa to fffff80002c80d00
STACK_TEXT:  
fffff880`082f0368 fffff800`02d06ffa : 00000000`000000c1 fffff980`53ad4fe0 fffff980`53ad4f87 00000000`00710016 : nt!KeBugCheckEx
fffff880`082f0370 fffff800`02d7fa03 : fffffa80`019971c0 fffff800`02c90ee6 00000000`00000001 00000000`00000000 : nt!MiCheckSpecialPoolSlop+0x9a
fffff880`082f03b0 fffff800`02dab93b : fffff800`02c01000 00000000`20206f49 ffffffff`ffdce779 fffff980`791a4990 : nt!MmFreeSpecialPool+0x1d3
fffff880`082f04f0 fffff800`02c847a1 : fffff980`791a4fbb fffff800`00000001 00000000`00000001 fffff880`00000005 : nt!ExDeferredFreePool+0xf33
fffff880`082f05a0 fffff800`0311d19f : fffff980`791a4990 fffff980`a55e0b01 fffff980`791a4901 00000000`00000000 : nt!IopfCompleteRequest+0xac1
fffff880`082f0680 fffff880`01254e84 : fffff980`47300e40 fffff980`00000001 fffff980`47300e40 fffff980`791a4990 : nt!IovCompleteRequest+0x19f
fffff880`082f0750 fffff880`012dbd76 : 00000000`00000000 fffff980`a55e0bc0 00000000`00000000 fffff980`47300e01 : Ntfs!NtfsExtendedCompleteRequestInternal+0x114
fffff880`082f0790 fffff880`012dbff1 : 00000000`00000010 fffff880`012dbf50 00000000`00000010 00000000`00010286 : Ntfs!NtfsQueryDirectory+0x1cec
fffff880`082f0b30 fffff880`012de8ef : fffff980`47300e40 00000000`00000000 00000000`00000002 00000000`00000000 : Ntfs!NtfsCommonDirectoryControl+0xa1
fffff880`082f0b70 fffff800`03123c16 : fffff980`791a4990 fffff980`791a4990 fffff980`47300e40 fffff880`082f0b98 : Ntfs!NtfsFsdDirectoryControl+0x10f
fffff880`082f0be0 fffff880`0101c6af : fffff980`06782de0 00000000`00000002 fffff980`06782de0 fffff980`67b34f40 : nt!IovCallDriver+0x566
fffff880`082f0c40 fffff800`03123c16 : fffff980`791a4990 00000000`00000002 fffff980`36c98f20 00000000`000008f4 : fltmgr!FltpDispatch+0x9f
fffff880`082f0ca0 fffff800`02f69acd : fffff980`791a4990 00000000`00000001 fffff980`36c98f20 fffff980`8860af40 : nt!IovCallDriver+0x566
fffff880`082f0d00 fffff800`02c7ff93 : fffff980`49d60b60 fffff880`082f0ed0 fffff880`082f1008 fffff880`082f0df8 : nt!NtQueryDirectoryFile+0x1ad
fffff880`082f0de0 fffff800`02c7c530 : fffff880`010412d1 fffff980`00000060 fffff980`4a7b0f98 fffff980`acba8f10 : nt!KiSystemServiceCopyEnd+0x13
fffff880`082f0fe8 fffff880`010412d1 : fffff980`00000060 fffff980`4a7b0f98 fffff980`acba8f10 fffff980`4a7b0f98 : nt!KiServiceLinkage
fffff880`082f0ff0 fffff880`0103eafe : fffff980`4a7b0f98 00000000`00000038 00000000`00000000 00000000`00000038 : fltmgr!FltpNormalizeNameComponent+0x221
fffff880`082f10f0 fffff880`0103ff81 : fffff980`0000003c 00000000`0000004a 00000000`00000039 00000000`00000000 : fltmgr!FltpExpandShortNames+0x14e
fffff880`082f1150 fffff880`0103fe1e : fffff980`acba8f10 fffff880`01040000 00000000`00000000 00000000`00000000 : fltmgr!FltpGetNormalizedFileNameWorker+0xc1
fffff880`082f1190 fffff880`010214fb : fffffa80`04bf8080 00000000`00000000 fffff980`7778af50 fffff880`082f2000 : fltmgr!FltpCreateFileNameInformation+0xee
fffff880`082f11f0 fffff880`0102cb44 : 00000000`00008000 fffff980`7778af50 00000000`00000000 00000000`00000401 : fltmgr!FltpGetFileNameInformation+0x26b
fffff880`082f1270 fffff880`0105d1f7 : fffff980`acba8f10 00000000`00000401 fffff980`7fc08de0 fffff880`082f1350 : fltmgr!FltGetFileNameInformation+0x184
fffff880`082f1300 fffff880`0107036b : fffff980`b6522fb0 00000000`00000001 fffff880`082f13d0 fffff980`2ff1cfb0 : fltmgr!FltvGetFileNameInformation+0x47
fffff880`082f1330 fffff880`0106ebdb : fffff301`820c5e27 fffff800`00000001 00000000`00000000 00000000`00010bdd : fileinfo!FIStreamGetInfo+0x11f
fffff880`082f13b0 fffff880`0105a9cb : 00000000`00000000 fffff980`b6522fb0 00000000`00000008 fffff980`00000000 : fileinfo!FIPostCreateCallback+0x1c7
fffff880`082f1440 fffff880`0101f288 : fffff980`040babc0 fffff980`4de56fb8 fffff301`820c5e27 00000000`00000000 : fltmgr!FltvPostOperation+0x9b
fffff880`082f14c0 fffff880`0101dd1b : fffff980`4de56fb8 fffff980`7fc08f00 fffff980`08a0cbb0 fffff980`08a0cdd0 : fltmgr!FltpPerformPostCallbacks+0x368
fffff880`082f1590 fffff880`0103d2b9 : fffff980`4de56990 fffff980`059e4800 fffff980`4de56900 fffff980`06782de0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x39b
fffff880`082f1620 fffff800`03123c16 : fffff980`4de56990 00000000`00000002 00000000`00000040 00000000`00000000 : fltmgr!FltpCreate+0x2a9
fffff880`082f16d0 fffff800`02f7e625 : 00000000`00000005 fffff980`711c8cc8 fffff980`4e5f4b10 fffff980`3bd66f40 : nt!IovCallDriver+0x566
fffff880`082f1730 fffff800`02f7aec8 : fffff980`06322cd0 fffff800`00000000 fffff980`711c8b10 fffff800`00000001 : nt!IopParseDevice+0x5a5
fffff880`082f18c0 fffff800`02f7c0e6 : 00000000`00000000 fffff980`711c8b10 fffff980`4ad92b30 fffff980`00728f30 : nt!ObpLookupObjectName+0x588
fffff880`082f19b0 fffff800`02f7d9ec : fffff980`8a894fb0 00000000`00000000 fffff800`02e06901 fffff800`031f1b7f : nt!ObOpenObjectByName+0x306
fffff880`082f1a80 fffff800`02f88608 : 00000000`00f44eb0 00000000`80000000 00000000`00f44eb8 00000000`00f44f00 : nt!IopCreateFile+0x2bc
fffff880`082f1b20 fffff800`02c7ff93 : 00000000`00000000 fffff800`02f6921c fffff880`082f1ca0 00000000`00000000 : nt!NtCreateFile+0x78
fffff880`082f1bb0 00000000`77cf186a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00f44e48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77cf186a
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!MiCheckSpecialPoolSlop+9a
fffff800`02d06ffa cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt!MiCheckSpecialPoolSlop+9a
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  X64_0xC1_23_VRFK_nt!MiCheckSpecialPoolSlop+9a
BUCKET_ID:  X64_0xC1_23_VRFK_nt!MiCheckSpecialPoolSlop+9a
Followup: MachineOwner
---------

The asus probe driver is still showing up in your drivers.
Code:
 AsIO     AsIO.sys     Mon Dec 17 17:11:49 2007
Drivers - Clean Left over Files after Uninstalling
Be careful, you can cause crashes by uninstalling the wrong things.


Still getting this MSE error.
Update MSE after you have the Index rebuilt.
Code:
Event[82]:
  Log Name: System
  Source: Microsoft Antimalware
  Date: 2011-05-30T19:09:21.000
  Event ID: 3002
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Ryan-PC
  Description: 
Microsoft Antimalware Real-Time Protection feature has encountered an error and failed.
  Feature: Behavior Monitoring
  Error Code: 0x80004005
  Error description: Unspecified error 
  Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection.
My System SpecsSystem Spec
31 May 2011   #47
Ran

Windows 7 Profesional 64 bit
 
 

-I edited my last post with the info about malwarebytes
-The voltages have been changed.
-I do have two sticks of 1GB of ram in another computer, but now that I think about it, I do after all need 4 because I am running 64x Win 7. Currently I have two sticks of 2 GB, DDR3 ram from ADATA.
-I am a little wary of using driver sweeper again, as last time I spent more than 24 hours with my computer trying to remove sp1 so that I could do a repair install, failing, and then just using system restore. Also, it can be used for "NVIDIA (Display and Chipset), ATI (Display), Creative (Sound), Ageia (PhysX), MMouse and Realtek (Sound)" and I am needing to remove asus drivers. Is there another way to make sure it is gone? I can not find it in my drivers folder does that mean anything?
-MSE insists that it is completely updated.
-I will run memtest again tonight and update with the results.

EDIT: I just downloaded http://www.nirsoft.net/utils/driverview.html, and it is not showing that the asio.sys driver is running.
EDIT2: Just got another bsod, which seems related to usb. The only usb I have plugged in, is the one for the alternate mouse that I am using. I moved it from a front port to a different one in the back.
My System SpecsSystem Spec
01 Jun 2011   #48
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

The dump file indicate the cause is:
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.

Below it blames a Windows driver, which are usually not the cause. When the debugger can't find the actual cause it blames a driver that is involved in the crash.

This type of debugger report is normally hardware caused. The failure to define arguments indicates this.

Code:
 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
 
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP: 
+3530376235653462
00000000`00000000 ??              ???
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR:  0x1E_0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
CURRENT_IRQL:  2
EXCEPTION_RECORD:  fffff88002ffcc88 -- (.exr 0xfffff88002ffcc88)
ExceptionAddress: fffff88000c4ab77 (Wdf01000!FxIoQueue::ProcessCancelledRequests+0x0000000000000057)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME:  fffff88002ffcd30 -- (.trap 0xfffff88002ffcd30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffff9801a128c50
rdx=effff9801a128d48 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000c4ab77 rsp=fffff88002ffcec0 rbp=fffff9801a128c50
 r8=fffff9808504eed8  r9=0000000000000000 r10=fffff9801a680c60
r11=fffff9801a128cf8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
Wdf01000!FxIoQueue::ProcessCancelledRequests+0x57:
fffff880`00c4ab77 488b4208        mov     rax,qword ptr [rdx+8] ds:effff980`1a128d50=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002c946be to fffff80002c9ccd0
STACK_TEXT:  
fffff880`02ffbd68 fffff800`02c946be : 00000000`00000000 fffff880`00c93c14 fffff880`02ffc4e0 fffff800`02cc8890 : nt!KeBugCheck
fffff880`02ffbd70 fffff800`02cc855d : fffff800`02ea3968 fffff800`02de0cbc fffff800`02c1d000 fffff880`02ffcc88 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffbda0 fffff800`02cc7335 : fffff800`02de40fc fffff880`02ffbe18 fffff880`02ffcc88 fffff800`02c1d000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffbdd0 fffff800`02cd83b1 : fffff880`02ffcc88 fffff880`02ffc4e0 fffff880`00000000 fffff880`00000003 : nt!RtlDispatchException+0x415
fffff880`02ffc4b0 fffff800`02c9c382 : fffff880`02ffcc88 fffff980`1a128c50 fffff880`02ffcd30 fffff980`1a128c50 : nt!KiDispatchException+0x135
fffff880`02ffcb50 fffff800`02c9ac8a : fffff880`02ffcd80 fffff800`02d9c582 00000000`00000863 00000000`00000963 : nt!KiExceptionDispatch+0xc2
fffff880`02ffcd30 fffff880`00c4ab77 : fffff880`00c84302 fffff880`00c481fa fffff980`1a128c50 fffff980`1a128c50 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffcec0 fffff880`00c485ec : 00000000`00000003 00000000`00000003 fffff980`1a680c02 fffff880`02ffd0a0 : Wdf01000!FxIoQueue::ProcessCancelledRequests+0x57
fffff880`02ffcf40 fffff880`00c47f98 : 00000000`00000000 00000000`00000002 00000000`00000000 fffff980`8504efc2 : Wdf01000!FxIoQueue::DispatchEvents+0x12c
fffff880`02ffcfb0 fffff880`00c4d558 : fffff980`1a680f02 fffff980`8504ee70 fffff980`1a680c60 fffff980`8504ee70 : Wdf01000!FxIoQueue::QueueRequest+0x2bc
fffff880`02ffd020 fffff880`00c37245 : fffff980`8504ee70 fffff980`1a680c60 00000000`00000002 fffff980`0b4aee20 : Wdf01000!FxPkgIo::Dispatch+0x37c
fffff880`02ffd0a0 fffff800`0313fc16 : fffff980`1a680c60 00000000`00000002 fffff980`1a680c60 fffff800`0313b37e : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`02ffd0d0 fffff800`0313ec42 : fffff980`1a680f28 00000000`00000002 fffff980`1a03cf50 fffff980`2bda0f40 : nt!IovCallDriver+0x566
fffff880`02ffd130 fffff800`0313fc16 : fffff980`1a680c60 00000000`00000002 fffff980`1a03ce00 fffff800`03134d3d : nt!ViFilterDispatchPower+0x62
fffff880`02ffd160 fffff880`0661248f : fffff980`1a680c60 fffff980`1a0aeb30 fffff980`1a0aef08 fffff980`9ade8f40 : nt!IovCallDriver+0x566
fffff880`02ffd1c0 fffff880`06611f5b : fffff980`1a680fb8 fffff980`1a0aec01 fffff880`02ffd280 fffff980`1a0aeb30 : hidusb!HumReadReport+0x13f
fffff880`02ffd210 fffff880`06622555 : fffff980`1a6eaf01 fffff980`1a6eaf20 fffff980`1a680c60 00000000`00000005 : hidusb!HumInternalIoctl+0x137
fffff880`02ffd280 fffff880`06622d75 : fffff980`1a6eaf20 fffff980`1a0aeca0 00000000`00000000 00000000`00000005 : HIDCLASS!HidpSubmitInterruptRead+0xdd
fffff880`02ffd2e0 fffff800`031415d6 : fffff980`1a680fb8 fffff980`1a0aeca0 fffff880`02ffd501 fffff980`1a680c00 : HIDCLASS!HidpInterruptReadComplete+0x37d
fffff880`02ffd370 fffff800`02ca0091 : fffff980`1a680fbb fffff800`00000001 00000000`00000000 fffff880`00000005 : nt!IovpLocalCompletionRoutine+0x166
fffff880`02ffd3d0 fffff800`0313919f : fffff980`1a680c60 fffff980`1a128c00 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x3b1
fffff880`02ffd4b0 fffff880`00c31a52 : 00000000`00000000 fffff980`1a128c50 00000000`00000000 00000000`00000001 : nt!IovCompleteRequest+0x19f
fffff880`02ffd580 fffff880`00c2213e : fffff980`1a680c60 fffff980`00000001 00000000`00000000 fffff980`1a680c60 : Wdf01000!FxRequest::CompleteInternal+0x646
fffff880`02ffd630 fffff880`0660157d : fffff980`08f72f80 fffff980`806ace70 fffff980`806ace70 00000000`00000000 : Wdf01000!imp_WdfRequestCompleteWithInformation+0x1aa
fffff880`02ffd6a0 fffff980`08f72f80 : fffff980`806ace70 fffff980`806ace70 00000000`00000000 fffffa80`03f7d380 : LUsbFilt+0x157d
fffff880`02ffd6a8 fffff980`806ace70 : fffff980`806ace70 00000000`00000000 fffffa80`03f7d380 00000000`00000010 : 0xfffff980`08f72f80
fffff880`02ffd6b0 fffff980`806ace70 : 00000000`00000000 fffffa80`03f7d380 00000000`00000010 00000000`000000c0 : 0xfffff980`806ace70
fffff880`02ffd6b8 00000000`00000000 : fffffa80`03f7d380 00000000`00000010 00000000`000000c0 00000000`00000000 : 0xfffff980`806ace70
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
hidusb!HumReadReport+13f
fffff880`0661248f 488b4c2460      mov     rcx,qword ptr [rsp+60h]
SYMBOL_STACK_INDEX:  f
SYMBOL_NAME:  hidusb!HumReadReport+13f
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: hidusb
IMAGE_NAME:  hidusb.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a665
FAILURE_BUCKET_ID:  X64_0x1E_0_VRFK_hidusb!HumReadReport+13f
BUCKET_ID:  X64_0x1E_0_VRFK_hidusb!HumReadReport+13f
Followup: MachineOwner
---------

Driver verifier is showing this Windows driver is at fault.
It is a USB Miniport Driver for Input Devices.

Code:
 
3: kd> lmvm hidusb
start             end                 module name
fffff880`06610000 fffff880`0661e000   hidusb     (pdb symbols)          c:\symbols\hidusb.pdb\57B441A60E0C47FDBEEF72B8B1C797AD1\hidusb.pdb
    Loaded symbol image file: hidusb.sys
    Mapped memory image file: c:\symbols\hidusb.sys\4CE7A665e000\hidusb.sys
    Image path: hidusb.sys
    Image name: hidusb.sys
    Timestamp:        Sat Nov 20 18:43:49 2010 (4CE7A665)
    CheckSum:         00012706
    ImageSize:        0000E000
    File version:     6.1.7601.17514
    Product version:  6.1.7601.17514
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        2.0 Dll
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     HIDUSB.SYS
    OriginalFilename: HIDUSB.SYS
    ProductVersion:   6.1.7601.17514
    FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
    FileDescription:  USB Miniport Driver for Input Devices
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
Disable the Driver Verifier.

Let's check into the hardware that might be causing this, possibilities are CPU, RAM, Video Card, PSU, motherboard.

If moving the mouse to a different USB port doesn't help, can you find/borrow a PS2 mouse?

Remove your RAM and install the 2GB RAM you mentioned that you have available.
Win7 will run on 1GB RAM, even with 2GB RAM it might be slower, but will run.
Do the normal things you do that produce a crash. If you don't have any more crashes, then this would indicate the cause.

Report back the results of these two steps, include any crash dump files if you have another crash.

Next steps will be:
Find or borrow Video card to test with.
Find or borrow PSU to test with.

Other event log errors.

Code:
Event[2]:
  Log Name: System
  Source: NetBT
  Date: 2011-05-31T19:01:04.767
  Event ID: 4321
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Ryan-PC
  Description: 
The name "WORKGROUP      :1d" could not be registered on the interface with IP address 192.168.0.6. The computer with the IP address 192.168.0.2 did not allow the name to be claimed by this computer.
This might be caused by two computers having the same name.


Code:
Event[59]:
  Log Name: System
  Source: Microsoft Antimalware
  Date: 2011-05-31T18:45:29.000
  Event ID: 3002
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Ryan-PC
  Description: 
Microsoft Antimalware Real-Time Protection feature has encountered an error and failed.
  Feature: Behavior Monitoring
  Error Code: 0x80004005
  Error description: Unspecified error 
  Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection.
Uninstall MSE from the controll panel > Programs and Features
Re-install Microsoft Security Essentials
My System SpecsSystem Spec
01 Jun 2011   #49
Ran

Windows 7 Profesional 64 bit
 
 

-Memtest ran over night with no errors.
-I will switch the ram today
-I'm excited to turn verifier off haha. It is such a pain. It really slows down my computer.

Thanks again for your help. Its really appreciated.

EDIT: Found out that our other computer had older ram and mine would not fit its slots, so instead I just returned only one stick of ram to my computer. If I get another bsod, I can switch the two out.

EDIT2:Got another bsod, and so i switched the ram sticks. Soon after, my computer restarted on its own, and during the starting process it froze at initializing usb controllers.
My System SpecsSystem Spec
01 Jun 2011   #50
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

Same as the last one.
The dump file indicate the cause is:
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.

Below it blames a Windows driver, which are usually not the cause. When the debugger can't find the actual cause it blames a driver that is involved in the crash.



Code:
 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------

EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP: 
+3563663561376437
00000000`00000000 ??              ???
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR:  0x1E_0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
CURRENT_IRQL:  0
EXCEPTION_RECORD:  fffff880091e8588 -- (.exr 0xfffff880091e8588)
ExceptionAddress: fffff88000e2482e (ataport!IdeExecuteScsiCrb+0x0000000000000016)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME:  fffff88003cff6c0 -- (.trap 0xfffff88003cff6c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a00390c000 rbx=0000000000000000 rcx=fffff880040ed000
rdx=0000000000000ff8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002fc01c0 rsp=fffff88003cff850 rbp=fffff8a00397bde6
 r8=0000000000000ffc  r9=0000000000000fff r10=fffff880040ed000
r11=fffff8a00397bde6 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!MiPerformFixups+0x80:
fffff800`02fc01c0 410fb603        movzx   eax,byte ptr [r11] ds:fffff8a0`0397bde6=??
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002cdc6be to fffff80002ce4cd0
STACK_TEXT:  
fffff880`091e7668 fffff800`02cdc6be : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`02d3c0cb : nt!KeBugCheck
fffff880`091e7670 fffff800`02d1055d : fffff800`02ee9a54 fffff800`02e2c0d8 fffff800`02c65000 fffff880`091e8588 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`091e76a0 fffff800`02d0f335 : fffff800`02e2c0d0 fffff880`091e7718 fffff880`091e8588 fffff800`02c65000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`091e76d0 fffff800`02d203b1 : fffff880`091e8588 fffff880`091e7de0 fffff880`00000000 fffffa80`030b3f80 : nt!RtlDispatchException+0x415
fffff880`091e7db0 fffff800`02ce4382 : fffff880`091e8588 00000000`00000000 fffff880`091e8630 fffffa80`0286d1b0 : nt!KiDispatchException+0x135
fffff880`091e8450 fffff800`02ce2c8a : fffffa80`0286d1b0 fffffa80`02787c10 fffffa80`02854100 fffff880`00f980d3 : nt!KiExceptionDispatch+0xc2
fffff880`091e8630 fffff880`00e2482e : 00000000`00005000 fffffa80`030b3dc0 fffffa80`030b3c60 fffff880`00e2d7cb : nt!KiGeneralProtectionFault+0x10a
fffff880`091e87c0 fffff880`00e247f9 : fffffa80`030b3f80 fffffa80`030b3c60 fffffa80`00000020 fffffa80`0286d1b0 : ataport!IdeExecuteScsiCrb+0x16
fffff880`091e87f0 fffff880`00e289cb : fffffa80`0286d060 fffffa80`030b3f80 fffffa80`0286d1b0 fffff880`00e7104e : ataport!IdePortTranslateSrbToCrb+0x29d
fffff880`091e8820 fffff880`00e244ee : fffffa80`030b3c60 00000000`00000000 fffffa80`027a69b0 fffffa80`030b3c60 : ataport!IdePortPdoDispatch+0x87
fffff880`091e8850 fffff880`00e6b7a7 : fffffa80`030b3c60 00000000`00000000 ffffe3c5`836d7e11 fffff880`049c140e : ataport!IdePortDispatch+0x16
fffff880`091e8880 fffff880`00e73789 : fffff880`00e91b50 fffffa80`04d8d390 00000000`00005000 fffffa80`030b3dc0 : ACPI!ACPIDispatchForwardIrp+0x37
fffff880`091e88b0 fffff880`00e6ba3f : fffff880`00e91b50 fffffa80`02265010 fffffa80`030b3c60 00000000`00000000 : ACPI!ACPIIrpDispatchDeviceControl+0x75
fffff880`091e88e0 fffff880`01990445 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000001 : ACPI!ACPIDispatchIrp+0x12b
fffff880`091e8960 fffff880`01990975 : fffffa80`028c7010 fffffa80`027a69b0 00000000`00020000 fffff880`00000001 : CLASSPNP!ServiceTransferRequest+0x355
fffff880`091e8a00 fffff880`00f0b0af : fffffa80`043342a0 00000000`ffffffff fffffa80`04334520 fffffa80`01b9e420 : CLASSPNP!ClassReadWrite+0xd5
fffff880`091e8a50 fffff880`00f2018c : fffffa80`027b7a90 fffffa80`043342a0 fffffa80`043342a0 00000000`00000702 : partmgr!PmGlobalDispatch+0x9f
fffff880`091e8a80 fffff880`019402bf : 00000000`ffffffff fffffa80`027c2b90 fffffa80`043342a0 fffffa80`044e82b0 : volmgr!VmReadWrite+0x11c
fffff880`091e8ac0 fffff880`0194053c : fffffa80`027c2b90 fffff880`0123fe44 fffffa80`044e82b0 00000000`00000001 : fvevol!FveReadWrite+0x47
fffff880`091e8b00 fffff880`018e8031 : fffff880`087b0b50 00000000`00000022 fffff880`00000001 fffff880`091e8bf0 : fvevol!FveFilterRundownReadWrite+0x1dc
fffff880`091e8b60 fffff880`018e7405 : fffffa80`027bbb60 fffffa80`043342a0 fffffa80`01b9e420 00000000`031b9000 : rdyboost!SmdProcessReadWrite+0xbf9
fffff880`091e8cd0 fffff880`0188cdf4 : fffffa80`028ca190 fffff880`03cff290 fffffa80`0407f260 fffff880`087b1690 : rdyboost!SmdDispatchReadWrite+0xd9
fffff880`091e8d00 fffff880`0124339a : fffff880`03cff130 fffffa80`01b9e420 fffff880`087b1690 fffffa80`0208cb60 : volsnap! ?? ::FNODOBFM::`string'+0x57b
fffff880`091e8d30 fffff800`02cdc817 : fffff880`087b1690 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsStorageDriverCallout+0x16
fffff880`091e8d60 fffff800`02cdc7d1 : 00000000`00000000 00000000`00000000 fffff880`091e9000 fffff800`02cf1832 : nt!KxSwitchKernelStackCallout+0x27
fffff880`03cff000 fffff800`02cf1832 : 00000000`00000000 00000000`00000002 fffff8a0`02bb9230 fffff800`02ce78a4 : nt!KiSwitchKernelStackContinue
fffff880`03cff020 fffff880`0124bdd9 : fffff880`01243384 00000000`00000000 00000000`00000000 fffffa80`02889100 : nt!KeExpandKernelStackAndCalloutEx+0x2a2
fffff880`03cff100 fffff880`01232465 : 00000000`00000000 fffff880`010d8163 fffff880`03cff1d0 fffff880`03cff1b8 : Ntfs!NtfsCallStorageDriver+0x31
fffff880`03cff160 fffff880`01231e28 : 00000000`00000000 00000000`00000000 fffffa80`04334688 00000000`33d6b000 : Ntfs!NtfsPagingFileIo+0x3e5
fffff880`03cff260 fffff880`0108dbcf : fffffa80`04334688 fffffa80`043342a0 fffffa80`04d9d190 00000000`00000000 : Ntfs! ?? ::FNODOBFM::`string'+0x8ba9
fffff880`03cff310 fffff880`0108c6df : fffffa80`028068e0 fffffa80`0407f201 fffffa80`02806800 fffffa80`043342a0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`03cff3a0 fffff800`02d0cc25 : fffffa80`043342c0 fffffa80`018c5330 fffffa80`01ce2600 fffff880`009e9180 : fltmgr!FltpDispatch+0xcf
fffff880`03cff400 fffff800`02d0c6f9 : 00000000`00000000 00000000`00000000 fffffa80`01ce2540 fffffa80`01ce2540 : nt!IoPageRead+0x255
fffff880`03cff490 fffff800`02cf2fa9 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff8a0`02bb92e0 : nt!MiIssueHardFault+0x255
fffff880`03cff560 fffff800`02ce2e2e : 00000000`00000000 fffff8a0`0397bde6 fffff880`03cff600 fffff880`040ed000 : nt!MmAccessFault+0x1399
fffff880`03cff6c0 fffff800`02fc01c0 : fffffa80`028068e0 fffffa80`043342a0 fffff880`03cff8c0 00000000`00004000 : nt!KiPageFault+0x16e
fffff880`03cff850 fffff800`02fbc327 : fffffa80`00000000 fffffa80`0407f260 00000000`00001395 fffff8a0`0390c000 : nt!MiPerformFixups+0x80
fffff880`03cff8b0 fffff800`02d1475b : ffffffff`ffffffff fffff880`03cffa78 00000000`00004000 fffffa80`04334200 : nt!MiRelocateImagePfn+0xf7
fffff880`03cff910 fffff800`02d0c72f : fffffa80`02e817c0 fffff880`03cffa80 fffffa80`01a42ec8 fffffa80`02e817c0 : nt!MiWaitForInPageComplete+0x7ef
fffff880`03cff9f0 fffff800`02cf307a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff680`00000000 : nt!MiIssueHardFault+0x28b
fffff880`03cffac0 fffff800`02ce2e2e : 00000000`00000000 00000000`70c48050 ffffffff`ffffd801 00000000`00d6f860 : nt!MmAccessFault+0x146a
fffff880`03cffc20 00000000`773c6882 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`043cfae4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773c6882

STACK_COMMAND:  kb
FOLLOWUP_IP: 
ataport!IdeExecuteScsiCrb+16
fffff880`00e2482e 8b8898000000    mov     ecx,dword ptr [rax+98h]
SYMBOL_STACK_INDEX:  7
SYMBOL_NAME:  ataport!IdeExecuteScsiCrb+16
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: ataport
IMAGE_NAME:  ataport.SYS
DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79293
FAILURE_BUCKET_ID:  X64_0x1E_0_ataport!IdeExecuteScsiCrb+16
BUCKET_ID:  X64_0x1E_0_ataport!IdeExecuteScsiCrb+16
Followup: MachineOwner
---------
Unless you can start replacing some of the hardware for testing, run a repair install, follow this tutorial: Repair Install
My System SpecsSystem Spec
Reply

 Multiple BSODs




Thread Tools




Similar help and support threads
Thread Forum
Lenovo T440s, multiple BSODs. Hardware replaced but BSODs continue
Thanks in advance for any advice. The BDODs appear to be of multiple types. Motherboard, RAM, wireless card and SSD were all replaced in early October and system completely reinstalled but BSODs continue. They are more likely to occur 1-2 min after waking from sleep, but recently also occurred...
BSOD Help and Support
Multiple BSODs from multiple apps PAGE_FAULT_IN_NONPAGED_AREA
Hi. Last year, I bought a new PC for graphical software and gaming. From the beggining it had problems (I was recieving BSODs), so, I tested RAMs. It resulted that RAMs we're bad. I returned them in warrantly. (The PC was assembled by the shop, components we're choosen by me so that aren't any...
BSOD Help and Support
Multiple BSODs, Multiple Bugchecks (0xD1, 0x3B, 0x50, 0x0A)
I've been having BSOD trouble over the past four or five months now. The BSODs typically happen once a week, sometimes twice, with small strings of daily crashes here and there. I'm at my wit's end when it comes to trying to figure out where the problem lies. All of my parts are under warranty, so...
BSOD Help and Support
Multiple BSODs, Random Occurences, Multiple Error Codes
Hey there, So just to start things off, I'm 18 and don't really have much technical knowledge when it comes to computer hardware and errors, etc. I started getting BSODs a while back, but they weren't very frequent, so I uninstalled all the programmes I had on my laptop and it stopped for...
BSOD Help and Support
Multiple BSODs, multiple BCCodes, does not happen in safe mode.
Last couple weeks i've been having a large amount of bluescreens, including but not limited to bccodes 116, d1, 4e, 1a, 50 and 7a. Last night it also froze two or 3 times with no bluescreen. I recently upgraded my Phenom 9550, Biostar A770E and 6GB of DDR2-800 with an i5-2500k, an MSi P67S-C43 and...
BSOD Help and Support


Our Sites

Site Links

About Us

Find 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 15:42.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App