Solved Lots of BSODs, different errors

[CarlTR6]

Waarschuwing
Als Verifier vlaggen een kritische bestuurder kon laten op uw computer opgestart. Zorg ervoor dat u hebt gemaakt van een systeem herstelpunt en Windows 7 installatie DVD of reparatie disc.


1. Begint te typen verifier.exe in het start menu en open Verifier.

Driver Verifier - in-en uitschakelen-snip1.png

2. Selecteer "Aangepaste instellingen (voor code ontwikkelaars)", en klik op Volgende.

Driver Verifier - in-en uitschakelen-snip2.png

3. Zorg ervoor dat standaard instellingen, kracht in afwachting van I / O-verzoeken, en IRP Logging worden geselecteerd, en klik op Volgende.

Driver Verifier - in-en uitschakelen-snip3.png

4. Kies "Kiezen driver namen uit een lijst", en klik op Volgende.

Driver Verifier - in-en uitschakelen-snip4.png

5. Klik op "Provider" aan de top van de lijst door de fabrikant te sorteren. Selecteer alle drivers die niet door Microsoft Corporation. De enige andere stuurprogramma's die niet krijgen geselecteerd zijn amdxata.sys en secdrv.sys.

Driver Verifier - in-en uitschakelen-snip5.png

6. Druk op Volgende en op OK om het venster.

Driver Verifier - in-en uitschakelen-snip6.png

Na een reboot, moet driver verificateur worden ingeschakeld.


Optie twee
Uitschakelen Driver Verifier

1. Begint te typen verifier.exe in het start menu en open Verifier.

Klik op de afbeelding voor een grotere versie Naam: snip1.PNG Bekeken: 23 Grootte: 196,6 KB ID: 88815


2. Selecteer "Delete bestaande instellingen"

Driver Verifier - in-en uitschakelen-snip7.png


Als u niet kunt krijgen in Windows uit te schakelen Verifier, proberen met behulp van de Veilige modus.

Als u nog niet kunt krijgen in Windows, dan opstarten van de Windows 7-schijf en een systeem te herstellen.

Courtesy of Google Translate

 

[Veliremus]

Myeah, that's not gonna work . Google is good, but it cannot translate those technical terms.

But I know how to run Verifier, I just need to know which options to select. I've attached a screenshot. If you'll just compare it to yours, and tell me which options to click, that would be great. I'm guessing the first three, four, and the last two?

 

[cybercore]

DRIVER VERIFIER http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

BSOD's will be more frequent with it on, but hopefully it can more accurately detect which driver and therefore which corresponding device is causing the crashes.

 

[Veliremus]

Okay, thanks!

Before I do that, though, I have thought about two possible causes:

1) In my start-up items, I found this item: "P17RunE RunDll32 P17RunE.dll,RunDLLEntry"

Note that it runs via RunDll32, a 32-bit application. When I disable it, I still have sound, but the rundll32 is no longer executed. Could 64-bit windows be choking on this app?

2) I play Spelunky a lot. It's a 32-bit application, and crashes everytime you close it on Windows 7. I've noticed, though, that its process lingers in active memory. It also causes an application called WerFault32.exe to be active, which also is a 32-bit app. Maybe this lingering process is causing the problems?

 

[CarlTR6]

One the first page of Verifier, select the second option - Custom settings and click on next.

On the second Verifier page, select the first option and check boxes 1, 2, and 4. Click on next.

On the third page, select the 4th, the last option, and click on next.

This bring up the fourth page and will load all of your currently loaded drivers. Put a check in the box beside each driver that is not a Microsoft driver. Click on Finish and reboot.

You can compare your Driver Veririfer Screens with the screen shots in the tutorial. The key is to select Custom settings on the first screen (page) of Verifier. I hope this helps. I do not get the page you of which you post the screen shot when I select Custom.

 

[Veliremus]

That's clear, thank you . I will try it if my PC crashes again (First I'm going to see if this Spelunky or rundll32 was the cause).

Oh, as an additional question: the Event Viewer still complains about adfs.sys not starting. So I guess some service is still trying to start it... But Photoshop is gone now, only Flash Plugin and Adobe Reader are there (and I have since uninstalled and reinstalled that as well). I used ServiWin (ServiWin: Windows Services/Drivers Tool (start/stop/restart service)) to stop it from booting. Is that the right way, or do I need to disable something else?

 

[CarlTR6]

Uninstall Adobe Reader; then download and install the latest version. I suggest that you download and install Revo uninstaller and use it rather than than the Windows uninstaller for uninstalling Adobe products.

 

[Veliremus]

Well, I Revo uninstalled Reader, but that didn't help. I reinstalled Photoshop, and tried to remove the Adobe Driver application by itself, but that didn't take care of that driver either.

But disabling it should be enough, right?

And I haven't had any BSODS (*knocks on wood*) since I discovered that Spelunky.exe + WerFault32.exe process I was talking about. Could it have been the problem? I mean, I could logically understand that I would get memory management errors when a failing process is left running on a core.

 

[CarlTR6]

Well, I Revo uninstalled Reader, but that didn't help. I reinstalled Photoshop, and tried to remove the Adobe Driver application by itself, but that didn't take care of that driver either.

But disabling it should be enough, right?

Yes, disabling it will be enough. Rename it from .sys to .bak.

And I haven't had any BSODS (*knocks on wood*) since I discovered that Spelunky.exe + WerFault32.exe process I was talking about. Could it have been the problem? I mean, I could logically understand that I would get memory management errors when a failing process is left running on a core.[/QUOTE]

Yes, that could have been the problem. Troubleshooting most often involves removing all suspected or potential causes until you eliminate the crashes.

 

[Veliremus]

Well, thanks you both for your help. Like I said, I really appreciate it! I will see how it goes and post back after a while to inform you of the status of my problem.

 

[Veliremus]

Okay, so no good...

I just tried to start Starcraft 2, and got a SYSTEM_SERVICE_EXCEPTION. Weirdly, it hasn't seemed to have made a minidump of this. I then reset, and when I got into Windows, before the logon, I got another BSOD, which was dumped.

I had Verifier.exe on, I think. New info is attached, and new MEMORY.DMP can be found here:
http://www.veliremus.com/files/caprica/22oct_dmp.rar

So this time I hadn't played Spelunky at all... Should I try a repair install, see how that works out? As a matter of fact, maybe even a clean install... I'm really at the end of my rope here, guys. I'm thinking I will never find out what's wrong.

(Since the last time, I have updated my graphics driver and have installed Avast again, as it was not the problem, and MSE was giving that .etl bug)

 

[cybercore]

I ran that Windows MemTest. A few hours, 165% coverage, zero errors. But isolating the sticks, how would that show errors? In other words, why would errors not show up with two of them in, but only with one in? I would expect the opposite to be true.

Practically as we have witnessed this before, memtest sometimes sooner detects errors when run on sticks separately. Skip this if not an option for you.


Your latest crash dump (it's cut on drivers' list):

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
Probably caused by : CI.dll ( CI!SHATransform+51e )

CI.dll is windows code integrity module. I suspect the crash may have been caused by a toolbar - uninstall any toolbars you have. Or even malware. You installed Avast back - no problem, but for the period of troubleshooting we'd rather you have MSE, cause Avast quite often causes crashes directly as well as indirectly, such as violating system integrity.

Start -> cmd -> sfc /scannow




Make sure these drivers have been updated:

nvoclk64.sys Mon Aug 18 19:00:01 2008
NTUNES, update or remove - no overclocking on any hardware part, for now plz

nusb3hub.sys Mon Oct 26 16:19:44 2009
motherboard USB 3.0 Device Driver, by NEC Electronics Corporation (the latest version is April 2010)

fffff880`03360e98 fffff800`030d4ca9 : 00000000`0000000a 00000000`00000006 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03360ea0 fffff800`030d3920 : fffff880`033610a0 fffff980`02d1aee0 00000001`1197f860 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`03360fe0 fffff800`030f52b3 : fffff980`02d1aee0 fffff880`033612c0 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`03361170 fffff800`030b20c7 : 00000000`00000006 0000007f`ffffffff 00000000`d135d200 00000000`00000000 : nt!IopCompleteRequest+0xae3
fffff880`03361240 fffff800`030b2487 : 00000000`12c1963e 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`033612c0 fffff880`00d25fbe : cccccccc`415e415d 06df92d3`cab44b40 415c5f5e`4a93d289 488bc448`e60ae3bc : nt!KiApcInterrupt+0xd7
fffff880`03361450 fffff880`00d26d0c : fffff880`03361648 fffffa80`89580848 fffff980`89681048 fffff800`1da65864 : CI!SHATransform+0x51e
fffff880`033614e0 fffff880`00ce3824 : fffff8a0`006500d0 fffff980`031800e8 00000000`00000000 00000000`00000000 : CI!A_SHAUpdate+0xcc
fffff880`03361520 fffff880`00cdbb38 : fffff980`03180190 00000000`00000000 00000000`00000400 00000006`00001000 : CI!HashpHashBytes+0x40
fffff880`03361550 fffff880`00cdb281 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : CI!CipImageGetImageHash+0x310
fffff880`03361730 fffff880`00cd9fbb : 00000000`00000001 fffff880`033619f0 fffff880`033619f0 80000000`00000020 : CI!CipValidateFileHash+0x211
fffff880`033618a0 fffff800`0334068e : 00000000`00000011 00000000`000fffff fffffa80`05e30830 00000000`00000000 : CI!CiValidateImageHeader+0x213
fffff880`03361980 fffff800`0334057c : 00000000`00000001 00000000`01000000 fffffa80`05e30390 00000000`00000000 : nt!SeValidateImageHeader+0x2e
fffff880`033619c0 fffff800`033d0d95 : fffffa80`05e30830 fffffa80`05e30390 00000000`00000001 00000000`00000011 : nt!MiValidateImageHeader+0xa4
fffff880`03361a80 fffff800`033c6013 : fffff880`03361ce0 00000000`00000000 fffff880`03361f98 00000000`00000001 : nt!MmCreateSection+0x8c9
fffff880`03361c90 fffff800`030d4993 : fffffa80`03731b60 fffff880`03361f38 fffff880`03361d28 00000000`00000000 : nt!NtCreateSection+0x162
fffff880`03361d10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

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


Loading Dump File [G:\102210-21060-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*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`03065000 PsLoadedModuleList = 0xfffff800`032a2e50
Debug session time: Fri Oct 22 11:08:38.752 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:09.845
Loading Kernel Symbols
...............................................................
.........................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {6, 2, 0, fffff800030f52b3}

Probably caused by : CI.dll ( CI!SHATransform+51e )

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

4: 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: 0000000000000006, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff800030f52b3, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330d0e0
 0000000000000006 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!IopCompleteRequest+ae3
fffff800`030f52b3 488b09          mov     rcx,qword ptr [rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

IRP_ADDRESS:  ffffffffffffff8e

TRAP_FRAME:  fffff88003360fe0 -- (.trap 0xfffff88003360fe0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88003361f80 rbx=0000000000000000 rcx=0000000000000006
rdx=0000000000000006 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030f52b3 rsp=fffff88003361170 rbp=fffff880033612c0
 r8=0000000000000100  r9=0000000000000000 r10=0000000000000002
r11=fffff800030f47d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
nt!IopCompleteRequest+0xae3:
fffff800`030f52b3 488b09          mov     rcx,qword ptr [rcx] ds:0460:00000000`00000006=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030d4ca9 to fffff800030d5740

STACK_TEXT:  
fffff880`03360e98 fffff800`030d4ca9 : 00000000`0000000a 00000000`00000006 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03360ea0 fffff800`030d3920 : fffff880`033610a0 fffff980`02d1aee0 00000001`1197f860 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`03360fe0 fffff800`030f52b3 : fffff980`02d1aee0 fffff880`033612c0 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`03361170 fffff800`030b20c7 : 00000000`00000006 0000007f`ffffffff 00000000`d135d200 00000000`00000000 : nt!IopCompleteRequest+0xae3
fffff880`03361240 fffff800`030b2487 : 00000000`12c1963e 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`033612c0 fffff880`00d25fbe : cccccccc`415e415d 06df92d3`cab44b40 415c5f5e`4a93d289 488bc448`e60ae3bc : nt!KiApcInterrupt+0xd7
fffff880`03361450 fffff880`00d26d0c : fffff880`03361648 fffffa80`89580848 fffff980`89681048 fffff800`1da65864 : CI!SHATransform+0x51e
fffff880`033614e0 fffff880`00ce3824 : fffff8a0`006500d0 fffff980`031800e8 00000000`00000000 00000000`00000000 : CI!A_SHAUpdate+0xcc
fffff880`03361520 fffff880`00cdbb38 : fffff980`03180190 00000000`00000000 00000000`00000400 00000006`00001000 : CI!HashpHashBytes+0x40
fffff880`03361550 fffff880`00cdb281 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : CI!CipImageGetImageHash+0x310
fffff880`03361730 fffff880`00cd9fbb : 00000000`00000001 fffff880`033619f0 fffff880`033619f0 80000000`00000020 : CI!CipValidateFileHash+0x211
fffff880`033618a0 fffff800`0334068e : 00000000`00000011 00000000`000fffff fffffa80`05e30830 00000000`00000000 : CI!CiValidateImageHeader+0x213
fffff880`03361980 fffff800`0334057c : 00000000`00000001 00000000`01000000 fffffa80`05e30390 00000000`00000000 : nt!SeValidateImageHeader+0x2e
fffff880`033619c0 fffff800`033d0d95 : fffffa80`05e30830 fffffa80`05e30390 00000000`00000001 00000000`00000011 : nt!MiValidateImageHeader+0xa4
fffff880`03361a80 fffff800`033c6013 : fffff880`03361ce0 00000000`00000000 fffff880`03361f98 00000000`00000001 : nt!MmCreateSection+0x8c9
fffff880`03361c90 fffff800`030d4993 : fffffa80`03731b60 fffff880`03361f38 fffff880`03361d28 00000000`00000000 : nt!NtCreateSection+0x162
fffff880`03361d10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13


STACK_COMMAND:  kb

FOLLOWUP_IP: 
CI!SHATransform+51e
fffff880`00d25fbe 4133cb          xor     ecx,r11d

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  CI!SHATransform+51e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: CI

IMAGE_NAME:  CI.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5be01d

FAILURE_BUCKET_ID:  X64_0xA_VRF_CI!SHATransform+51e

BUCKET_ID:  X64_0xA_VRF_CI!SHATransform+51e

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

4: kd> lmtn
start             end                 module name
fffff800`00bcc000 fffff800`00bd6000   kdcom    kdcom.dll    Tue Jul 14 04:31:07 2009 (4A5BDFDB)
fffff800`0301c000 fffff800`03065000   hal      hal.dll      Tue Jul 14 04:27:36 2009 (4A5BDF08)
fffff800`03065000 fffff800`03641000   nt       ntkrnlmp.exe Sat Jun 19 07:16:41 2010 (4C1C44A9)
fffff880`00c19000 fffff880`00c5d000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 04:29:10 2009 (4A5BDF66)
fffff880`00c5d000 fffff880`00c71000   PSHED    PSHED.dll    Tue Jul 14 04:32:23 2009 (4A5BE027)
fffff880`00c71000 fffff880`00ccf000   CLFS     CLFS.SYS     Tue Jul 14 02:19:57 2009 (4A5BC11D)
fffff880`00ccf000 fffff880`00d8f000   CI       CI.dll       Tue Jul 14 04:32:13 2009 (4A5BE01D)
fffff880`00d8f000 fffff880`00deb000   volmgrx  volmgrx.sys  Tue Jul 14 02:20:33 2009 (4A5BC141)
fffff880`00e00000 fffff880`00e2a000   ataport  ataport.SYS  Tue Jul 14 02:19:52 2009 (4A5BC118)
fffff880`00e2a000 fffff880`00ece000   Wdf01000 Wdf01000.sys Tue Jul 14 02:22:07 2009 (4A5BC19F)
fffff880`00ece000 fffff880`00edd000   WDFLDR   WDFLDR.SYS   Tue Jul 14 02:19:54 2009 (4A5BC11A)
fffff880`00edd000 fffff880`00f34000   ACPI     ACPI.sys     Tue Jul 14 02:19:34 2009 (4A5BC106)
fffff880`00f34000 fffff880`00f3d000   WMILIB   WMILIB.SYS   Tue Jul 14 02:19:51 2009 (4A5BC117)
fffff880`00f3d000 fffff880`00f47000   msisadrv msisadrv.sys Tue Jul 14 02:19:26 2009 (4A5BC0FE)
fffff880`00f47000 fffff880`00f7a000   pci      pci.sys      Tue Jul 14 02:19:51 2009 (4A5BC117)
fffff880`00f7a000 fffff880`00f87000   vdrvroot vdrvroot.sys Tue Jul 14 03:01:31 2009 (4A5BCADB)
fffff880`00f87000 fffff880`00f9c000   partmgr  partmgr.sys  Tue Jul 14 02:19:58 2009 (4A5BC11E)
fffff880`00f9c000 fffff880`00fb1000   volmgr   volmgr.sys   Tue Jul 14 02:19:57 2009 (4A5BC11D)
fffff880`00fb1000 fffff880`00fb8000   pciide   pciide.sys   Tue Jul 14 02:19:49 2009 (4A5BC115)
fffff880`00fb8000 fffff880`00fc8000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 02:19:48 2009 (4A5BC114)
fffff880`00fc8000 fffff880`00fe2000   mountmgr mountmgr.sys Tue Jul 14 02:19:54 2009 (4A5BC11A)
fffff880`00fe2000 fffff880`00feb000   atapi    atapi.sys    Tue Jul 14 02:19:47 2009 (4A5BC113)
fffff880`01000000 fffff880`0105e000   msrpc    msrpc.sys    Tue Jul 14 02:21:32 2009 (4A5BC17C)
fffff880`0105e000 fffff880`010a8000   fwpkclnt fwpkclnt.sys Tue Jul 14 02:21:08 2009 (4A5BC164)
fffff880`010a8000 fffff880`010b9000   Npfs     Npfs.SYS     Tue Jul 14 02:19:48 2009 (4A5BC114)
fffff880`010be000 fffff880`0114a000   mv91xx   mv91xx.sys   Thu Jul 01 04:55:14 2010 (4C2BF582)
fffff880`0114a000 fffff880`01179000   SCSIPORT SCSIPORT.SYS Tue Jul 14 03:01:04 2009 (4A5BCAC0)
fffff880`01179000 fffff880`01181000   mvxxmm   mvxxmm.sys   Thu Jul 01 04:54:57 2010 (4C2BF571)
fffff880`01181000 fffff880`0118c000   amdxata  amdxata.sys  Tue May 19 20:56:59 2009 (4A12F2EB)
fffff880`0118c000 fffff880`011d8000   fltmgr   fltmgr.sys   Tue Jul 14 02:19:59 2009 (4A5BC11F)
fffff880`011d8000 fffff880`011ec000   fileinfo fileinfo.sys Tue Jul 14 02:34:25 2009 (4A5BC481)
fffff880`01201000 fffff880`013a4000   Ntfs     Ntfs.sys     Tue Jul 14 02:20:47 2009 (4A5BC14F)
fffff880`013a4000 fffff880`013be000   ksecdd   ksecdd.sys   Tue Jul 14 02:20:54 2009 (4A5BC156)
fffff880`013be000 fffff880`013e9000   ksecpkg  ksecpkg.sys  Fri Dec 11 08:03:32 2009 (4B21E0B4)
fffff880`013e9000 fffff880`013f4000   Msfs     Msfs.SYS     Tue Jul 14 02:19:47 2009 (4A5BC113)
fffff880`01400000 fffff880`01460000   NETIO    NETIO.SYS    Tue Jul 14 02:21:46 2009 (4A5BC18A)
fffff880`01460000 fffff880`01470000   vmstorfl vmstorfl.sys Tue Jul 14 02:42:54 2009 (4A5BC67E)
fffff880`01479000 fffff880`014ec000   cng      cng.sys      Tue Jul 14 02:49:40 2009 (4A5BC814)
fffff880`014ec000 fffff880`014fd000   pcw      pcw.sys      Tue Jul 14 02:19:27 2009 (4A5BC0FF)
fffff880`014fd000 fffff880`01507000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 02:19:45 2009 (4A5BC111)
fffff880`01507000 fffff880`015f9000   ndis     ndis.sys     Tue Jul 14 02:21:40 2009 (4A5BC184)
fffff880`01603000 fffff880`01800000   tcpip    tcpip.sys    Mon Jun 14 06:39:04 2010 (4C15A458)
fffff880`01800000 fffff880`01809000   rdpencdd rdpencdd.sys Tue Jul 14 03:16:34 2009 (4A5BCE62)
fffff880`01809000 fffff880`01812000   rdprefmp rdprefmp.sys Tue Jul 14 03:16:35 2009 (4A5BCE63)
fffff880`01817000 fffff880`01863000   volsnap  volsnap.sys  Tue Jul 14 02:20:08 2009 (4A5BC128)
fffff880`01863000 fffff880`0186b000   spldr    spldr.sys    Mon May 11 19:56:27 2009 (4A0858BB)
fffff880`0186b000 fffff880`018a5000   rdyboost rdyboost.sys Tue Jul 14 02:34:34 2009 (4A5BC48A)
fffff880`018a5000 fffff880`018b7000   mup      mup.sys      Tue Jul 14 02:23:45 2009 (4A5BC201)
fffff880`018b7000 fffff880`018c0000   hwpolicy hwpolicy.sys Tue Jul 14 02:19:22 2009 (4A5BC0FA)
fffff880`018c0000 fffff880`018fa000   fvevol   fvevol.sys   Sat Sep 26 05:34:26 2009 (4ABD7DB2)
fffff880`018fa000 fffff880`01910000   disk     disk.sys     Tue Jul 14 02:19:57 2009 (4A5BC11D)
fffff880`01910000 fffff880`01940000   CLASSPNP CLASSPNP.SYS Tue Jul 14 02:19:58 2009 (4A5BC11E)
fffff880`01940000 fffff880`0194e000   crashdmp crashdmp.sys Tue Jul 14 03:01:01 2009 (4A5BCABD)
fffff880`0194e000 fffff880`0195a000   dump_dumpata dump_dumpata.sys Tue Jul 14 02:19:47 2009 (4A5BC113)
fffff880`0195a000 fffff880`01963000   dump_atapi dump_atapi.sys Tue Jul 14 02:19:47 2009 (4A5BC113)
fffff880`01963000 fffff880`01976000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 02:21:51 2009 (4A5BC18F)
fffff880`01976000 fffff880`019a0000   cdrom    cdrom.sys    Tue Jul 14 02:19:54 2009 (4A5BC11A)
fffff880`019a0000 fffff880`019a9000   Null     Null.SYS     Tue Jul 14 02:19:37 2009 (4A5BC109)
fffff880`019a9000 fffff880`019b0000   Beep     Beep.SYS     Tue Jul 14 03:00:13 2009 (4A5BCA8D)
fffff880`019b0000 fffff880`019be000   vga      vga.sys      Tue Jul 14 02:38:47 2009 (4A5BC587)
fffff880`019be000 fffff880`019e3000   VIDEOPRT VIDEOPRT.SYS Tue Jul 14 02:38:51 2009 (4A5BC58B)
fffff880`019e3000 fffff880`019f3000   watchdog watchdog.sys Tue Jul 14 02:37:35 2009 (4A5BC53F)
fffff880`019f3000 fffff880`019fc000   RDPCDD   RDPCDD.sys   Tue Jul 14 03:16:34 2009 (4A5BCE62)
fffff880`02c00000 fffff880`02c51000   rdbss    rdbss.sys    Tue Jul 14 02:24:09 2009 (4A5BC219)
fffff880`02c51000 fffff880`02c5d000   nsiproxy nsiproxy.sys Tue Jul 14 02:21:02 2009 (4A5BC15E)
fffff880`02c65000 fffff880`02c83000   tdx      tdx.sys      Tue Jul 14 02:21:15 2009 (4A5BC16B)
fffff880`02c83000 fffff880`02c90000   TDI      TDI.SYS      Tue Jul 14 02:21:18 2009 (4A5BC16E)
fffff880`02c90000 fffff880`02d1a000   afd      afd.sys      Tue Jul 14 02:21:40 2009 (4A5BC184)
fffff880`02d1a000 fffff880`02d24000   aswRdr   aswRdr.SYS   Tue Sep 07 17:47:47 2010 (4C865093)
fffff880`02d24000 fffff880`02d69000   netbt    netbt.sys    Tue Jul 14 02:21:28 2009 (4A5BC178)
fffff880`02d69000 fffff880`02d72000   wfplwf   wfplwf.sys   Tue Jul 14 03:09:26 2009 (4A5BCCB6)
fffff880`02d72000 fffff880`02d98000   pacer    pacer.sys    Tue Jul 14 03:09:41 2009 (4A5BCCC5)
fffff880`02d98000 fffff880`02da7000   netbios  netbios.sys  Tue Jul 14 03:09:26 2009 (4A5BCCB6)
fffff880`02da7000 fffff880`02dc2000   wanarp   wanarp.sys   Tue Jul 14 03:10:21 2009 (4A5BCCED)
fffff880`02dc2000 fffff880`02dd6000   termdd   termdd.sys   Tue Jul 14 03:16:36 2009 (4A5BCE64)
fffff880`02dd6000 fffff880`02de1000   mssmbios mssmbios.sys Tue Jul 14 02:31:10 2009 (4A5BC3BE)
fffff880`02de1000 fffff880`02df0000   discache discache.sys Tue Jul 14 02:37:18 2009 (4A5BC52E)
fffff880`03cc1000 fffff880`03d44000   csc      csc.sys      Tue Jul 14 02:24:26 2009 (4A5BC22A)
fffff880`03d44000 fffff880`03d62000   dfsc     dfsc.sys     Tue Jul 14 02:23:44 2009 (4A5BC200)
fffff880`03d62000 fffff880`03d73000   blbdrive blbdrive.sys Tue Jul 14 02:35:59 2009 (4A5BC4DF)
fffff880`03d73000 fffff880`03d96000   aswSP    aswSP.SYS    Tue Sep 07 17:52:07 2010 (4C865197)
fffff880`03d96000 fffff880`03d9c000   AsIO     AsIO.sys     Mon Aug 03 10:03:16 2009 (4A768BB4)
fffff880`03d9c000 fffff880`03dc2000   tunnel   tunnel.sys   Tue Jul 14 03:09:37 2009 (4A5BCCC1)
fffff880`03dc2000 fffff880`03dd8000   intelppm intelppm.sys Tue Jul 14 02:19:25 2009 (4A5BC0FD)
fffff880`03e00000 fffff880`03e46000   dxgmms1  dxgmms1.sys  Tue Jul 14 02:38:32 2009 (4A5BC578)
fffff880`03e46000 fffff880`03e6a000   HDAudBus HDAudBus.sys Tue Jul 14 03:06:13 2009 (4A5BCBF5)
fffff880`03efe000 fffff880`03ff2000   dxgkrnl  dxgkrnl.sys  Fri Oct 02 04:00:14 2009 (4AC5509E)
fffff880`05601000 fffff880`061d2180   nvlddmkm nvlddmkm.sys Fri Oct 08 10:41:00 2010 (4CAECB0C)
fffff880`061d3000 fffff880`061d4180   nvBridge nvBridge.kmd Fri Oct 08 09:47:30 2010 (4CAEBE82)

 

[Veliremus]

Okay, I guess I'll install MSE back then...

I don't have any toolbars installed. Not on any browsers.

The drivers you talk about, I have already updated, if you remember . nTune is gone now, and the USB3 monitor is on the latest version.

I've run scannow, but that didn't come up with any errors (although it did crash when I scanned, but that was only one time).

I've since turned off Verifier, or should I leave that on?

Meanwhile, I'm taking out the audio card and installing the onboard card to see if that helps.

 

[Tews]

Leave it off for now to see if your problem has been resolved ..... Let us know how it comes out...

 

[cybercore]

The drivers you talk about, I have already updated, if you remember . nTune is gone now, and the USB3 monitor is on the latest version.

Sure, but the .dmp you have attached on this page doesn't show complete drivers list - that you have in the system right now, I can't see all of them, that's why I mentioned it was cut on drivers and was making sure they were fine.


Driver verifier - as Tews said turn it off for now.

 

[Veliremus]

About the sfc /scannow: I ran it again, went downstairs, and when I came back up, it showed the Windows login screen... I guess it crashed and rebooted?

Repair install sounds pretty good right now.

 

[cybercore]

Well, keep us updated.

The faster way would be reformat and reinstall the OS with the latest drivers. This way it'd be easier to know if it was a hardware related problem.

 

[Veliremus]

I think I'm going to try repair install first, as I don't have time make a complete clean install in the next few days. If the problem is not solved, I'll go for clean .

 

[Veliremus]

What the hell? I tried the Repair Install (popped the DVD in while I was in Windows and clicked Upgrade) and it began. Came back later to the Windows login screen, but when I logged in, it said that it had put back my original Windows because this version cannot be installed. But it's the same DVD... What happened here?

 

[cybercore]

Veliremus,

I would do as follows:

1. Reformat and Clean install
2. For a couple of days test the system with only Microsoft generic drivers in place - those that get automatically installed with windows. If any unknown devices in windows device manger, with yellow marks next to them, disable those. See if your clean system crashes over a day or two. If it crashes, you gotta hardware problem for sure.

3. If the vanilla install doesn't crash, install drivers, make sure you get the latest, and ensure you don't install any old ones - just leave those outdated devices disabled and unplugged. Of AV's install MSE ONLY.

4. Now if it crashes with the drivers from manufacturers, it still looks like your hardware, or a bad driver so attach the .dmp's for us to take a look through.

It is indeed a pain in the ankle, but you want to locate the cause right? Please take the time to do vanilla install, as I described in 1-4. Attach all the .dmp's you accumulate over this period of troubleshooting.


* A few years ago I had something similar: occasional crashes, bsod errors like 7f, 1a, and others, not really pointing to anything. Whatever I did, reinstalled drivers, tested memory, didn't test the video card as it behaved very well, GF 6600, could play Crysis 800x600 like 2 hours in a row, 45C degrees maximum, all being fine and somehow crashes didn't coincide with the gameplay. Nothing helped and there were no evident causes - until 1 month later, at boot, in bios setup, I noticed visual artifacts and finally got video_tdr_error 116. I replaced the card with 7600 and lived happily a year and a half, then bought a new system cause I needed faster hardware.

So each case is so different, but occasionally hardware wears out so "smoothly" one can hardly notice. Hopefully not in your case, so reformat and reinstall.


~~~~~~~~~~~~~~

RAM - http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

CPU - http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

HDD - HD Diagnostic