Hey all,
I've watched this forum for a while (best one yet, as far as I can tell, expertise-wise) and I've tried to solve and diagnose as much as I can by myself, but now I really need help. This thing is killing me...
My problem:
BSODs! Lots of them! I�ve tried searching for similar topics, but while they do exist, I didn�t want to invade any of them. And because of the fact that my BSODs seem to vary a lot (see attachment).
MEMORY_MANAGEMENT is the one that repeats most, but I did a 12 hour Memtest run on my memory and it seems fine. The culprit is always named by BlueScreenViewer as ntoskrnl.exe (except for one crash, that was caused by the LAN driver, since updated).
They happen at random, it seems. One time I was copying files, one time I was playing Starcraft 2, one time I was just chatting on MSN and browsing in Firefox. Spotify on, most of the time (except during Starcraft of course). Pretty sure there was always sound playing.
Recently I also noticed that the audio seems to stutter (like right now, after BSOD). At one time, it wouldn�t stop stuttering, so I reinstalled the Creative driver. It seemed to solve it, if only temporarily.
Additional details:
This is not the first problem I�ve had problems with my new build (few months old). I used to own a HD5850 Toxic from AMD, which glitched like hell. I RMAed it for this Nvidia, which runs fine.
The crashes occurred a few days (weeks?) after I got the new card. I don�t think it�s related to the card, though. Once, I got a POST message after a BSOD (and one more time after a normal reboot) which said: overclocking failed. But I don�t overclock...
What I have tried:
-IntelBurnTest (maximum, 6 runs): stable
-Memtest86+ (12 hours): zero errors
-Western Digital Lifeguard Diagnostic (Extended Test): zero errors
-Furmark (60 minutes): stable
-Prime95 (can�t recall how long): zero errors
-SiSoft Sandra Burn Test: pass
-Updated the BIOS to latest version
-Reseated RAM
-Updated my drivers and my Windows
-Turned off the Audio Devices on my graphics card
-sfc /scannow: pass (but I got a BSOD the first time I tried...)
-Switching from Avast to Microsoft Security Essentials: no change
-Scanning for malware (Avast, Hitmanpro, MSE, MalwareBytes): no malware
What I have not tried:
-A repair install or complete new install (I�ve avoided this, because I didn�t want to lose all my stuff). But so much went wrong with that old card, and I installed and reinstalled so much stuff back then, that maybe my Windows install got corrupted. I�m thinking that is to be my next step, though.
-Taking out the audiocard. Since I have sound problems...maybe that�s it. I�ve heard Creative drivers suck, and this is not a state-of-the-art card.
My system:
Intel i7 860 @ 2.80GHz
Corsair XMS 4GB RAM
Asus P7P55D-E Pro
MSI Geforce GTX460 Cyclone 1GB OC
Cooler Master CM 690 Advanced II
Windows 7 Ultimate x64 (Upgrade from XP)
http://tweakers.net/gallery/242647?inv_id=78046#tab:inventaris
Attached are my dumps. I can upload the latest MEMORY.DMP, but that�s like 400MB, so only on request.
I hope you guys can help me! First that bogus AMD card, now this... It sucks the fun right out of buying a kick-ass new computer .
-Veliremus
SOLUTION (Sort of):
It turned out that, even though I had zero Memtest errors, the Corsair memory was the culprit. The retailer said it is a compatibility issue with Asus and Corsair. Picking a Kingston set of the QVL list of my motherboard seems to have fixed the problem. Two weeks without BSODs now.
I've watched this forum for a while (best one yet, as far as I can tell, expertise-wise) and I've tried to solve and diagnose as much as I can by myself, but now I really need help. This thing is killing me...
My problem:
BSODs! Lots of them! I�ve tried searching for similar topics, but while they do exist, I didn�t want to invade any of them. And because of the fact that my BSODs seem to vary a lot (see attachment).
MEMORY_MANAGEMENT is the one that repeats most, but I did a 12 hour Memtest run on my memory and it seems fine. The culprit is always named by BlueScreenViewer as ntoskrnl.exe (except for one crash, that was caused by the LAN driver, since updated).
They happen at random, it seems. One time I was copying files, one time I was playing Starcraft 2, one time I was just chatting on MSN and browsing in Firefox. Spotify on, most of the time (except during Starcraft of course). Pretty sure there was always sound playing.
Recently I also noticed that the audio seems to stutter (like right now, after BSOD). At one time, it wouldn�t stop stuttering, so I reinstalled the Creative driver. It seemed to solve it, if only temporarily.
Additional details:
This is not the first problem I�ve had problems with my new build (few months old). I used to own a HD5850 Toxic from AMD, which glitched like hell. I RMAed it for this Nvidia, which runs fine.
The crashes occurred a few days (weeks?) after I got the new card. I don�t think it�s related to the card, though. Once, I got a POST message after a BSOD (and one more time after a normal reboot) which said: overclocking failed. But I don�t overclock...
What I have tried:
-IntelBurnTest (maximum, 6 runs): stable
-Memtest86+ (12 hours): zero errors
-Western Digital Lifeguard Diagnostic (Extended Test): zero errors
-Furmark (60 minutes): stable
-Prime95 (can�t recall how long): zero errors
-SiSoft Sandra Burn Test: pass
-Updated the BIOS to latest version
-Reseated RAM
-Updated my drivers and my Windows
-Turned off the Audio Devices on my graphics card
-sfc /scannow: pass (but I got a BSOD the first time I tried...)
-Switching from Avast to Microsoft Security Essentials: no change
-Scanning for malware (Avast, Hitmanpro, MSE, MalwareBytes): no malware
What I have not tried:
-A repair install or complete new install (I�ve avoided this, because I didn�t want to lose all my stuff). But so much went wrong with that old card, and I installed and reinstalled so much stuff back then, that maybe my Windows install got corrupted. I�m thinking that is to be my next step, though.
-Taking out the audiocard. Since I have sound problems...maybe that�s it. I�ve heard Creative drivers suck, and this is not a state-of-the-art card.
My system:
Intel i7 860 @ 2.80GHz
Corsair XMS 4GB RAM
Asus P7P55D-E Pro
MSI Geforce GTX460 Cyclone 1GB OC
Cooler Master CM 690 Advanced II
Windows 7 Ultimate x64 (Upgrade from XP)
http://tweakers.net/gallery/242647?inv_id=78046#tab:inventaris
Attached are my dumps. I can upload the latest MEMORY.DMP, but that�s like 400MB, so only on request.
I hope you guys can help me! First that bogus AMD card, now this... It sucks the fun right out of buying a kick-ass new computer .
-Veliremus
SOLUTION (Sort of):
It turned out that, even though I had zero Memtest errors, the Corsair memory was the culprit. The retailer said it is a compatibility issue with Asus and Corsair. Picking a Kingston set of the QVL list of my motherboard seems to have fixed the problem. Two weeks without BSODs now.
Hey all,
I've watched this forum for a while (best one yet, as far as I can tell, expertise-wise) and I've tried to solve and diagnose as much as I can by myself, but now I really need help. This thing is killing me...
My problem:
BSODs! Lots of them! I�ve tried searching for similar topics, but while they do exist, I didn�t want to invade any of them. And because of the fact that my BSODs seem to vary a lot (see attachment).
MEMORY_MANAGEMENT is the one that repeats most, but I did a 12 hour Memtest run on my memory and it seems fine. The culprit is always named by BlueScreenViewer as ntoskrnl.exe (except for one crash, that was caused by the LAN driver, since updated).
They happen at random, it seems. One time I was copying files, one time I was playing Starcraft 2, one time I was just chatting on MSN and browsing in Firefox. Spotify on, most of the time (except during Starcraft of course). Pretty sure there was always sound playing.
Recently I also noticed that the audio seems to stutter (like right now, after BSOD). At one time, it wouldn�t stop stuttering, so I reinstalled the Creative driver. It seemed to solve it, if only temporarily.
Additional details:
This is not the first problem I�ve had problems with my new build (few months old). I used to own a HD5850 Toxic from AMD, which glitched like hell. I RMAed it for this Nvidia, which runs fine.
The crashes occurred a few days (weeks?) after I got the new card. I don�t think it�s related to the card, though. Once, I got a POST message after a BSOD (and one more time after a normal reboot) which said: overclocking failed. But I don�t overclock...
What I have tried:
-IntelBurnTest (maximum, 6 runs): stable
-Memtest86+ (12 hours): zero errors
-Western Digital Lifeguard Diagnostic (Extended Test): zero errors
-Furmark (60 minutes): stable
-Prime95 (can�t recall how long): zero errors
-SiSoft Sandra Burn Test: pass
-Updated the BIOS to latest version
-Reseated RAM
-Updated my drivers and my Windows
-Turned off the Audio Devices on my graphics card
-sfc /scannow: pass (but I got a BSOD the first time I tried...)
-Switching from Avast to Microsoft Security Essentials: no change
-Scanning for malware (Avast, Hitmanpro, MSE, MalwareBytes): no malware
What I have not tried:
-A repair install or complete new install (I�ve avoided this, because I didn�t want to lose all my stuff). But so much went wrong with that old card, and I installed and reinstalled so much stuff back then, that maybe my Windows install got corrupted. I�m thinking that is to be my next step, though.
-Taking out the audiocard. Since I have sound problems...maybe that�s it. I�ve heard Creative drivers suck, and this is not a state-of-the-art card.
My system:
Intel i7 860 @ 2.80GHz
Corsair XMS 4GB RAM
Asus P7P55D-E Pro
MSI Geforce GTX460 Cyclone 1GB OC
Cooler Master CM 690 Advanced II
Windows 7 Ultimate x64 (Upgrade from XP)
http://tweakers.net/gallery/242647?inv_id=78046#tab:inventaris
Attached are my dumps. I can upload the latest MEMORY.DMP, but that�s like 400MB, so only on request.
I hope you guys can help me! First that bogus AMD card, now this... It sucks the fun right out of buying a kick-ass new computer .
-Veliremus
I've watched this forum for a while (best one yet, as far as I can tell, expertise-wise) and I've tried to solve and diagnose as much as I can by myself, but now I really need help. This thing is killing me...
My problem:
BSODs! Lots of them! I�ve tried searching for similar topics, but while they do exist, I didn�t want to invade any of them. And because of the fact that my BSODs seem to vary a lot (see attachment).
MEMORY_MANAGEMENT is the one that repeats most, but I did a 12 hour Memtest run on my memory and it seems fine. The culprit is always named by BlueScreenViewer as ntoskrnl.exe (except for one crash, that was caused by the LAN driver, since updated).
They happen at random, it seems. One time I was copying files, one time I was playing Starcraft 2, one time I was just chatting on MSN and browsing in Firefox. Spotify on, most of the time (except during Starcraft of course). Pretty sure there was always sound playing.
Recently I also noticed that the audio seems to stutter (like right now, after BSOD). At one time, it wouldn�t stop stuttering, so I reinstalled the Creative driver. It seemed to solve it, if only temporarily.
Additional details:
This is not the first problem I�ve had problems with my new build (few months old). I used to own a HD5850 Toxic from AMD, which glitched like hell. I RMAed it for this Nvidia, which runs fine.
The crashes occurred a few days (weeks?) after I got the new card. I don�t think it�s related to the card, though. Once, I got a POST message after a BSOD (and one more time after a normal reboot) which said: overclocking failed. But I don�t overclock...
What I have tried:
-IntelBurnTest (maximum, 6 runs): stable
-Memtest86+ (12 hours): zero errors
-Western Digital Lifeguard Diagnostic (Extended Test): zero errors
-Furmark (60 minutes): stable
-Prime95 (can�t recall how long): zero errors
-SiSoft Sandra Burn Test: pass
-Updated the BIOS to latest version
-Reseated RAM
-Updated my drivers and my Windows
-Turned off the Audio Devices on my graphics card
-sfc /scannow: pass (but I got a BSOD the first time I tried...)
-Switching from Avast to Microsoft Security Essentials: no change
-Scanning for malware (Avast, Hitmanpro, MSE, MalwareBytes): no malware
What I have not tried:
-A repair install or complete new install (I�ve avoided this, because I didn�t want to lose all my stuff). But so much went wrong with that old card, and I installed and reinstalled so much stuff back then, that maybe my Windows install got corrupted. I�m thinking that is to be my next step, though.
-Taking out the audiocard. Since I have sound problems...maybe that�s it. I�ve heard Creative drivers suck, and this is not a state-of-the-art card.
My system:
Intel i7 860 @ 2.80GHz
Corsair XMS 4GB RAM
Asus P7P55D-E Pro
MSI Geforce GTX460 Cyclone 1GB OC
Cooler Master CM 690 Advanced II
Windows 7 Ultimate x64 (Upgrade from XP)
http://tweakers.net/gallery/242647?inv_id=78046#tab:inventaris
Attached are my dumps. I can upload the latest MEMORY.DMP, but that�s like 400MB, so only on request.
I hope you guys can help me! First that bogus AMD card, now this... It sucks the fun right out of buying a kick-ass new computer .
-Veliremus
If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:
* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Start your own thread in the appropriate section of the forum and attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.
BTW
Blue screen view isnt always accurate, nor comprehensive giving OS files often as the cause.
Creative 5.1 drivers clearly a problem I have them too.
I do apologize, I could have sworn the attachment was successfully uploaded.
I will upload the MEMORY.DMP as soon as possible. In the mean-time, I've added the attachment to my initial post.
I will upload the MEMORY.DMP as soon as possible. In the mean-time, I've added the attachment to my initial post.
Okay, managed to upload it:
http://www.veliremus.com/files/caprica/7oct_dmp.rar
And here's an older one:
http://www.veliremus.com/files/caprica/17sept_dmp.rar
And as in the first post:
http://www.sevenforums.com/attachmen...d_jcgriff2.rar
http://www.veliremus.com/files/caprica/7oct_dmp.rar
And here's an older one:
http://www.veliremus.com/files/caprica/17sept_dmp.rar
And as in the first post:
http://www.sevenforums.com/attachmen...d_jcgriff2.rar
And here's another one. I think this was the one that happened when Driver Verifier was on. Ironically, it didn't give any explanation like the other did.
http://www.veliremus.com/files/caprica/2oct_dmp.rar
Any ideas, anyone?
http://www.veliremus.com/files/caprica/2oct_dmp.rar
Any ideas, anyone?
100710-16910-01.dmp
MEMORY_MANAGEMENT (1a)
win32k!memset+80
100210-14617-01.dmp
PFN_LIST_CORRUPT (4e)
memory_corruption ( nt!MiBadShareCount+4c )
100410-22089-01.dmp
CLOCK_WATCHDOG_TIMEOUT (101)
Stack: nt!, win32k!, hal!, nt!
Unknown_Image ( ANALYSIS_INCONCLUSIVE )
1. Update:
nvoclk64.sys Mon Aug 18 19:00:01 2008
NVidia System Utility Driver (overclocking related)
adfs.SYS Thu Jun 26 23:52:37 2008
Adobe
P17.sys Tue Apr 21 09:12:47 2009
Creative SB Audigy LS
AsIO.sys Mon Aug 03 10:03:16 2009
ASUS Probe
nusb3xhc.sys Mon Oct 26 16:19:48 2009
USB 3.0 Device Driver NEC Electronics Corporation
2. If crashes persist:
1) run memtest.org overnight RAM - Test with Memtest86+
2) enable driver verifier Driver Verifier - Enable and Disable
3) attach your latest crash dumps
MEMORY_MANAGEMENT (1a)
win32k!memset+80
100210-14617-01.dmp
PFN_LIST_CORRUPT (4e)
memory_corruption ( nt!MiBadShareCount+4c )
100410-22089-01.dmp
CLOCK_WATCHDOG_TIMEOUT (101)
Stack: nt!, win32k!, hal!, nt!
Unknown_Image ( ANALYSIS_INCONCLUSIVE )
1. Update:
nvoclk64.sys Mon Aug 18 19:00:01 2008
NVidia System Utility Driver (overclocking related)
adfs.SYS Thu Jun 26 23:52:37 2008
Adobe
P17.sys Tue Apr 21 09:12:47 2009
Creative SB Audigy LS
AsIO.sys Mon Aug 03 10:03:16 2009
ASUS Probe
nusb3xhc.sys Mon Oct 26 16:19:48 2009
USB 3.0 Device Driver NEC Electronics Corporation
2. If crashes persist:
1) run memtest.org overnight RAM - Test with Memtest86+
2) enable driver verifier Driver Verifier - Enable and Disable
3) attach your latest crash dumps
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:\a\Minidump\D M P\100710-16910-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`02e4f000 PsLoadedModuleList = 0xfffff800`0308ce50 System Uptime: 0 days 1:07:55.816 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {5003, fffff90000812000, 1f39, 70300003ee5} Probably caused by : win32k.sys ( win32k!memset+80 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000005003, The subtype of the bugcheck. Arg2: fffff90000812000 Arg3: 0000000000001f39 Arg4: 0000070300003ee5 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_5003 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: spotify.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff8800547e0b0 -- (.trap 0xfffff8800547e0b0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff900c2c6b000 rbx=0000000000000000 rcx=fffff900c2c71000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff960000e3b90 rsp=fffff8800547e248 rbp=0000000000000001 r8=0000000000000008 r9=000000000000074b r10=000000000000007f r11=0000000000000034 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc win32k!memset+0x80: fffff960`000e3b90 488911 mov qword ptr [rcx],rdx ds:8cc0:fffff900`c2c71000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002f2ee58 to fffff80002ebf740 STACK_TEXT: fffff880`0547dd48 fffff800`02f2ee58 : 00000000`0000001a 00000000`00005003 fffff900`00812000 00000000`00001f39 : nt!KeBugCheckEx fffff880`0547dd50 fffff800`02edbca2 : 00000000`00000001 fffff900`c2c71000 fffff880`0547e0b0 fffff6fc`80616388 : nt! ?? ::FNODOBFM::`string'+0x29f57 fffff880`0547de40 fffff800`02ed9cf1 : fffff900`c2b13ff8 00000000`00002c6b fffff880`039f8bd0 fffff800`02ed768f : nt!MiDispatchFault+0x8c2 fffff880`0547df50 fffff800`02ebd82e : 00000000`00000001 fffff900`c2c6b000 00000000`35316800 fffff900`c2c6b000 : nt!MmAccessFault+0x8f1 fffff880`0547e0b0 fffff960`000e3b90 : fffff960`000d29d2 fffff900`c0a9a9f0 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e fffff880`0547e248 fffff960`000d29d2 : fffff900`c0a9a9f0 00000000`00000000 00000000`00000000 fffff960`000e4d0a : win32k!memset+0x80 fffff880`0547e250 fffff960`000d3eeb : 00000000`00000001 fffff880`0547e458 00000000`00000001 00000000`00000000 : win32k!AllocateObject+0xf2 fffff880`0547e290 fffff960`00254886 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SURFMEM::bCreateDIB+0x1fb fffff880`0547e380 fffff960`000be741 : 00000980`00000000 fffffa80`036cb040 fffff900`c08aece8 00000000`00000018 : win32k!EngHTBlt+0x9fe fffff880`0547e7d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!EngStretchBltNew+0x2b9 STACK_COMMAND: kb FOLLOWUP_IP: win32k!memset+80 fffff960`000e3b90 488911 mov qword ptr [rcx],rdx SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: win32k!memset+80 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c483f FAILURE_BUCKET_ID: X64_0x1a_5003_win32k!memset+80 BUCKET_ID: X64_0x1a_5003_win32k!memset+80 Followup: MachineOwner --------- 2: kd> lmtn start end module name fffff800`00ba8000 fffff800`00bb2000 kdcom kdcom.dll Tue Jul 14 04:31:07 2009 (4A5BDFDB) fffff800`02e06000 fffff800`02e4f000 hal hal.dll Tue Jul 14 04:27:36 2009 (4A5BDF08) fffff800`02e4f000 fffff800`0342b000 nt ntkrnlmp.exe Sat Jun 19 07:16:41 2010 (4C1C44A9) fffff880`00c00000 fffff880`00c10000 PCIIDEX PCIIDEX.SYS Tue Jul 14 02:19:48 2009 (4A5BC114) fffff880`00c10000 fffff880`00c2a000 mountmgr mountmgr.sys Tue Jul 14 02:19:54 2009 (4A5BC11A) fffff880`00c2a000 fffff880`00c54000 ataport ataport.SYS Tue Jul 14 02:19:52 2009 (4A5BC118) fffff880`00c54000 fffff880`00c5f000 amdxata amdxata.sys Tue May 19 20:56:59 2009 (4A12F2EB) fffff880`00c8d000 fffff880`00cd1000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 04:29:10 2009 (4A5BDF66) fffff880`00cd1000 fffff880`00ce5000 PSHED PSHED.dll Tue Jul 14 04:32:23 2009 (4A5BE027) fffff880`00ce5000 fffff880`00d43000 CLFS CLFS.SYS Tue Jul 14 02:19:57 2009 (4A5BC11D) fffff880`00d43000 fffff880`00d9a000 ACPI ACPI.sys Tue Jul 14 02:19:34 2009 (4A5BC106) fffff880`00d9a000 fffff880`00df6000 volmgrx volmgrx.sys Tue Jul 14 02:20:33 2009 (4A5BC141) fffff880`00e00000 fffff880`00e0d000 vdrvroot vdrvroot.sys Tue Jul 14 03:01:31 2009 (4A5BCADB) fffff880`00e0d000 fffff880`00e22000 partmgr partmgr.sys Tue Jul 14 02:19:58 2009 (4A5BC11E) fffff880`00e22000 fffff880`00e37000 volmgr volmgr.sys Tue Jul 14 02:19:57 2009 (4A5BC11D) fffff880`00e37000 fffff880`00e3e000 pciide pciide.sys Tue Jul 14 02:19:49 2009 (4A5BC115) fffff880`00e3e000 fffff880`00e47000 atapi atapi.sys Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`00e47000 fffff880`00f07000 CI CI.dll Tue Jul 14 04:32:13 2009 (4A5BE01D) fffff880`00f07000 fffff880`00fab000 Wdf01000 Wdf01000.sys Tue Jul 14 02:22:07 2009 (4A5BC19F) fffff880`00fab000 fffff880`00fba000 WDFLDR WDFLDR.SYS Tue Jul 14 02:19:54 2009 (4A5BC11A) fffff880`00fba000 fffff880`00fc3000 WMILIB WMILIB.SYS Tue Jul 14 02:19:51 2009 (4A5BC117) fffff880`00fc3000 fffff880`00fcd000 msisadrv msisadrv.sys Tue Jul 14 02:19:26 2009 (4A5BC0FE) fffff880`00fcd000 fffff880`01000000 pci pci.sys Tue Jul 14 02:19:51 2009 (4A5BC117) fffff880`0102a000 fffff880`01076000 fltmgr fltmgr.sys Tue Jul 14 02:19:59 2009 (4A5BC11F) fffff880`01076000 fffff880`0108a000 fileinfo fileinfo.sys Tue Jul 14 02:34:25 2009 (4A5BC481) fffff880`0108a000 fffff880`010e8000 msrpc msrpc.sys Tue Jul 14 02:21:32 2009 (4A5BC17C) fffff880`010e8000 fffff880`0115b000 cng cng.sys Tue Jul 14 02:49:40 2009 (4A5BC814) fffff880`0115b000 fffff880`011a7000 volsnap volsnap.sys Tue Jul 14 02:20:08 2009 (4A5BC128) fffff880`011a7000 fffff880`011e1000 rdyboost rdyboost.sys Tue Jul 14 02:34:34 2009 (4A5BC48A) fffff880`01200000 fffff880`0121a000 ksecdd ksecdd.sys Tue Jul 14 02:20:54 2009 (4A5BC156) fffff880`0121a000 fffff880`0122b000 pcw pcw.sys Tue Jul 14 02:19:27 2009 (4A5BC0FF) fffff880`0122b000 fffff880`01235000 Fs_Rec Fs_Rec.sys Tue Jul 14 02:19:45 2009 (4A5BC111) fffff880`01235000 fffff880`0123e000 hwpolicy hwpolicy.sys Tue Jul 14 02:19:22 2009 (4A5BC0FA) fffff880`01250000 fffff880`013f3000 Ntfs Ntfs.sys Tue Jul 14 02:20:47 2009 (4A5BC14F) fffff880`01400000 fffff880`0144a000 fwpkclnt fwpkclnt.sys Tue Jul 14 02:21:08 2009 (4A5BC164) fffff880`0144a000 fffff880`0145a000 vmstorfl vmstorfl.sys Tue Jul 14 02:42:54 2009 (4A5BC67E) fffff880`0145a000 fffff880`01462000 spldr spldr.sys Mon May 11 19:56:27 2009 (4A0858BB) fffff880`01462000 fffff880`01474000 mup mup.sys Tue Jul 14 02:23:45 2009 (4A5BC201) fffff880`0147b000 fffff880`0156d000 ndis ndis.sys Tue Jul 14 02:21:40 2009 (4A5BC184) fffff880`0156d000 fffff880`015cd000 NETIO NETIO.SYS Tue Jul 14 02:21:46 2009 (4A5BC18A) fffff880`015cd000 fffff880`015f8000 ksecpkg ksecpkg.sys Fri Dec 11 08:03:32 2009 (4B21E0B4) fffff880`01600000 fffff880`017fd000 tcpip tcpip.sys Mon Jun 14 06:39:04 2010 (4C15A458) fffff880`01800000 fffff880`0182d000 MpFilter MpFilter.sys Sat Mar 20 07:58:08 2010 (4BA463F0) fffff880`0182d000 fffff880`01836000 Null Null.SYS Tue Jul 14 02:19:37 2009 (4A5BC109) fffff880`01836000 fffff880`0183d000 Beep Beep.SYS Tue Jul 14 03:00:13 2009 (4A5BCA8D) fffff880`0183d000 fffff880`0184b000 vga vga.sys Tue Jul 14 02:38:47 2009 (4A5BC587) fffff880`0184b000 fffff880`01870000 VIDEOPRT VIDEOPRT.SYS Tue Jul 14 02:38:51 2009 (4A5BC58B) fffff880`01870000 fffff880`01880000 watchdog watchdog.sys Tue Jul 14 02:37:35 2009 (4A5BC53F) fffff880`01880000 fffff880`01889000 RDPCDD RDPCDD.sys Tue Jul 14 03:16:34 2009 (4A5BCE62) fffff880`01889000 fffff880`01892000 rdpencdd rdpencdd.sys Tue Jul 14 03:16:34 2009 (4A5BCE62) fffff880`01892000 fffff880`0189b000 rdprefmp rdprefmp.sys Tue Jul 14 03:16:35 2009 (4A5BCE63) fffff880`0189b000 fffff880`018a6000 Msfs Msfs.SYS Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`018a6000 fffff880`018b7000 Npfs Npfs.SYS Tue Jul 14 02:19:48 2009 (4A5BC114) fffff880`018b7000 fffff880`018d5000 tdx tdx.sys Tue Jul 14 02:21:15 2009 (4A5BC16B) fffff880`018d5000 fffff880`018e2000 TDI TDI.SYS Tue Jul 14 02:21:18 2009 (4A5BC16E) fffff880`018f6000 fffff880`01930000 fvevol fvevol.sys Sat Sep 26 05:34:26 2009 (4ABD7DB2) fffff880`01930000 fffff880`01946000 disk disk.sys Tue Jul 14 02:19:57 2009 (4A5BC11D) fffff880`01946000 fffff880`01976000 CLASSPNP CLASSPNP.SYS Tue Jul 14 02:19:58 2009 (4A5BC11E) fffff880`019ac000 fffff880`019d6000 cdrom cdrom.sys Tue Jul 14 02:19:54 2009 (4A5BC11A) fffff880`02c38000 fffff880`02cc2000 afd afd.sys Tue Jul 14 02:21:40 2009 (4A5BC184) fffff880`02cc2000 fffff880`02d07000 netbt netbt.sys Tue Jul 14 02:21:28 2009 (4A5BC178) fffff880`02d07000 fffff880`02d10000 wfplwf wfplwf.sys Tue Jul 14 03:09:26 2009 (4A5BCCB6) fffff880`02d10000 fffff880`02d36000 pacer pacer.sys Tue Jul 14 03:09:41 2009 (4A5BCCC5) fffff880`02d36000 fffff880`02d45000 netbios netbios.sys Tue Jul 14 03:09:26 2009 (4A5BCCB6) fffff880`02d45000 fffff880`02d60000 wanarp wanarp.sys Tue Jul 14 03:10:21 2009 (4A5BCCED) fffff880`02d60000 fffff880`02d74000 termdd termdd.sys Tue Jul 14 03:16:36 2009 (4A5BCE64) fffff880`02d74000 fffff880`02dc5000 rdbss rdbss.sys Tue Jul 14 02:24:09 2009 (4A5BC219) fffff880`02dc5000 fffff880`02dd1000 nsiproxy nsiproxy.sys Tue Jul 14 02:21:02 2009 (4A5BC15E) fffff880`02dd1000 fffff880`02ddc000 mssmbios mssmbios.sys Tue Jul 14 02:31:10 2009 (4A5BC3BE) fffff880`02ddc000 fffff880`02deb000 discache discache.sys Tue Jul 14 02:37:18 2009 (4A5BC52E) fffff880`04034000 fffff880`040b7000 csc csc.sys Tue Jul 14 02:24:26 2009 (4A5BC22A) fffff880`040b7000 fffff880`040d5000 dfsc dfsc.sys Tue Jul 14 02:23:44 2009 (4A5BC200) fffff880`040d5000 fffff880`040e6000 blbdrive blbdrive.sys Tue Jul 14 02:35:59 2009 (4A5BC4DF) fffff880`040e6000 fffff880`040ec000 AsIO AsIO.sys Mon Aug 03 10:03:16 2009 (4A768BB4) fffff880`040ec000 fffff880`04112000 tunnel tunnel.sys Tue Jul 14 03:09:37 2009 (4A5BCCC1) fffff880`04112000 fffff880`04128000 intelppm intelppm.sys Tue Jul 14 02:19:25 2009 (4A5BC0FD) fffff880`04128000 fffff880`04143000 raspppoe raspppoe.sys Tue Jul 14 03:10:17 2009 (4A5BCCE9) fffff880`04143000 fffff880`04164000 raspptp raspptp.sys Tue Jul 14 03:10:18 2009 (4A5BCCEA) fffff880`04164000 fffff880`0417e000 rassstp rassstp.sys Tue Jul 14 03:10:25 2009 (4A5BCCF1) fffff880`0417e000 fffff880`0418d000 kbdclass kbdclass.sys Tue Jul 14 02:19:50 2009 (4A5BC116) fffff880`0418d000 fffff880`0419c000 mouclass mouclass.sys Tue Jul 14 02:19:50 2009 (4A5BC116) fffff880`0419c000 fffff880`041ae000 umbus umbus.sys Tue Jul 14 03:06:56 2009 (4A5BCC20) fffff880`04200000 fffff880`0422f000 nusb3xhc nusb3xhc.sys Mon Oct 26 16:19:48 2009 (4AE5B004) fffff880`0422f000 fffff880`04230f00 USBD USBD.SYS Tue Jul 14 03:06:23 2009 (4A5BCBFF) fffff880`04231000 fffff880`04325000 dxgkrnl dxgkrnl.sys Fri Oct 02 04:00:14 2009 (4AC5509E) fffff880`04325000 fffff880`0436b000 dxgmms1 dxgmms1.sys Tue Jul 14 02:38:32 2009 (4A5BC578) fffff880`0436b000 fffff880`0438f000 HDAudBus HDAudBus.sys Tue Jul 14 03:06:13 2009 (4A5BCBF5) fffff880`0438f000 fffff880`043a0000 usbehci usbehci.sys Tue Jul 14 03:06:30 2009 (4A5BCC06) fffff880`043a0000 fffff880`043f6000 USBPORT USBPORT.SYS Tue Jul 14 03:06:31 2009 (4A5BCC07) fffff880`043f6000 fffff880`043ff000 wmiacpi wmiacpi.sys Tue Jul 14 02:31:02 2009 (4A5BC3B6) fffff880`04400000 fffff880`0443d000 portcls portcls.sys Tue Jul 14 03:06:27 2009 (4A5BCC03) fffff880`0443d000 fffff880`0445f000 drmk drmk.sys Tue Jul 14 04:01:25 2009 (4A5BD8E5) fffff880`0445f000 fffff880`04464200 ksthunk ksthunk.sys Tue Jul 14 03:00:19 2009 (4A5BCA93) fffff880`04465000 fffff880`0446d000 ASACPI ASACPI.sys Thu Jul 16 06:31:29 2009 (4A5E9F11) fffff880`0446d000 fffff880`0447a000 GEARAspiWDM GEARAspiWDM.sys Mon May 18 15:17:04 2009 (4A1151C0) fffff880`0447a000 fffff880`0447b480 swenum swenum.sys Tue Jul 14 03:00:18 2009 (4A5BCA92) fffff880`0447c000 fffff880`045fb000 P17 P17.sys Tue Apr 21 09:12:47 2009 (49ED63DF) fffff880`04c00000 fffff880`04c0e000 monitor monitor.sys Tue Jul 14 02:38:52 2009 (4A5BC58C) fffff880`04c0e000 fffff880`04c31000 luafv luafv.sys Tue Jul 14 02:26:13 2009 (4A5BC295) fffff880`04c31000 fffff880`04c52000 WudfPf WudfPf.sys Tue Jul 14 03:05:37 2009 (4A5BCBD1) fffff880`04c52000 fffff880`04c67000 lltdio lltdio.sys Tue Jul 14 03:08:50 2009 (4A5BCC92) fffff880`04c67000 fffff880`04c7f000 rspndr rspndr.sys Tue Jul 14 03:08:50 2009 (4A5BCC92) fffff880`04cb5000 fffff880`04d0f000 usbhub usbhub.sys Tue Jul 14 03:07:09 2009 (4A5BCC2D) fffff880`04d0f000 fffff880`04d26000 nusb3hub nusb3hub.sys Mon Oct 26 16:19:44 2009 (4AE5B000) fffff880`04d26000 fffff880`04d3b000 NDProxy NDProxy.SYS Tue Jul 14 03:10:05 2009 (4A5BCCDD) fffff880`04d3b000 fffff880`04d4c000 usbaapl64 usbaapl64.sys Thu Apr 01 06:20:15 2010 (4BB410EF) fffff880`04d4c000 fffff880`04d5a000 hidusb hidusb.sys Tue Jul 14 03:06:22 2009 (4A5BCBFE) fffff880`04d5a000 fffff880`04d73000 HIDCLASS HIDCLASS.SYS Tue Jul 14 03:06:21 2009 (4A5BCBFD) fffff880`04d73000 fffff880`04d7b080 HIDPARSE HIDPARSE.SYS Tue Jul 14 03:06:17 2009 (4A5BCBF9) fffff880`04d7c000 fffff880`04d99000 usbccgp usbccgp.sys Tue Jul 14 03:06:45 2009 (4A5BCC15) fffff880`04d99000 fffff880`04da6000 mouhid mouhid.sys Tue Jul 14 03:00:20 2009 (4A5BCA94) fffff880`04da6000 fffff880`04db2000 Dxapi Dxapi.sys Tue Jul 14 02:38:28 2009 (4A5BC574) fffff880`04db2000 fffff880`04dc0000 kbdhid kbdhid.sys Tue Jul 14 03:00:20 2009 (4A5BCA94) fffff880`04dc0000 fffff880`04dce000 crashdmp crashdmp.sys Tue Jul 14 03:01:01 2009 (4A5BCABD) fffff880`04dce000 fffff880`04dda000 dump_dumpata dump_dumpata.sys Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`04dda000 fffff880`04de3000 dump_atapi dump_atapi.sys Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`04de3000 fffff880`04df6000 dump_dumpfve dump_dumpfve.sys Tue Jul 14 02:21:51 2009 (4A5BC18F) fffff880`05a00000 fffff880`05a23000 mrxsmb20 mrxsmb20.sys Sat Feb 27 09:52:26 2010 (4B88CF3A) fffff880`05a23000 fffff880`05a3b000 adfs adfs.SYS Thu Jun 26 23:52:37 2008 (48640195) fffff880`05a3b000 fffff880`05a44000 cpuz134_x64 cpuz134_x64.sys Fri Jul 09 14:16:58 2010 (4C37052A) fffff880`05a44000 fffff880`05a53000 nvoclk64 nvoclk64.sys Mon Aug 18 19:00:01 2008 (48A99C81) fffff880`05a66000 fffff880`05b2e000 HTTP HTTP.sys Tue Jul 14 02:22:16 2009 (4A5BC1A8) fffff880`05b2e000 fffff880`05b4c000 bowser bowser.sys Tue Jul 14 02:23:50 2009 (4A5BC206) fffff880`05b4c000 fffff880`05b64000 mpsdrv mpsdrv.sys Tue Jul 14 03:08:25 2009 (4A5BCC79) fffff880`05b64000 fffff880`05b91000 mrxsmb mrxsmb.sys Sat Feb 27 09:52:19 2010 (4B88CF33) fffff880`05b91000 fffff880`05bdf000 mrxsmb10 mrxsmb10.sys Sat Feb 27 09:52:28 2010 (4B88CF3C) fffff880`05e01000 fffff880`05ea7000 peauth peauth.sys Tue Jul 14 04:01:19 2009 (4A5BD8DF) fffff880`05ea7000 fffff880`05eb2000 secdrv secdrv.SYS Wed Sep 13 16:18:38 2006 (4508052E) fffff880`05eb2000 fffff880`05edf000 srvnet srvnet.sys Tue Jun 22 06:20:32 2010 (4C202C00) fffff880`05edf000 fffff880`05ef1000 tcpipreg tcpipreg.sys Tue Jul 14 03:09:49 2009 (4A5BCCCD) fffff880`05ef1000 fffff880`05f59000 srv2 srv2.sys Tue Jun 22 06:20:47 2010 (4C202C0F) fffff880`05f59000 fffff880`05fef000 srv srv.sys Tue Jun 22 06:21:11 2010 (4C202C27) fffff880`05fef000 fffff880`05fff000 MpNWMon MpNWMon.sys Sat Mar 20 07:58:00 2010 (4BA463E8) fffff880`08ca5000 fffff880`08cb0000 asyncmac asyncmac.sys Tue Jul 14 03:10:13 2009 (4A5BCCE5) fffff880`0fe00000 fffff880`0fe16000 AgileVpn AgileVpn.sys Tue Jul 14 03:10:24 2009 (4A5BCCF0) fffff880`0fe16000 fffff880`0fe3a000 rasl2tp rasl2tp.sys Tue Jul 14 03:10:11 2009 (4A5BCCE3) fffff880`0fe3a000 fffff880`0fe46000 ndistapi ndistapi.sys Tue Jul 14 03:10:00 2009 (4A5BCCD8) fffff880`0fe46000 fffff880`0fe75000 ndiswan ndiswan.sys Tue Jul 14 03:10:11 2009 (4A5BCCE3) fffff880`0fe75000 fffff880`0fe80000 rdpbus rdpbus.sys Tue Jul 14 03:17:46 2009 (4A5BCEAA) fffff880`0fe85000 fffff880`10b16e00 nvlddmkm nvlddmkm.sys Sat Jul 10 00:15:58 2010 (4C37918E) fffff880`10b17000 fffff880`10b18180 nvBridge nvBridge.kmd Sat Jul 10 00:07:54 2010 (4C378FAA) fffff880`10b19000 fffff880`10b6f000 Rt64win7 Rt64win7.sys Wed Jun 23 12:10:45 2010 (4C21CF95) fffff880`10b6f000 fffff880`10bb2000 ks ks.sys Thu Mar 04 06:32:25 2010 (4B8F37D9) fffff880`10bb2000 fffff880`10bf0000 1394ohci 1394ohci.sys Tue Jul 14 03:07:12 2009 (4A5BCC30) fffff880`10bf0000 fffff880`10c00000 CompositeBus CompositeBus.sys Tue Jul 14 03:00:33 2009 (4A5BCAA1) fffff960`00020000 fffff960`0032f000 win32k win32k.sys Sat Jun 19 07:31:59 2010 (4C1C483F) fffff960`00510000 fffff960`0051a000 TSDDD TSDDD.dll unavailable (00000000) fffff960`00630000 fffff960`00657000 cdd cdd.dll Wed May 19 22:48:26 2010 (4BF4408A) fffff960`00800000 fffff960`00861000 ATMFD ATMFD.DLL Thu May 27 07:11:31 2010 (4BFDF0F3) Unloaded modules: fffff880`08c34000 fffff880`08ca5000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01976000 fffff880`01984000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01984000 fffff880`01990000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01990000 fffff880`01999000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01999000 fffff880`019ac000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:\a\Minidump\D M P\100210-14617-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`02e03000 PsLoadedModuleList = 0xfffff800`03040e50 System Uptime: 0 days 5:14:11.097 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 4E, {99, c5828, 2, 1084e3} Probably caused by : memory_corruption ( nt!MiBadShareCount+4c ) Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PFN_LIST_CORRUPT (4e) Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc). If a kernel debugger is available get the stack trace. Arguments: Arg1: 0000000000000099, A PTE or PFN is corrupt Arg2: 00000000000c5828, page frame number Arg3: 0000000000000002, current page state Arg4: 00000000001084e3, 0 Debugging Details: ------------------ BUGCHECK_STR: 0x4E_99 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: MsMpEng.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002f0338c to fffff80002e73740 STACK_TEXT: fffff880`0669d998 fffff800`02f0338c : 00000000`0000004e 00000000`00000099 00000000`000c5828 00000000`00000002 : nt!KeBugCheckEx fffff880`0669d9a0 fffff800`02ed04d2 : 00000000`00000002 00000000`00000000 fffffa80`01265190 00000000`00000000 : nt!MiBadShareCount+0x4c fffff880`0669d9e0 fffff800`02f3429d : fffffa80`01265190 fffff880`0669db40 00000000`00000080 00000000`000a0418 : nt! ?? ::FNODOBFM::`string'+0x11aa2 fffff880`0669da40 fffff800`02e203a4 : fffff680`000195a8 fffff880`0669db40 00000000`00000000 ffffffff`ffffffff : nt!MiRemoveLowestPriorityStandbyPage+0x2ad fffff880`0669dac0 fffff800`02e7182e : 00000000`00000001 00000000`032b4640 00000000`00000001 fffffa80`064e9800 : nt! ?? ::FNODOBFM::`string'+0x43485 fffff880`0669dc20 00000000`683e1dbf : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`0b15e8f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x683e1dbf STACK_COMMAND: kb FOLLOWUP_IP: nt!MiBadShareCount+4c fffff800`02f0338c cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!MiBadShareCount+4c FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:\a\Minidump\D M P\100410-22089-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`02e09000 PsLoadedModuleList = 0xfffff800`03046e50 System Uptime: 0 days 3:54:55.595 Loading Kernel Symbols ............................................................... ................................................................ ....................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 101, {19, 0, fffff88002f64180, 2} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff88002f64180, The PRCB address of the hung processor. Arg4: 0000000000000002, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: explorer.exe CURRENT_IRQL: d STACK_TEXT: fffff880`0b4a9af8 fffff800`02e27453 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`02f64180 : nt!KeBugCheckEx fffff880`0b4a9b00 fffff800`02e81de7 : 00000000`00000000 fffff800`00000002 00000000`00002710 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4dfe fffff880`0b4a9b90 fffff800`033ef895 : fffff800`03414460 fffff880`0b4a9d40 fffff800`03414460 00000000`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`0b4a9c90 fffff800`02e75c33 : 00000000`3d901e94 fffff800`02ff3e80 fffff800`02ff3e80 00000000`00000001 : hal!HalpHpetClockInterrupt+0x8d fffff880`0b4a9cc0 fffff800`02e87608 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163 fffff880`0b4a9e50 fffff800`02e123f3 : 00000000`00000001 00000000`00000000 fffff880`03f1cc00 00000000`00000000 : nt!KeFlushMultipleRangeTb+0x258 fffff880`0b4a9f20 fffff800`02f80478 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x478da fffff880`0b4aa080 fffff800`02f80928 : 00000000`00000001 fffff800`02f80693 00000000`0a2ff29c 00000000`030115a1 : nt!MiPurgeSpecialPoolPaged+0x18 fffff880`0b4aa0b0 fffff800`02fac390 : 00000000`000000e0 00000000`34616c47 00000000`00040c20 fffff900`c966cf20 : nt!MmFreeSpecialPool+0x468 fffff880`0b4aa1f0 fffff960`001a4bb0 : fffff980`11adaf80 00000000`00000001 fffff900`c10ec280 fffff900`c627c630 : nt!ExDeferredFreePool+0xf4d fffff880`0b4aa2a0 fffff960`0016bf00 : fffff880`0b4aa328 00000000`030115a1 00000000`00000000 00000000`00000000 : win32k!FreeObject+0x40 fffff880`0b4aa2d0 fffff960`001a5ca5 : fffff880`0b4aa440 00000000`170115d6 00000000`00000001 fffff900`c000cf40 : win32k!RGNOBJ::vDeleteRGNOBJ+0x24 fffff880`0b4aa300 fffff960`002db6c9 : fffff880`0b4aa440 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!XDCOBJ::bCleanDC+0xfd fffff880`0b4aa3c0 fffff960`001a7466 : fffff880`0b4aa440 00000000`00000000 00000000`00000000 ffffffff`8f0513da : win32k!bDeleteDCInternalWorker+0x29 fffff880`0b4aa420 fffff960`00166690 : 00000000`170115d6 fffff880`0b4aa520 00000000`00000000 00000000`00000000 : win32k!bDeleteDCInternal+0x56 fffff880`0b4aa470 fffff800`02e78993 : fffffa80`049f95a0 fffff880`0b4aa520 00000000`0185000f 00000000`00000000 : win32k!NtGdiDeleteObjectApp+0x120 fffff880`0b4aa4a0 000007fe`fead118a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0a2fe988 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fead118a STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_VRF_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_VRF_ANALYSIS_INCONCLUSIVE Followup: MachineOwner ---------
Thank you for your reply! I really appreciate the help . My results are below:
- I have uninstalled nTune, so nvoclk64.sys is now gone
- I have updated the NEC USB controller, so nusb3xhc.sys has been updated
- I have uninstalled Adobe Photoshop, but it did not remove adfs.SYS... Can I just delete it from my driver folder?
- The same goes for Asus PC Probe, uninstalled, but it did not remove AsIO.sys
- I've tried updating p17.sys but it is already as far up to date as possible. I have the newest Creative drivers...
So how do I go about deleting those two drivers? And that audio driver, I guess I've got no chance there, right?
As for the Memtest: as stated, I have run it for 12 hours without errors. And the Driver Verifier caught one BSOD, which is that CLOCK_WATCHDOG_TIMEOUT, I think. But analysis inconclusive?
(new JCGriff attached)
- I have uninstalled nTune, so nvoclk64.sys is now gone
- I have updated the NEC USB controller, so nusb3xhc.sys has been updated
- I have uninstalled Adobe Photoshop, but it did not remove adfs.SYS... Can I just delete it from my driver folder?
- The same goes for Asus PC Probe, uninstalled, but it did not remove AsIO.sys
- I've tried updating p17.sys but it is already as far up to date as possible. I have the newest Creative drivers...
So how do I go about deleting those two drivers? And that audio driver, I guess I've got no chance there, right?
As for the Memtest: as stated, I have run it for 12 hours without errors. And the Driver Verifier caught one BSOD, which is that CLOCK_WATCHDOG_TIMEOUT, I think. But analysis inconclusive?
(new JCGriff attached)
The latest crash dump I found in your new attachment is 100710-16910-01, I already did this one (see my post above).
You can delete adfs.SYS if you uninstalled Adobe completely. Do not touch AsIO.sys though, as I'm not sure it was used by ASUS Probe only - AsIO ASUS Input/Output, could be used by something else too.
You can delete adfs.SYS if you uninstalled Adobe completely. Do not touch AsIO.sys though, as I'm not sure it was used by ASUS Probe only - AsIO ASUS Input/Output, could be used by something else too.
I just made that attachment to have you confirm that the drivers are gone/updated .
So I can just delete it as I would any normal file?
So I can just delete it as I would any normal file?
I just made that attachment to have you confirm that the drivers are gone/updated .
So I can just delete it as I would any normal file?
So I can just delete it as I would any normal file?
I renamed it to .old, and let the AsIO.sys be. I'll report back if I get another BSOD.
How about that amdxata.sys? I don't have an AMD videocard anymore, but my motherboard does have AMD Crossfire support, could it be part of that?
How about that amdxata.sys? I don't have an AMD videocard anymore, but my motherboard does have AMD Crossfire support, could it be part of that?
So far I haven't seen amdxata.sys any newer than yours, don't worry about it. : )
Cool. Well, let's hope the BSODs are gone now. *crosses his fingers*
Logically, the nTune could explain it. Before this videocard I had no problems (read: a lot of problems, but with the stupid ATI card). Then I got the nVidia and installed nTune. And nTune was indeed in my start-up items. So I hope it was the cause of the problems. We'll see .
Thanks again for the help. Will post back in a few days to let you know how it's going.
Logically, the nTune could explain it. Before this videocard I had no problems (read: a lot of problems, but with the stupid ATI card). Then I got the nVidia and installed nTune. And nTune was indeed in my start-up items. So I hope it was the cause of the problems. We'll see .
Thanks again for the help. Will post back in a few days to let you know how it's going.
Let's hope. Your nTunes is a bit outdated, there should be an update for it:
nvoclk64.sys Mon Aug 18 19:00:01 2008
nvoclk64.sys Mon Aug 18 19:00:01 2008
Ntfs... sounds like hard-disk trouble. But I did a run with the WD tool and it didn't find any errors. Maybe Windows got corrupted?
I'm getting so weary of this . What should I do now? I have half a mind to take out the audio card and see if that helps. Or just do a clean install of Windows...
Mini-dump attached.
Error code 50, PAGE_FAULT_IN_NONPAGED_AREA. Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.
The dump blames memory corruption which can be caused by any of the above.
Try updating this driver:
I don't think your problem is with your Win 7 OS; I think it is a hardware/hardware related problem (driver). Update the driver above and reboot. Then follow cybercore's advice in the post below.
The dump blames memory corruption which can be caused by any of the above.
Code:
Kernel base = 0xfffff800`02e55000 PsLoadedModuleList = 0xfffff800`03092e50 Debug session time: Mon Oct 11 06:38:00.750 2010 (GMT-4) System Uptime: 0 days 3:03:39.717 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff7ff92e7218c, 8, fffff7ff92e7218c, 5} Could not read faulting driver name Probably caused by : memory_corruption Followup: memory_corruption --------- 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffff7ff92e7218c, memory referenced. Arg2: 0000000000000008, value 0 = read operation, 1 = write operation. Arg3: fffff7ff92e7218c, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000005, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fd0e0 fffff7ff92e7218c FAULTING_IP: +5ad5952f0057dcac fffff7ff`92e7218c ?? ??? MM_INTERNAL_CODE: 5 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x50 PROCESS_NAME: msiexec.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff88009b82f00 -- (.trap 0xfffff88009b82f00) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000018 rsi=0000000000000000 rdi=0000000000000000 rip=fffff7ff92e7218c rsp=fffff88009b83090 rbp=fffff88009b83100 r8=fffff88009b83160 r9=fffff6fb40000000 r10=fffff68000000000 r11=fffff6fb40000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc fffff7ff`92e7218c ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002f448c1 to fffff80002ec5740 STACK_TEXT: fffff880`09b82d98 fffff800`02f448c1 : 00000000`00000050 fffff7ff`92e7218c 00000000`00000008 fffff880`09b82f00 : nt!KeBugCheckEx fffff880`09b82da0 fffff800`02ec382e : 00000000`00000008 00000000`00000000 00000980`00000000 0000007f`fffffff8 : nt! ?? ::FNODOBFM::`string'+0x40e8b fffff880`09b82f00 fffff7ff`92e7218c : 00000000`00000000 00000000`00000000 00000000`215fc01e fffffa80`064970e0 : nt!KiPageFault+0x16e fffff880`09b83090 00000000`00000000 : 00000000`00000000 00000000`215fc01e fffffa80`064970e0 00000001`00000000 : 0xfffff7ff`92e7218c STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt 16 errors : !nt (fffff80002ec5100-fffff80002ec51b8) fffff80002ec5100 *da 89 4d 80 48 89 45 88 *eb 81 ec 38 01 00 00 0f ..M.H.E....8.... fffff80002ec5110 *8b 74 24 30 0f 29 7c 24 *67 44 0f 29 44 24 50 44 .t$0.)|$gD.)D$PD fffff80002ec5120 *86 29 4c 24 60 44 0f 29 *5b 24 70 44 0f 29 9c 24 .)L$`D.)[$pD.).$ fffff80002ec5130 *15 00 00 00 44 0f 29 a4 *95 90 00 00 00 44 0f 29 ....D.)......D.) ... fffff80002ec5180 *59 89 b4 24 10 01 00 00 *3a 89 9c 24 00 01 00 00 Y..$....:..$.... fffff80002ec5190 *c0 83 ec 70 65 48 8b 0c *df 88 01 00 00 48 8b 49 ...peH.......H.I fffff80002ec51a0 *69 48 8d 49 50 48 89 4c *65 40 0f ae 01 48 8d 85 iH.IPH.Le@...H.. fffff80002ec51b0 *4c 01 00 00 48 89 44 24 *88 48 2b c4 48 89 44 24 L...H.D$.H+.H.D$ MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: STRIDE FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE Followup: memory_corruption --------- 6: kd> lmtsmn start end module name fffff880`0fe00000 fffff880`0fe3e000 1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30) fffff880`00f68000 fffff880`00fbf000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`02c32000 fffff880`02cbc000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`0fe4e000 fffff880`0fe64000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0) fffff880`0112f000 fffff880`0113a000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`0443d000 fffff880`04445000 ASACPI ASACPI.sys Wed Jul 15 23:31:29 2009 (4A5E9F11) fffff880`03d4b000 fffff880`03d51000 AsIO AsIO.sys Mon Aug 03 03:03:16 2009 (4A768BB4) fffff880`07147000 fffff880`07152000 asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5) fffff880`00e9b000 fffff880`00ea4000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00fd2000 fffff880`00ffc000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118) fffff960`008d0000 fffff960`00931000 ATMFD ATMFD.DLL Thu May 27 00:11:31 2010 (4BFDF0F3) fffff880`014b6000 fffff880`014bd000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`03d3a000 fffff880`03d4b000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`06cda000 fffff880`06cf8000 bowser bowser.sys Mon Jul 13 19:23:50 2009 (4A5BC206) fffff960`00760000 fffff960`00787000 cdd cdd.dll unavailable (00000000) fffff880`015d2000 fffff880`015fc000 cdrom cdrom.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`00c00000 fffff880`00cc0000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D) fffff880`01450000 fffff880`01480000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00d26000 fffff880`00d84000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`014be000 fffff880`01531000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`0fe3e000 fffff880`0fe4e000 CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`06dae000 fffff880`06db7000 cpuz134_x64 cpuz134_x64.sys Fri Jul 09 07:16:58 2010 (4C37052A) fffff880`02c00000 fffff880`02c0e000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`03c99000 fffff880`03d1c000 csc csc.sys Mon Jul 13 19:24:26 2009 (4A5BC22A) fffff880`03d1c000 fffff880`03d3a000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200) fffff880`02dd6000 fffff880`02de5000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`0143a000 fffff880`01450000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`045d5000 fffff880`045f7000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5) fffff880`03df7000 fffff880`03e00000 dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`02c0e000 fffff880`02c1a000 dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`02c1a000 fffff880`02c2d000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`01480000 fffff880`0148c000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574) fffff880`04232000 fffff880`04326000 dxgkrnl dxgkrnl.sys Thu Oct 01 21:00:14 2009 (4AC5509E) fffff880`04326000 fffff880`0436c000 dxgmms1 dxgmms1.sys Mon Jul 13 19:38:32 2009 (4A5BC578) fffff880`01186000 fffff880`0119a000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`0113a000 fffff880`01186000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`01542000 fffff880`0154c000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`01400000 fffff880`0143a000 fvevol fvevol.sys Fri Sep 25 22:34:26 2009 (4ABD7DB2) fffff880`017b6000 fffff880`01800000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164) fffff880`04445000 fffff880`04452000 GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0) fffff800`02e0c000 fffff800`02e55000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`0436c000 fffff880`04390000 HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5) fffff880`0149a000 fffff880`014b3000 HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD) fffff880`01ec3000 fffff880`01ecb080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9) fffff880`0148c000 fffff880`0149a000 hidusb hidusb.sys Mon Jul 13 20:06:22 2009 (4A5BCBFE) fffff880`06c12000 fffff880`06cda000 HTTP HTTP.sys Mon Jul 13 19:22:16 2009 (4A5BC1A8) fffff880`0162a000 fffff880`01633000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff880`03d77000 fffff880`03d8d000 intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`10bec000 fffff880`10bfb000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`01ef6000 fffff880`01f04000 kbdhid kbdhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff800`00bc2000 fffff800`00bcc000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`10ba9000 fffff880`10bec000 ks ks.sys Wed Mar 03 23:32:25 2010 (4B8F37D9) fffff880`01200000 fffff880`0121a000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156) fffff880`0178b000 fffff880`017b6000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4) fffff880`045f7000 fffff880`045fc200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93) fffff880`01f56000 fffff880`01f6b000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`01f12000 fffff880`01f35000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295) fffff880`00cce000 fffff880`00d12000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66) fffff880`01f04000 fffff880`01f12000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C) fffff880`03c00000 fffff880`03c0f000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`01ecc000 fffff880`01ed9000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`00e81000 fffff880`00e9b000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`0121a000 fffff880`01247000 MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0) fffff880`070c6000 fffff880`070d6000 MpNWMon MpNWMon.sys Sat Mar 20 01:58:00 2010 (4BA463E8) fffff880`06cf8000 fffff880`06d10000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79) fffff880`06d10000 fffff880`06d3d000 mrxsmb mrxsmb.sys Sat Feb 27 02:52:19 2010 (4B88CF33) fffff880`06d3d000 fffff880`06d8b000 mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C) fffff880`06d8b000 fffff880`06dae000 mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A) fffff880`0105e000 fffff880`01069000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00fc8000 fffff880`00fd2000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`0119a000 fffff880`011f8000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C) fffff880`02dcb000 fffff880`02dd6000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`01618000 fffff880`0162a000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`0106c000 fffff880`010f8000 mv91xx mv91xx.sys Wed Jun 30 21:55:14 2010 (4C2BF582) fffff880`01127000 fffff880`0112f000 mvxxmm mvxxmm.sys Wed Jun 30 21:54:57 2010 (4C2BF571) fffff880`01639000 fffff880`0172b000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`0fe88000 fffff880`0fe94000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8) fffff880`03d8d000 fffff880`03dbc000 ndiswan ndiswan.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`02de5000 fffff880`02dfa000 NDProxy NDProxy.SYS Mon Jul 13 20:10:05 2009 (4A5BCCDD) fffff880`02d30000 fffff880`02d3f000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`02cbc000 fffff880`02d01000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178) fffff880`0172b000 fffff880`0178b000 NETIO NETIO.SYS Mon Jul 13 19:21:46 2009 (4A5BC18A) fffff880`00ea4000 fffff880`00eb5000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`02dbf000 fffff880`02dcb000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`02e55000 fffff800`03431000 nt ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9) fffff880`0124c000 fffff880`013ef000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F) fffff880`013ef000 fffff880`013f8000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109) fffff880`03c7b000 fffff880`03c93000 nusb3hub nusb3hub.sys Thu Jan 21 22:22:18 2010 (4B5919EA) fffff880`04200000 fffff880`04230000 nusb3xhc nusb3xhc.sys Thu Jan 21 22:22:21 2010 (4B5919ED) fffff880`10b51000 fffff880`10b52180 nvBridge nvBridge.kmd Fri Jul 09 17:07:54 2010 (4C378FAA) fffff880`0febf000 fffff880`10b50e00 nvlddmkm nvlddmkm.sys Fri Jul 09 17:15:58 2010 (4C37918E) fffff880`04456000 fffff880`045d5000 P17 P17.sys Tue Apr 21 02:12:47 2009 (49ED63DF) fffff880`02d0a000 fffff880`02d30000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5) fffff880`00e40000 fffff880`00e55000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00e00000 fffff880`00e33000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`00e6a000 fffff880`00e71000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115) fffff880`00e71000 fffff880`00e81000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`01531000 fffff880`01542000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`01e00000 fffff880`01ea6000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF) fffff880`04400000 fffff880`0443d000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00d12000 fffff880`00d26000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`0fe64000 fffff880`0fe88000 rasl2tp rasl2tp.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`0fe94000 fffff880`0feaf000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9) fffff880`03dbc000 fffff880`03ddd000 raspptp raspptp.sys Mon Jul 13 20:10:18 2009 (4A5BCCEA) fffff880`03ddd000 fffff880`03df7000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1) fffff880`02d6e000 fffff880`02dbf000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219) fffff880`0feaf000 fffff880`0feba000 rdpbus rdpbus.sys Mon Jul 13 20:17:46 2009 (4A5BCEAA) fffff880`01043000 fffff880`0104c000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`0104c000 fffff880`01055000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`01055000 fffff880`0105e000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`01598000 fffff880`015d2000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A) fffff880`01f6b000 fffff880`01f83000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`10b53000 fffff880`10ba9000 Rt64win7 Rt64win7.sys Wed Jun 23 05:10:45 2010 (4C21CF95) fffff880`010f8000 fffff880`01127000 SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0) fffff880`06db7000 fffff880`06dc2000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E) fffff880`01610000 fffff880`01618000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`07030000 fffff880`070c6000 srv srv.sys Mon Jun 21 23:21:11 2010 (4C202C27) fffff880`01f83000 fffff880`01feb000 srv2 srv2.sys Mon Jun 21 23:20:47 2010 (4C202C0F) fffff880`06dc2000 fffff880`06def000 srvnet srvnet.sys Mon Jun 21 23:20:32 2010 (4C202C00) fffff880`04452000 fffff880`04453480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92) fffff880`01803000 fffff880`01a00000 tcpip tcpip.sys Sun Jun 13 23:39:04 2010 (4C15A458) fffff880`06c00000 fffff880`06c12000 tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD) fffff880`00cc0000 fffff880`00ccd000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E) fffff880`00de0000 fffff880`00dfe000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B) fffff880`02d5a000 fffff880`02d6e000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64) fffff960`004e0000 fffff960`004ea000 TSDDD TSDDD.dll Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`03d51000 fffff880`03d77000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1) fffff880`03c0f000 fffff880`03c21000 umbus umbus.sys Mon Jul 13 20:06:56 2009 (4A5BCC20) fffff880`01ed9000 fffff880`01ef6000 usbccgp usbccgp.sys Mon Jul 13 20:06:45 2009 (4A5BCC15) fffff880`04230000 fffff880`04231f00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF) fffff880`04390000 fffff880`043a1000 usbehci usbehci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`03c21000 fffff880`03c7b000 usbhub usbhub.sys Mon Jul 13 20:07:09 2009 (4A5BCC2D) fffff880`043a1000 fffff880`043f7000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07) fffff880`00e33000 fffff880`00e40000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`01000000 fffff880`0100e000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`0100e000 fffff880`01033000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`01600000 fffff880`01610000 vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E) fffff880`00e55000 fffff880`00e6a000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00d84000 fffff880`00de0000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141) fffff880`0154c000 fffff880`01598000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128) fffff880`02d3f000 fffff880`02d5a000 wanarp wanarp.sys Mon Jul 13 20:10:21 2009 (4A5BCCED) fffff880`01033000 fffff880`01043000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00eb5000 fffff880`00f59000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00f59000 fffff880`00f68000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`02d01000 fffff880`02d0a000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff960`00020000 fffff960`0032f000 win32k win32k.sys Sat Jun 19 00:31:59 2010 (4C1C483F) fffff880`043f7000 fffff880`04400000 wmiacpi wmiacpi.sys Mon Jul 13 19:31:02 2009 (4A5BC3B6) fffff880`00fbf000 fffff880`00fc8000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`01f35000 fffff880`01f56000 WudfPf WudfPf.sys Mon Jul 13 20:05:37 2009 (4A5BCBD1) Unloaded modules: fffff880`07152000 fffff880`0716d000 USBSTOR.SYS Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`070d6000 fffff880`07147000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01480000 fffff880`0148e000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0148e000 fffff880`0149a000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0149a000 fffff880`014a3000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`014a3000 fffff880`014b6000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000
Quote:
P17.sys Tue Apr 21 02:12:47 2009 - WDM Audio Miniport belongs to the software Creative SB Audigy LS or SB Live! 24-bit by Creative Technology Ltd.Creative Worldwide Support
101110-17191-01.dmp
BugCheck 50, {fffff7ff92e7218c, 8, fffff7ff92e7218c, 5}
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced
Could not read faulting driver name
X64_MEMORY_CORRUPTION_STRIDE
Probably caused by : memory_corruption
You have updated all you could. Next:
1) run memtest.org overnight RAM - Test with Memtest86+
2) enable driver verifier Driver Verifier - Enable and Disable
BugCheck 50, {fffff7ff92e7218c, 8, fffff7ff92e7218c, 5}
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced
Could not read faulting driver name
X64_MEMORY_CORRUPTION_STRIDE
Probably caused by : memory_corruption
You have updated all you could. Next:
1) run memtest.org overnight RAM - Test with Memtest86+
2) enable driver verifier Driver Verifier - Enable and Disable
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:\a\Minidump\D M P\101110-17191-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`02e55000 PsLoadedModuleList = 0xfffff800`03092e50 Debug session time: Mon Oct 11 13:38:00.750 2010 (GMT-5) System Uptime: 0 days 3:03:39.717 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff7ff92e7218c, 8, fffff7ff92e7218c, 5} Could not read faulting driver name Probably caused by : memory_corruption Followup: memory_corruption --------- 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffff7ff92e7218c, memory referenced. Arg2: 0000000000000008, value 0 = read operation, 1 = write operation. Arg3: fffff7ff92e7218c, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000005, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fd0e0 fffff7ff92e7218c FAULTING_IP: +0 fffff7ff`92e7218c ?? ??? MM_INTERNAL_CODE: 5 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x50 PROCESS_NAME: msiexec.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff88009b82f00 -- (.trap 0xfffff88009b82f00) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000018 rsi=0000000000000000 rdi=0000000000000000 rip=fffff7ff92e7218c rsp=fffff88009b83090 rbp=fffff88009b83100 r8=fffff88009b83160 r9=fffff6fb40000000 r10=fffff68000000000 r11=fffff6fb40000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc fffff7ff`92e7218c ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002f448c1 to fffff80002ec5740 STACK_TEXT: fffff880`09b82d98 fffff800`02f448c1 : 00000000`00000050 fffff7ff`92e7218c 00000000`00000008 fffff880`09b82f00 : nt!KeBugCheckEx fffff880`09b82da0 fffff800`02ec382e : 00000000`00000008 00000000`00000000 00000980`00000000 0000007f`fffffff8 : nt! ?? ::FNODOBFM::`string'+0x40e8b fffff880`09b82f00 fffff7ff`92e7218c : 00000000`00000000 00000000`00000000 00000000`215fc01e fffffa80`064970e0 : nt!KiPageFault+0x16e fffff880`09b83090 00000000`00000000 : 00000000`00000000 00000000`215fc01e fffffa80`064970e0 00000001`00000000 : 0xfffff7ff`92e7218c STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt 16 errors : !nt (fffff80002ec5100-fffff80002ec51b8) fffff80002ec5100 *da 89 4d 80 48 89 45 88 *eb 81 ec 38 01 00 00 0f ..M.H.E....8.... fffff80002ec5110 *8b 74 24 30 0f 29 7c 24 *67 44 0f 29 44 24 50 44 .t$0.)|$gD.)D$PD fffff80002ec5120 *86 29 4c 24 60 44 0f 29 *5b 24 70 44 0f 29 9c 24 .)L$`D.)[$pD.).$ fffff80002ec5130 *15 00 00 00 44 0f 29 a4 *95 90 00 00 00 44 0f 29 ....D.)......D.) ... fffff80002ec5180 *59 89 b4 24 10 01 00 00 *3a 89 9c 24 00 01 00 00 Y..$....:..$.... fffff80002ec5190 *c0 83 ec 70 65 48 8b 0c *df 88 01 00 00 48 8b 49 ...peH.......H.I fffff80002ec51a0 *69 48 8d 49 50 48 89 4c *65 40 0f ae 01 48 8d 85 iH.IPH.Le@...H.. fffff80002ec51b0 *4c 01 00 00 48 89 44 24 *88 48 2b c4 48 89 44 24 L...H.D$.H+.H.D$ MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: STRIDE FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE Followup: memory_corruption --------- 6: kd> lmtn start end module name fffff800`00bc2000 fffff800`00bcc000 kdcom kdcom.dll Tue Jul 14 04:31:07 2009 (4A5BDFDB) fffff800`02e0c000 fffff800`02e55000 hal hal.dll Tue Jul 14 04:27:36 2009 (4A5BDF08) fffff800`02e55000 fffff800`03431000 nt ntkrnlmp.exe Sat Jun 19 07:16:41 2010 (4C1C44A9) fffff880`00c00000 fffff880`00cc0000 CI CI.dll Tue Jul 14 04:32:13 2009 (4A5BE01D) fffff880`00cc0000 fffff880`00ccd000 TDI TDI.SYS Tue Jul 14 02:21:18 2009 (4A5BC16E) fffff880`00cce000 fffff880`00d12000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 04:29:10 2009 (4A5BDF66) fffff880`00d12000 fffff880`00d26000 PSHED PSHED.dll Tue Jul 14 04:32:23 2009 (4A5BE027) fffff880`00d26000 fffff880`00d84000 CLFS CLFS.SYS Tue Jul 14 02:19:57 2009 (4A5BC11D) fffff880`00d84000 fffff880`00de0000 volmgrx volmgrx.sys Tue Jul 14 02:20:33 2009 (4A5BC141) fffff880`00de0000 fffff880`00dfe000 tdx tdx.sys Tue Jul 14 02:21:15 2009 (4A5BC16B) fffff880`00e00000 fffff880`00e33000 pci pci.sys Tue Jul 14 02:19:51 2009 (4A5BC117) fffff880`00e33000 fffff880`00e40000 vdrvroot vdrvroot.sys Tue Jul 14 03:01:31 2009 (4A5BCADB) fffff880`00e40000 fffff880`00e55000 partmgr partmgr.sys Tue Jul 14 02:19:58 2009 (4A5BC11E) fffff880`00e55000 fffff880`00e6a000 volmgr volmgr.sys Tue Jul 14 02:19:57 2009 (4A5BC11D) fffff880`00e6a000 fffff880`00e71000 pciide pciide.sys Tue Jul 14 02:19:49 2009 (4A5BC115) fffff880`00e71000 fffff880`00e81000 PCIIDEX PCIIDEX.SYS Tue Jul 14 02:19:48 2009 (4A5BC114) fffff880`00e81000 fffff880`00e9b000 mountmgr mountmgr.sys Tue Jul 14 02:19:54 2009 (4A5BC11A) fffff880`00e9b000 fffff880`00ea4000 atapi atapi.sys Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`00ea4000 fffff880`00eb5000 Npfs Npfs.SYS Tue Jul 14 02:19:48 2009 (4A5BC114) fffff880`00eb5000 fffff880`00f59000 Wdf01000 Wdf01000.sys Tue Jul 14 02:22:07 2009 (4A5BC19F) fffff880`00f59000 fffff880`00f68000 WDFLDR WDFLDR.SYS Tue Jul 14 02:19:54 2009 (4A5BC11A) fffff880`00f68000 fffff880`00fbf000 ACPI ACPI.sys Tue Jul 14 02:19:34 2009 (4A5BC106) fffff880`00fbf000 fffff880`00fc8000 WMILIB WMILIB.SYS Tue Jul 14 02:19:51 2009 (4A5BC117) fffff880`00fc8000 fffff880`00fd2000 msisadrv msisadrv.sys Tue Jul 14 02:19:26 2009 (4A5BC0FE) fffff880`00fd2000 fffff880`00ffc000 ataport ataport.SYS Tue Jul 14 02:19:52 2009 (4A5BC118) fffff880`01000000 fffff880`0100e000 vga vga.sys Tue Jul 14 02:38:47 2009 (4A5BC587) fffff880`0100e000 fffff880`01033000 VIDEOPRT VIDEOPRT.SYS Tue Jul 14 02:38:51 2009 (4A5BC58B) fffff880`01033000 fffff880`01043000 watchdog watchdog.sys Tue Jul 14 02:37:35 2009 (4A5BC53F) fffff880`01043000 fffff880`0104c000 RDPCDD RDPCDD.sys Tue Jul 14 03:16:34 2009 (4A5BCE62) fffff880`0104c000 fffff880`01055000 rdpencdd rdpencdd.sys Tue Jul 14 03:16:34 2009 (4A5BCE62) fffff880`01055000 fffff880`0105e000 rdprefmp rdprefmp.sys Tue Jul 14 03:16:35 2009 (4A5BCE63) fffff880`0105e000 fffff880`01069000 Msfs Msfs.SYS Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`0106c000 fffff880`010f8000 mv91xx mv91xx.sys Thu Jul 01 04:55:14 2010 (4C2BF582) fffff880`010f8000 fffff880`01127000 SCSIPORT SCSIPORT.SYS Tue Jul 14 03:01:04 2009 (4A5BCAC0) fffff880`01127000 fffff880`0112f000 mvxxmm mvxxmm.sys Thu Jul 01 04:54:57 2010 (4C2BF571) fffff880`0112f000 fffff880`0113a000 amdxata amdxata.sys Tue May 19 20:56:59 2009 (4A12F2EB) fffff880`0113a000 fffff880`01186000 fltmgr fltmgr.sys Tue Jul 14 02:19:59 2009 (4A5BC11F) fffff880`01186000 fffff880`0119a000 fileinfo fileinfo.sys Tue Jul 14 02:34:25 2009 (4A5BC481) fffff880`0119a000 fffff880`011f8000 msrpc msrpc.sys Tue Jul 14 02:21:32 2009 (4A5BC17C) fffff880`01200000 fffff880`0121a000 ksecdd ksecdd.sys Tue Jul 14 02:20:54 2009 (4A5BC156) fffff880`0121a000 fffff880`01247000 MpFilter MpFilter.sys Sat Mar 20 07:58:08 2010 (4BA463F0) fffff880`0124c000 fffff880`013ef000 Ntfs Ntfs.sys Tue Jul 14 02:20:47 2009 (4A5BC14F) fffff880`013ef000 fffff880`013f8000 Null Null.SYS Tue Jul 14 02:19:37 2009 (4A5BC109) fffff880`01400000 fffff880`0143a000 fvevol fvevol.sys Sat Sep 26 05:34:26 2009 (4ABD7DB2) fffff880`0143a000 fffff880`01450000 disk disk.sys Tue Jul 14 02:19:57 2009 (4A5BC11D) fffff880`01450000 fffff880`01480000 CLASSPNP CLASSPNP.SYS Tue Jul 14 02:19:58 2009 (4A5BC11E) fffff880`01480000 fffff880`0148c000 Dxapi Dxapi.sys Tue Jul 14 02:38:28 2009 (4A5BC574) fffff880`0148c000 fffff880`0149a000 hidusb hidusb.sys Tue Jul 14 03:06:22 2009 (4A5BCBFE) fffff880`0149a000 fffff880`014b3000 HIDCLASS HIDCLASS.SYS Tue Jul 14 03:06:21 2009 (4A5BCBFD) fffff880`014b6000 fffff880`014bd000 Beep Beep.SYS Tue Jul 14 03:00:13 2009 (4A5BCA8D) fffff880`014be000 fffff880`01531000 cng cng.sys Tue Jul 14 02:49:40 2009 (4A5BC814) fffff880`01531000 fffff880`01542000 pcw pcw.sys Tue Jul 14 02:19:27 2009 (4A5BC0FF) fffff880`01542000 fffff880`0154c000 Fs_Rec Fs_Rec.sys Tue Jul 14 02:19:45 2009 (4A5BC111) fffff880`0154c000 fffff880`01598000 volsnap volsnap.sys Tue Jul 14 02:20:08 2009 (4A5BC128) fffff880`01598000 fffff880`015d2000 rdyboost rdyboost.sys Tue Jul 14 02:34:34 2009 (4A5BC48A) fffff880`015d2000 fffff880`015fc000 cdrom cdrom.sys Tue Jul 14 02:19:54 2009 (4A5BC11A) fffff880`01600000 fffff880`01610000 vmstorfl vmstorfl.sys Tue Jul 14 02:42:54 2009 (4A5BC67E) fffff880`01610000 fffff880`01618000 spldr spldr.sys Mon May 11 19:56:27 2009 (4A0858BB) fffff880`01618000 fffff880`0162a000 mup mup.sys Tue Jul 14 02:23:45 2009 (4A5BC201) fffff880`0162a000 fffff880`01633000 hwpolicy hwpolicy.sys Tue Jul 14 02:19:22 2009 (4A5BC0FA) fffff880`01639000 fffff880`0172b000 ndis ndis.sys Tue Jul 14 02:21:40 2009 (4A5BC184) fffff880`0172b000 fffff880`0178b000 NETIO NETIO.SYS Tue Jul 14 02:21:46 2009 (4A5BC18A) fffff880`0178b000 fffff880`017b6000 ksecpkg ksecpkg.sys Fri Dec 11 08:03:32 2009 (4B21E0B4) fffff880`017b6000 fffff880`01800000 fwpkclnt fwpkclnt.sys Tue Jul 14 02:21:08 2009 (4A5BC164) fffff880`01803000 fffff880`01a00000 tcpip tcpip.sys Mon Jun 14 06:39:04 2010 (4C15A458) fffff880`01e00000 fffff880`01ea6000 peauth peauth.sys Tue Jul 14 04:01:19 2009 (4A5BD8DF) fffff880`01ec3000 fffff880`01ecb080 HIDPARSE HIDPARSE.SYS Tue Jul 14 03:06:17 2009 (4A5BCBF9) fffff880`01ecc000 fffff880`01ed9000 mouhid mouhid.sys Tue Jul 14 03:00:20 2009 (4A5BCA94) fffff880`01ed9000 fffff880`01ef6000 usbccgp usbccgp.sys Tue Jul 14 03:06:45 2009 (4A5BCC15) fffff880`01ef6000 fffff880`01f04000 kbdhid kbdhid.sys Tue Jul 14 03:00:20 2009 (4A5BCA94) fffff880`01f04000 fffff880`01f12000 monitor monitor.sys Tue Jul 14 02:38:52 2009 (4A5BC58C) fffff880`01f12000 fffff880`01f35000 luafv luafv.sys Tue Jul 14 02:26:13 2009 (4A5BC295) fffff880`01f35000 fffff880`01f56000 WudfPf WudfPf.sys Tue Jul 14 03:05:37 2009 (4A5BCBD1) fffff880`01f56000 fffff880`01f6b000 lltdio lltdio.sys Tue Jul 14 03:08:50 2009 (4A5BCC92) fffff880`01f6b000 fffff880`01f83000 rspndr rspndr.sys Tue Jul 14 03:08:50 2009 (4A5BCC92) fffff880`01f83000 fffff880`01feb000 srv2 srv2.sys Tue Jun 22 06:20:47 2010 (4C202C0F) fffff880`02c00000 fffff880`02c0e000 crashdmp crashdmp.sys Tue Jul 14 03:01:01 2009 (4A5BCABD) fffff880`02c0e000 fffff880`02c1a000 dump_dumpata dump_dumpata.sys Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`02c1a000 fffff880`02c2d000 dump_dumpfve dump_dumpfve.sys Tue Jul 14 02:21:51 2009 (4A5BC18F) fffff880`02c32000 fffff880`02cbc000 afd afd.sys Tue Jul 14 02:21:40 2009 (4A5BC184) fffff880`02cbc000 fffff880`02d01000 netbt netbt.sys Tue Jul 14 02:21:28 2009 (4A5BC178) fffff880`02d01000 fffff880`02d0a000 wfplwf wfplwf.sys Tue Jul 14 03:09:26 2009 (4A5BCCB6) fffff880`02d0a000 fffff880`02d30000 pacer pacer.sys Tue Jul 14 03:09:41 2009 (4A5BCCC5) fffff880`02d30000 fffff880`02d3f000 netbios netbios.sys Tue Jul 14 03:09:26 2009 (4A5BCCB6) fffff880`02d3f000 fffff880`02d5a000 wanarp wanarp.sys Tue Jul 14 03:10:21 2009 (4A5BCCED) fffff880`02d5a000 fffff880`02d6e000 termdd termdd.sys Tue Jul 14 03:16:36 2009 (4A5BCE64) fffff880`02d6e000 fffff880`02dbf000 rdbss rdbss.sys Tue Jul 14 02:24:09 2009 (4A5BC219) fffff880`02dbf000 fffff880`02dcb000 nsiproxy nsiproxy.sys Tue Jul 14 02:21:02 2009 (4A5BC15E) fffff880`02dcb000 fffff880`02dd6000 mssmbios mssmbios.sys Tue Jul 14 02:31:10 2009 (4A5BC3BE) fffff880`02dd6000 fffff880`02de5000 discache discache.sys Tue Jul 14 02:37:18 2009 (4A5BC52E) fffff880`02de5000 fffff880`02dfa000 NDProxy NDProxy.SYS Tue Jul 14 03:10:05 2009 (4A5BCCDD) fffff880`03c00000 fffff880`03c0f000 mouclass mouclass.sys Tue Jul 14 02:19:50 2009 (4A5BC116) fffff880`03c0f000 fffff880`03c21000 umbus umbus.sys Tue Jul 14 03:06:56 2009 (4A5BCC20) fffff880`03c21000 fffff880`03c7b000 usbhub usbhub.sys Tue Jul 14 03:07:09 2009 (4A5BCC2D) fffff880`03c7b000 fffff880`03c93000 nusb3hub nusb3hub.sys Fri Jan 22 05:22:18 2010 (4B5919EA) fffff880`03c99000 fffff880`03d1c000 csc csc.sys Tue Jul 14 02:24:26 2009 (4A5BC22A) fffff880`03d1c000 fffff880`03d3a000 dfsc dfsc.sys Tue Jul 14 02:23:44 2009 (4A5BC200) fffff880`03d3a000 fffff880`03d4b000 blbdrive blbdrive.sys Tue Jul 14 02:35:59 2009 (4A5BC4DF) fffff880`03d4b000 fffff880`03d51000 AsIO AsIO.sys Mon Aug 03 10:03:16 2009 (4A768BB4) fffff880`03d51000 fffff880`03d77000 tunnel tunnel.sys Tue Jul 14 03:09:37 2009 (4A5BCCC1) fffff880`03d77000 fffff880`03d8d000 intelppm intelppm.sys Tue Jul 14 02:19:25 2009 (4A5BC0FD) fffff880`03d8d000 fffff880`03dbc000 ndiswan ndiswan.sys Tue Jul 14 03:10:11 2009 (4A5BCCE3) fffff880`03dbc000 fffff880`03ddd000 raspptp raspptp.sys Tue Jul 14 03:10:18 2009 (4A5BCCEA) fffff880`03ddd000 fffff880`03df7000 rassstp rassstp.sys Tue Jul 14 03:10:25 2009 (4A5BCCF1) fffff880`03df7000 fffff880`03e00000 dump_atapi dump_atapi.sys Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`04200000 fffff880`04230000 nusb3xhc nusb3xhc.sys Fri Jan 22 05:22:21 2010 (4B5919ED) fffff880`04230000 fffff880`04231f00 USBD USBD.SYS Tue Jul 14 03:06:23 2009 (4A5BCBFF) fffff880`04232000 fffff880`04326000 dxgkrnl dxgkrnl.sys Fri Oct 02 04:00:14 2009 (4AC5509E) fffff880`04326000 fffff880`0436c000 dxgmms1 dxgmms1.sys Tue Jul 14 02:38:32 2009 (4A5BC578) fffff880`0436c000 fffff880`04390000 HDAudBus HDAudBus.sys Tue Jul 14 03:06:13 2009 (4A5BCBF5) fffff880`04390000 fffff880`043a1000 usbehci usbehci.sys Tue Jul 14 03:06:30 2009 (4A5BCC06) fffff880`043a1000 fffff880`043f7000 USBPORT USBPORT.SYS Tue Jul 14 03:06:31 2009 (4A5BCC07) fffff880`043f7000 fffff880`04400000 wmiacpi wmiacpi.sys Tue Jul 14 02:31:02 2009 (4A5BC3B6) fffff880`04400000 fffff880`0443d000 portcls portcls.sys Tue Jul 14 03:06:27 2009 (4A5BCC03) fffff880`0443d000 fffff880`04445000 ASACPI ASACPI.sys Thu Jul 16 06:31:29 2009 (4A5E9F11) fffff880`04445000 fffff880`04452000 GEARAspiWDM GEARAspiWDM.sys Mon May 18 15:17:04 2009 (4A1151C0) fffff880`04452000 fffff880`04453480 swenum swenum.sys Tue Jul 14 03:00:18 2009 (4A5BCA92) fffff880`04456000 fffff880`045d5000 P17 P17.sys Tue Apr 21 09:12:47 2009 (49ED63DF) fffff880`045d5000 fffff880`045f7000 drmk drmk.sys Tue Jul 14 04:01:25 2009 (4A5BD8E5) fffff880`045f7000 fffff880`045fc200 ksthunk ksthunk.sys Tue Jul 14 03:00:19 2009 (4A5BCA93) fffff880`06c00000 fffff880`06c12000 tcpipreg tcpipreg.sys Tue Jul 14 03:09:49 2009 (4A5BCCCD) fffff880`06c12000 fffff880`06cda000 HTTP HTTP.sys Tue Jul 14 02:22:16 2009 (4A5BC1A8) fffff880`06cda000 fffff880`06cf8000 bowser bowser.sys Tue Jul 14 02:23:50 2009 (4A5BC206) fffff880`06cf8000 fffff880`06d10000 mpsdrv mpsdrv.sys Tue Jul 14 03:08:25 2009 (4A5BCC79) fffff880`06d10000 fffff880`06d3d000 mrxsmb mrxsmb.sys Sat Feb 27 09:52:19 2010 (4B88CF33) fffff880`06d3d000 fffff880`06d8b000 mrxsmb10 mrxsmb10.sys Sat Feb 27 09:52:28 2010 (4B88CF3C) fffff880`06d8b000 fffff880`06dae000 mrxsmb20 mrxsmb20.sys Sat Feb 27 09:52:26 2010 (4B88CF3A) fffff880`06dae000 fffff880`06db7000 cpuz134_x64 cpuz134_x64.sys Fri Jul 09 14:16:58 2010 (4C37052A) fffff880`06db7000 fffff880`06dc2000 secdrv secdrv.SYS Wed Sep 13 16:18:38 2006 (4508052E) fffff880`06dc2000 fffff880`06def000 srvnet srvnet.sys Tue Jun 22 06:20:32 2010 (4C202C00) fffff880`07030000 fffff880`070c6000 srv srv.sys Tue Jun 22 06:21:11 2010 (4C202C27) fffff880`070c6000 fffff880`070d6000 MpNWMon MpNWMon.sys Sat Mar 20 07:58:00 2010 (4BA463E8) fffff880`07147000 fffff880`07152000 asyncmac asyncmac.sys Tue Jul 14 03:10:13 2009 (4A5BCCE5) fffff880`0fe00000 fffff880`0fe3e000 1394ohci 1394ohci.sys Tue Jul 14 03:07:12 2009 (4A5BCC30) fffff880`0fe3e000 fffff880`0fe4e000 CompositeBus CompositeBus.sys Tue Jul 14 03:00:33 2009 (4A5BCAA1) fffff880`0fe4e000 fffff880`0fe64000 AgileVpn AgileVpn.sys Tue Jul 14 03:10:24 2009 (4A5BCCF0) fffff880`0fe64000 fffff880`0fe88000 rasl2tp rasl2tp.sys Tue Jul 14 03:10:11 2009 (4A5BCCE3) fffff880`0fe88000 fffff880`0fe94000 ndistapi ndistapi.sys Tue Jul 14 03:10:00 2009 (4A5BCCD8) fffff880`0fe94000 fffff880`0feaf000 raspppoe raspppoe.sys Tue Jul 14 03:10:17 2009 (4A5BCCE9) fffff880`0feaf000 fffff880`0feba000 rdpbus rdpbus.sys Tue Jul 14 03:17:46 2009 (4A5BCEAA) fffff880`0febf000 fffff880`10b50e00 nvlddmkm nvlddmkm.sys Sat Jul 10 00:15:58 2010 (4C37918E) fffff880`10b51000 fffff880`10b52180 nvBridge nvBridge.kmd Sat Jul 10 00:07:54 2010 (4C378FAA) fffff880`10b53000 fffff880`10ba9000 Rt64win7 Rt64win7.sys Wed Jun 23 12:10:45 2010 (4C21CF95) fffff880`10ba9000 fffff880`10bec000 ks ks.sys Thu Mar 04 06:32:25 2010 (4B8F37D9) fffff880`10bec000 fffff880`10bfb000 kbdclass kbdclass.sys Tue Jul 14 02:19:50 2009 (4A5BC116) fffff960`00020000 fffff960`0032f000 win32k win32k.sys Sat Jun 19 07:31:59 2010 (4C1C483F) fffff960`004e0000 fffff960`004ea000 TSDDD TSDDD.dll Tue Jul 14 03:16:34 2009 (4A5BCE62) fffff960`00760000 fffff960`00787000 cdd cdd.dll unavailable (00000000) fffff960`008d0000 fffff960`00931000 ATMFD ATMFD.DLL Thu May 27 07:11:31 2010 (4BFDF0F3) Unloaded modules: fffff880`07152000 fffff880`0716d000 USBSTOR.SYS Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`070d6000 fffff880`07147000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01480000 fffff880`0148e000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0148e000 fffff880`0149a000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0149a000 fffff880`014a3000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`014a3000 fffff880`014b6000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000
By "You have updated all you could" I mean:
Thank you for your reply! I really appreciate the help . My results are below:
- I have uninstalled nTune, so nvoclk64.sys is now gone
- I have updated the NEC USB controller, so nusb3xhc.sys has been updated
- I have uninstalled Adobe Photoshop, but it did not remove adfs.SYS... Can I just delete it from my driver folder?
- The same goes for Asus PC Probe, uninstalled, but it did not remove AsIO.sys
- I've tried updating p17.sys but it is already as far up to date as possible. I have the newest Creative drivers...
So how do I go about deleting those two drivers? And that audio driver, I guess I've got no chance there, right?
As for the Memtest: as stated, I have run it for 12 hours without errors. And the Driver Verifier caught one BSOD, which is that CLOCK_WATCHDOG_TIMEOUT, I think. But analysis inconclusive?
(new JCGriff attached)
- I have uninstalled nTune, so nvoclk64.sys is now gone
- I have updated the NEC USB controller, so nusb3xhc.sys has been updated
- I have uninstalled Adobe Photoshop, but it did not remove adfs.SYS... Can I just delete it from my driver folder?
- The same goes for Asus PC Probe, uninstalled, but it did not remove AsIO.sys
- I've tried updating p17.sys but it is already as far up to date as possible. I have the newest Creative drivers...
So how do I go about deleting those two drivers? And that audio driver, I guess I've got no chance there, right?
As for the Memtest: as stated, I have run it for 12 hours without errors. And the Driver Verifier caught one BSOD, which is that CLOCK_WATCHDOG_TIMEOUT, I think. But analysis inconclusive?
(new JCGriff attached)
Run memtest under Windows now:
MemTest: RAM reliability tester for Windows
Sometimes it takes to isolate sticks to test them separately and in different slots.
If this one doesn't detect errors either, then disable your Creative in device manager, to see if it makes any difference.
MemTest: RAM reliability tester for Windows
Sometimes it takes to isolate sticks to test them separately and in different slots.
If this one doesn't detect errors either, then disable your Creative in device manager, to see if it makes any difference.
@CarlTR6: I cannot update that driver. As I said, I already have the latest version available. Plus, I have already run Memtest+ for 12 hours.
@cybercore:
Okay, so 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. But I can try it, I suppose. Though switching slots might not be possible; the blue slots are especially reserved for dual-channel.
As for Driver Verifier, I've tried that once. Willing try it again, but I didn't know which tests to use, so I clicked most of them. My Windows is Dutch, so if you could please show me which tests need to be enabled (like: the first, the second, the third, etc) because I can't translate these technical terms.
@cybercore:
Okay, so 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. But I can try it, I suppose. Though switching slots might not be possible; the blue slots are especially reserved for dual-channel.
As for Driver Verifier, I've tried that once. Willing try it again, but I didn't know which tests to use, so I clicked most of them. My Windows is Dutch, so if you could please show me which tests need to be enabled (like: the first, the second, the third, etc) because I can't translate these technical terms.
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
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
Myeah, that's not gonna work :P. 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?
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?
DRIVER VERIFIER Driver Verifier - Enable and Disable
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.
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.
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?
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?
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.
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.
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?
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?
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.
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.
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.
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?
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.[/QUOTE]
Yes, that could have been the problem. Troubleshooting most often involves removing all suspected or potential causes until you eliminate the crashes.
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.
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)
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)
Quote:
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.
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)
Code:
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
Code:
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)
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.
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.
Leave it off for now to see if your problem has been resolved ..... Let us know how it comes out...
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.
Driver verifier - as Tews said turn it off for now.
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.
Repair install sounds pretty good right now.
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.
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.
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 .
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?
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 - RAM - Test with Memtest86+
CPU - http://www.sevenforums.com/tutorials...t-prime95.html
HDD - HD Diagnostic
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 - RAM - Test with Memtest86+
CPU - http://www.sevenforums.com/tutorials...t-prime95.html
HDD - HD Diagnostic
Okay, that sounds reasonable... *sigh* Man, what a pain in the ass. But I guess I'll try that out, I agree it would be a good way of finding out whether it's software or hardware. Having got time today, but will start this adventure in a day or two. Cross your fingers for me .
Also, would you say I'd use the onboard audio? Because I'm pretty sure Windows automatically uses Creative drivers for that audiocard. Then again, the VIA audio is said be to notoriously sucky...
And what about enabling AHCI? Both my motherboard and HDD support it, and I guess I'd like to use the features it provides (namely NCQ). So do I enable it in the BIOS before beginning the install/format?
And lastly, I'm a loving the tutorials on this site, really fantastic! I wondered if there is one that details the order in which it would be best to install your driver (eg. motherboard first, then gfx card, then audio, etc). Can't seem to find it.
EDIT: FYI, I followed this guide:
Repair Install
But now a friend is telling me that I should boot the DVD and choose Repair instead of running it from Windows. Maybe I should try that first?
EDIT2: Hm, doesn't seem to be such an option in boot. Guess I'll try to run the Repair Install like in the guide once more before trying a clean install.
EDIT3: Nope, again failed. Didn't get a message this time, but oddly enough, the Event Viewer shows a crash. And IE suddenly opened when I logged in.
Also, would you say I'd use the onboard audio? Because I'm pretty sure Windows automatically uses Creative drivers for that audiocard. Then again, the VIA audio is said be to notoriously sucky...
And what about enabling AHCI? Both my motherboard and HDD support it, and I guess I'd like to use the features it provides (namely NCQ). So do I enable it in the BIOS before beginning the install/format?
And lastly, I'm a loving the tutorials on this site, really fantastic! I wondered if there is one that details the order in which it would be best to install your driver (eg. motherboard first, then gfx card, then audio, etc). Can't seem to find it.
EDIT: FYI, I followed this guide:
Repair Install
But now a friend is telling me that I should boot the DVD and choose Repair instead of running it from Windows. Maybe I should try that first?
EDIT2: Hm, doesn't seem to be such an option in boot. Guess I'll try to run the Repair Install like in the guide once more before trying a clean install.
EDIT3: Nope, again failed. Didn't get a message this time, but oddly enough, the Event Viewer shows a crash. And IE suddenly opened when I logged in.
So, interesting development, guys.
I wipe my partition, make new ones, format it, etc (all using Partition Wizard Boot CD). And I wanted the system to run on AHCI, so I enable it in the BIOS, both the Intel chipset and the Marvell controller. I try to install Windows, but I get a Disk Read Error. Later a PFN_LIST_CORRUPT when I tried again. Oh-oh. Turns out that putting the Intel back to IDE fixed it, but, long story short: eventually I physically trace the HDD SATA cable (I have a Cooler Master 690 Advanced II, which has cable management, so that's difficult to do) and guess what I find.....the HD is plugged into the regular SATA ports, and not in the Marvell! I totally missed this when I check last time. Apparently, it wasn't correctly installed by the webshop. Booting, now suddenly a Marvell display appears which confirms I've got a 1TB 6GB/s HDD plugged in.
So I try the Windows install again, and it freezes at 96%. But after I install the Marvell Controller (AHCI) driver in the Windows installation, it works. Of course, then I got to the unpleasant discovery that my product code didn't work (I thought you could just install Windows with the upgrade!) so I had to install XP first. Fun, fun, fun (read: killlll meeee!). After that, the Windows installation worked. I've got Windows running now.
It's interesting, isn't it? Maybe having the Marvell driver installed in Windows, but not having a disk on it, was causing the random BSODs? Anyway, it's on vanilla now, let's see how it works.
About operation Vanilla Install: how about the Windows Updates? Right now, I don't have any sound from my Creative. Also some sort of ATK update is available, and an Nvidia graphics driver. Are these the generic Microsoft drivers, or are they actual drivers? Should I install them?
(I'm making an image now, so I NEVER have to go through this again... Man, this literally took all day. My god.)
EDIT: Maybe I should switch to my normal onboard audio and see if that does get generic drivers? Because if I want to "mimic my normal behaviour", I'm going to at least need sound so I can use Spotify and watch movies.
I wipe my partition, make new ones, format it, etc (all using Partition Wizard Boot CD). And I wanted the system to run on AHCI, so I enable it in the BIOS, both the Intel chipset and the Marvell controller. I try to install Windows, but I get a Disk Read Error. Later a PFN_LIST_CORRUPT when I tried again. Oh-oh. Turns out that putting the Intel back to IDE fixed it, but, long story short: eventually I physically trace the HDD SATA cable (I have a Cooler Master 690 Advanced II, which has cable management, so that's difficult to do) and guess what I find.....the HD is plugged into the regular SATA ports, and not in the Marvell! I totally missed this when I check last time. Apparently, it wasn't correctly installed by the webshop. Booting, now suddenly a Marvell display appears which confirms I've got a 1TB 6GB/s HDD plugged in.
So I try the Windows install again, and it freezes at 96%. But after I install the Marvell Controller (AHCI) driver in the Windows installation, it works. Of course, then I got to the unpleasant discovery that my product code didn't work (I thought you could just install Windows with the upgrade!) so I had to install XP first. Fun, fun, fun (read: killlll meeee!). After that, the Windows installation worked. I've got Windows running now.
It's interesting, isn't it? Maybe having the Marvell driver installed in Windows, but not having a disk on it, was causing the random BSODs? Anyway, it's on vanilla now, let's see how it works.
About operation Vanilla Install: how about the Windows Updates? Right now, I don't have any sound from my Creative. Also some sort of ATK update is available, and an Nvidia graphics driver. Are these the generic Microsoft drivers, or are they actual drivers? Should I install them?
(I'm making an image now, so I NEVER have to go through this again... Man, this literally took all day. My god.)
EDIT: Maybe I should switch to my normal onboard audio and see if that does get generic drivers? Because if I want to "mimic my normal behaviour", I'm going to at least need sound so I can use Spotify and watch movies.
You can disable Creative or any other device in Control Panel -> System -> Device Manager.
Again, I'd be moving this way:
1. Clean install. As soon as done, do not install any drivers yet. Just go to Device Manager and disable any unknown devices and ones with the yellow marks next to them. Run your system this way for a couple of days. I know this is no fun - yes I do.
If crashes happen, you gotta hardware problem. Attach the .dmp's.
2. Next, install the drivers ensuring they are the end of 2009 or preferably the middle of 2010. + Install this BSOD-proof MSE. Run your system this way for a couple of days, see if any crashes and attach the .dmp's.
Now if it doesn't a single time crash on the system with generic drivers only but does on it with the drivers from manufacturers, it could be a driver then. Or yet a device.
Of course memtest, prime95, and hdd diagnostics would do the job but I guess you've run them already and they didn't detect any errrors. So now it's either a driver issue or a well hidden hardware problem.
Fingers crossrd, you know praying, and good luck. I'll be around.
Again, I'd be moving this way:
1. Clean install. As soon as done, do not install any drivers yet. Just go to Device Manager and disable any unknown devices and ones with the yellow marks next to them. Run your system this way for a couple of days. I know this is no fun - yes I do.
If crashes happen, you gotta hardware problem. Attach the .dmp's.
2. Next, install the drivers ensuring they are the end of 2009 or preferably the middle of 2010. + Install this BSOD-proof MSE. Run your system this way for a couple of days, see if any crashes and attach the .dmp's.
Now if it doesn't a single time crash on the system with generic drivers only but does on it with the drivers from manufacturers, it could be a driver then. Or yet a device.
Of course memtest, prime95, and hdd diagnostics would do the job but I guess you've run them already and they didn't detect any errrors. So now it's either a driver issue or a well hidden hardware problem.
Fingers crossrd, you know praying, and good luck. I'll be around.
Well, it's not so much that I'm having problems with the fun aspect (the fun aspect of working on this PC ended a few months ago, I just want to get it working properly :P). I'm just saying it's hard to actually do stuff on my PC without sound, hehe. But okay, I'll try. But I've already installed MSE in this step, because I do need protection, right?
As for all those diagnostics, yeah, I ran them a lot. Especially memtest and HDD Diagnostics. But I'm sort of hopeful that both installing a clean Windows and switching to the Marvell controller will have fixed the problem.
I've got a couple of The Tudors episodes which I suppose I'll just continously run in the background. Can I install K-lite Codec pack, or would you advise against it?
Thanks for your tips, again .
As for all those diagnostics, yeah, I ran them a lot. Especially memtest and HDD Diagnostics. But I'm sort of hopeful that both installing a clean Windows and switching to the Marvell controller will have fixed the problem.
I've got a couple of The Tudors episodes which I suppose I'll just continously run in the background. Can I install K-lite Codec pack, or would you advise against it?
Thanks for your tips, again .
Well, that's why I'm saying I know how hard and depressing it is, but since any BSOD has in fact only two causes, hardware or drivers, and since you have sorted your drivers and run the diagnostics without errors yet, you need to locate the cause what's crashing you. So,
I don't think K-Lite will crash you, just get the latest if you need it. Probably gonna watch movies, cartoons, huh? ; )
Quote:
1. Clean install. As soon as done, do not install any drivers yet. Just go to Device Manager and disable any unknown devices and ones with the yellow marks next to them. Run your system this way for a couple of days. I know this is no fun - yes I do.
If crashes happen, you gotta hardware problem. Attach the .dmp's.
2. Next, install the drivers ensuring they are the end of 2009 or preferably the middle of 2010. + Install this BSOD-proof MSE. Run your system this way for a couple of days, see if any crashes and attach the .dmp's.
If crashes happen, you gotta hardware problem. Attach the .dmp's.
2. Next, install the drivers ensuring they are the end of 2009 or preferably the middle of 2010. + Install this BSOD-proof MSE. Run your system this way for a couple of days, see if any crashes and attach the .dmp's.
I don't think K-Lite will crash you, just get the latest if you need it. Probably gonna watch movies, cartoons, huh? ; )
But about that whole Marvell controller thing, do you see any way how that could explain the BSODs? I mean, it would be great if that had been the problem, 'cause that would mean actually properly using it now would fix the BSODs .
EDIT: Oh wait, I still can't watch stuff without sound, lol.
Status update: no BSODs so far. Of course, it's hard to simulate my usual behaviour (K-lite refused to show anything without a videocard driver and Spotify wouldn't play without an audiocard driver), but I've spent quite some time installing a lot of stuff, and no errors. So, one more day, and then I'm installing the drivers . Wish me luck!
I do wish you luck!
Nope, it wasn't meant to be...
I didn't even start installing my drivers. I plugged in my old MyBook to load some backups unto. Deleted a lot of stuff there, whilst browsing through some images on my computer, and boom. MEMORY_MANAGEMENT BSOD.
I am royally screwed now, right? It must have been a hardware issue after all. Maybe it's the motherboard.
Ho man, I'm at the end of my wits now.
EDIT:
What about this, though? The sticks are supposed to be DDR3-1333, but when I was scanning with one stick in, I suddenly noticed that it's too high. Shouldn't that 1337 be 1333? And shouldn't that 2046GB be 2048GB?
http://img502.imageshack.us/img502/1899/ramweird.jpg
This isn't right, is it?
I didn't even start installing my drivers. I plugged in my old MyBook to load some backups unto. Deleted a lot of stuff there, whilst browsing through some images on my computer, and boom. MEMORY_MANAGEMENT BSOD.
I am royally screwed now, right? It must have been a hardware issue after all. Maybe it's the motherboard.
Ho man, I'm at the end of my wits now.
EDIT:
What about this, though? The sticks are supposed to be DDR3-1333, but when I was scanning with one stick in, I suddenly noticed that it's too high. Shouldn't that 1337 be 1333? And shouldn't that 2046GB be 2048GB?
http://img502.imageshack.us/img502/1899/ramweird.jpg
This isn't right, is it?
Okay, second stick also shows the same speeds.
I called the webshop, and they said that Asus and Corsair is a combination they recently recommend against. So, I'm sending the whole thing back, I guess.
I called the webshop, and they said that Asus and Corsair is a combination they recently recommend against. So, I'm sending the whole thing back, I guess.
I am sure sorry to hear that you have to send the whole thing back; but it does look like you have found the problem. Please keep us updated.
Good news, they are replacing the memory with Kingston KVR1333D3N9K2/4G.
Whether they found an actual defect or just went with my extensive diagnostics remains to be seen, but hey, I don't care. I'm just glad I'm getting new memory.
Whether they found an actual defect or just went with my extensive diagnostics remains to be seen, but hey, I don't care. I'm just glad I'm getting new memory.
Absolutely! That is very good. Let us know how your system does with the new memory. I suspect they tested everything themselves.
Okay, the PC is back. Time will tell if the problem has been fixed. But sensor programs still say the memory runs at 668MHz instead of 667MHz, is that a problem?
I am not a RAM expert by any stretch of the imagination. I suggest that you start a thread in the Hardware & Devices section. There are some really knowledge folks there about RAM and motherboards.
Cool, I'll do that.
In the mean time, I'll post back here to see if this RAM switching has finally solved the damn problem. *crosses fingers*
In the mean time, I'll post back here to see if this RAM switching has finally solved the damn problem. *crosses fingers*
Thanks much; we are looking forward to a good report.
As am I, man . As am I.
Okay, seems like the frequency difference is within the boundaries:
RAM frequency indiscrepancy
Good, will post back in a few days to see if my PC stays this way .
RAM frequency indiscrepancy
Good, will post back in a few days to see if my PC stays this way .
Thanks for the update. And that is great news, the kind we like to hear!
Well, I'm almost too afraid to say this, but it's been over two weeks now, and I have had zero problems. I don't want to jinx it, *knocks on wood*, but it would seem this new Kingston memory did the trick.
I added my "solution" to the initial post. Thank you, guys, once more, for helping me get to the root of my trouble . Reps coming your way.
I added my "solution" to the initial post. Thank you, guys, once more, for helping me get to the root of my trouble . Reps coming your way.
That is the news we like to hear! Congratualtions. I am glad you are running smoothly. You are very welcome for the help. Happy computing!
Không có nhận xét nào:
Đăng nhận xét