I had another bsod today. please refer to this page (post#26 for a brief synopsis) for what has been done. I am really at a loss. It happened this time as I was running the scannow command. I am attaching the two files I was directed to.
Attachment 123624
Attachment 123625
Thanks for any help.
Attachment 123624
Attachment 123625
Thanks for any help.
Remove SpeedFan, its driver is outdated
The dmp(s) point to ntkrpamp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause. We need to run driver verifier to pinpoint the faulting driver...
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
Then upload the new dumps
Code:
speedfan.sys fffff880`015e4000 fffff880`015eb000 0x00007000 0x45168798 24/09/2006 17:26:48
The dmp(s) point to ntkrpamp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause. We need to run driver verifier to pinpoint the faulting driver...
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
Then upload the new dumps
You got CPU-Z 133 & 134 - uninstall 133.
Speedfan by itself is a good temperatures monitoring tool, and so far speedfan.sys 2006 appears to be the latest and working fine. However, you also have CoreTemp which I suspect has a conflict with Speedfan:
ALSysIO64.sys Sun Apr 19 15:41:04 2009
Go ahead and uninstall both CoreTemp and Speedfan, then navigate to C:\Windows\system32\drivers and ensure that these 2 drivers are gone -> ALSysIO64.sys and Speedfan.sys. Reboot and see how it goes.
Other than this CoreTemp, your drivers are in perfect shape now. If you're still getting BSOD's after the removal of CoreTemp and Speedfan, this will likely mean you got a hardware problem - possibly a defective RAM stick or it set wrong in the bios.
Crash Dumps:
Drivers:
Speedfan by itself is a good temperatures monitoring tool, and so far speedfan.sys 2006 appears to be the latest and working fine. However, you also have CoreTemp which I suspect has a conflict with Speedfan:
ALSysIO64.sys Sun Apr 19 15:41:04 2009
Go ahead and uninstall both CoreTemp and Speedfan, then navigate to C:\Windows\system32\drivers and ensure that these 2 drivers are gone -> ALSysIO64.sys and Speedfan.sys. Reboot and see how it goes.
Other than this CoreTemp, your drivers are in perfect shape now. If you're still getting BSOD's after the removal of CoreTemp and Speedfan, this will likely mean you got a hardware problem - possibly a defective RAM stick or it set wrong in the bios.
Crash Dumps:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:\a\Minidump\D M P\121510-14523-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 (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02a11000 PsLoadedModuleList = 0xfffff800`02c4ee50 Debug session time: Wed Dec 15 13:20:01.903 2010 (UTC - 5:00) System Uptime: 0 days 6:34:17.245 Loading Kernel Symbols ............................................................... ................................................................ .................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff820032287d0, 0, fffff80002bb60f3, 5} Could not read faulting driver name Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 ) Followup: MachineOwner --------- 2: 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: fffff820032287d0, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff80002bb60f3, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000005, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb90e0 fffff820032287d0 FAULTING_IP: nt!ExFreePoolWithTag+43 fffff800`02bb60f3 418b45f0 mov eax,dword ptr [r13-10h] MM_INTERNAL_CODE: 5 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: System CURRENT_IRQL: 0 TRAP_FRAME: fffff88002f4c8b0 -- (.trap 0xfffff88002f4c8b0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffff820032287e0 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002bb60f3 rsp=fffff88002f4ca40 rbp=fffff80002c265a0 r8=0000000000000001 r9=0000000000000000 r10=fffff80002a11000 r11=0000000000000155 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!ExFreePoolWithTag+0x43: fffff800`02bb60f3 418b45f0 mov eax,dword ptr [r13-10h] ds:0155:ffffffff`fffffff0=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002b008c1 to fffff80002a81740 STACK_TEXT: fffff880`02f4c748 fffff800`02b008c1 : 00000000`00000050 fffff820`032287d0 00000000`00000000 fffff880`02f4c8b0 : nt!KeBugCheckEx fffff880`02f4c750 fffff800`02a7f82e : 00000000`00000000 fffff880`01276550 fffff8a0`02f8dd00 fffff8a0`000d6cb0 : nt! ?? ::FNODOBFM::`string'+0x40e8b fffff880`02f4c8b0 fffff800`02bb60f3 : 00000000`00000001 fffff8a0`007f9690 00000000`00000000 fffffa80`06393140 : nt!KiPageFault+0x16e fffff880`02f4ca40 fffff800`02a57c09 : fffff8a0`076c4d60 fffff8a0`076c4da0 fffff800`02c265a0 fffff8a0`076b77f0 : nt!ExFreePoolWithTag+0x43 fffff880`02f4caf0 fffff880`01276646 : fffff880`01276550 00000000`00000001 fffff880`01276550 fffffa80`00000313 : nt!FsRtlUninitializeBaseMcb+0x41 fffff880`02f4cb20 fffff800`02a8e961 : fffffa80`0641db60 fffff880`02f4cb50 00000000`00000000 00000000`00000003 : Ntfs!NtfsMcbCleanupLruQueue+0xf6 fffff880`02f4ccb0 fffff800`02d25c06 : 070240c0`c2600c1f fffffa80`0641db60 00000000`00000080 fffffa80`06406040 : nt!ExpWorkerThread+0x111 fffff880`02f4cd40 fffff800`02a5fc26 : fffff880`02e88180 fffffa80`0641db60 fffff880`02e93040 0a280fb0`f0a44e00 : nt!PspSystemThreadStartup+0x5a fffff880`02f4cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!ExFreePoolWithTag+43 fffff800`02bb60f3 418b45f0 mov eax,dword ptr [r13-10h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!ExFreePoolWithTag+43 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0x50_nt!ExFreePoolWithTag+43 BUCKET_ID: X64_0x50_nt!ExFreePoolWithTag+43 Followup: MachineOwner --------- Drivers:
Code:
start end module name fffff880`00e00000 fffff880`00e57000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`03efb000 fffff880`03f85000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`04073000 fffff880`04089000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0) fffff880`07339000 fffff880`07341000 ALSysIO64 ALSysIO64.sys Sun Apr 19 15:41:04 2009 (49EB7E50) fffff880`04167000 fffff880`0417c000 amdppm amdppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`00c00000 fffff880`00c0b000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`073b2000 fffff880`073bd000 asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5) fffff880`00fcc000 fffff880`00fd5000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00fd5000 fffff880`00fff000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118) fffff880`04608000 fffff880`04dfd000 atikmdag atikmdag.sys Tue Oct 26 22:29:53 2010 (4CC78EA1) fffff880`0417c000 fffff880`041c7000 atikmpag atikmpag.sys Tue Oct 26 22:14:23 2010 (4CC78AFF) fffff880`02af4000 fffff880`02afb000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`04130000 fffff880`04141000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`02600000 fffff880`0261e000 bowser bowser.sys Mon Jul 13 19:23:50 2009 (4A5BC206) fffff960`00750000 fffff960`00777000 cdd cdd.dll unavailable (00000000) fffff880`02a94000 fffff880`02abe000 cdrom cdrom.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`00cdc000 fffff880`00d9c000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D) fffff880`01000000 fffff880`01030000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00c7e000 fffff880`00cdc000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`010c0000 fffff880`01133000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`041ef000 fffff880`041ff000 CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`052f7000 fffff880`05300000 cpuz133_x64 cpuz133_x64.sys Tue May 11 05:58:57 2010 (4BE92A61) fffff880`05300000 fffff880`05309000 cpuz134_x64 cpuz134_x64.sys Fri Jul 09 07:16:58 2010 (4C37052A) fffff880`04e2f000 fffff880`04e3d000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`0408f000 fffff880`04112000 csc csc.sys Mon Jul 13 19:24:26 2009 (4A5BC22A) fffff880`04112000 fffff880`04130000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200) fffff880`03ec3000 fffff880`03ed2000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`013e7000 fffff880`013fd000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`04fc5000 fffff880`04fe7000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5) fffff880`04e3d000 fffff880`04e49000 dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`02a6f000 fffff880`02a82000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`02a64000 fffff880`02a6f000 dump_msahci dump_msahci.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`01030000 fffff880`0103c000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574) fffff880`0426b000 fffff880`0435f000 dxgkrnl dxgkrnl.sys Thu Oct 01 21:00:14 2009 (4AC5509E) fffff880`0435f000 fffff880`043a5000 dxgmms1 dxgmms1.sys Mon Jul 13 19:38:32 2009 (4A5BC578) fffff880`01042000 fffff880`01056000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`00c0b000 fffff880`00c57000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`0122b000 fffff880`01235000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`011b9000 fffff880`011f3000 fvevol fvevol.sys Fri Sep 25 22:34:26 2009 (4ABD7DB2) fffff880`01400000 fffff880`0144a000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164) fffff800`02fed000 fffff800`03036000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`043a5000 fffff880`043c9000 HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5) fffff880`04f2c000 fffff880`04f88000 HdAudio HdAudio.sys Mon Jul 13 20:06:59 2009 (4A5BCC23) fffff880`04e00000 fffff880`04e19000 HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD) fffff880`04e19000 fffff880`04e21080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9) fffff880`04fed000 fffff880`04ffb000 hidusb hidusb.sys Mon Jul 13 20:06:22 2009 (4A5BCBFE) fffff880`02737000 fffff880`027ff000 HTTP HTTP.sys Mon Jul 13 19:22:16 2009 (4A5BC1A8) fffff880`01235000 fffff880`0123e000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff880`02a46000 fffff880`02a55000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`02a82000 fffff880`02a90000 kbdhid kbdhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff800`00ba0000 fffff800`00baa000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`04e4f000 fffff880`04e92000 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`015b1000 fffff880`015dc000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4) fffff880`04fe7000 fffff880`04fec200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93) fffff880`0270a000 fffff880`0271f000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`026c6000 fffff880`026e9000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295) fffff880`00c5d000 fffff880`00c6a000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65) fffff880`026b8000 fffff880`026c6000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C) fffff880`02a55000 fffff880`02a64000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`04e22000 fffff880`04e2f000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`00fb2000 fffff880`00fcc000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`02abe000 fffff880`02aeb000 MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0) fffff880`07329000 fffff880`07339000 MpNWMon MpNWMon.sys Sat Mar 20 01:58:00 2010 (4BA463E8) fffff880`0261e000 fffff880`02636000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79) fffff880`02636000 fffff880`02663000 mrxsmb mrxsmb.sys Sat Feb 27 02:52:19 2010 (4B88CF33) fffff880`02663000 fffff880`026b1000 mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C) fffff880`052d4000 fffff880`052f7000 mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A) fffff880`00eeb000 fffff880`00ef6000 msahci msahci.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`02b59000 fffff880`02b64000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00e60000 fffff880`00e6a000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`01062000 fffff880`010c0000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C) fffff880`03eb8000 fffff880`03ec3000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`015eb000 fffff880`015fd000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`0145f000 fffff880`01551000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`02ba0000 fffff880`02bac000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8) fffff880`02bac000 fffff880`02bdb000 ndiswan ndiswan.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`04f17000 fffff880`04f2c000 NDProxy NDProxy.SYS Mon Jul 13 20:10:05 2009 (4A5BCCDD) fffff880`03e00000 fffff880`03e0f000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`03f85000 fffff880`03fca000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178) fffff880`01551000 fffff880`015b1000 NETIO NETIO.SYS Mon Jul 13 19:21:46 2009 (4A5BC18A) fffff880`02b64000 fffff880`02b75000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`03eac000 fffff880`03eb8000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`02a11000 fffff800`02fed000 nt ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9) fffff880`01244000 fffff880`013e7000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F) fffff880`02aeb000 fffff880`02af4000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109) fffff880`04ea4000 fffff880`04ebd000 nusb3hub nusb3hub.sys Thu Sep 30 00:00:03 2010 (4CA40B43) fffff880`043c9000 fffff880`043f9000 nusb3xhc nusb3xhc.sys Thu Sep 30 00:00:03 2010 (4CA40B43) fffff880`03fd3000 fffff880`03ff9000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5) fffff880`041d2000 fffff880`041ef000 parport parport.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`00eaa000 fffff880`00ebf000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00e6a000 fffff880`00e9d000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`00ed4000 fffff880`00edb000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115) fffff880`00edb000 fffff880`00eeb000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`0121a000 fffff880`0122b000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`05309000 fffff880`053af000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF) fffff880`04f88000 fffff880`04fc5000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00c6a000 fffff880`00c7e000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`01056000 fffff880`01061e00 PxHlpa64 PxHlpa64.sys Fri May 15 17:43:06 2009 (4A0DE1EA) fffff880`03ed2000 fffff880`03ef6000 rasl2tp rasl2tp.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`02bdb000 fffff880`02bf6000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9) fffff880`02a00000 fffff880`02a21000 raspptp raspptp.sys Mon Jul 13 20:10:18 2009 (4A5BCCEA) fffff880`02a21000 fffff880`02a3b000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1) fffff880`03e5b000 fffff880`03eac000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219) fffff880`02a3b000 fffff880`02a46000 rdpbus rdpbus.sys Mon Jul 13 20:17:46 2009 (4A5BCEAA) fffff880`02b3e000 fffff880`02b47000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`02b47000 fffff880`02b50000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`02b50000 fffff880`02b59000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`0117f000 fffff880`011b9000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A) fffff880`0271f000 fffff880`02737000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`04200000 fffff880`04265000 Rt64win7 Rt64win7.sys Mon Oct 25 05:33:07 2010 (4CC54ED3) fffff880`053af000 fffff880`053ba000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E) fffff880`04067000 fffff880`04073000 serenum serenum.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`03e0f000 fffff880`03e2c000 serial serial.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`015e4000 fffff880`015eb000 speedfan speedfan.sys Sun Sep 24 09:26:48 2006 (45168798) fffff880`015dc000 fffff880`015e4000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`07293000 fffff880`07329000 srv srv.sys Thu Aug 26 23:38:00 2010 (4C773318) fffff880`05200000 fffff880`05267000 srv2 srv2.sys Thu Aug 26 23:37:46 2010 (4C77330A) fffff880`053ba000 fffff880`053e7000 srvnet srvnet.sys Thu Aug 26 23:37:24 2010 (4C7732F4) fffff880`043fb000 fffff880`043fc480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92) fffff880`01603000 fffff880`01800000 tcpip tcpip.sys Sun Jun 13 23:39:04 2010 (4C15A458) fffff880`053e7000 fffff880`053f9000 tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD) fffff880`02b93000 fffff880`02ba0000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E) fffff880`02b75000 fffff880`02b93000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B) fffff880`03e47000 fffff880`03e5b000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64) fffff960`00460000 fffff960`0046a000 TSDDD TSDDD.dll unavailable (00000000) fffff880`04141000 fffff880`04167000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1) fffff880`04e92000 fffff880`04ea4000 umbus umbus.sys Mon Jul 13 20:06:56 2009 (4A5BCC20) fffff880`043f9000 fffff880`043faf00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF) fffff880`04056000 fffff880`04067000 usbehci usbehci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`04ebd000 fffff880`04f17000 usbhub usbhub.sys Mon Jul 13 20:07:09 2009 (4A5BCC2D) fffff880`041c7000 fffff880`041d2000 usbohci usbohci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`04000000 fffff880`04056000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07) fffff880`00e9d000 fffff880`00eaa000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`02afb000 fffff880`02b09000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`02b09000 fffff880`02b2e000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`0144a000 fffff880`0145a000 vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E) fffff880`00ebf000 fffff880`00ed4000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00d9c000 fffff880`00df8000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141) fffff880`01133000 fffff880`0117f000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128) fffff880`03e2c000 fffff880`03e47000 wanarp wanarp.sys Mon Jul 13 20:10:21 2009 (4A5BCCED) fffff880`02b2e000 fffff880`02b3e000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00eff000 fffff880`00fa3000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00fa3000 fffff880`00fb2000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`03fca000 fffff880`03fd3000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff960`00040000 fffff960`0034f000 win32k win32k.sys unavailable (00000000) fffff880`00e57000 fffff880`00e60000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`026e9000 fffff880`0270a000 WudfPf WudfPf.sys Mon Jul 13 20:05:37 2009 (4A5BCBD1) Unloaded modules: fffff880`07341000 fffff880`073b2000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00071000 fffff880`01030000 fffff880`0103e000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000E000 fffff880`011f3000 fffff880`011ff000 dump_pciidex Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000C000 fffff880`02a76000 fffff880`02a81000 dump_msahci. Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000B000 fffff880`02a81000 fffff880`02a94000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00013000
I was in the process of responding that I had done what you asked and had another BSOD. Here is the minidump fileAttachment 123635
I'm getting pretty good with doing this
If the verifier report is not in the minidump file where do I find it? BTW, I don't thik it is hardware. I run memtest86 at least 10 times with ram in almost every configuration single sticks, different slots and together both from cold and hot boot. I have run prime and furmark. I have run checkdisk and scannow several times as well as downloaded testing programs from the manuf. of my HDs. all passed. I have done a secure erase of my SSD and a clean install of windows and transfered nothing from the previous installation back. I am running MSE instead of Norton.
I just had 3 more bsods right in a row. I have turned off verifier.
Attachment 123672
Attachment 123673
Attachment 123674
Attachment 123672
Attachment 123673
Attachment 123674
I have installed windows on a spinner to make sure the problem was not the SSD. The problems seemed to start shortly after I installed it. But it was performing properly and passed all of the smart tests. I sure don't remember things being this slow.
Code:
BugCheck C9, {224, fffff8800113fc34, fffff9800f356c10, 2} DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9) The IO manager has caught a misbehaving driver Unable to load image \SystemRoot\System32\Drivers\PxHlpa64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for PxHlpa64.sys *** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys Probably caused by : PxHlpa64.sys ( PxHlpa64+8c34 ) So the Driver Verifier blames PxEngine :
PxHlpa64.sys Fri May 15 17:43:06 2009
Px Engine Device Driver for 64-bit Windows
Sonic Solutions
PX Engine was created by Roxio/Sonic Solutions to offer compatibility with its line of software products dealing with optical media. Used by many CD/DVD programs and burning software - feel free to update them all.
What you should do now:
1. Disable Driver Verifier, boot in safe mode if necessary
2. If BSOD's happen again after you disable the verifier, go to C:\Windows\System32\drivers and rename PxHlpa64.sys to PxHlpa64.BAK. This will break your CD/DVD program, but can easily be renamed back after your system is fixed.
3. If despite all the blue screen crashes persist, you got a hardware problem. One very common widespread hardware fault is a defective RAM stick or RAM improperly set in BIOS.
You may also want to run memtest overnight, as detailed here:
RAM - Test with Memtest86+
~~~~~~~~~~~~
CRASH DUMPS:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:\a\Minidump\D M P\121510-20841-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 (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02a0a000 PsLoadedModuleList = 0xfffff800`02c47e50 Debug session time: Wed Dec 15 17:10:40.166 2010 (UTC - 5:00) System Uptime: 0 days 0:00:37.148 Loading Kernel Symbols ............................................................... ................................................................ .................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C9, {224, fffff88001126c34, fffff98010070c10, 2} Unable to load image \SystemRoot\System32\Drivers\PxHlpa64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for PxHlpa64.sys *** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys Probably caused by : PxHlpa64.sys ( PxHlpa64+8c34 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9) The IO manager has caught a misbehaving driver. Arguments: Arg1: 0000000000000224, An IRP dispatch handler has returned a status that is inconsistent with the IRP's IoStatus.Status field. Arg2: fffff88001126c34, The address in the driver's code where the error was detected. Arg3: fffff98010070c10, IRP address. Arg4: 0000000000000002, Expected status code. Debugging Details: ------------------ BUGCHECK_STR: 0xc9_224 DRIVER_VERIFIER_IO_VIOLATION_TYPE: 224 FAULTING_IP: PxHlpa64+8c34 fffff880`01126c34 53 push rbx FOLLOWUP_IP: PxHlpa64+8c34 fffff880`01126c34 53 push rbx IRP_ADDRESS: fffff98010070c10 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002f043dc to fffff80002a7a740 STACK_TEXT: fffff880`031683b8 fffff800`02f043dc : 00000000`000000c9 00000000`00000224 fffff880`01126c34 fffff980`10070c10 : nt!KeBugCheckEx fffff880`031683c0 fffff800`02f0e47a : fffff800`02f029f0 fffff880`01126c34 fffff980`10070c10 00000000`00000002 : nt!VerifierBugCheckIfAppropriate+0x3c fffff880`03168400 fffff800`02f0f3f3 : fffff880`01126c34 fffffa80`09ee7b58 00000000`00000002 00000000`ffffffff : nt!ViErrorFinishReport+0xda fffff880`03168450 fffff800`02f1a759 : fffffa80`09ee7aa0 fffffa80`09ee7aa0 fffffa80`09ee7b58 fffff880`01128a98 : nt!VfErrorReport4+0x83 fffff880`03168540 fffff800`02f1ab63 : fffffa80`09ee7aa0 00000000`00000002 fffffa80`08b61030 fffff8a0`03048f10 : nt!IovpCallDriver2+0x179 fffff880`031685a0 fffff800`02f20c2e : fffff980`10070c10 fffff980`10070c10 00000000`00000002 fffffa80`08b61030 : nt!VfAfterCallDriver+0x353 fffff880`031685f0 fffff800`02f234da : fffff980`10070f20 fffffa80`08b61030 fffffa80`081f7e00 fffffa80`09ee7aa0 : nt!IovCallDriver+0x57e fffff880`03168650 fffff800`02f20c16 : fffff980`10070c10 00000000`00000002 fffffa80`081f7e00 fffffa80`09981330 : nt!ViFilterDispatchPnp+0xea fffff880`03168680 fffff880`00f2f93c : fffff980`10070f68 00000000`00000000 fffffa80`08f8ab60 fffffa80`09981330 : nt!IovCallDriver+0x566 fffff880`031686e0 fffff880`00f282ce : 00000000`00000001 fffff880`031687f0 fffff880`03168700 fffffa80`08f8ab00 : Wdf01000!FxPkgFdo::ProcessRemoveDeviceOverload+0x74 fffff880`03168710 fffff880`00f26dd6 : fffffa80`08bef502 00000000`00000002 00000000`00000000 fffffa80`08f8ab60 : Wdf01000!FxPkgPnp::_PnpRemoveDevice+0x126 fffff880`03168780 fffff880`00ef6245 : fffff980`10070c10 fffff980`10070c10 fffffa80`08ee2e20 fffffa80`08ee2e20 : Wdf01000!FxPkgPnp::Dispatch+0x1b2 fffff880`031687f0 fffff880`00ef614b : fffff880`031688d8 fffff980`10070c10 00000000`00000002 fffffa80`08ee2e20 : Wdf01000!FxDevice::Dispatch+0xa9 fffff880`03168820 fffff800`02f20c16 : fffff980`10070c10 00000000`00000002 fffffa80`08ee2e20 fffff880`03168978 : Wdf01000!FxDevice::DispatchWithLock+0x93 fffff880`03168860 fffff800`02ce6519 : fffffa80`08ee2e20 00000000`c00000bb fffff880`03168978 fffffa80`09ea8010 : nt!IovCallDriver+0x566 fffff880`031688c0 fffff800`02e64831 : fffffa80`08ec1b70 00000000`00000000 fffffa80`08f23a90 00000000`00000801 : nt!IopSynchronousCall+0xc5 fffff880`03168930 fffff800`02b7bbf3 : fffff8a0`03347e90 fffff8a0`03347e90 00000000`00000000 00000000`00000000 : nt!IopRemoveDevice+0x101 fffff880`031689f0 fffff800`02e64384 : fffffa80`08f23a90 00000000`00000000 00000000`00000002 00000000`00000018 : nt!PnpRemoveLockedDeviceNode+0x1a3 fffff880`03168a40 fffff800`02e64490 : 00000000`00000000 fffff8a0`06dc3901 fffff8a0`032a7de0 ffffcb91`ce93dd7c : nt!PnpDeleteLockedDeviceNode+0x44 fffff880`03168a70 fffff800`02ef4984 : 00000000`00000002 00000000`00000000 fffffa80`08eafd90 fffff8a0`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0 fffff880`03168ae0 fffff800`02ef4fdc : fffff880`00000000 00000000`00010200 fffff880`03168c00 00000000`00000000 : nt!PnpProcessQueryRemoveAndEject+0xc34 fffff880`03168c20 fffff800`02de00dc : 00000000`00000000 fffffa80`09e3d170 fffff8a0`06dc9bc0 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c fffff880`03168c50 fffff800`02a87961 : fffff800`02ce6008 fffff8a0`06dc3920 fffff800`02c1f5f8 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x58ffb fffff880`03168cb0 fffff800`02d1ec06 : 00000000`00000000 fffffa80`063fe680 00000000`00000080 fffffa80`063e4040 : nt!ExpWorkerThread+0x111 fffff880`03168d40 fffff800`02a58c26 : fffff880`03088180 fffffa80`063fe680 fffff880`03093040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`03168d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb SYMBOL_NAME: PxHlpa64+8c34 FOLLOWUP_NAME: MachineOwner MODULE_NAME: PxHlpa64 IMAGE_NAME: PxHlpa64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a0de1ea FAILURE_BUCKET_ID: X64_0xc9_224_VRF_PxHlpa64+8c34 BUCKET_ID: X64_0xc9_224_VRF_PxHlpa64+8c34 Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:\a\Minidump\D M P\121510-14523-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 (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02a11000 PsLoadedModuleList = 0xfffff800`02c4ee50 Debug session time: Wed Dec 15 13:20:01.903 2010 (UTC - 5:00) System Uptime: 0 days 6:34:17.245 Loading Kernel Symbols ............................................................... ................................................................ .................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff820032287d0, 0, fffff80002bb60f3, 5} Could not read faulting driver name Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 ) Followup: MachineOwner --------- 2: 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: fffff820032287d0, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff80002bb60f3, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000005, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb90e0 fffff820032287d0 FAULTING_IP: nt!ExFreePoolWithTag+43 fffff800`02bb60f3 418b45f0 mov eax,dword ptr [r13-10h] MM_INTERNAL_CODE: 5 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: System CURRENT_IRQL: 0 TRAP_FRAME: fffff88002f4c8b0 -- (.trap 0xfffff88002f4c8b0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffff820032287e0 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002bb60f3 rsp=fffff88002f4ca40 rbp=fffff80002c265a0 r8=0000000000000001 r9=0000000000000000 r10=fffff80002a11000 r11=0000000000000155 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!ExFreePoolWithTag+0x43: fffff800`02bb60f3 418b45f0 mov eax,dword ptr [r13-10h] ds:0155:ffffffff`fffffff0=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002b008c1 to fffff80002a81740 STACK_TEXT: fffff880`02f4c748 fffff800`02b008c1 : 00000000`00000050 fffff820`032287d0 00000000`00000000 fffff880`02f4c8b0 : nt!KeBugCheckEx fffff880`02f4c750 fffff800`02a7f82e : 00000000`00000000 fffff880`01276550 fffff8a0`02f8dd00 fffff8a0`000d6cb0 : nt! ?? ::FNODOBFM::`string'+0x40e8b fffff880`02f4c8b0 fffff800`02bb60f3 : 00000000`00000001 fffff8a0`007f9690 00000000`00000000 fffffa80`06393140 : nt!KiPageFault+0x16e fffff880`02f4ca40 fffff800`02a57c09 : fffff8a0`076c4d60 fffff8a0`076c4da0 fffff800`02c265a0 fffff8a0`076b77f0 : nt!ExFreePoolWithTag+0x43 fffff880`02f4caf0 fffff880`01276646 : fffff880`01276550 00000000`00000001 fffff880`01276550 fffffa80`00000313 : nt!FsRtlUninitializeBaseMcb+0x41 fffff880`02f4cb20 fffff800`02a8e961 : fffffa80`0641db60 fffff880`02f4cb50 00000000`00000000 00000000`00000003 : Ntfs!NtfsMcbCleanupLruQueue+0xf6 fffff880`02f4ccb0 fffff800`02d25c06 : 070240c0`c2600c1f fffffa80`0641db60 00000000`00000080 fffffa80`06406040 : nt!ExpWorkerThread+0x111 fffff880`02f4cd40 fffff800`02a5fc26 : fffff880`02e88180 fffffa80`0641db60 fffff880`02e93040 0a280fb0`f0a44e00 : nt!PspSystemThreadStartup+0x5a fffff880`02f4cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!ExFreePoolWithTag+43 fffff800`02bb60f3 418b45f0 mov eax,dword ptr [r13-10h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!ExFreePoolWithTag+43 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0x50_nt!ExFreePoolWithTag+43 BUCKET_ID: X64_0x50_nt!ExFreePoolWithTag+43 Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:\a\Minidump\D M P\121510-20763-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 (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02a0a000 PsLoadedModuleList = 0xfffff800`02c47e50 Debug session time: Wed Dec 15 17:09:35.434 2010 (UTC - 5:00) System Uptime: 0 days 0:01:51.792 Loading Kernel Symbols ............................................................... ................................................................ .................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C9, {224, fffff880010a1c34, fffff98012892c10, 2} Unable to load image \SystemRoot\System32\Drivers\PxHlpa64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for PxHlpa64.sys *** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys Probably caused by : PxHlpa64.sys ( PxHlpa64+8c34 ) Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9) The IO manager has caught a misbehaving driver. Arguments: Arg1: 0000000000000224, An IRP dispatch handler has returned a status that is inconsistent with the IRP's IoStatus.Status field. Arg2: fffff880010a1c34, The address in the driver's code where the error was detected. Arg3: fffff98012892c10, IRP address. Arg4: 0000000000000002, Expected status code. Debugging Details: ------------------ BUGCHECK_STR: 0xc9_224 DRIVER_VERIFIER_IO_VIOLATION_TYPE: 224 FAULTING_IP: PxHlpa64+8c34 fffff880`010a1c34 53 push rbx FOLLOWUP_IP: PxHlpa64+8c34 fffff880`010a1c34 53 push rbx IRP_ADDRESS: fffff98012892c10 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002f043dc to fffff80002a7a740 STACK_TEXT: fffff880`02f6f3b8 fffff800`02f043dc : 00000000`000000c9 00000000`00000224 fffff880`010a1c34 fffff980`12892c10 : nt!KeBugCheckEx fffff880`02f6f3c0 fffff800`02f0e47a : fffff800`02f029f0 fffff880`010a1c34 fffff980`12892c10 00000000`00000002 : nt!VerifierBugCheckIfAppropriate+0x3c fffff880`02f6f400 fffff800`02f0f3f3 : fffff880`010a1c34 fffffa80`09e030c8 00000000`00000002 00000000`ffffffff : nt!ViErrorFinishReport+0xda fffff880`02f6f450 fffff800`02f1a759 : fffffa80`09e03010 fffffa80`09e03010 fffffa80`09e030c8 fffff880`010a3a98 : nt!VfErrorReport4+0x83 fffff880`02f6f540 fffff800`02f1ab63 : fffffa80`09e03010 00000000`00000002 fffffa80`09db5030 fffff8a0`081fa8b0 : nt!IovpCallDriver2+0x179 fffff880`02f6f5a0 fffff800`02f20c2e : fffff980`12892c10 fffff980`12892c10 00000000`00000002 fffffa80`09db5030 : nt!VfAfterCallDriver+0x353 fffff880`02f6f5f0 fffff800`02f234da : fffff980`12892f20 fffffa80`09db5030 fffffa80`09d2be00 fffffa80`09e03010 : nt!IovCallDriver+0x57e fffff880`02f6f650 fffff800`02f20c16 : fffff980`12892c10 00000000`00000002 fffffa80`09d2be00 fffffa80`09c9f540 : nt!ViFilterDispatchPnp+0xea fffff880`02f6f680 fffff880`00ee693c : fffff980`12892f68 00000000`00000000 fffffa80`098aa6b0 fffffa80`09c9f540 : nt!IovCallDriver+0x566 fffff880`02f6f6e0 fffff880`00edf2ce : 00000000`00000001 fffff880`02f6f7f0 fffff880`02f6f700 fffffa80`098aa600 : Wdf01000!FxPkgFdo::ProcessRemoveDeviceOverload+0x74 fffff880`02f6f710 fffff880`00edddd6 : fffffa80`08c07402 00000000`00000002 00000000`00000000 fffffa80`098aa6b0 : Wdf01000!FxPkgPnp::_PnpRemoveDevice+0x126 fffff880`02f6f780 fffff880`00ead245 : fffff980`12892c10 fffff980`12892c10 fffffa80`0993f060 fffffa80`0993f060 : Wdf01000!FxPkgPnp::Dispatch+0x1b2 fffff880`02f6f7f0 fffff880`00ead14b : fffff880`02f6f8d8 fffff980`12892c10 00000000`00000002 fffffa80`0993f060 : Wdf01000!FxDevice::Dispatch+0xa9 fffff880`02f6f820 fffff800`02f20c16 : fffff980`12892c10 00000000`00000002 fffffa80`0993f060 fffff880`02f6f978 : Wdf01000!FxDevice::DispatchWithLock+0x93 fffff880`02f6f860 fffff800`02ce6519 : fffffa80`0993f060 00000000`c00000bb fffff880`02f6f978 fffffa80`09b5a0e0 : nt!IovCallDriver+0x566 fffff880`02f6f8c0 fffff800`02e64831 : fffffa80`09b48060 00000000`00000000 fffffa80`09d2ba00 00000000`00000801 : nt!IopSynchronousCall+0xc5 fffff880`02f6f930 fffff800`02b7bbf3 : fffff8a0`07d7c8d0 fffff8a0`07d7c8d0 00000000`00000000 00000000`00000000 : nt!IopRemoveDevice+0x101 fffff880`02f6f9f0 fffff800`02e64384 : fffffa80`09d2ba00 00000000`00000000 00000000`00000002 fffffa80`09d61060 : nt!PnpRemoveLockedDeviceNode+0x1a3 fffff880`02f6fa40 fffff800`02e64490 : 00000000`00000000 fffff8a0`08021a01 fffff8a0`080526b0 ffffcb8e`ac27eba9 : nt!PnpDeleteLockedDeviceNode+0x44 fffff880`02f6fa70 fffff800`02ef4984 : 00000000`00000002 00000000`00000000 fffffa80`092b5b60 fffff8a0`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0 fffff880`02f6fae0 fffff800`02ef4fdc : fffff880`00000000 00000000`00010200 fffff880`02f6fc00 00000000`00000000 : nt!PnpProcessQueryRemoveAndEject+0xc34 fffff880`02f6fc20 fffff800`02de00dc : 00000000`00000000 fffffa80`08f924b0 fffff8a0`07e74f20 00000000`00000001 : nt!PnpProcessTargetDeviceEvent+0x4c fffff880`02f6fc50 fffff800`02a87961 : fffff800`02ce6008 fffff8a0`08021a50 fffff800`02c1f5f8 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x58ffb fffff880`02f6fcb0 fffff800`02d1ec06 : 000007fe`fe62b62e fffffa80`0703a040 00000000`00000080 fffffa80`063fd040 : nt!ExpWorkerThread+0x111 fffff880`02f6fd40 fffff800`02a58c26 : fffff880`02e88180 fffffa80`0703a040 fffff880`02e93040 fffff800`02d32af1 : nt!PspSystemThreadStartup+0x5a fffff880`02f6fd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb SYMBOL_NAME: PxHlpa64+8c34 FOLLOWUP_NAME: MachineOwner MODULE_NAME: PxHlpa64 IMAGE_NAME: PxHlpa64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a0de1ea FAILURE_BUCKET_ID: X64_0xc9_224_VRF_PxHlpa64+8c34 BUCKET_ID: X64_0xc9_224_VRF_PxHlpa64+8c34 Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:\a\Minidump\D M P\121510-20560-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 (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02a58000 PsLoadedModuleList = 0xfffff800`02c95e50 Debug session time: Wed Dec 15 17:11:44.340 2010 (UTC - 5:00) System Uptime: 0 days 0:00:37.322 Loading Kernel Symbols ............................................................... ................................................................ .................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C9, {224, fffff8800113fc34, fffff9800f356c10, 2} Unable to load image \SystemRoot\System32\Drivers\PxHlpa64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for PxHlpa64.sys *** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys Probably caused by : PxHlpa64.sys ( PxHlpa64+8c34 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9) The IO manager has caught a misbehaving driver. Arguments: Arg1: 0000000000000224, An IRP dispatch handler has returned a status that is inconsistent with the IRP's IoStatus.Status field. Arg2: fffff8800113fc34, The address in the driver's code where the error was detected. Arg3: fffff9800f356c10, IRP address. Arg4: 0000000000000002, Expected status code. Debugging Details: ------------------ BUGCHECK_STR: 0xc9_224 DRIVER_VERIFIER_IO_VIOLATION_TYPE: 224 FAULTING_IP: PxHlpa64+8c34 fffff880`0113fc34 53 push rbx FOLLOWUP_IP: PxHlpa64+8c34 fffff880`0113fc34 53 push rbx IRP_ADDRESS: fffff9800f356c10 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002f523dc to fffff80002ac8740 STACK_TEXT: fffff880`031843b8 fffff800`02f523dc : 00000000`000000c9 00000000`00000224 fffff880`0113fc34 fffff980`0f356c10 : nt!KeBugCheckEx fffff880`031843c0 fffff800`02f5c47a : fffff800`02f509f0 fffff880`0113fc34 fffff980`0f356c10 00000000`00000002 : nt!VerifierBugCheckIfAppropriate+0x3c fffff880`03184400 fffff800`02f5d3f3 : fffff880`0113fc34 fffffa80`09e35b18 00000000`00000002 00000000`ffffffff : nt!ViErrorFinishReport+0xda fffff880`03184450 fffff800`02f68759 : fffffa80`09e35a60 fffffa80`09e35a60 fffffa80`09e35b18 fffff880`01141a98 : nt!VfErrorReport4+0x83 fffff880`03184540 fffff800`02f68b63 : fffffa80`09e35a60 00000000`00000002 fffffa80`08b94030 fffff8a0`06aeb700 : nt!IovpCallDriver2+0x179 fffff880`031845a0 fffff800`02f6ec2e : fffff980`0f356c10 fffff980`0f356c10 00000000`00000002 fffffa80`08b94030 : nt!VfAfterCallDriver+0x353 fffff880`031845f0 fffff800`02f714da : fffff980`0f356f20 fffffa80`08b94030 fffffa80`08fa9b00 fffffa80`09e35a60 : nt!IovCallDriver+0x57e fffff880`03184650 fffff800`02f6ec16 : fffff980`0f356c10 00000000`00000002 fffffa80`08fa9b00 fffffa80`09e2a950 : nt!ViFilterDispatchPnp+0xea fffff880`03184680 fffff880`00f1393c : fffff980`0f356f68 00000000`00000000 fffffa80`08fa6b60 fffffa80`09e2a950 : nt!IovCallDriver+0x566 fffff880`031846e0 fffff880`00f0c2ce : 00000000`00000001 fffff880`031847f0 fffff880`03184700 fffffa80`08fa6b00 : Wdf01000!FxPkgFdo::ProcessRemoveDeviceOverload+0x74 fffff880`03184710 fffff880`00f0add6 : fffffa80`08c10b02 00000000`00000002 00000000`00000000 fffffa80`08fa6b60 : Wdf01000!FxPkgPnp::_PnpRemoveDevice+0x126 fffff880`03184780 fffff880`00eda245 : fffff980`0f356c10 fffff980`0f356c10 fffffa80`08fa8e20 fffffa80`08fa8e20 : Wdf01000!FxPkgPnp::Dispatch+0x1b2 fffff880`031847f0 fffff880`00eda14b : fffff880`031848d8 fffff980`0f356c10 00000000`00000002 fffffa80`08fa8e20 : Wdf01000!FxDevice::Dispatch+0xa9 fffff880`03184820 fffff800`02f6ec16 : fffff980`0f356c10 00000000`00000002 fffffa80`08fa8e20 fffff880`03184978 : Wdf01000!FxDevice::DispatchWithLock+0x93 fffff880`03184860 fffff800`02d34519 : fffffa80`08fa8e20 00000000`c00000bb fffff880`03184978 fffffa80`09deaba0 : nt!IovCallDriver+0x566 fffff880`031848c0 fffff800`02eb2831 : fffffa80`08fabb70 00000000`00000000 fffffa80`08fab8a0 00000000`00000801 : nt!IopSynchronousCall+0xc5 fffff880`03184930 fffff800`02bc9bf3 : fffff8a0`02a77770 fffff8a0`02a77770 00000000`00000000 00000000`00000000 : nt!IopRemoveDevice+0x101 fffff880`031849f0 fffff800`02eb2384 : fffffa80`08fab8a0 00000000`00000000 00000000`00000002 00000000`00000000 : nt!PnpRemoveLockedDeviceNode+0x1a3 fffff880`03184a40 fffff800`02eb2490 : 00000000`00000000 fffff8a0`06c54101 fffff8a0`031d30d0 ffffca11`7e74faad : nt!PnpDeleteLockedDeviceNode+0x44 fffff880`03184a70 fffff800`02f42984 : 00000000`00000002 00000000`00000000 fffffa80`08f26c80 fffff8a0`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0 fffff880`03184ae0 fffff800`02f42fdc : fffff880`00000000 00000000`00010200 fffff880`03184c00 00000000`00000000 : nt!PnpProcessQueryRemoveAndEject+0xc34 fffff880`03184c20 fffff800`02e2e0dc : 00000000`00000000 fffffa80`09d7c630 fffff8a0`06c494e0 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c fffff880`03184c50 fffff800`02ad5961 : fffff800`02d34008 fffff8a0`06c54190 fffff800`02c6d5f8 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x58ffb fffff880`03184cb0 fffff800`02d6cc06 : 00000000`00000000 fffffa80`0705b040 00000000`00000080 fffffa80`063e4040 : nt!ExpWorkerThread+0x111 fffff880`03184d40 fffff800`02aa6c26 : fffff880`03088180 fffffa80`0705b040 fffff880`03093040 fffff8a0`0012e000 : nt!PspSystemThreadStartup+0x5a fffff880`03184d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb SYMBOL_NAME: PxHlpa64+8c34 FOLLOWUP_NAME: MachineOwner MODULE_NAME: PxHlpa64 IMAGE_NAME: PxHlpa64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a0de1ea FAILURE_BUCKET_ID: X64_0xc9_224_VRF_PxHlpa64+8c34 BUCKET_ID: X64_0xc9_224_VRF_PxHlpa64+8c34 Followup: MachineOwner --------- DRIVERS:
Code:
start end module name fffff880`00f56000 fffff880`00fad000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`02ce6000 fffff880`02d70000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`043d3000 fffff880`043e9000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0) fffff880`0405d000 fffff880`04072000 amdppm amdppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`00c35000 fffff880`00c40000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`00ddb000 fffff880`00de4000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00c00000 fffff880`00c2a000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118) fffff880`04802000 fffff880`04ff7000 atikmdag atikmdag.sys Tue Oct 26 22:29:53 2010 (4CC78EA1) fffff880`04072000 fffff880`040bd000 atikmpag atikmpag.sys Tue Oct 26 22:14:23 2010 (4CC78AFF) fffff880`019aa000 fffff880`019b1000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`011db000 fffff880`011ec000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`070f9000 fffff880`07117000 bowser bowser.sys Mon Jul 13 19:23:50 2009 (4A5BC206) fffff960`00600000 fffff960`00627000 cdd cdd.dll unavailable (00000000) fffff880`071d6000 fffff880`071f3000 cdfs cdfs.sys Mon Jul 13 19:19:46 2009 (4A5BC112) fffff880`0194a000 fffff880`01974000 cdrom cdrom.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`00d01000 fffff880`00dc1000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D) fffff880`018e2000 fffff880`01912000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00ca3000 fffff880`00d01000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`01000000 fffff880`01073000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`043c3000 fffff880`043d3000 CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`071cd000 fffff880`071d6000 cpuz134_x64 cpuz134_x64.sys Fri Jul 09 07:16:58 2010 (4C37052A) fffff880`06519000 fffff880`06527000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`01859000 fffff880`018dc000 csc csc.sys Mon Jul 13 19:24:26 2009 (4A5BC22A) fffff880`02cc3000 fffff880`02ce1000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200) fffff880`02cb4000 fffff880`02cc3000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`0121b000 fffff880`01231000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`064a6000 fffff880`064c8000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5) fffff880`06527000 fffff880`06533000 dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`0653e000 fffff880`06551000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`06533000 fffff880`0653e000 dump_msahci dump_msahci.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`0656c000 fffff880`06578000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574) fffff880`040bd000 fffff880`041b1000 dxgkrnl dxgkrnl.sys Thu Oct 01 21:00:14 2009 (4AC5509E) fffff880`041b1000 fffff880`041f7000 dxgmms1 dxgmms1.sys Mon Jul 13 19:38:32 2009 (4A5BC578) fffff880`01123000 fffff880`01137000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`010d7000 fffff880`01123000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`01211000 fffff880`0121b000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`00c40000 fffff880`00c7a000 fvevol fvevol.sys Fri Sep 25 22:34:26 2009 (4ABD7DB2) fffff880`01599000 fffff880`015e3000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164) fffff800`02a0f000 fffff800`02a58000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`04000000 fffff880`04024000 HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5) fffff880`04576000 fffff880`045d2000 HdAudio HdAudio.sys Mon Jul 13 20:06:59 2009 (4A5BCC23) fffff880`064dc000 fffff880`064f5000 HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD) fffff880`064f5000 fffff880`064fd080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9) fffff880`064ce000 fffff880`064dc000 hidusb hidusb.sys Mon Jul 13 20:06:22 2009 (4A5BCBFE) fffff880`07031000 fffff880`070f9000 HTTP HTTP.sys Mon Jul 13 19:22:16 2009 (4A5BC1A8) fffff880`01412000 fffff880`0141b000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff880`04479000 fffff880`04488000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`0650b000 fffff880`06519000 kbdhid kbdhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff800`00bbc000 fffff800`00bc6000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`04499000 fffff880`044dc000 ks ks.sys Wed Mar 03 23:32:25 2010 (4B8F37D9) fffff880`013da000 fffff880`013f4000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156) fffff880`0156e000 fffff880`01599000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4) fffff880`064c8000 fffff880`064cd200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93) fffff880`065ca000 fffff880`065df000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`06586000 fffff880`065a9000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295) fffff880`00c82000 fffff880`00c8f000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65) fffff880`06578000 fffff880`06586000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C) fffff880`04488000 fffff880`04497000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`064fe000 fffff880`0650b000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`00dc1000 fffff880`00ddb000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`01974000 fffff880`019a1000 MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0) fffff880`07aea000 fffff880`07afa000 MpNWMon MpNWMon.sys Sat Mar 20 01:58:00 2010 (4BA463E8) fffff880`07117000 fffff880`0712f000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79) fffff880`0712f000 fffff880`0715c000 mrxsmb mrxsmb.sys Sat Feb 27 02:52:19 2010 (4B88CF33) fffff880`0715c000 fffff880`071aa000 mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C) fffff880`071aa000 fffff880`071cd000 mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A) fffff880`00c2a000 fffff880`00c35000 msahci msahci.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`01812000 fffff880`0181d000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00fb6000 fffff880`00fc0000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`01143000 fffff880`011a1000 msrpc msrpc.sys Mon Jul
I have a question. I posted on the OCZ board to see if there was a test to detemine if the SSD was the problem. They are suggesting that I increase the voltage on the South Bridge. That is not something I would really want to do, but if I have to.... What do you guys think?
BTW, that was from a member of the OCZ Staff.
Increasing the voltage on the southbridge would increase power to the hard drive controller, if that's what they are thinking. I *highly* doubt the problem is being caused by insufficient power to Southbridge, but I guess anything is possible.
You might give that a try, but be careful not to give it too much of an increase.
I'd say the PSU is an object of suspicion here; a cheap PSU can cause BSODs and other failures, even though it delivers enough juice most of the time. Do you have a better one you can try? If not, I suggest that you purchase one from a store with a good return policy.
Also, we might just wait to see if removing that driver did the trick as well; have you gotten any BSODs since then?
Jonathan, Here is the file you requested. I have posted it before but not recently.
Attachment 123953
This might be long but... I do not disagree with you about the PSU, I know it is junk. But I am thinking more about the MB. Here is why.
According to the MB specs. It will support 16GB, 4GB in each slot. It supports DDR3 2000(OC), 1600(OC), 1333, and 1066.
I have 4x4GB sticks of DDR3-1333, one in each slot. When I first ram memtest I got errors on slots 3&4. I removed stick 4 and got another error. I removed stick 3 and ran 7 passes with no errors. I removed all of the ram. I ran stick3 in slot 1 with no errors. I then ran stick 2 in slot 3 with no errors, I ran sticks 3&4 in slots 1&2 with no errors. At this time I am running stick 3 in slot1 and stick 2 in slot 2. I have run the test twice for 7 passes once hot and once cold. No errors each time. What that looks like to me is that alone, all slots are good. But if you have 1&2 slots populated, 3&4 will show errors. You tell me if I am wrong. I have spent many entire days between memtest, prime and furmark running tests.
Another thing I noticed. And I apologize but I don't know which one I have. But there were 2 types of 1055T processors made-95W and 125W. According to Cupid HW monitor my CPU is pulling 140W. I don't know if that is an error by Cupid-as the 6 core processors are relatively new. But, everything in bios is at default levels. I only changed the display screen to see POST, The boot order, and changed the raid mode to AHCI ( that is the only option to put the SATA ports into AHCI). And no I am not running raid, that was just the only way I could change it.
Everything else is set to default. I can post the results of cup-z and cupid HW if you like.
Those are my thoughts as well as the concern that I am not confident I can do the work to replace the PSU or MB, or probably both. If I have to replace the MB I am sure I will replace the PSU.
You did a very good job on the Memtest diagnostics; that took a lot of patience!
Did you try running sticks 3&4 in slots 3&4?
Also, try putting all the sticks in, and increasing the RAM voltage a little bit.
Finally, could you post screenshots of the SPD and Memory tabs of CPU-Z?
CPUID - System & hardware benchmark, monitoring, reporting
Attachment 123960
Attachment 123961
My Ram is rated 9-9-9-24 1.5v
If it helps, these are my readings in BIOS Cell Menu and HW Monitor
Attachment 123982
BTW, Core temp monitior on my desktop says 31�C.
Try increasing the RAM voltages to 1.65v. It should be under Cell Menu.
This page might come in handy for you: MSI USA – Computer, Laptop, Notebook, Desktop, Mainboard, Graphics and more
My bios looks nothing like the one from your link. However, I did get in there and the dram frequency is set to auto. I tried to change it to i.6 and it switched back to auto and said auto was 1.6. I'll try again, but I hope 'dram frequency' is what you are referring to. I still have verifier running.
O.K. I changed Dram Voltage to 1.651. However Speccy and CPU z still show 1.5. I went back into BIOS and it said 1.651.
Let's just cross our fingers now, and hope the BSODs stop.
Thanks Jonathan, but I've tried the crossing fingers thing several times lately but I still BSOD'd. Maybe it will work this time.
I just had 2 more bsods, but these were my fault. I was trying to update my bios when the crash occurred.
Attachment 124009
Attachment 124010
Honestly, I do suspect a motherboard problem now. I guess it's up to you; replace the PSU and motherboard, whichever is cheapest/easiest. If neither are under warranty, or both are, replace the motherboard first. If only one is under warranty, try to get that replaced first.
Jonathan, I tend to agree with you. The MB is under warranty, but from what I have heard, MSI will be difficult to deal with and a minimum 6 week turn around time. I'll Replace the PSU in any case. The PSU is not worth RMA. I hope you or someone will help me out on this.
I am thinking about buying a new MB and PSU. What brand MB is easiest to update bios? It is a nightmare with MSI. After you update it you have to go inside the case, move the jumpers to clear CMOS, then hope it works. Not good for a normal user. Asrock claims to make it easy from within bios I dont know.
I was thinking about this PSU CORSAIR HX Series CMPSU-650HX 650W Newegg.com - CORSAIR HX Series CMPSU-650HX 650W ATX12V v2.2 / EPS12V 2.91 SLI Ready 80 PLUS BRONZE Certified Modular Active PFC Power Supply
Will this work in a rosewill Challanger case?
Yes, that ATX PSU will work great in a ATX case. And it appears to be a very good PSU as well!
I have an Asrock motherboard; all I have to do to update the BIOS is run the file I download; it requires one reboot. I know Asus boards are the same way, but I don't know about anything else.
I wouldn't base my decision of what motherboard to get on how easy it is to update the BIOS, though. Flashing the BIOS is something most people never do; it's one of the riskier and least helpful procedures most of the time. If you ever encountered a situation where you needed to update the BIOS, you wouldn't mind the hassle.
If I RMA my MB or buy a new one will that mean I have to purchase a new OS? Mine is an OEM from the guy who put my system together. I understand that they go by the s# of the MB>
I believe OEM keys are tied to the motherboard, unfortunately. You probably won't have a problem, though I can't guarantee anything. If you replace the motherboard with an identical one, you will maximize your chances of success there.
Well, after over a week I had another BSOD last night. This time it has made the computer not want to start. It will still post as normal but then sit tere with a black screen for several minutes. Eventually it usually starts. That is rather uncommon for an SSD with a 38 second boot time. I went into bios and set everything to default, have run scannow and checkdisk with no reports of problems. I ran startup repair 3 times and the diagnostic tool in the installation disk. I am trying to get up the money and the nerve to replace the MB and PSU. Here are the usual folders.
Attachment 127896
Attachment 127897
I just had another.
Attachment 127898
BTW, I don't know if it means anything but in the past when I ran diskpart the SSD was always listed as disk 2, now it is disk 3.
I see nothing wrong from a software side, and no clues in the dumps.
Could you get your hands on a different hard drive to install to?
A tip for hardware: if you suspect a bad part, shop around for stores with good return policies. You can purchase a new PSU, for instance, and return it if it doesn't help. Just be sure to read the fine print!
I don't know if it will work, but I just applied for an RMA on my MB. I am also going to buy a 650W Corsair PSU if I get the RMA. Then I am just going to pray that I can put it together. I can't afford to pay someone.
Also, the startup repair I did must have helped. Startup is much better now. Will probably buy the PSU from Newegg or Amazon.
Did you have some indication that my HD was the problem. I have run all of the diagnostics from the respective mfgrs and all passed. But, because you thought it necessary, I have disconnected my SSD and installed on my WD1002FAEX. - that is not fun - fast is fun.
We know this is a hardware problem; we just need to figure out what. Hard drive is one of the main components we must check.
Jonathan, we now know it was not my SSD. I am on the Western Digital now.
Attachment 128372
Carry on with the RMA or replacement of the other parts; have you run Prime95 yet though?
http://www.sevenforums.com/tutorials...t-prime95.html
yes, i ran prime and furmark.
I don't know why I keep posting these, I guess one will eventually show the reason. This was on my SSD after a secure erase and clean install. Am waiting to hear from MSI on the RMA. Am also going to get a new PSU. If that does not solve the problem, I'll sell you the computer.
Attachment 128488
Yeah, there is not anything more to be learned from the dumps. You can still post them if you like, but I can't use them to help. It is clearly a hardware problem.
Jonathan, you will be pleased to know that my RMA was approved and I sent my MB in today. I am also going to purchase a corsair 650w PSU. It was not hard taking it out, I just hope I can put it back together. I have never done this before so it is a challenge. I like challenges though. I may be calling on you or someone for help.
BTW: the would not let me give you a rep. But I tried. I owe you one.
Great, good job. Don't hesitate to post at all, we are here to help.
A little tip: use an anti-static strap when installing the board, or at least touch a metal part of the case frequently to avoid zapping the motherboard.
Jonathan, I just wanted to thank you again for all of your help. Maybe in a couple of weeks I will be writing you on my fixed computer. I'll let you know how it goes. At this point it is almost like building a new computer.
Thanks again,
Steve
Thanks for the report Steve. I appreciate the update!
Jonathan, Just wanted you to know that I received my Motherboard yesterday. I also bought a Corsair 650HX, a coolermaster TX3, and another side fan for my case. I have the HS with 2 92mm fans in push/pull. It is together now and so far seems to be ok.
I also wanted you to know that I am rather proud of myself as this was my first build.
Thanks so much for all of your help, I don't know what I would have done without you. It is people like you that makes this forum the best on the net. Thanks very much.
Steve
Well glad to hear that; good job on the build! When I built my rig (still my main machine, check my system specs), I was fortunate that everything went smoothly. When problems arose, though, I can imagine you were wondering what you did wrong!
I never said nothing went wrong. I had to reseat the HSF at least 3 times. When I first started up I was at idle 60�C, I am now idleing at 24�. Wiring was a nightmare. There is absolutely no room to wire in my case! Glad I got a modular PSU. It's bad enough with that. Next case I buy- I'll be able to put my lawnchair in there so I can watch.�� Quote: Originally Posted by Jonathan_King
Well glad to hear that; good job on the build! When I built my rig (still my main machine, check my system specs), I was fortunate that everything went smoothly. When problems arose, though, I can imagine you were wondering what you did wrong!
Thanks again. But I may have to brag some.For a month I had to listen to my wife tell me I didn't know what I was doing and that I was going to ruin a new computer. Secretly, I'm hoping she was wrong - time will tell.
I have a unique solution to the "cable management" problem:
Attachment 135096
Apologies for the poor quality, I used my webcam, in a dim room.
How did you get a picture of my case?
LOL, cabling never was my thing! I just keep an eye on my temperatures every now and then; if the chips are not overheating, I guess it's not a big problem.
I know you didn't want to hear from me again. But, I had another BSOD. I have run prime95 and memtest86. I have rma'd my MB and bought a new PSU. Not Sure what the problem is. I attached the info you will request. The jcgriff file is from the previous bsods as well as tonights. the previous ones are from before the RMA.
Attachment 137153
Attachment 137154
Sorry I had to bother you again.
Hello Steve,
These drivers need to be updated....
Quote:tifsfilt.sys Thu Aug 30 00:37:29 2007 - Acronis True Image Filter
Uninstall or purchase a new copy (Backup software for data backup and disaster recovery in Windows and Linux - Acronis)
timntr.sys Thu Aug 30 00:38:23 2007 - Acronis True Image Backup Archive Explorer
See Above
tdrpman.sys Tue Nov 13 02:36:33 2007 - Acronis Try&Decide and Restore Points Volume Filter Driver
See Above
snapman.sys Thu Nov 22 21:19:33 2007 - Acronis True Image Snapshot Manager driver
See Above
PxHlpa64.sys Sat May 16 09:43:06 2009 - A component of many CD/DVD programs
Rename this driver to find the CD/DVD program - see note below
ALSysIO64.sys Mon Apr 20 07:41:04 2009 - CoreTemp
Core Temp�� Note
Go to C:\Windows\System32\drivers and rename PxHlpa64.sys to PxHlpa64.BAK. This will break your CD/DVD program, but can easily be renamed after we've finished.
Regards....
Dean
BSOD Bugcheck Summary:
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {ffffd8a003840708, 0, fffff800031ab788, 7} Could not read faulting driver name Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+218 ) Followup: MachineOwner --------- 2: 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: ffffd8a003840708, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff800031ab788, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000007, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031070e0 ffffd8a003840708 FAULTING_IP: nt!CmpKcbCacheLookup+218 fffff800`031ab788 418b4710 mov eax,dword ptr [r15+10h] MM_INTERNAL_CODE: 7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: notepad.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff8800ac11fb0 -- (.trap 0xfffff8800ac11fb0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000050 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800031ab788 rsp=fffff8800ac12140 rbp=fffff8a000097d8f r8=0000000000000002 r9=0000000000000000 r10=0000000000000000 r11=fffff8800ac122d8 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!CmpKcbCacheLookup+0x218: fffff800`031ab788 418b4710 mov eax,dword ptr [r15+10h] ds:0b04:00000000`00000010=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002f4e849 to fffff80002ecf740 STACK_TEXT: fffff880`0ac11e48 fffff800`02f4e849 : 00000000`00000050 ffffd8a0`03840708 00000000`00000000 fffff880`0ac11fb0 : nt!KeBugCheckEx fffff880`0ac11e50 fffff800`02ecd82e : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`0111552d : nt! ?? ::FNODOBFM::`string'+0x40e0b fffff880`0ac11fb0 fffff800`031ab788 : fffff8a0`00010180 00000000`e9fe1463 fffff880`0ac126c4 fffff800`031a7876 : nt!KiPageFault+0x16e fffff880`0ac12140 fffff800`031aad08 : fffff880`0ac122d8 fffff880`00000004 fffff880`0ac126c8 fffff880`0ac126e0 : nt!CmpKcbCacheLookup+0x218 fffff880`0ac12230 fffff800`031a8f61 : fffff8a0`02592a10 fffff880`0ac126e0 fffff880`0ac12718 fffff880`0ac12700 : nt!CmpBuildHashStackAndLookupCache+0x328 fffff880`0ac12610 fffff800`031c8e84 : fffff800`031a8cc0 00000000`00000000 fffffa80`0cdf3640 fffff880`02ce5401 : nt!CmpParseKey+0x2a1 fffff880`0ac128e0 fffff800`031cde4d : fffffa80`0cdf3640 fffff880`0ac12a40 00000000`00000040 fffffa80`0caa8270 : nt!ObpLookupObjectName+0x585 fffff880`0ac129e0 fffff800`031acdcc : 00000000`10160b00 00000000`00000000 fffff8a0`02592a01 fffff880`0ac12aa8 : nt!ObOpenObjectByName+0x1cd fffff880`0ac12a90 fffff800`031aef0f : 00000000`0027b0e0 00000000`00020019 00000000`0027b168 00000000`00000000 : nt!CmOpenKey+0x28a fffff880`0ac12be0 fffff800`02ece993 : 00000000`00000000 00000000`00000000 00000000`00da7a01 ffffffff`c0000034 : nt!NtOpenKeyEx+0xf fffff880`0ac12c20 00000000`77150caa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0027b078 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77150caa STACK_COMMAND: kb FOLLOWUP_IP: nt!CmpKcbCacheLookup+218 fffff800`031ab788 418b4710 mov eax,dword ptr [r15+10h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!CmpKcbCacheLookup+218 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0x50_nt!CmpKcbCacheLookup+218 BUCKET_ID: X64_0x50_nt!CmpKcbCacheLookup+218 Followup: MachineOwner --------- 2: kd> lmtsmn start end module name fffff880`00f83000 fffff880`00fda000 ACPI ACPI.sys Tue Jul 14 11:19:34 2009 (4A5BC106) fffff880`02c00000 fffff880`02c8a000 afd afd.sys Tue Jul 14 11:21:40 2009 (4A5BC184) fffff880`043be000 fffff880`043d4000 AgileVpn AgileVpn.sys Tue Jul 14 12:10:24 2009 (4A5BCCF0) fffff880`07ba3000 fffff880`07bab000 ALSysIO64 ALSysIO64.sys Mon Apr 20 07:41:04 2009 (49EB7E50) fffff880`050bb000 fffff880`050cf000 amdiox64 amdiox64.sys Fri Feb 19 04:17:53 2010 (4B7D5A21) fffff880`041b4000 fffff880`041c9000 amdppm amdppm.sys Tue Jul 14 11:19:25 2009 (4A5BC0FD) fffff880`00ddc000 fffff880`00de7000 amdxata amdxata.sys Wed May 20 05:56:59 2009 (4A12F2EB) fffff880`07a71000 fffff880`07a7c000 asyncmac asyncmac.sys Tue Jul 14 12:10:13 2009 (4A5BCCE5) fffff880`00d9e000 fffff880`00da7000 atapi atapi.sys Tue Jul 14 11:19:47 2009 (4A5BC113) fffff880`00da7000 fffff880`00dd1000 ataport ataport.SYS Tue Jul 14 11:19:52 2009 (4A5BC118) fffff880`04804000 fffff880`04ff9000 atikmdag atikmdag.sys Wed Oct 27 15:29:53 2010 (4CC78EA1) fffff880`042c8000 fffff880`04313000 atikmpag atikmpag.sys Wed Oct 27 15:14:23 2010 (4CC78AFF) fffff880`02d0e000 fffff880`02d15000 Beep Beep.SYS Tue Jul 14 12:00:13 2009 (4A5BCA8D) fffff880`040a1000 fffff880`040b2000 blbdrive blbdrive.sys Tue Jul 14 11:35:59 2009 (4A5BC4DF) fffff880`03cdf000 fffff880`03cfd000 bowser bowser.sys Tue Jul 14 11:23:50 2009 (4A5BC206) fffff960`00670000 fffff960`00697000 cdd cdd.dll Thu May 20 07:48:26 2010 (4BF4408A) fffff880`02caa000 fffff880`02cd4000 cdrom cdrom.sys Tue Jul 14 11:19:54 2009 (4A5BC11A) fffff880`00cc4000 fffff880`00d84000 CI CI.dll Tue Jul 14 13:32:13 2009 (4A5BE01D) fffff880`00c00000 fffff880`00c30000 CLASSPNP CLASSPNP.SYS Tue Jul 14 11:19:58 2009 (4A5BC11E) fffff880`00c66000 fffff880`00cc4000 CLFS CLFS.SYS Tue Jul 14 11:19:57 2009 (4A5BC11D) fffff880`01000000 fffff880`01073000 cng cng.sys Tue Jul 14 11:49:40 2009 (4A5BC814) fffff880`043ae000 fffff880`043be000 CompositeBus CompositeBus.sys Tue Jul 14 12:00:33 2009 (4A5BCAA1) fffff880`03db3000 fffff880`03dbc000 cpuz133_x64 cpuz133_x64.sys Tue May 11 21:58:57 2010 (4BE92A61) fffff880`03dbc000 fffff880`03dc5000 cpuz134_x64 cpuz134_x64.sys Fri Jul 09 23:16:58 2010 (4C37052A) fffff880`068be000 fffff880`068cc000 crashdmp crashdmp.sys Tue Jul 14 12:01:01 2009 (4A5BCABD) fffff880`04000000 fffff880`04083000 csc csc.sys Tue Jul 14 11:24:26 2009 (4A5BC22A) fffff880`04083000 fffff880`040a1000 dfsc dfsc.sys Tue Jul 14 11:23:44 2009 (4A5BC200) fffff880`0417f000 fffff880`0418e000 discache discache.sys Tue Jul 14 11:37:18 2009 (4A5BC52E) fffff880`01800000 fffff880`01816000 disk disk.sys Tue Jul 14 11:19:57 2009 (4A5BC11D) fffff880`0503d000 fffff880`0505f000 drmk drmk.sys Tue Jul 14 13:01:25 2009 (4A5BD8E5) fffff880`068cc000 fffff880`068d8000 dump_dumpata dump_dumpata.sys Tue Jul 14 11:19:47 2009 (4A5BC113) fffff880`068e3000 fffff880`068f6000 dump_dumpfve dump_dumpfve.sys Tue Jul 14 11:21:51 2009 (4A5BC18F) fffff880`068d8000 fffff880`068e3000 dump_msahci dump_msahci.sys Tue Jul 14 12:01:01 2009 (4A5BCABD) fffff880`068f6000 fffff880`06902000 Dxapi Dxapi.sys Tue Jul 14 11:38:28 2009 (4A5BC574) fffff880`044bf000 fffff880`045b3000 dxgkrnl dxgkrnl.sys Fri Oct 02 14:00:14 2009 (4AC5509E) fffff880`045b3000 fffff880`045f9000 dxgmms1 dxgmms1.sys Tue Jul 14 11:38:32 2009 (4A5BC578) fffff880`0113c000 fffff880`01150000 fileinfo fileinfo.sys Tue Jul 14 11:34:25 2009 (4A5BC481) fffff880`010f0000 fffff880`0113c000 fltmgr fltmgr.sys Tue Jul 14 11:19:59 2009 (4A5BC11F) fffff880`01211000 fffff880`0121b000 Fs_Rec Fs_Rec.sys Tue Jul 14 11:19:45 2009 (4A5BC111) fffff880`011ba000 fffff880`011f4000 fvevol fvevol.sys Sat Sep 26 14:34:26 2009 (4ABD7DB2) fffff880`015ab000 fffff880`015f5000 fwpkclnt fwpkclnt.sys Tue Jul 14 11:21:08 2009 (4A5BC164) fffff800`02e16000 fffff800`02e5f000 hal hal.dll Tue Jul 14 13:27:36 2009 (4A5BDF08) fffff880`04400000 fffff880`04424000 HDAudBus HDAudBus.sys Tue Jul 14 12:06:13 2009 (4A5BCBF5) fffff880`05169000 fffff880`051c5000 HdAudio HdAudio.sys Tue Jul 14 12:06:59 2009 (4A5BCC23) fffff880`06910000 fffff880`06929000 HIDCLASS HIDCLASS.SYS Tue Jul 14 12:06:21 2009 (4A5BCBFD) fffff880`06929000 fffff880`06931080 HIDPARSE HIDPARSE.SYS Tue Jul 14 12:06:17 2009 (4A5BCBF9) fffff880`06902000 fffff880`06910000 hidusb hidusb.sys Tue Jul 14 12:06:22 2009 (4A5BCBFE) fffff880`03c17000 fffff880`03cdf000 HTTP HTTP.sys Tue Jul 14 11:22:16 2009 (4A5BC1A8) fffff880`019f1000 fffff880`019fa000 hwpolicy hwpolicy.sys Tue Jul 14 11:19:22 2009 (4A5BC0FA) fffff880`0429c000 fffff880`042ab000 kbdclass kbdclass.sys Tue Jul 14 11:19:50 2009 (4A5BC116) fffff880`06932000 fffff880`06940000 kbdhid kbdhid.sys Tue Jul 14 12:00:20 2009 (4A5BCA94) fffff800`00bd5000 fffff800`00bdf000 kdcom kdcom.dll Tue Jul 14 13:31:07 2009 (4A5BDFDB) fffff880`05078000 fffff880`050bb000 ks ks.sys Thu Mar 04 17:32:25 2010 (4B8F37D9) fffff880`013e6000 fffff880`01400000 ksecdd ksecdd.sys Tue Jul 14 11:20:54 2009 (4A5BC156) fffff880`01460000 fffff880`0148b000 ksecpkg ksecpkg.sys Fri Dec 11 19:03:32 2009 (4B21E0B4) fffff880`0505f000 fffff880`05064200 ksthunk ksthunk.sys Tue Jul 14 12:00:19 2009 (4A5BCA93) fffff880`069b6000 fffff880`069cb000 lltdio lltdio.sys Tue Jul 14 12:08:50 2009 (4A5BCC92) fffff880`0695b000 fffff880`0697e000 luafv luafv.sys Tue Jul 14 11:26:13 2009 (4A5BC295) fffff880`00c45000 fffff880`00c52000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Tue Jul 14 13:29:09 2009 (4A5BDF65) fffff880`0694d000 fffff880`0695b000 monitor monitor.sys Tue Jul 14 11:38:52 2009 (4A5BC58C) fffff880`042ab000 fffff880`042ba000 mouclass mouclass.sys Tue Jul 14 11:19:50 2009 (4A5BC116) fffff880`06940000 fffff880`0694d000 mouhid mouhid.sys Tue Jul 14 12:00:20 2009 (4A5BCA94) fffff880`00d84000 fffff880`00d9e000 mountmgr mountmgr.sys Tue Jul 14 11:19:54 2009 (4A5BC11A) fffff880`02cd4000 fffff880`02d05000 MpFilter MpFilter.sys Wed Sep 15 12:19:28 2010 (4C901110) fffff880`07b7e000 fffff880`07b8e000 MpNWMon MpNWMon.sys Wed Sep 15 12:19:30 2010 (4C901112) fffff880`03cfd000 fffff880`03d15000 mpsdrv mpsdrv.sys Tue Jul 14 12:08:25 2009 (4A5BCC79) fffff880`03d15000 fffff880`03d42000 mrxsmb mrxsmb.sys Sat Feb 27 20:52:19 2010 (4B88CF33) fffff880`03d42000 fffff880`03d90000 mrxsmb10 mrxsmb10.sys Sat Feb 27 20:52:28 2010 (4B88CF3C) fffff880`03d90000 fffff880`03db3000 mrxsmb20 mrxsmb20.sys Sat Feb 27 20:52:26 2010 (4B88CF3A) fffff880`00dd1000 fffff880`00ddc000 msahci msahci.sys Tue Jul 14 12:01:01 2009 (4A5BCABD) fffff880`02d73000 fffff880`02d7e000 Msfs Msfs.SYS Tue Jul 14 11:19:47 2009 (4A5BC113) fffff880`00fe3000 fffff880`00fed000 msisadrv msisadrv.sys Tue Jul 14 11:19:26 2009 (4A5BC0FE) fffff880`0115c000 fffff880`011ba000 msrpc msrpc.sys Tue Jul 14 11:21:32 2009 (4A5BC17C) fffff880`04174000 fffff880`0417f000 mssmbios mssmbios.sys Tue Jul 14 11:31:10 2009 (4A5BC3BE) fffff880`019df000 fffff880`019f1000 mup mup.sys Tue Jul 14 11:23:45 2009 (4A5BC201) fffff880`014b9000 fffff880`015ab000 ndis ndis.sys Tue Jul 14 11:21:40 2009 (4A5BC184) fffff880`04200000 fffff880`0420c000 ndistapi ndistapi.sys Tue Jul 14 12:10:00 2009 (4A5BCCD8) fffff880`0420c000 fffff880`0423b000 ndiswan ndiswan.sys Tue Jul 14 12:10:11 2009 (4A5BCCE3) fffff880`05154000 fffff880`05169000 NDProxy NDProxy.SYS Tue Jul 14 12:10:05 2009 (4A5BCCDD) fffff880`02c93000 fffff880`02ca2000 netbios netbios.sys Tue Jul 14 12:09:26 2009 (4A5BCCB6) fffff880`02dba000 fffff880`02dff000 netbt netbt.sys Tue Jul 14 11:21:28 2009 (4A5BC178) fffff880`01400000 fffff880`01460000 NETIO NETIO.SYS Fri Apr 09 14:43:59 2010 (4BBE946F) fffff880`07b8e000 fffff880`07ba3000 NisDrvWFP NisDrvWFP.sys Wed Sep 15 12:20:25 2010 (4C901149) fffff880`02d7e000 fffff880`02d8f000 Npfs Npfs.SYS Tue Jul 14 11:19:48 2009 (4A5BC114) fffff880`04168000 fffff880`04174000 nsiproxy nsiproxy.sys Tue Jul 14 11:21:02 2009 (4A5BC15E) fffff800`02e5f000 fffff800`0343b000 nt ntkrnlmp.exe Sat Jun 19 16:16:41 2010 (4C1C44A9) fffff880`01243000 fffff880`013e6000 Ntfs Ntfs.sys Tue Jul 14 11:20:47 2009 (4A5BC14F) fffff880`02d05000 fffff880`02d0e000 Null Null.SYS Tue Jul 14 11:19:37 2009 (4A5BC109) fffff880`050e1000 fffff880`050fa000 nusb3hub nusb3hub.sys Thu Sep 30 17:00:03 2010 (4CA40B43) fffff880`0448a000 fffff880`044ba000 nusb3xhc nusb3xhc.sys Thu Sep 30 17:00:03 2010 (4CA40B43) fffff880`0121b000 fffff880`01241000 pacer pacer.sys Tue Jul 14 12:09:41 2009 (4A5BCCC5) fffff880`04391000 fffff880`043ae000 parport parport.sys Tue Jul 14 12:00:40 2009 (4A5BCAA8) fffff880`00e40000 fffff880`00e55000 partmgr partmgr.sys Tue Jul 14 11:19:58 2009 (4A5BC11E) fffff880`00e00000 fffff880`00e33000 pci pci.sys Tue Jul 14 11:19:51 2009 (4A5BC117) fffff880`00ec6000 fffff880`00ecd000 pciide pciide.sys Tue Jul 14 11:19:49 2009 (4A5BC115) fffff880`00fed000 fffff880`00ffd000 PCIIDEX PCIIDEX.SYS Tue Jul 14 11:19:48 2009 (4A5BC114) fffff880`01200000 fffff880`01211000 pcw pcw.sys Tue Jul 14 11:19:27 2009 (4A5BC0FF) fffff880`0624f000 fffff880`062f5000 peauth peauth.sys Tue Jul 14 13:01:19 2009 (4A5BD8DF) fffff880`05000000 fffff880`0503d000 portcls portcls.sys Tue Jul 14 12:06:27 2009 (4A5BCC03) fffff880`00c52000 fffff880`00c66000 PSHED PSHED.dll Tue Jul 14 13:32:23 2009 (4A5BE027) fffff880`01150000 fffff880`0115be00 PxHlpa64 PxHlpa64.sys Sat May 16 09:43:06 2009 (4A0DE1EA) fffff880`043d4000 fffff880`043f8000 rasl2tp rasl2tp.sys Tue Jul 14 12:10:11 2009 (4A5BCCE3) fffff880`0423b000 fffff880`04256000 raspppoe raspppoe.sys Tue Jul 14 12:10:17 2009 (4A5BCCE9) fffff880`04256000 fffff880`04277000 raspptp raspptp.sys Tue Jul 14 12:10:18 2009 (4A5BCCEA) fffff880`04277000 fffff880`04291000 rassstp rassstp.sys Tue Jul 14 12:10:25 2009 (4A5BCCF1) fffff880`04117000 fffff880`04168000 rdbss rdbss.sys Tue Jul 14 11:24:09 2009 (4A5BC219) fffff880`04291000 fffff880`0429c000 rdpbus rdpbus.sys Tue Jul 14 12:17:46 2009 (4A5BCEAA) fffff880`02d58000 fffff880`02d61000 RDPCDD RDPCDD.sys Tue Jul 14 12:16:34 2009 (4A5BCE62) fffff880`02d61000 fffff880`02d6a000 rdpencdd rdpencdd.sys Tue Jul 14 12:16:34 2009 (4A5BCE62) fffff880`02d6a000 fffff880`02d73000 rdprefmp rdprefmp.sys Tue Jul 14 12:16:35 2009 (4A5BCE63) fffff880`010ae000 fffff880`010e8000 rdyboost rdyboost.sys Tue Jul 14 11:34:34 2009 (4A5BC48A) fffff880`069cb000 fffff880`069e3000 rspndr rspndr.sys Tue Jul 14 12:08:50 2009 (4A5BCC92) fffff880`04424000 fffff880`0448a000 Rt64win7 Rt64win7.sys Thu Nov 11 19:35:36 2010 (4CDB8EB8) fffff880`06671000 fffff880`068bdf80 RTKVHD64 RTKVHD64.sys Tue Jul 06 22:05:16 2010 (4C32FFDC) fffff880`062f5000 fffff880`06300000 secdrv secdrv.SYS Thu Sep 14 01:18:38 2006 (4508052E) fffff880`04385000 fffff880`04391000 serenum serenum.sys Tue Jul 14 12:00:33 2009 (4A5BCAA1) fffff880`040cb000 fffff880`040e8000 serial serial.sys Tue Jul 14 12:00:40 2009 (4A5BCAA8) fffff880`01073000 fffff880`010ae000 snapman snapman.sys Thu Nov 22 21:19:33 2007 (47453B95) fffff880`019d7000 fffff880`019df000 spldr spldr.sys Tue May 12 04:56:27 2009 (4A0858BB) fffff880`07ae8000 fffff880`07b7e000 srv srv.sys Fri Aug 27 15:38:00 2010 (4C773318) fffff880`0633f000 fffff880`063a6000 srv2 srv2.sys Fri Aug 27 15:37:46 2010 (4C77330A) fffff880`06300000 fffff880`0632d000 srvnet srvnet.sys Fri Aug 27 15:37:24 2010 (4C7732F4) fffff880`044bc000 fffff880`044bd480 swenum swenum.sys Tue Jul 14 12:00:18 2009 (4A5BCA92) fffff880`01603000 fffff880`01800000 tcpip tcpip.sys Mon Jun 14 15:39:04 2010 (4C15A458) fffff880`0632d000 fffff880`0633f000 tcpipreg tcpipreg.sys Tue Jul 14 12:09:49 2009 (4A5BCCCD) fffff880`02dad000 fffff880`02dba000 TDI TDI.SYS Tue Jul 14 11:21:18 2009 (4A5BC16E) fffff880`01943000 fffff880`019d7000 tdrpman tdrpman.sys Tue Nov 13 02:36:33 2007 (473856E1) fffff880`02d8f000 fffff880`02dad000 tdx tdx.sys Tue Jul 14 11:21:15 2009 (4A5BC16B) fffff880`04103000 fffff880`04117000 termdd termdd.sys Tue Jul 14 12:16:36 2009 (4A5BCE64) fffff880`0697e000 fffff880`06995000 tifsfilt tifsfilt.sys Thu Aug 30 00:37:29 2007 (46D56889) fffff880`01837000 fffff880`018e7000 timntr timntr.sys Thu Aug 30 00:38:23 2007 (46D568BF) fffff960`004a0000 fffff960`004aa000 TSDDD TSDDD.dll unavailable (00000000) fffff880`0418e000 fffff880`041b4000 tunnel tunnel.sys Tue Jul 14 12:09:37 2009 (4A5BCCC1) fffff880`050cf000 fffff880`050e1000 umbus umbus.sys Tue Jul 14 12:06:56 2009 (4A5BCC20) fffff880`044ba000 fffff880`044bbf00 USBD USBD.SYS Tue Jul 14 12:06:23 2009 (4A5BCBFF) fffff880`04374000 fffff880`04385000 usbehci usbehci.sys Tue Jul 14 12:06:30 2009 (4A5BCC06) fffff880`050fa000 fffff880`05154000 usbhub usbhub.sys Tue Jul 14 12:07:09 2009 (4A5BCC2D) fffff880`04313000 fffff880`0431e000 usbohci usbohci.sys Tue Jul 14 12:06:30 2009 (4A5BCC06) fffff880`0431e000 fffff880`04374000 USBPORT USBPORT.SYS Tue Jul 14 12:06:31 2009 (4A5BCC07) fffff880`00e33000 fffff880`00e40000 vdrvroot vdrvroot.sys Tue Jul 14 12:01:31 2009 (4A5BCADB) fffff880`02d15000 fffff880`02d23000 vga vga.sys Tue Jul 14 11:38:47 2009 (4A5BC587) fffff880`02d23000 fffff880`02d48000 VIDEOPRT VIDEOPRT.SYS Tue Jul 14 11:38:51 2009 (4A5BC58B) fffff880`018e7000 fffff880`018f7000 vmstorfl vmstorfl.sys Tue Jul 14 11:42:54 2009 (4A5BC67E) fffff880`00e55000 fffff880`00e6a000 volmgr volmgr.sys Tue Jul 14 11:19:57 2009 (4A5BC11D) fffff880`00e6a000 fffff880`00ec6000 volmgrx volmgrx.sys Tue Jul 14 11:20:33 2009 (4A5BC141) fffff880`018f7000 fffff880`01943000 volsnap volsnap.sys Tue Jul 14 11:20:08 2009 (4A5BC128) fffff880`040e8000 fffff880`04103000 wanarp wanarp.sys Tue Jul 14 12:10:21 2009 (4A5BCCED) fffff880`02d48000 fffff880`02d58000 watchdog watchdog.sys Tue Jul 14 11:37:35 2009 (4A5BC53F) fffff880`00ed0000 fffff880`00f74000 Wdf01000 Wdf01000.sys Tue Jul 14 11:22:07 2009 (4A5BC19F) fffff880`00f74000 fffff880`00f83000 WDFLDR WDFLDR.SYS Tue Jul 14 11:19:54 2009 (4A5BC11A) fffff880`02c8a000 fffff880`02c93000 wfplwf wfplwf.sys Tue Jul 14 12:09:26 2009 (4A5BCCB6) fffff960`000f0000 fffff960`00400000 win32k win32k.sys Wed Oct 20 16:08:46 2010 (4CBE5D3E) fffff880`00fda000 fffff880`00fe3000 WMILIB WMILIB.SYS Tue Jul 14 11:19:51 2009 (4A5BC117) fffff880`06995000 fffff880`069b6000 WudfPf WudfPf.sys Tue Jul 14 12:05:37 2009 (4A5BCBD1) Unloaded modules: fffff880`07a00000 fffff880`07a71000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00071000 fffff880`01816000 fffff880`01824000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000E000 fffff880`01824000 fffff880`01830000 dump_pciidex Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000C000 fffff880`015f5000 fffff880`01600000 dump_msahci. Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000B000 fffff880`0148b000 fffff880`0149e000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00013000
Dean, I uninstalled Acronis (free version from Seagate - DiskWizzard), I renamed the driver you told me about. It was the driver to my CD/DVD player (Samsung SH S222A SB02). I downloaded the newest driver from Samsung. It said it could not find the DVD. In device manager I tried to update the driver but it said I had the current driver. I directed it to the downloaded driver and it said the same thing. I renamed the driver back so that the Samsung program could find it, but it would not update it. As far as coretemp. that must have been an old driver. I installed the newest version today, ver. 2.6 which is the newest. I didn't understand what you wanted me to do at Core Temp, I have the newest version. Should I rename that driver too?
I would uninstall Coretemp and find another one.
done. anything else? I don't know if you have been able to read through this thread, but This is becoming rediculous. I have run memtest at least 10 times in every config. (at 11 hours each test), I have run pime95 and Furmark. I have updated drivers RMA'd my Motherboard, bought a new Corsair PSU. I am really getting at the end of my rope. Would you like to buy a computer? Seriously, I don't know what to do. Maybe it will last until Bulldozer comes out. Then I can decide between bulldozer and the i7-2600K. The bad part is this computer is only 5 months old. If you have any words of wisdom, I sure would love to hear them. Jonathan has been through this with me and I can't say enough good things about him. He may have called you when he saw my bsod post
After uninstalling the programs, I have run CC Cleaner to clean the registry. Do you have any suggestions of a temp program. I have speedfan but was told to uninstall it the last go around. BTW, I still have the DVD Driver.
Try Realtemp
No more BSODs -yet. But, just in case it makes a difference. I had Western Digital's Acronis installed yesterday. It wasn't operating quite right so I uninstalled it and installed Seagate's version. Due to your suggestion, both are uninstalled now. I also installed 2 92mm fans on my CPU cooler and a 120mm in my case. I don't think that is the cause but... Also the PWM connection on my just replaced MB does not work, so 4 fans are connected to the PSU, 1 fan to the MB case fan connection (I only have one case fan header). I just wanted you to know in case you think it is relevant.
I may have done these myself. I just flashed my bios. Everything seemed to go OK. and I just removed 2 sticks of ram. After flashing bios reset CMOS set everything back to optimized defaults except boot order and set raid to ahci, No I don't run raid, but this is the only way to set the controllers to ahci. After that no problems in startup, just getting BSODs again.
Attachment 137967
Attachment 137968
And Another.
Attachment 138008
I've just had 2 within a few minutes of each other please help. I've tried 2 PSU's, RMA'd the MB and run prime and memtest, scannow and checkdisk and diagnostic programs from the HD manuf.
Attachment 138028
Attachment 138029
Make sure AHCI is enabled in Windows: AHCI : Enable in Windows 7 / Vista
Also, you can add multiple files to the zip folder; just drag all the other dump files into the zip folder, and then upload the single folder.
...Summary of the dumps:
Code:Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Sat Feb 12 10:37:26.837 2011 (UTC - 5:00) System Uptime: 0 days 0:04:20.227 Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+51d ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: firefox.exe FAILURE_BUCKET_ID: X64_0x3B_nt!ExAllocatePoolWithTag+51d SystemProductName = MS-7642 ��������������������������������������������������������������������������������������`` Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Sat Feb 12 10:32:08.101 2011 (UTC - 5:00) System Uptime: 0 days 0:07:24.490 Probably caused by : Ntfs.sys ( Ntfs!NtfsRestartIndexEnumeration+271 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: explorer.exe BUGCHECK_STR: 0x24 FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsRestartIndexEnumeration+271 SystemProductName = MS-7642 ��������������������������������������������������������������������������������������`` Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Sat Feb 12 10:23:37.953 2011 (UTC - 5:00) System Uptime: 0 days 0:01:04.342 Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a56 ) BUGCHECK_STR: 0x19_3 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe FAILURE_BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+a56 SystemProductName = MS-7642 ��������������������������������������������������������������������������������������`` Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Sat Feb 12 07:30:29.457 2011 (UTC - 5:00) System Uptime: 0 days 0:59:05.846 Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) BUGCHECK_STR: 0x1E_0 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e SystemProductName = MS-7642 ��������������������������������������������������������������������������������������`` Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Fri Feb 11 23:02:35.014 2011 (UTC - 5:00) System Uptime: 0 days 0:20:39.388 Probably caused by : ntkrnlmp.exe ( nt!CmpBuildHashStackAndLookupCache+2a5 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: svchost.exe FAILURE_BUCKET_ID: X64_0x3B_nt!CmpBuildHashStackAndLookupCache+2a5 SystemProductName = MS-7642 ��������������������������������������������������������������������������������������`` Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Fri Dec 24 02:02:45.018 2010 (UTC - 5:00) System Uptime: 0 days 0:56:34.031 Probably caused by : ndis.sys ( ndis!ndisOidRequestComplete+38c ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: svchost.exe FAILURE_BUCKET_ID: X64_0x3B_ndis!ndisOidRequestComplete+38c SystemProductName = MS-7642 ��������������������������������������������������������������������������������������``
Thank you Jonathan. Since my last post I have gone back to the previous version of BIOS. I have run memtest86 and prime with no errors. AHCI is enabled in bios. In my bios, I have to select the raid version to enable ahci even though I don't use raid. If you recall, I rma'd my MB and bought a new PSU (Corsair 650HX modular). I have again run the diagnostic programs from my hard drives without errors. I have run scannow and checkdisk. I have talked to technical support at MSI 3 times. They know less than me. I was told that my problem was I need a better processor. I told him that since I was running a PhenomII x6, what processor would he suggest. He hung up. Truthfully, I am at a loss. If you want all of the dump files together, let me know- I will gladly provide them. It is just that some of the files are from before I RMA'd the MB and some after. Let me know if you want them all or if you want me to sort them. And thanks for your help.
I just had another.
Attachment 138056
More. they are happening fater than I can post them here.
Attachment 138059
Attachment 138060
Attachment 138061
First, I will echo something Jonathan said earlier:
Software troubleshooting will get us nowhere at this stage.Yeah, there is not anything more to be learned from the dumps. You can still post them if you like, but I can't use them to help. It is clearly a hardware problem.
I had a look through the thread, I will just confirm - you have only had the PSU and Motherboard replaced?
Have you tried running Windows with only one stick of RAM? Just because the stress tests passed does not mean that your components aren't faulty.
No, I have not tried 1 stick. I was using 4x4GB sticks but have taken 2 of those sticks out now. I am only using 2 sticks. I can try 1 if you think it will help, but this board is supposed to be able to run 16GB. I think I have lost all confidence in this motherboard.
I would try one and if that doesn't work, swap it for one of the other four.
In your set up anyway the memory controller is on your Phenom II not your motherboard. Therefore with the types of memory issues you have been getting, if you get problems under all four sticks of RAM I would think that your CPU is faulty.
That's wonderful news.
OK, now I am running 1 stick of ram in dimm slot 1. Just want you to know I am trying everything I can. I think I could have bought a super computer for what I have spent on this one. a new CPU won't help matters any. But, I'll do what I have to.
I've been through it before, I ended up replacing CPU, Motherboard, RAM in one $500 shot to fix it. At least you have only bought a new PSU so far?
One stick does not work. So, I gues next I should try a different stick in another slot?
First try that stick in a different slot. If that fails too then try another stick in the slot it failed on.
I'll give it a try.
OK it's done. Same stick different slot.
So the stick now works on a different slot?
The stick worked in the sirst slot, It just BSOD'd. So, Following what I understood you to say, I took it out of that slot and put it in a different slot. It cleared CMOS but it is working so far. Did I understand you correctly?
Yes, that is what I intended. If you get another BSOD then swap it for another stick (same slot is fine).
OK, another BSOD. I took that stick of ram out and put different stick in. Is that correct? It does not sound like we are testing ram or slots. I presume we are testing the CPU somehow. Is that correct? If it is, how is this testing the CPU? I just want to learn about things.
Another BSOD. Is there any reason to try another stick?
Yes. If you still get BSODs no matter which slot the single stick is in, and no matter which single stick is in place, then it is very unlikely that the problem is your RAM (usually only one or two sticks are bad, not all four).Another BSOD. Is there any reason to try another stick?
We can use that with the fact that you have had the motherboard replaced (correct?) to conclude that the problem here is probably your CPU.
The third stick is in. And yes, I replaced the motherboard and the PSU. I do have another CPU. It is a PhenomIIx2, not quite the same as what is in here now, but if that's the problem we should be able to tell.
By all means, try the other CPU.
I need to order a few things from Newegg, I'll order it tomorrow then install the CPU.
To bring everyone up to date: had a bsod on the 3rd stick. Put the 4th stick in and immediately had another bsod. The order to Newegg has already been placed. But I'm sure I won't like the X2
I thought you already had a X2 ready? (at least that's what it sounded like from above).
I do. I just needed a few other things before I do it.
Just checking, because it wasn't my intention to have you buy a new CPU just yet, but if you already had that one around...
Thanks for looking out for me. I need all the help I can get.
OK guys, here's the deal. I guess I don't have another processor. I installed it this morning-got nothing, the monitor wouldn't even come on. I reinstalled it 3 more times - same thing. I thought it was a video problem. I uninstalled my video card-still nothing. I pluged it in DVI, HDMI and VGA still nothing. I reinstalled the original CPU and booted up the first time. So, I guess the CPU I thought I had is DOA. Now I have to reinstall the video card and find some way to buy a CPU. Any Suggestions?
I hope you guys haven't left me for dead. I was able to RMA the x2 CPU. Sent it off today. I have some new ram coming should be here Thursday. Any other suggestions or are you convinced it is the CPU?
I am not convinced at all. Given the previous history....Any other suggestions or are you convinced it is the CPU?
If I were you I would wait for the X2 replacement and test with that before getting the X6 replaced. While you are waiting you can use the new RAM to doublecheck that it isn't a RAM issue.
Thanks for the help and suggestions. I am still not sure about the MB and if it is the MB, I am not sure I want to try a third one. I know the CPU fan connector does not work and - just the way I think, if one thing doesn't work, how many other things are causing problems.
How sure are you the connector doesn't work? Have you tested it with multiple fans? Checked the BIOS to make sure it isn't disabled for whatever crazy reason?
If you are pretty sure, I would RMA the motherboard on that alone.
I got the ram in today and installed it. I don't think it is running at the correct speed though. It is G Skill F3-12800CL7D-4GBRM (2X2). The timings are 7-8-7-24 1.6V. I have set the timings as best I can. To enable you to set timings you have to change the dram timing modes. The options are DCT0,DCT1,Both. I put both. I think the problem is the FSB/Dram ratio. I don't know what it should be. My choices are 1:2, 1:2.66, 1:3.33 and 1:4. Any suggestions?
I am still getting BSODs. But it seems much better, just occasionally now. I have had none since the new ram, but it has only been in for a couple hours.
Attachment 138915
Attachment 138916
Just an update. Over 24 Hours and no BSOD.
That's an excellent sign. I have asked someone to come and have a look at your timings too, I will admit I know next to nothing about that area.Just an update. Over 24 Hours and no BSOD.
I had a BSOD yesterday. However, I had been 'playing' with bios settings. I reset everything to default settings only changing boot order and set to ahci. No problems since. Just an update.
Looks like you have done some thorough hardware testing.Thanks very much for the reply. I uninstalled driver verifier for Roxio and renamed the offending driver. The system would not start and went through startup repair. Then it rebooted. After reboot I uninstalled Roxio. So, we'll see what happens now.
As far as hardware- here is a brief list of what I have done copied from a previous thread about this.
so far I have:
1. Updated 2 drivers - the network driver from the manuf. website and the USB 3.0 (NEC) from MSI.
2. I have run prime95 and Furmark - Both passed.
3. I have run memtest 86 probably 7 times now. I have run it with 16GB installed which showed two bad sticks. I located and removed those sticks. I have run it both hot and cold with the remaining two sticks - 4 times all passed.
I have run one of the good sticks from a slot where a stick failed 7 passes - it passed.
I ran one stick alone that failed in one of the slots that passed and it passed. Those tests I ran yesterday. I am currently running just those two sticks. I have run memtest on those two sticks for 7 passes with no errors.
3 I have seatools from seagate and my Seagate HD passed both the SMART test and the short drive self test.
I have WinDig from Western Digital- I ran tests with it on my WD drive and it passed.
I have OCZ's toolbox and it reports no problems with my SSD. I also have crysralDiskmart disk info test. It reports the SSD as 100% healthy.
Those tests should cover most of the hardware problems except the PSU. My PSU is an 'el-Cheepo' but it seems to work. It is 600W which is probably much more than I need.
At this point I don't know ahat else to do. I have probably done a few things I haven't mentioned. I am beginning to think maybe software. But I have very little on this SSD-about 20GB on a 90GB drive including windows.
I have had problems with both windows explorer and ie explorer. Both crash several times daily. I am using Firefox at this point.
I have the free version of Macrium installed and it does not work correctly. I may uninstall that to see if it helps.
I have run scannow and checkdisk on every HD I have several times withoun any errors.
I have deleated every BSOD report I have. I had so many on my desktop I didn't know which was which. Most of them have been uploaded to these 2 threads.
BTW, I forgot to mention that on 12/9 I did a secure erase of my ssd and then a clean install of windows. I transferred
nothing except my Documents folder from the other installation. My Seagate is the Data drive. Most of my libraries are there.
Since then I have installed windows on the Western Digiital to eliminate problems with the SSD. I did this on 12/15.
If the problem is hardware, I don't know what it could be.
And, to anticipate your next question, I do not and have never OC'd.
When RAM passes memtest86+ it doesn't guaranty that it's 100% OK, it still might be causing problems. Memtest86+ is an indication that the RAM possibly not the cause, but the settings from CPUZ can show some possible setting adjustments.
I see that you have previously un-installed CoreTemp and Speedfan, were the temps normal? What temps where you running at with the system stressed?
If possible useCore Temp to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Go to your BIOS and tell us what the CPU, RAM and CPU integrated North Bridge (CPU-NB) voltages are.
You can get the actual CPU voltages from CPUZ CPU tab but, the other tabs show the recommended voltages not actual.
An 'el-Cheepo' PSU can cause all kinds of issues, you should consider a good quality brand with more power than you think you need, 650 to 750W should be enough. The more hardware attached the more power you will need.Already done.
Just noticed your PSU in system specs, the CORSAIR HX650W modular is a good PSU and shouldn't be causing you any problems.
First thing I noticed is that RAM appears to be for Intel CPUs and boards, they will sometimes run on AMD boards but are a known issue.I got the ram in today and installed it. I don't think it is running at the correct speed though. It is G Skill F3-12800CL7D-4GBRM (2X2). The timings are 7-8-7-24 1.6V. I have set the timings as best I can. To enable you to set timings you have to change the dram timing modes. The options are DCT0,DCT1,Both. I put both. I think the problem is the FSB/Dram ratio. I don't know what it should be. My choices are 1:2, 1:2.66, 1:3.33 and 1:4. Any suggestions?
I am still getting BSODs. But it seems much better, just occasionally now. I have had none since the new ram, but it has only been in for a couple hours.
You may need to RMA it for some AMD RAM, lets try a few adjustments first.
The CPUZ Memory tab shows you what the RAM is set at currently, the SPD tab is the manufacturer recommended settings.
Your AMD CPU's integrated memory controller is known to not like running RAM at 1600 (800 MHz) so I would recommend leaving it at 1333 (667 MHz).
Your SPD tab, JEDEC#4, says you should be running at 685MHz, 667MHz should be fine it's not enough to try changing, timings at 9-9-9-25 and 1.5v.
The Memory tab shows the command rate 2T, this will help with stability, just leave it at 2T.
I would try these settings and see if you still get BSoDs, if you are then let us know the CPU-NB, or equivalent, voltage.
Sometimes a bump in the NB will help the memory controller and give you more stability.
I've just read the first page and last page, will view the rest and edit if necessary.
EDIT:
If you're trying to run 16GB RAM, or even 8GB then you will need to bump your CPU-NB voltage this is for the CPU integrated memory controller.
From your MOBO manual:
Quote:
- To enable successful system boot-up, always nsert the memory modules into the DIMM1 first.
- Due to the chpset resource deployment, the system densty wll only be detected up to 15+GB (not full 16GB) when each DIMM s installed wth a 4GB memory module.
What is your CPU-NB voltage?
Page 3-19 of your MOBO manual.
If it only shows 'Auto' then add the minimum voltage and tell us the new voltage reading.
Stock voltages for the PhenomII CPU-NB should be between 1.15-1.30v.
Is your BIOS American Megatrends?
How long did you run Prime95?
At that time I ran Prime for 5 hours but temps were so high, I shut it down, but the CPU showed no errors. I have since memtest86 changed ram. I realize that it is intel ram, but the reason I picked it is because this particular kit is on MSI's QVL list. Most of the ram on their QVL list is listed as intel ram. However, I have been running this ram for about 2 weeks 24/7. It has done much better. I have only had 2 bsods during that time. Once while I was changing values in bios so I consider that my fault and the second time was when I installed SP1. When it downloaded I restarted it installed during shutdown, reconfigured durind startup and as soon as windows loaded it BSOD'd. But it started back up and have had no problems since.
According to MSI's Afterburner utility which I don't believe is accurate- CPU V Core is 1.475 and CPU NB is 1.150.
According to BIOS h/W monitor, CPU temp is 34, sys temp is 36, Core VID is 1.368.
I think my Bios is not working correctly. I have set ram timings to the rated value of 7-8-7. Bios CPU-Z function (which is supposed to be the SPD tab on CPUz) still says it is 9-9-9. Yet when I get into windows, CPUz shows rhe timings I set. I have read the manual numerous times. It says I shoul be able to set valuse and tells how. I have tried every way I know ti increase CPU NB but it will not change it simply says auto.
I have read that according to AMD, to change ram speed to 1600, you increase FSB to 240 (stock 200x14). You can either leave it there which OC's the cpu to 3360 or you lower the multiplier. I did that. I lowered the multiplier to 12 which put me at 2880 (stock 2800). That's when I BSOD'd. I changed the multiplier back to 14 and have been running good ever since.
I'm trying to answer all of your questions. I cant find the type bios on the POST screen or Bios, but I believe it is AMD. Neither says anything about Award. I have never OC'd before and never wanted to, but I must admit that the computer seems to run smoother and quicker like this.
As far as temps, I was normally running (Core tenp) 23�C idle and after 1 hour of prime was at 49�C. Temps right now are 22�. Idle temps will get to 28-29� later in the day (Florida weather I guess). This is the way I am running right now. It seems to be stable.
Attachment 140778
Attachment 140779
Attachment 140780
Attachment 140781
EDIT: The 16GB you are referring to is what I was running. 16GB of DDR3-1333 9-9-9-24. I would have thought that would run on any system. After all the testing and replacing everything I figured it had to be the Ram or CPU. Ram was cheaper to try, so I bought 4GB of DDR3-1600 7-8-7-24. That is what I am running now. It seems to be much better, and again I have run it 24/7 for 10 days to 2 wks. I still believe the MB is not right. Talking to MSI is like talking to my 8 year old Granddaughter. He told be I couldn't run 1600 ram on this motherboard when the specs clearly say 1600-1800 or 2000. When I told him yhat he said my problem was that I needed a better CPU. I told him that this is an AM3 MB and I am running a PHIIx6, what would he suggest I buy? He Hung up. I certainly cannot depend on them for any help. I may just buy another MB. For what I have spent on this thing, I could have bought a supercomputer.
If it is any help, this is after Prime for about 1 hour. It may be the weather here in Fla, but it seems like the temps went up on this and my Dell after SP1. I still cannot adjust the CPU NB in Bios. But I can change the CPU NB Ratio (whatever that means). Under normal use temps never go over 33�C.
Also, I have a Cooler Master TX3 CPU Cooler. I know it is not rated very well but it was the largest I can fit in my case. It also does much better that the stock cooler. Under Prime with the stock cooler I hit 78�.
Attachment 140818
Attachment 140819
Attachment 140820
EDIT: System Monitor is a desktop gadget, but it gets its info from CoreTemp.
I don't know if this worked as I had to do it through Control Center (Afterburner), but I increased the CPU NB from 1.15 to 1.155. Does that sound about right? Ram is set to 1.613 (rated 1.6).
I will answer some questions below in Blue
Sometimes the Intel speced RAM will run on AMD board. There has been many sites with many threads on this issue, you can google it, most of the time the RAM reps recommend to RMA for AMD spec RAM.At that time I ran Prime for 5 hours but temps were so high, I shut it down, but the CPU showed no errors. I have since memtest86 changed ram. I realize that it is intel ram, but the reason I picked it is because this particular kit is on MSI's QVL list. Most of the ram on their QVL list is listed as intel ram. However, I have been running this ram for about 2 weeks 24/7. It has done much better. I have only had 2 bsods during that time. Once while I was changing values in bios so I consider that my fault and the second time was when I installed SP1. When it downloaded I restarted it installed during shutdown, reconfigured durind startup and as soon as windows loaded it BSOD'd. But it started back up and have had no problems since..
It is possible to get it running with setting adjustments, sometimes.
You need to set the CPU-NB to 1.20v.According to MSI's Afterburner utility which I don't believe is accurate- CPU V Core is 1.475 and CPU NB is 1.150.
Select the 'Auto' feild and press enter, it will give you options depending on your BIOS (the brand should be listed on the top of every page), select 'Manual' or the voltage you want, 1.20v.
The CPUZ SPD tab is the G. Skill recommended settings, not the actual settings, G. Skill puts this on your RAM and CPUZ is just reading it.According to BIOS h/W monitor, CPU temp is 34, sys temp is 36, Core VID is 1.368.
I think my Bios is not working correctly. I have set ram timings to the rated value of 7-8-7. Bios CPU-Z function (which is supposed to be the SPD tab on CPUz) still says it is 9-9-9.
The CPUZ 'Memory' tab will tell you what the RAM is actually running at.
CPUZ does not give you the current actual voltage for RAM, it is only the G. Skill recommended voltage.
You need to get the readings from BIOS for the actual voltages for the RAM and CPU-NB.
Select 'AUTO' hit enter, this will give you options, select 'Manual' if that option is listed. Otherwise select 1.20v or the smallest increase, example: +0.02v, it will then give you the actual voltage setting.Yet when I get into windows, CPUz shows rhe timings I set. I have read the manual numerous times. It says I shoul be able to set valuse and tells how. I have tried every way I know ti increase CPU NB but it will not change it simply says auto..
This is a well documented issue with AMD CPUs, google it or I will give you a link later, some have success, but it takes a lot of setting adjustments.I have read that according to AMD, to change ram speed to 1600, you increase FSB to 240 (stock 200x14). You can either leave it there which OC's the cpu to 3360 or you lower the multiplier. I did that. I lowered the multiplier to 12 which put me at 2880 (stock 2800). That's when I BSOD'd. I changed the multiplier back to 14 and have been running good ever since.
It is best to leave it at 1333MHz (667Mhz), the performance increase to 1600MHz is hardly noticeable.
Your G. Skill recommended should run 16GB at 1333MHZ 9-9-9-21, command rate of 2T.I'm trying to answer all of your questions. I cant find the type bios on the POST screen or Bios, but I believe it is AMD. Neither says anything about Award. I have never OC'd before and never wanted to, but I must admit that the computer seems to run smoother and quicker like this.
As far as temps, I was normally running (Core tenp) 23�C idle and after 1 hour of prime was at 49�C. Temps right now are 22�. Idle temps will get to 28-29� later in the day (Florida weather I guess). This is the way I am running right now. It seems to be stable.
EDIT: The 16GB you are referring to is what I was running. 16GB of DDR3-1333 9-9-9-24. I would have thought that would run on any system. After all the testing and replacing everything I figured it had to be the Ram or CPU. Ram was cheaper to try, so I bought 4GB of DDR3-1600 7-8-7-24. That is what I am running now. It seems to be much better, and again I have run it 24/7 for 10 days to 2 wks. I still believe the MB is not right. Talking to MSI is like talking to my 8 year old Granddaughter. He told be I couldn't run 1600 ram on this motherboard when the specs clearly say 1600-1800 or 2000. When I told him yhat he said my problem was that I needed a better CPU. I told him that this is an AM3 MB and I am running a PHIIx6, what would he suggest I buy? He Hung up. I certainly cannot depend on them for any help. I may just buy another MB. For what I have spent on this thing, I could have bought a supercomputer.
BUT, with 4 RAM cards and/or 4GB or higher you will need to bump the CPU-NB and maybe the RAM voltages.
This is a very common recommendation from the RAM suppliers web-sites, again if you want confirmation you can google it. Check the RAM sites, G. Skill, OCZ, Corsair, etc. Also the Over Clocking sites have good RAM stabilization info.
Let us know if you get the BIOS settings changes, most important is the CPU-NB bump to 1.20v.
I tried again but bios will not allow me to change the CPU NB. I adjusted it in Control Center and saved the profile to 1.2.it was at 1.15. The 16GB you are referring to is the old ram I was having trouble with. I have replaced that with 4GB (2X2) of DDR31600. I am only running the 4GB now. The dram voltage in bios is set to auto which is 1.6V. A lot of hardware has changed since this thread started, but with those changes and the new ram it seems to be running fairly stable right now. I still don't think this bios is working right. In the CPU NB settings the left panel says auto, the right panel tells how to change it but following those instructions it will not change. Pressing enter on auto gives me no options either. I have changed CPU Settings to manual and it still will not change CPU NB. If Control Center works, I have changed it there.
As stated before, I think I changed the CPU NB to 1.2 through Control Center. I lowered the dram voltage from the recommended 1.6 to 1.5, reset the timings from the rated 7-8-7 to 9-9-9. I also lowered the FSB from 240 to the stock 200X14. See if this is more like what you were suggesting.
Attachment 140929
Attachment 140930
Attachment 140931
Looks good, strange about not being able to change the CPU-NB voltage in BIOS.
Which BIOS version do you have?
Hopefully not a beta version, they can be buggy.
I'll do some checking on the BIOS issues.
Even 4GB RAM will sometimes need a CPU-NB voltage bump, it's actually the 2GB cards that need a bit more voltage. If you were still having crashes I think this will help. Your issues sound like they are being caused by under volted memory controller and maybe under volted RAM.
If you have another crash, bump the RAM voltage back to 1.6v and the CPU-NB to 1.25v.
Let us know how it's going.
I have the latest bios version put out to the public V1.8. I understand the bios is supposed to be in the first line of the POST screen. Mine says A7642AMS. Not sure what bios that is, but the 7642 part is MSI's model number for my MB.
Sorry I have given you such a hard time about this, but I just don't understand much of it. I realize this doesn't work out right but I just thought if I buy high performance ram, listed on their QVL list, I should be able to run it at it's performance rate and lower timimgs. I guess its like I would like to get what I paid for. Seems it doesn't work that way. But, at least it appears to be stable now and I am happy about that. When I decided to build this computer I never envisioned I would have to buy it twice. I would like to thank you for your help. It is people like you that makes this forum the best. I just want you to realize how frustrated I have been and how thankful I am for people like you.
Thanks again,
Steve
Glad to help, RAM issues are not an exact science. Due mainly to the slight differences in all electronic parts and systems, certain combinations can cause problems.
I've found this hardware BSoD issue is quite common. The RAM memory controller voltage bump helps a lot of this type of problems, not always the answer but is a good place to start, statisically it has the best results.
There is a lot of information on the Over Clocking sites, RAM troubleshooting methods are basically the same as RAM OC methods. Both are searching for stability.
Generally accepted steps are to manually enter the first four RAM timings.
Check and usually bump the RAM and/or Memory controller voltage.
If still not stable, then back off the RAM frequency, change the timings and voltages accordingly. Start with the RAM SPD recommended settings and tweak from there.
It's a trial and error process and difficult to do on a forum, usually takes a long time to walk someone through it. This is why RAM and OC sites won't OC RAM for someone. You have to read up and search for the steps on the various sites. When you ask specific questions, the experienced members will answer.
Other than that, it's a piece of cake
Two exact same computers may not run the same, luck of the draw.
Here is a couple links discussing the AMD memory controller problem with 1600 MHz RAM.
These are from the Gigabyte forum but the info pertains to all AMD boards and all RAM.
According to your mobo site the 1.8 BIOS version is for AMI BIOS, American Megatrends Inc.
Here is a rather direct answer to the changing voltage in BIOS question, from your MSI Forum.
Sticky:You can't change your Cell Menu voltages?
"Just read the manual and use correct keys!!
NumPad's +/- or PageUp/PageDown if you want to adjust values."
Your board manual page 3-2:
Quote:A7642AMS V1.0 020110 where:
- The items under each BIOS category described in this chapter are under contnuious update for better system performance. Therefore, the description may be slightly different from the latest BIOS and should be held for reference only.
- Upon boot-up, the 1st line appearng after the memory count is the BIOS verson. It is usually in the format:
1st digit refers to BIOS maker as A = AMI, W = AWARD, and P = PHOENIX.
2nd - 5th digit refers to the model number.
6th digit refers to the chipset as I = Intel, N = NVIDIA, A = AMD and V = VIA.
7th - 8th digit refers to the customer as MS = all standard customers.
V1.0 refers to the BIOS verson.
020110 refers to the date ths BIOS was released.Hope this helps.Quote:Control Keys
<?> Move to the previous tem
<?> Move to the next item
<?> Move to the item in the left hand
<?> Move to the tem in the right hand
<Enter> Select the item
<Esc> Jumps to the Exit menu or returns to the main menu from a submenu
<+/PU> Increase the numeric value or make changes
<-/PD> Decrease the numeric value or make changes
<F1> General Help
<F6> Load Optimzed Defaults
<F8> Load Fail-Safe Defaults
<F10> Save all the CMOS changes and exit
Gettng Help
After entering the Setup menu, the first menu you will see is the Main Menu.
Main Menu
The main menu lists the setup functions you can make changes to. You can use the
arrow keys ( *? ) to select the item. The on-line descrpton of the highlighted setup
functon is dsplayed at the bottom of the screen.
Sub-Menu
If you find a rght pointer symbol (as shown n the rght vew) appears to the left of certian fields that means a sub-menu can be launched from ths field. A sub-menu contains additional options for
a field parameter. You can use arrow keys ( *? ) to highlight the
field and press <Enter> to call up the sub-menu. Then you can use the control keys to
enter values and move from field to field wthn a sub-menu. If you want to return to the
man menu, just press the <Esc >.
General Help <F1>
The BIOS setup program provdes a General Help screen. You can call up this screen
from any menu by simply pressng <F1>. The Help screen lists the approprate keys to
use and the possble selections for the highlighted item. Press <Esc> to exit the Help
screen.
Let us know if you have any questions.
Không có nhận xét nào:
Đăng nhận xét