Good morning guys you have help me out before lets see if you guys got any ideas
ok so i have i have a 64bit windows 7 system
Specs:
Asus p7p55d
Corsair xms3 4GB
ATI radeon 5570HD
Sata 250 WD hard drive
i7 930
i keep getting random crashes when trying to play games dose not matter what game im in i still crash. now it is very random some days ill go all day without a problem then other days it get the BSOD and i cant seem to get windows debug to work properly says my symbols pack is wrong but i have installed all the right packs and pathed to the right spot. i have attached the last couple of dump files
any ideas??
ok so i have i have a 64bit windows 7 system
Specs:
Asus p7p55d
Corsair xms3 4GB
ATI radeon 5570HD
Sata 250 WD hard drive
i7 930
i keep getting random crashes when trying to play games dose not matter what game im in i still crash. now it is very random some days ill go all day without a problem then other days it get the BSOD and i cant seem to get windows debug to work properly says my symbols pack is wrong but i have installed all the right packs and pathed to the right spot. i have attached the last couple of dump files
any ideas??
This will take few minutes to look at the dump files. I will be back shortly. Refresh your page in about ten minutes; I will edit this post.
hehe alright thanks for such a fast response 
i really believe this problem to be a memory problem though...
i really believe this problem to be a memory problem though...
I apologize for the delay. We lost our power (not unusual this time of year) and it was just restored. I will get back on your dumps now.
Your dumps indicate hardware/hardware related problems.
Notice what each of these error codes has in common: memory and driver.
Memory corruption is blamed in three of the four dumps and DirectX is blames in one dump. Most likely DirectX is not the problem, but rather a video driver or card.
Here is a definite cause of BSOD's - ASACPI.sys Sun Mar 27 22:30:36 2005.
Uninstall Avira. Avira is known to cause crashes on some Win 7 systems and you can see that one of the error codes mentions antivirus programs. Uese this tool to uninstall Avira > Info > Tool. Install Microsoft Security Essentials and make sure Windows Firewall is turned on. If you want to reinstall Avira after you get your system running smoothly, you can try it. But I do not recommend doing so.
You also have some other out of date drivers. Win 7 does not like older drivers. They can and do cause memory corruption and crashes. I can see that you have been updating drivers. Very good.
If you need help with the drivers, please post. Once you update these drivers, especially ASACPI.sys, uninstall Avira, install MSE, reboot and run your system. Hopefully, you will have fixed the problem. If not, we will test your RAM. If you get another BSOD after these changes, please post and upload your latest BSOD.
Your dumps indicate hardware/hardware related problems.
Quote:
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
Usual causes: Memory corruption, Hardware (memory in particular), Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
STOP 0x0000004E: PFN_LIST_CORRUPT
Usual causes: Device driver, ?memory
Usual causes: Device driver, memory, kernel
STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
Usual causes: Memory corruption, Hardware (memory in particular), Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
STOP 0x0000004E: PFN_LIST_CORRUPT
Usual causes: Device driver, ?memory
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Dumps.zip\080310-15709-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02a55000 PsLoadedModuleList = 0xfffff800`02c92e50 Debug session time: Wed Aug 4 01:30:36.180 2010 (GMT-4) System Uptime: 0 days 9:07:50.242 Loading Kernel Symbols ............................................................... ................................................................ ............ Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {31, fffffa8005d8f150, fffff88007ff6000, fffff8a00233000c} Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+6378 ) Followup: MachineOwner --------- 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000000031, The subtype of the bugcheck. Arg2: fffffa8005d8f150 Arg3: fffff88007ff6000 Arg4: fffff8a00233000c Debugging Details: ------------------ BUGCHECK_STR: 0x1a_31 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: PerfTuneServic CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002df6b2d to fffff80002ac5600 STACK_TEXT: fffff880`07212848 fffff800`02df6b2d : 00000000`0000001a 00000000`00000031 fffffa80`05d8f150 fffff880`07ff6000 : nt!KeBugCheckEx fffff880`07212850 fffff800`02dadf45 : fffff880`07ff6000 ffffffff`f8e40000 00000000`004a0000 fffffa80`015122a0 : nt! ?? ::NNGAKEGL::`string'+0x6378 fffff880`072128a0 fffff800`02d9b17c : fffffa80`00000000 fffffa80`05cda060 00000000`00000000 fffffa80`00000000 : nt!MiPerformFixups+0x65 fffff880`072128f0 fffff800`02ab6b4c : fffffa80`015122a0 fffffa80`05ce3d40 00000000`00000000 fffffa80`06acea00 : nt!MiRelocateImagePfn+0x114 fffff880`07212950 fffff800`02ab742b : fffffa80`05ce3c80 fffff880`07212a80 fffffa80`068ccec8 fffff800`02ddc7d7 : nt!MiWaitForInPageComplete+0x89c fffff880`07212a30 fffff800`02ae079b : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff800`00000000 : nt!MiIssueHardFault+0x28b fffff880`07212ac0 fffff800`02ac36ee : 00000000`00000008 00000000`72cb0000 00000000`b2808e01 00000000`7efdb000 : nt!MmAccessFault+0x14bb fffff880`07212c20 00000000`7314be2f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`0030f638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7314be2f STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::NNGAKEGL::`string'+6378 fffff800`02df6b2d cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::NNGAKEGL::`string'+6378 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb FAILURE_BUCKET_ID: X64_0x1a_31_nt!_??_::NNGAKEGL::_string_+6378 BUCKET_ID: X64_0x1a_31_nt!_??_::NNGAKEGL::_string_+6378 Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Dumps.zip\080810-14757-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02a4c000 PsLoadedModuleList = 0xfffff800`02c89e50 Debug session time: Sun Aug 8 14:53:42.720 2010 (GMT-4) System Uptime: 0 days 0:28:57.782 Loading Kernel Symbols ............................................................... ................................................................ ............ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {8, 80050031, 6f8, fffff88005509cab} *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruption Followup: memory_corruption --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: 0000000080050031 Arg3: 00000000000006f8 Arg4: fffff88005509cab Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002abbb69 to fffff80002abc600 STACK_TEXT: fffff800`00ba4d28 fffff800`02abbb69 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx fffff800`00ba4d30 fffff800`02aba032 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff800`00ba4e70 fffff880`05509cab : ffff1bf8`890fc085 ffff1bf3`e9e08b44 1c26850f`01487f83 84000180`04e8ffff : nt!KiDoubleFaultAbort+0xb2 fffff880`054d5a0d ffff1bf8`890fc085 : ffff1bf3`e9e08b44 1c26850f`01487f83 84000180`04e8ffff b8ffff1c`19850fc0 : HTTP!UlpSetUrlInfoSpecial+0xb fffff880`054d5a15 ffff1bf3`e9e08b44 : 1c26850f`01487f83 84000180`04e8ffff b8ffff1c`19850fc0 ff1c12e9`c0000022 : 0xffff1bf8`890fc085 fffff880`054d5a1d 1c26850f`01487f83 : 84000180`04e8ffff b8ffff1c`19850fc0 ff1c12e9`c0000022 1bd4e941`24448aff : 0xffff1bf3`e9e08b44 fffff880`054d5a25 84000180`04e8ffff : b8ffff1c`19850fc0 ff1c12e9`c0000022 1bd4e941`24448aff 8affff1b`e1e9ffff : 0x1c26850f`01487f83 fffff880`054d5a2d b8ffff1c`19850fc0 : ff1c12e9`c0000022 1bd4e941`24448aff 8affff1b`e1e9ffff ed840fc0`84412444 : 0x84000180`04e8ffff fffff880`054d5a35 ff1c12e9`c0000022 : 1bd4e941`24448aff 8affff1b`e1e9ffff ed840fc0`84412444 0f01fe80`41fffffd : 0xb8ffff1c`19850fc0 fffff880`054d5a3d 1bd4e941`24448aff : 8affff1b`e1e9ffff ed840fc0`84412444 0f01fe80`41fffffd 3abc41ff`ff1beb85 : 0xff1c12e9`c0000022 fffff880`054d5a45 8affff1b`e1e9ffff : ed840fc0`84412444 0f01fe80`41fffffd 3abc41ff`ff1beb85 ffff1be0`e9c00000 : 0x1bd4e941`24448aff fffff880`054d5a4d ed840fc0`84412444 : 0f01fe80`41fffffd 3abc41ff`ff1beb85 ffff1be0`e9c00000 c418850f`6873394c : 0x8affff1b`e1e9ffff fffff880`054d5a55 0f01fe80`41fffffd : 3abc41ff`ff1beb85 ffff1be0`e9c00000 c418850f`6873394c 66ffffc3`e9e9ffff : 0xed840fc0`84412444 fffff880`054d5a5d 3abc41ff`ff1beb85 : ffff1be0`e9c00000 c418850f`6873394c 66ffffc3`e9e9ffff c7fa8166`0190ea81 : 0xf01fe80`41fffffd fffff880`054d5a65 ffff1be0`e9c00000 : c418850f`6873394c 66ffffc3`e9e9ffff c7fa8166`0190ea81 e9ffffc4`57860f00 : 0x3abc41ff`ff1beb85 fffff880`054d5a6d c418850f`6873394c : 66ffffc3`e9e9ffff c7fa8166`0190ea81 e9ffffc4`57860f00 90ea8166`ffffc6ea : 0xffff1be0`e9c00000 fffff880`054d5a75 66ffffc3`e9e9ffff : c7fa8166`0190ea81 e9ffffc4`57860f00 90ea8166`ffffc6ea 860f00c7`fa816601 : 0xc418850f`6873394c fffff880`054d5a7d c7fa8166`0190ea81 : e9ffffc4`57860f00 90ea8166`ffffc6ea 860f00c7`fa816601 ffc43de9`ffffc6da : 0x66ffffc3`e9e9ffff fffff880`054d5a85 e9ffffc4`57860f00 : 90ea8166`ffffc6ea 860f00c7`fa816601 ffc43de9`ffffc6da f9833774`01e983ff : 0xc7fa8166`0190ea81 fffff880`054d5a8d 90ea8166`ffffc6ea : 860f00c7`fa816601 ffc43de9`ffffc6da f9833774`01e983ff 00d02484`c7107401 : 0xe9ffffc4`57860f00 fffff880`054d5a95 860f00c7`fa816601 : ffc43de9`ffffc6da f9833774`01e983ff 00d02484`c7107401 b3e9c000`01840000 : 0x90ea8166`ffffc6ea fffff880`054d5a9d ffc43de9`ffffc6da : f9833774`01e983ff 00d02484`c7107401 b3e9c000`01840000 021c86b7`0fffffc6 : 0x860f00c7`fa816601 fffff880`054d5aa5 f9833774`01e983ff : 00d02484`c7107401 b3e9c000`01840000 021c86b7`0fffffc6 00000081`888d0000 : 0xffc43de9`ffffc6da fffff880`054d5aad 00d02484`c7107401 : b3e9c000`01840000 021c86b7`0fffffc6 00000081`888d0000 ffffc4ab`830fc83b : 0xf9833774`01e983ff fffff880`054d5ab5 b3e9c000`01840000 : 021c86b7`0fffffc6 00000081`888d0000 ffffc4ab`830fc83b 000000d0`24ac8944 : 0xd02484`c7107401 fffff880`054d5abd 021c86b7`0fffffc6 : 00000081`888d0000 ffffc4ab`830fc83b 000000d0`24ac8944 86b70fff`ffc691e9 : 0xb3e9c000`01840000 fffff880`054d5ac5 00000081`888d0000 : ffffc4ab`830fc83b 000000d0`24ac8944 86b70fff`ffc691e9 00ab888d`0000021c : 0x21c86b7`0fffffc6 fffff880`054d5acd ffffc4ab`830fc83b : 000000d0`24ac8944 86b70fff`ffc691e9 00ab888d`0000021c c489830f`c83b0000 : 0x81`888d0000 fffff880`054d5ad5 000000d0`24ac8944 : 86b70fff`ffc691e9 00ab888d`0000021c c489830f`c83b0000 00d024ac`8944ffff : 0xffffc4ab`830fc83b fffff880`054d5add 86b70fff`ffc691e9 : 00ab888d`0000021c c489830f`c83b0000 00d024ac`8944ffff 41ffffc6`6fe90000 : 0xd0`24ac8944 fffff880`054d5ae5 00ab888d`0000021c : c489830f`c83b0000 00d024ac`8944ffff 41ffffc6`6fe90000 45ffffc4`34e9c98b : 0x86b70fff`ffc691e9 fffff880`054d5aed c489830f`c83b0000 : 00d024ac`8944ffff 41ffffc6`6fe90000 45ffffc4`34e9c98b 0f000006`6124b438 : 0xab888d`0000021c fffff880`054d5af5 00d024ac`8944ffff : 41ffffc6`6fe90000 45ffffc4`34e9c98b 0f000006`6124b438 b70f45ff`ffc43684 : 0xc489830f`c83b0000 fffff880`054d5afd 41ffffc6`6fe90000 : 45ffffc4`34e9c98b 0f000006`6124b438 b70f45ff`ffc43684 45660000`03d02484 : 0xd024ac`8944ffff fffff880`054d5b05 45ffffc4`34e9c98b : 0f000006`6124b438 b70f45ff`ffc43684 45660000`03d02484 42c18b45`0d76c13b : 0x41ffffc6`6fe90000 fffff880`054d5b0d 0f000006`6124b438 : b70f45ff`ffc43684 45660000`03d02484 42c18b45`0d76c13b ffc41ae9`02094c8d : 0x45ffffc4`34e9c98b fffff880`054d5b15 b70f45ff`ffc43684 : 45660000`03d02484 42c18b45`0d76c13b ffc41ae9`02094c8d 4c8d42c0`b70f45ff : 0xf000006`6124b438 fffff880`054d5b1d 45660000`03d02484 : 42c18b45`0d76c13b ffc41ae9`02094c8d 4c8d42c0`b70f45ff 45ffffc4`0ce90201 : 0xb70f45ff`ffc43684 fffff880`054d5b25 42c18b45`0d76c13b : ffc41ae9`02094c8d 4c8d42c0`b70f45ff 45ffffc4`0ce90201 0f000006`6c24b438 : 0x45660000`03d02484 fffff880`054d5b2d ffc41ae9`02094c8d : 4c8d42c0`b70f45ff 45ffffc4`0ce90201 0f000006`6c24b438 b70f45ff`ffc40884 : 0x42c18b45`0d76c13b fffff880`054d5b35 4c8d42c0`b70f45ff : 45ffffc4`0ce90201 0f000006`6c24b438 b70f45ff`ffc40884 45660000`04802484 : 0xffc41ae9`02094c8d fffff880`054d5b3d 45ffffc4`0ce90201 : 0f000006`6c24b438 b70f45ff`ffc40884 45660000`04802484 42c18b45`0d76c13b : 0x4c8d42c0`b70f45ff fffff880`054d5b45 0f000006`6c24b438 : b70f45ff`ffc40884 45660000`04802484 42c18b45`0d76c13b ffc3ece9`02094c8d : 0x45ffffc4`0ce90201 fffff880`054d5b4d b70f45ff`ffc40884 : 45660000`04802484 42c18b45`0d76c13b ffc3ece9`02094c8d 4c8d42c0`b70f45ff : 0xf000006`6c24b438 fffff880`054d5b55 45660000`04802484 : 42c18b45`0d76c13b ffc3ece9`02094c8d 4c8d42c0`b70f45ff 45ffffc3`dee90201 : 0xb70f45ff`ffc40884 fffff880`054d5b5d 42c18b45`0d76c13b : ffc3ece9`02094c8d 4c8d42c0`b70f45ff 45ffffc3`dee90201 0f000006`6424b438 : 0x45660000`04802484 fffff880`054d5b65 ffc3ece9`02094c8d : 4c8d42c0`b70f45ff 45ffffc3`dee90201 0f000006`6424b438 b70f41ff`ffc3da84 : 0x42c18b45`0d76c13b fffff880`054d5b6d 4c8d42c0`b70f45ff : 45ffffc3`dee90201 0f000006`6424b438 b70f41ff`ffc3da84 41660000`04002484 : 0xffc3ece9`02094c8d fffff880`054d5b75 45ffffc3`dee90201 : 0f000006`6424b438 b70f41ff`ffc3da84 41660000`04002484 c8b70f44`0477c13b : 0x4c8d42c0`b70f45ff fffff880`054d5b7d 0f000006`6424b438 : b70f41ff`ffc3da84 41660000`04002484 c8b70f44`0477c13b c3bde902`094c8d42 : 0x45ffffc3`dee90201 fffff880`054d5b85 b70f41ff`ffc3da84 : 41660000`04002484 c8b70f44`0477c13b c3bde902`094c8d42 0000d024`8c8bffff : 0xf000006`6424b438 fffff880`054d5b8d 41660000`04002484 : c8b70f44`0477c13b c3bde902`094c8d42 0000d024`8c8bffff ffc3bbe9`c58b4100 : 0xb70f41ff`ffc3da84 fffff880`054d5b95 c8b70f44`0477c13b : c3bde902`094c8d42 0000d024`8c8bffff ffc3bbe9`c58b4100 000000d0`2484c7ff : 0x41660000`04002484 fffff880`054d5b9d c3bde902`094c8d42 : 0000d024`8c8bffff ffc3bbe9`c58b4100 000000d0`2484c7ff ffc5ade9`c000009a : 0xc8b70f44`0477c13b fffff880`054d5ba5 0000d024`8c8bffff : ffc3bbe9`c58b4100 000000d0`2484c7ff ffc5ade9`c000009a 90fffc64`f415ffff : 0xc3bde902`094c8d42 fffff880`054d5bad ffc3bbe9`c58b4100 : 000000d0`2484c7ff ffc5ade9`c000009a 90fffc64`f415ffff 01e983ff`ffc3f5e9 : 0xd024`8c8bffff fffff880`054d5bb5 000000d0`2484c7ff : ffc5ade9`c000009a 90fffc64`f415ffff 01e983ff`ffc3f5e9 c7107401`f9834c74 : 0xffc3bbe9`c58b4100 fffff880`054d5bbd ffc5ade9`c000009a : 90fffc64`f415ffff 01e983ff`ffc3f5e9 c7107401`f9834c74 01840000`00d02484 : 0xd0`2484c7ff fffff880`054d5bc5 90fffc64`f415ffff : 01e983ff`ffc3f5e9 c7107401`f9834c74 01840000`00d02484 48ffffc5`87e9c000 : 0xffc5ade9`c000009a fffff880`054d5bcd 01e983ff`ffc3f5e9 : c7107401`f9834c74 01840000`00d02484 48ffffc5`87e9c000 b0c9e8cf`8b48d68b : 0x90fffc64`f415ffff fffff880`054d5bd5 c7107401`f9834c74 : 01840000`00d02484 48ffffc5`87e9c000 b0c9e8cf`8b48d68b 84891578`c085fffb : 0x1e983ff`ffc3f5e9 fffff880`054d5bdd 01840000`00d02484 : 48ffffc5`87e9c000 b0c9e8cf`8b48d68b 84891578`c085fffb 39446600`0000d024 : 0xc7107401`f9834c74 fffff880`054d5be5 48ffffc5`87e9c000 : b0c9e8cf`8b48d68b 84891578`c085fffb 39446600`0000d024 f9850f00`0000b8b7 : 0x1840000`00d02484 fffff880`054d5bed b0c9e8cf`8b48d68b : 84891578`c085fffb 39446600`0000d024 f9850f00`0000b8b7 00000dbd`41ffffc3 : 0x48ffffc5`87e9c000 fffff880`054d5bf5 84891578`c085fffb : 39446600`0000d024 f9850f00`0000b8b7 00000dbd`41ffffc3 0000d024`ac8944c0 : 0xb0c9e8cf`8b48d68b fffff880`054d5bfd 39446600`0000d024 : f9850f00`0000b8b7 00000dbd`41ffffc3 0000d024`ac8944c0 8b48ffff`c550e900 : 0x84891578`c085fffb fffff880`054d5c05 f9850f00`0000b8b7 : 00000dbd`41ffffc3 0000d024`ac8944c0 8b48ffff`c550e900 fbadd2e8`cf8b48d6 : 0x39446600`0000d024 fffff880`054d5c0d 00000dbd`41ffffc3 : 0000d024`ac8944c0 8b48ffff`c550e900 fbadd2e8`cf8b48d6 24848915`78c085ff : 0xf9850f00`0000b8b7 fffff880`054d5c15 0000d024`ac8944c0 : 8b48ffff`c550e900 fbadd2e8`cf8b48d6 24848915`78c085ff b7394466`000000d0 : 0xdbd`41ffffc3 fffff880`054d5c1d 8b48ffff`c550e900 : fbadd2e8`cf8b48d6 24848915`78c085ff b7394466`000000d0 c3c2850f`000000b8 : 0xd024`ac8944c0 fffff880`054d5c25 fbadd2e8`cf8b48d6 : 24848915`78c085ff b7394466`000000d0 c3c2850f`000000b8 c000000d`bd41ffff : 0x8b48ffff`c550e900 fffff880`054d5c2d 24848915`78c085ff : b7394466`000000d0 c3c2850f`000000b8 c000000d`bd41ffff 000000d0`24ac8944 : 0xfbadd2e8`cf8b48d6 fffff880`054d5c35 b7394466`000000d0 : c3c2850f`000000b8 c000000d`bd41ffff 000000d0`24ac8944 d68b48ff`ffc519e9 : 0x24848915`78c085ff fffff880`054d5c3d c3c2850f`000000b8 : c000000d`bd41ffff 000000d0`24ac8944 d68b48ff`ffc519e9 00019f4b`e8cf8b48 : 0xb7394466`000000d0 fffff880`054d5c45 c000000d`bd41ffff : 000000d0`24ac8944 d68b48ff`ffc519e9 00019f4b`e8cf8b48 15ffffff`c3e8e990 : 0xc3c2850f`000000b8 STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -db !HTTP 255 errors : !HTTP (fffff88005509002-fffff88005509fba) fffff88005509000 b9 c5 *b0 00 c0 ff 15 b5 36 f9 *66 41 f6 42 0a 05 ........6.fA.B.. fffff88005509010 74 06 *ea 8b 42 18 eb 1c 44 89 *ca 24 28 44 89 74 t...B...D..$(D.t fffff88005509020 24 20 *83 33 c9 33 d2 45 8d 41 *fa 49 8b ca ff 15 $ .3.3.E.A.I.... fffff88005509030 1c 31 *7a ff 48 89 84 24 80 00 *58 00 49 3b c6 75 .1z.H..$..X.I;.u ... fffff88005509080 64 36 *dd ff 48 8b 4b 08 8a 41 *1e 02 41 20 a8 03 d6..H.K..A..A .. fffff88005509090 74 0b *0a c5 02 00 c0 ff 15 23 *40 f9 ff f6 41 0a t........#@...A. fffff880055090a0 05 74 *f5 48 8b 41 18 eb 19 44 *5a 74 24 28 44 89 .t.H.A...DZt$(D. fffff880055090b0 74 24 *33 45 33 c9 33 d2 45 8d *b9 01 ff 15 8e 30 t$3E3.3.E......0 ... fffff88005509100 39 57 *6f 72 70 48 8b cb ff 15 *7b 35 f9 ff 48 8b 9WorpH....{5..H. fffff88005509110 4b 08 *46 41 2c 02 41 20 a8 03 *b1 0b b9 c5 02 00 K.FA,.A ........ fffff88005509120 c0 ff *d5 99 35 f9 ff f6 41 0a *97 74 06 48 8b 41 ....5...A..t.H.A fffff88005509130 18 eb *91 44 89 74 24 28 44 89 *d4 24 20 45 33 c9 ...D.t$(D..$ E3. ... fffff88005509180 3c 35 *15 ff 4c 39 73 08 0f 84 *4c 00 00 00 39 57 <5..L9s...L...9W fffff88005509190 08 0f *ec 9f 00 00 00 48 8b cb *07 15 48 35 f9 ff .......H....H5.. fffff880055091a0 48 8b *f2 08 8a 41 2c 02 41 20 *a6 03 74 0b b9 c5 H....A,.A ..t... fffff880055091b0 02 00 *1a ff 15 07 35 f9 ff f6 *2a 0a 05 74 06 48 ......5...*..t.H ... fffff88005509200 00 00 *65 8d 8c 24 88 00 00 00 *62 89 4c 24 20 4c ..e..$....b.L$ L fffff88005509210 8b c0 *38 8b 55 00 49 8b cc e8 *4f f8 ff ff 8b f8 ..8.U.I...O..... fffff88005509220 89 44 *6f 30 41 3b c6 7c 0b 8b *f5 24 88 00 00 00 .Do0A;.|...$.... fffff88005509230 48 89 *f8 38 eb 4a 48 89 53 38 *d5 05 00 00 80 ff H..8.JH.S8...... ... fffff88005509280 81 ff *30 01 00 00 74 0e 89 7b *80 33 d2 48 8b cb ..0...t..{.3.H.. fffff88005509290 ff 15 *6a 34 f9 ff 8b c7 48 83 *81 40 41 5e 41 5d ..j4....H..@A^A] fffff880055092a0 41 5c *4b 5b c3 90 90 90 90 90 *8c 90 90 90 90 90 A\K[............ fffff880055092b0 48 89 *75 24 10 48 89 4c 24 08 *6c 57 41 54 48 83 H.u$.H.L$.lWATH. ... fffff88005509300 0b b9 *de 00 00 c0 ff 15 b4 33 *81 ff 4c 8b 61 18 .........3..L.a. fffff88005509310 4d 85 *af 75 0b b9 0d 00 00 c0 *4d 15 a0 33 f9 ff M..u......M..3.. fffff88005509320 49 8b *b0 24 08 33 d2 44 8d 42 *24 49 8b cc e8 2d I..$.3.D.B$I...- fffff88005509330 69 f6 *01 4c 8d 44 24 60 48 8b *0f 48 8b ce e8 9d i..L.D$`H..H.... ... fffff88005509380 75 0d *ed fb 05 00 00 80 74 05 *7b 0d 00 00 c0 89 u.......t.{..... fffff88005509390 5c 24 *2e 48 8b 7c 24 50 81 fb *76 01 00 00 74 0e \$.H.|$P..v...t. fffff880055093a0 89 5f *5a 33 d2 48 8b cf ff 15 *b0 33 f9 ff 8b c3 ._Z3.H.....3.... fffff880055093b0 48 8b *e3 24 58 48 83 c4 30 41 *b3 5f 5e c3 90 90 H..$XH..0A._^... ... fffff88005509400 01 00 *f0 3b 15 3b d6 fa ff 0f *32 2c 01 00 00 44 ...;.;....2,...D fffff88005509410 38 25 *61 c2 fa ff 74 63 ff 15 *15 33 f9 ff f0 48 8%a...tc...3...H fffff88005509420 0f ba *24 20 31 fa ff 00 73 0d *09 8d 0d 17 31 fa ..$ 1...s.....1. fffff88005509430 ff ff *18 09 33 f9 ff 48 8d 0d *1a 31 fa ff 4c 8b ....3..H...1..L. ... fffff88005509480 ff 33 *e4 44 8d 68 11 f0 4c 0f *23 2d b8 30 fa ff .3.D.h..L.#-.0.. fffff88005509490 74 0d *52 8d 0d af 30 fa ff ff *91 b9 32 f9 ff 48 t.R...0.....2..H fffff880055094a0 8d 0d *90 30 fa ff 4c 8b c5 8b *7a e8 70 3b fe ff ...0..L...z.p;.. fffff880055094b0 8b f0 *9a 8b c5 f0 4c 0f b1 25 *f4 30 fa ff 74 0d ......L..%.0..t. ... fffff88005509500 ff 4c *db c5 8b d7 e8 05 f1 ff *da 48 83 ca ff 8b .L.........H.... fffff88005509510 f0 f0 *6f 0f c1 15 2e 30 fa ff *d9 c2 02 74 12 f6 ..o....0.....t.. fffff88005509520 c2 04 *a5 0d 48 8d 0d 1d 30 fa *a6 ff 15 07 32 f9 ....H...0.....2. fffff88005509530 ff ff *fc 11 32 f9 ff 8b c6 eb *92 b8 0d 00 00 c0 ....2........... ... fffff88005509580 54 48 *64 ec e0 04 00 00 48 8b *94 71 fb f9 ff 48 THd.....H..q...H fffff88005509590 33 c4 *e6 89 84 24 d0 04 00 00 *c2 ff 48 8b d9 8d 3....$......H... fffff880055095a0 47 01 *c2 bc 24 90 00 00 00 89 *8b 24 98 00 00 00 G...$......$.... fffff880055095b0 89 84 *bd 94 00 00 00 e8 74 c1 *18 ff 40 3a c7 75 ........t...@:.u ... fffff88005509600 31 fa *bd ff 15 4f 31 f9 ff f6 *1f 70 31 fa ff 08 1....O1....p1... fffff88005509610 41 bc *69 00 00 00 75 64 ff 15 *a5 31 f9 ff f0 48 A.i...ud...1...H WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view entire output. MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: STRIDE FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE Followup: memory_corruption --------- Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Dumps.zip\081510-16161-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02c00000 PsLoadedModuleList = 0xfffff800`02e3de50 Debug session time: Sun Aug 15 13:56:39.102 2010 (GMT-4) System Uptime: 0 days 0:38:46.424 Loading Kernel Symbols ............................................................... ................................................................ ............. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff8a00cb2bea4, 0, fffff88004820cf7, 2} Could not read faulting driver name Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b ) Followup: MachineOwner --------- 0: 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: fffff8a00cb2bea4, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff88004820cf7, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000002, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ea80e0 fffff8a00cb2bea4 FAULTING_IP: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b fffff880`04820cf7 0fba63540d bt dword ptr [rbx+54h],0Dh MM_INTERNAL_CODE: 2 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: System CURRENT_IRQL: 0 TRAP_FRAME: fffff880059b7750 -- (.trap 0xfffff880059b7750) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff8a00c003c20 rbx=0000000000000000 rcx=fffffa8005bb4000 rdx=fffffa800457d930 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88004820cf7 rsp=fffff880059b78e0 rbp=fffffa800528f488 r8=fffffa8004e97601 r9=0000000000000000 r10=0000000000000000 r11=00000000000000e2 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2b: fffff880`04820cf7 0fba63540d bt dword ptr [rbx+54h],0Dh ds:3770:00000000`00000054=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002cef8f2 to fffff80002c70740 STACK_TEXT: fffff880`059b75e8 fffff800`02cef8f2 : 00000000`00000050 fffff8a0`0cb2bea4 00000000`00000000 fffff880`059b7750 : nt!KeBugCheckEx fffff880`059b75f0 fffff800`02c6e82e : 00000000`00000000 fffff8a0`0cb2be50 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40ec0 fffff880`059b7750 fffff880`04820cf7 : 00000000`ffffd978 00000000`0000000f fffffa80`05bac000 fffffa80`05bad0d0 : nt!KiPageFault+0x16e fffff880`059b78e0 fffff880`0481ded3 : 00000000`00000000 fffffa80`051dd180 00000000`000000b2 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2b fffff880`059b7910 fffff880`0483865d : 00000000`00000000 fffff8a0`07ff1270 fffffa80`00000000 fffffa80`04e97690 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f fffff880`059b7ae0 fffff880`04838398 : fffff880`009ef040 fffff880`04837d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241 fffff880`059b7cd0 fffff880`04837e96 : 00000000`00000000 fffffa80`0458e0a0 00000000`00000080 fffffa80`05b94010 : dxgmms1!VidSchiSubmitQueueCommand+0x50 fffff880`059b7d00 fffff800`02f14c06 : 00000000`02041b46 fffffa80`05bb3770 fffffa80`03c71b30 fffffa80`05bb3770 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`059b7d40 fffff800`02c4ec26 : fffff880`009ea180 fffffa80`05bb3770 fffff880`009f50c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`059b7d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b fffff880`04820cf7 0fba63540d bt dword ptr [rbx+54h],0Dh SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578 FAILURE_BUCKET_ID: X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b BUCKET_ID: X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Dumps.zip\082310-14398-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02c5d000 PsLoadedModuleList = 0xfffff800`02e9ae50 Debug session time: Tue Aug 24 00:47:25.277 2010 (GMT-4) System Uptime: 0 days 2:35:04.323 Loading Kernel Symbols ............................................................... ................................................................ ............. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 4E, {2, 3c9f3, 13ffff, 1} Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+8e ) Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PFN_LIST_CORRUPT (4e) Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc). If a kernel debugger is available get the stack trace. Arguments: Arg1: 0000000000000002, A list entry was corrupt Arg2: 000000000003c9f3, entry in list being removed Arg3: 000000000013ffff, highest physical page number Arg4: 0000000000000001, reference count of entry being removed Debugging Details: ------------------ BUGCHECK_STR: 0x4E_2 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: SearchProtocol CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002cee6be to fffff80002ccd740 STACK_TEXT: fffff880`08c86e98 fffff800`02cee6be : 00000000`0000004e 00000000`00000002 00000000`0003c9f3 00000000`0013ffff : nt!KeBugCheckEx fffff880`08c86ea0 fffff800`02cbbba1 : fffffa80`04d35b10 fffffa80`00000000 00000000`00000000 fffff8a0`03094838 : nt!MiUnlinkPageFromLockedList+0x8e fffff880`08c86f30 fffff800`02cb9954 : fffff8a0`03094010 fffff8a0`03094838 fffffa80`04d35b90 fffffa80`04d35b90 : nt!MiFlushSectionInternal+0xc78 fffff880`08c87170 fffff800`02cb042c : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmFlushSection+0x1f4 fffff880`08c87230 fffff800`02fc879a : 00000000`00000000 00000000`00000006 00000000`01000000 00000000`00000000 : nt!MiFlushDataSection+0x190 fffff880`08c872a0 fffff800`02fbe013 : fffff880`08c87500 00000000`00000000 fffff880`08c875a8 fffff880`08c874f8 : nt!MmCreateSection+0x2ce fffff880`08c874b0 fffff800`031296b5 : fffff8a0`0a34fd30 00000000`00000000 00000000`00000001 00000002`00000000 : nt!NtCreateSection+0x162 fffff880`08c87530 fffff800`03129a67 : 00000000`00000010 fffff8a0`0a1c2ad0 fffff880`08c876c0 00000000`0000002c : nt!PfSnGetSectionObject+0x2d5 fffff880`08c87620 fffff800`03129e97 : fffff880`08c87740 00000000`00000001 00000000`00000000 00000000`00000000 : nt!PfSnPrefetchSections+0x247 fffff880`08c87710 fffff800`0312a2bf : 00000001`d42d60d5 fffffa80`06348520 fffff8a0`042a5000 00000000`00000000 : nt!PfSnPrefetchScenario+0x187 fffff880`08c87980 fffff800`02f226df : 00000000`00000000 00000000`0cb8cade fffffa80`03e26aa0 00000000`00000000 : nt!PfSnBeginAppLaunch+0x35f fffff880`08c87a50 fffff800`02f9b2fc : fffffa80`05239550 fffffa80`03e26aa0 00000000`14050800 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x50100 fffff880`08c87a80 fffff800`02cabd55 : fffff880`009b1180 00000000`00000000 fffff800`02f9b200 fffffa80`05239550 : nt!PspUserThreadStartup+0xfc fffff880`08c87ae0 fffff800`02cabcd7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16 fffff880`08c87c20 00000000`77423000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn 00000000`000bff18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77423000 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiUnlinkPageFromLockedList+8e fffff800`02cee6be cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!MiUnlinkPageFromLockedList+8e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x4E_2_nt!MiUnlinkPageFromLockedList+8e BUCKET_ID: X64_0x4E_2_nt!MiUnlinkPageFromLockedList+8e Followup: MachineOwner ---------
Here is a definite cause of BSOD's - ASACPI.sys Sun Mar 27 22:30:36 2005.
Quote:
The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).
You also have some other out of date drivers. Win 7 does not like older drivers. They can and do cause memory corruption and crashes. I can see that you have been updating drivers. Very good.
Quote:
intelsmb.sys Wed May 13 03:31:00 2009
IOCBIOS.SYS Thu Jul 09 13:47:22 2009
IOCBIOS.SYS Thu Jul 09 13:47:22 2009
wow great stuff man! ok well let me just say this i had a asus Gforce 260 installed in it and i was still having the problems so i switched the graphics card out for an ati 5570HD and im still getting the problems i have updated many drivers with no change. i have also reformatted the computer multiple times. im really thinking its a memory problem thanks for all the help man much appreciated. i have been pulling my hair out over this problem ugh!
Thank you. That is what we are for. 
Refresh your page; I have completed the initial analysis.
Refresh your page; I have completed the initial analysis. ok so i uninstalled avira installed MSE my driver ASACPI.sys is from 2005 i updated this driver
how would i go about obtaining
intelsmb.sys
iocbios.sys
thank you!
how would i go about obtaining
intelsmb.sys
iocbios.sys
thank you!
i checked intel's website for the drivers i downloaded them but there even later versions then what i have installed on the computer...
Allright so i was playing MW2 when i got another BSOD so i dont think avira and or that asacpi.sys was our problem i have uploaded my new dump log thank you
Please remove your Intel Tuning program.
If BSODs persist, enable verifier: Driver Verifier - Enable and Disable
Wait for a few crashes, then follow these directions: http://www.sevenforums.com/crashes-d...tructions.html
...Summary of the Dumps:
If BSODs persist, enable verifier: Driver Verifier - Enable and Disable
Wait for a few crashes, then follow these directions: http://www.sevenforums.com/crashes-d...tructions.html
...Summary of the Dumps:
Code:
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Tue Aug 24 14:49:43.350 2010 (UTC - 4:00) System Uptime: 0 days 1:13:23.286 BugCheck 50, {fffff8802fe98560, 1, fffff880055420fb, 2} Probably caused by : memory_corruption BUGCHECK_STR: 0x50 PROCESS_NAME: svchost.exe �������������������������������������������������������������������������������������� ok i uninstalled intel tuning program but im pretty sure i had that disabled and was not running anyways. i enabled the verifier so i will wait and see if i get another crash today
So i got it to Blue screen again this time with driver verifier on and ran the program you guys wanted me to so he is my dump..
thanks for the help guys
thanks for the help guys
This is a Driver Verifier enabled dump and it blames the driver viahduaa.sys. This is a sound card driver, VIA High Definition Audio Driver, VIA Technologies, Inc. This driver is up to date. On the off chance that driver is corrupted, download a fresh copy of this driver. Uninstall the curren driver and install the new one. Turn off Driver Verifier before you do this.
You still have two outdated driver on your system. Update these drivers if you can.
intelsmb.sys Wed May 13 03:31:00 2009 - system Management Bus 2.0 (SMBus) Driver is a driver file from company Intel Corporation belonging to product Intel(R) SMBus Controller. This is a chipset driver.
IOCBIOS.SYS Thu Jul 09 13:47:22 2009 - Intel(R) Overclocking Device Driver is a driver file from company Intel Corporation belonging to product Intel(R) Extreme Tuning Utility Performance Tuning Driver.
Are you overclocking? If so, please return everything to default values. Do you use the tuning utility? If not you can uninstall it or disable it by renaming the driver.
After you complete these tasks, reenable Driver Verifier.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Dump files.zip\Windows7_BSOD_jcgriff2\082710-18642-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02c5e000 PsLoadedModuleList = 0xfffff800`02e9be50 Debug session time: Fri Aug 27 15:45:18.913 2010 (GMT-4) System Uptime: 0 days 1:46:09.975 Loading Kernel Symbols ............................................................... ................................................................ ............. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {ffffffff8b41017a, 1, fffff88005f7fc02, 5} Unable to load image \SystemRoot\system32\drivers\viahduaa.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for viahduaa.sys *** ERROR: Module load completed but symbols could not be loaded for viahduaa.sys Could not read faulting driver name Probably caused by : viahduaa.sys ( viahduaa+162c02 ) Followup: MachineOwner --------- 7: 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: ffffffff8b41017a, memory referenced. Arg2: 0000000000000001, value 0 = read operation, 1 = write operation. Arg3: fffff88005f7fc02, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000005, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f060e0 ffffffff8b41017a FAULTING_IP: viahduaa+162c02 fffff880`05f7fc02 df8d7a01418b fisttp word ptr [rbp-74BEFE86h] MM_INTERNAL_CODE: 5 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0x50 PROCESS_NAME: audiodg.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff880086f65c0 -- (.trap 0xfffff880086f65c0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff880086f67f0 rbx=0000000000000000 rcx=0000000000000002 rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88005f7fc02 rsp=fffff880086f6758 rbp=0000000000000000 r8=0000000000000001 r9=0000000000000000 r10=0000000000000000 r11=fffff98009aeae70 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc viahduaa+0x162c02: fffff880`05f7fc02 df8d7a01418b fisttp word ptr [rbp-74BEFE86h] ss:0018:ffffffff`8b41017a=???? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002d4d8c1 to fffff80002cce740 STACK_TEXT: fffff880`086f6458 fffff800`02d4d8c1 : 00000000`00000050 ffffffff`8b41017a 00000000`00000001 fffff880`086f65c0 : nt!KeBugCheckEx fffff880`086f6460 fffff800`02ccc82e : 00000000`00000001 00000000`c000000d 00000980`00000000 0000007f`fffffff8 : nt! ?? ::FNODOBFM::`string'+0x40e8b fffff880`086f65c0 fffff880`05f7fc02 : fffff880`05f48ce3 00000000`c000000d fffffa80`0664d000 fffffa80`066292b8 : nt!KiPageFault+0x16e fffff880`086f6758 fffff880`05f48ce3 : 00000000`c000000d fffffa80`0664d000 fffffa80`066292b8 fffff800`03173c42 : viahduaa+0x162c02 fffff880`086f6760 00000000`c000000d : fffffa80`0664d000 fffffa80`066292b8 fffff800`03173c42 fffff880`086f67f0 : viahduaa+0x12bce3 fffff880`086f6768 fffffa80`0664d000 : fffffa80`066292b8 fffff800`03173c42 fffff880`086f67f0 fffff880`086f67f8 : 0xc000000d fffff880`086f6770 fffffa80`066292b8 : fffff800`03173c42 fffff880`086f67f0 fffff880`086f67f8 fffff980`44702f68 : 0xfffffa80`0664d000 fffff880`086f6778 fffff800`03173c42 : fffff880`086f67f0 fffff880`086f67f8 fffff980`44702f68 fffffa80`066292b8 : 0xfffffa80`066292b8 fffff880`086f6780 fffffa80`0664d000 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt!ViFilterDispatchGeneric+0x62 fffff880`086f67b0 00000000`00000000 : 00000000`00000000 00000000`00000001 00000000`00000000 fffff980`44702d30 : 0xfffffa80`0664d000 STACK_COMMAND: kb FOLLOWUP_IP: viahduaa+162c02 fffff880`05f7fc02 df8d7a01418b fisttp word ptr [rbp-74BEFE86h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: viahduaa+162c02 FOLLOWUP_NAME: MachineOwner MODULE_NAME: viahduaa IMAGE_NAME: viahduaa.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4b4af7de FAILURE_BUCKET_ID: X64_0x50_VRF_viahduaa+162c02 BUCKET_ID: X64_0x50_VRF_viahduaa+162c02 Followup: MachineOwner --------- 7: kd> lmtsmn start end module name fffff880`04800000 fffff880`0483e000 1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30) fffff880`00f3f000 fffff880`00f96000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`02c1b000 fffff880`02ca5000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`04fd6000 fffff880`04fec000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0) fffff880`00c2a000 fffff880`00c35000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`043c9000 fffff880`043d1000 ASACPI ASACPI.sys Wed May 13 21:25:17 2009 (4A0B72FD) fffff880`073ae000 fffff880`073b9000 asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5) fffff880`00dd5000 fffff880`00dde000 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`040c4000 fffff880`040e7000 AtiHdmi AtiHdmi.sys Thu May 06 05:20:39 2010 (4BE289E7) fffff880`04850000 fffff880`04f7f000 atikmdag atikmdag.sys Tue Jul 06 21:37:28 2010 (4C33DA58) fffff880`040f2000 fffff880`04138000 atikmpag atikmpag.sys Tue Jul 06 21:15:42 2010 (4C33D53E) fffff880`0194d000 fffff880`01954000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`02deb000 fffff880`02dfc000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`03d86000 fffff880`03da4000 bowser bowser.sys Mon Jul 13 19:23:50 2009 (4A5BC206) fffff960`00690000 fffff960`006b7000 cdd cdd.dll unavailable (00000000) fffff880`018ed000 fffff880`01917000 cdrom cdrom.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`00cfb000 fffff880`00dbb000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D) fffff880`01887000 fffff880`018b7000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00c9d000 fffff880`00cfb000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`0114d000 fffff880`011c0000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`043ed000 fffff880`043fd000 CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`05fd7000 fffff880`05fe5000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`01800000 fffff880`0181e000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200) fffff880`02ddc000 fffff880`02deb000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`01235000 fffff880`0124b000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00dde000 fffff880`00e00000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5) fffff880`05ff1000 fffff880`05ffa000 dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`05fe5000 fffff880`05ff1000 dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`05e00000 fffff880`05e13000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`05fcb000 fffff880`05fd7000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574) fffff880`042d5000 fffff880`043c9000 dxgkrnl dxgkrnl.sys Thu Oct 01 21:00:14 2009 (4AC5509E) fffff880`04200000 fffff880`04246000 dxgmms1 dxgmms1.sys Mon Jul 13 19:38:32 2009 (4A5BC578) fffff880`010db000 fffff880`010ef000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`0108f000 fffff880`010db000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`0122b000 fffff880`01235000 Fs_Rec Fs_Rec.sys unavailable (00000000) fffff880`011c0000 fffff880`011fa000 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`02c15000 fffff800`02c5e000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`04246000 fffff880`0426a000 HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5) fffff880`018b7000 fffff880`018d0000 HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD) fffff880`05e13000 fffff880`05e1b080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9) fffff880`041f0000 fffff880`041fe000 hidusb hidusb.sys Mon Jul 13 20:06:22 2009 (4A5BCBFE) fffff880`03cbe000 fffff880`03d86000 HTTP HTTP.sys Mon Jul 13 19:22:16 2009 (4A5BC1A8) fffff880`015e7000 fffff880`015f0000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff880`02c00000 fffff880`02c16000 intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`043dd000 fffff880`043ec880 intelsmb intelsmb.sys Wed May 13 03:31:00 2009 (4A0A7734) fffff880`06cc2000 fffff880`06ccc000 IOCBIOS IOCBIOS.SYS Thu Jul 09 13:47:22 2009 (4A562D2A) fffff880`0483e000 fffff880`0484d000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`03c31000 fffff880`03c3f000 kbdhid kbdhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff800`00bd3000 fffff800`00bdd000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`04000000 fffff880`04043000 ks ks.sys Mon Jul 13 20:00:31 2009 (4A5BCA9F) fffff880`01200000 fffff880`0121a000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156) fffff880`015bc000 fffff880`015e7000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4) fffff880`04ff8000 fffff880`04ffd200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93) fffff880`03c91000 fffff880`03ca6000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`03c4d000 fffff880`03c70000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295) fffff880`00c45000 fffff880`00c89000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66) fffff880`03c3f000 fffff880`03c4d000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C) fffff880`041e1000 fffff880`041f0000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`018d0000 fffff880`018dd000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`00dbb000 fffff880`00dd5000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`01917000 fffff880`01944000 MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0) fffff880`0732d000 fffff880`0733d000 MpNWMon MpNWMon.sys Sat Mar 20 01:58:00 2010 (4BA463E8) fffff880`03da4000 fffff880`03dbc000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79) fffff880`03dbc000 fffff880`03de9000 mrxsmb mrxsmb.sys Sat Feb 27 02:52:19 2010 (4B88CF33) fffff880`06c51000 fffff880`06c9f000 mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C) fffff880`06c9f000 fffff880`06cc2000 mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A) fffff880`019b2000 fffff880`019bd000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00f9f000 fffff880`00fa9000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`010ef000 fffff880`0114d000 msrpc msrpc.sys unavailable (00000000) fffff880`02dd1000 fffff880`02ddc000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`01452000 fffff880`01464000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`0146a000 fffff880`0155c000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`04fec000 fffff880`04ff8000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8) fffff880`0415c000 fffff880`0418b000 ndiswan ndiswan.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`040af000 fffff880`040c4000 NDProxy NDProxy.SYS Mon Jul 13 20:10:05 2009 (4A5BCCDD) fffff880`02d19000 fffff880`02d28000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`02ca5000 fffff880`02cea000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178) fffff880`0155c000 fffff880`015bc000 NETIO NETIO.SYS Mon Jul 13 19:21:46 2009 (4A5BC18A) fffff880`019bd000 fffff880`019ce000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`02dc5000 fffff880`02dd1000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`02c5e000 fffff800`0323a000 nt ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9) fffff880`01251000 fffff880`013f4000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F) fffff880`01944000 fffff880`0194d000 Null Null.SYS unavailable (00000000) fffff880`02cf3000 fffff880`02d19000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5) fffff880`00fe9000 fffff880`00ffe000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00fa9000 fffff880`00fdc000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`00e71000 fffff880`00e78000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115) fffff880`00e78000 fffff880`00e88000 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`06ccc000 fffff880`06d72000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF) fffff880`01844000 fffff880`01881000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00c89000 fffff880`00c9d000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`04138000 fffff880`0415c000 rasl2tp rasl2tp.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`0418b000 fffff880`041a6000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9) fffff880`041a6000 fffff880`041c7000 raspptp raspptp.sys Mon Jul 13 20:10:18 2009 (4A5BCCEA) fffff880`041c7000 fffff880`041e1000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1) fffff880`02d74000 fffff880`02dc5000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219) fffff880`01997000 fffff880`019a0000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`019a0000 fffff880`019a9000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`019a9000 fffff880`019b2000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`0104c000 fffff880`01086000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A) fffff880`03ca6000 fffff880`03cbe000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`04f7f000 fffff880`04fd6000 Rt64win7 Rt64win7.sys Thu Mar 04 08:42:52 2010 (4B8FB8DC) fffff880`06d72000 fffff880`06d7d000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E) fffff880`043d1000 fffff880`043dd000 serenum serenum.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`02d28000 fffff880`02d45000 serial serial.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`0144a000 fffff880`01452000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`07297000 fffff880`0732d000 srv srv.sys Mon Jun 21 23:21:11 2010 (4C202C27) fffff880`0722f000 fffff880`07297000 srv2 srv2.sys Mon Jun 21 23:20:47 2010 (4C202C0F) fffff880`06d7d000 fffff880`06daa000 srvnet srvnet.sys Mon Jun 21 23:20:32 2010 (4C202C00) fffff880`043fd000 fffff880`043fe480 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`06daa000 fffff880`06dbc000 tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD) fffff880`019ec000 fffff880`019f9000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E) fffff880`019ce000 fffff880`019ec000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B) fffff880`02d60000 fffff880`02d74000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64) fffff960`00550000 fffff960`0055a000 TSDDD TSDDD.dll Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`0181e000 fffff880`01844000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1) fffff880`04043000 fffff880`04055000 umbus umbus.sys Mon Jul 13 20:06:56 2009 (4A5BCC20) fffff880`03c14000 fffff880`03c31000 usbccgp usbccgp.sys Mon Jul 13 20:06:45 2009 (4A5BCC15) fffff880`05ffa000 fffff880`05ffbf00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF) fffff880`0426a000 fffff880`0427b000 usbehci usbehci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`04055000 fffff880`040af000 usbhub usbhub.sys Mon Jul 13 20:07:09 2009 (4A5BCC2D) fffff880`0427b000 fffff880`042d1000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07) fffff880`00fdc000 fffff880`00fe9000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`01954000 fffff880`01962000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`05e1d000 fffff880`05fcb000 viahduaa viahduaa.sys Mon Jan 11 05:05:18 2010 (4B4AF7DE) fffff880`01962000 fffff880`01987000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`00e00000 fffff880`00e15000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00e15000 fffff880`00e71000 volmgrx volmgrx.sys unavailable (00000000) fffff880`01000000 fffff880`0104c000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128) fffff880`02d45000 fffff880`02d60000 wanarp wanarp.sys Mon Jul 13 20:10:21 2009 (4A5BCCED) fffff880`01987000 fffff880`01997000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00e8c000 fffff880`00f30000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00f30000 fffff880`00f3f000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`02cea000 fffff880`02cf3000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff960`00060000 fffff960`0036f000 win32k win32k.sys Sat Jun 19 00:31:59 2010 (4C1C483F) fffff880`00f96000 fffff880`00f9f000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`03c70000 fffff880`03c91000 WudfPf WudfPf.sys Mon Jul 13 20:05:37 2009 (4A5BCBD1) Unloaded modules: fffff880`0733d000 fffff880`073ae000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`018b7000 fffff880`018c5000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`018c5000 fffff880`018d1000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`018d1000 fffff880`018da000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`018da000 fffff880`018ed000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000
intelsmb.sys Wed May 13 03:31:00 2009 - system Management Bus 2.0 (SMBus) Driver is a driver file from company Intel Corporation belonging to product Intel(R) SMBus Controller. This is a chipset driver.
IOCBIOS.SYS Thu Jul 09 13:47:22 2009 - Intel(R) Overclocking Device Driver is a driver file from company Intel Corporation belonging to product Intel(R) Extreme Tuning Utility Performance Tuning Driver.
Are you overclocking? If so, please return everything to default values. Do you use the tuning utility? If not you can uninstall it or disable it by renaming the driver.
After you complete these tasks, reenable Driver Verifier.
ok so i turned off driver verifier then uninstalled via drivers and reinstalled them i did have a intel tuning program on there but i have uninstalled that a lil bit ago so idk why that driver is still hanging around.
were would i go to get an updated intelsmb.sys i went to intels website and downloaded there driver package but its and older driver then what i have installed?
thanks for the help
were would i go to get an updated intelsmb.sys i went to intels website and downloaded there driver package but its and older driver then what i have installed?
thanks for the help
You are very welcome.
That Intel driver may be the latest one available. You might try the website of your computer manufacturer or the website for you motherboard.
It would help us if your would fill out system specs. Go to your User CP at the top of the page, look in the left column and click on Edit system specs. Filling in your specs will help us help you.
You can make this easier by downloading Speccy.
Run your computer with the changes you made. If you get another BSOD, upload it and re-enable Driver Verifier. Please keep us updated.
That Intel driver may be the latest one available. You might try the website of your computer manufacturer or the website for you motherboard.
It would help us if your would fill out system specs. Go to your User CP at the top of the page, look in the left column and click on Edit system specs. Filling in your specs will help us help you.
You can make this easier by downloading Speccy.
Run your computer with the changes you made. If you get another BSOD, upload it and re-enable Driver Verifier. Please keep us updated.
alright thanks i uploaded the system specs i did check the motherboards driver list and saw no update for that file. i will keep you updated on the next bsod
thanks!
thanks!
Very good. We will be here.
Ok so let me say this you guys are by far the best support forum that i have ever used so much good info on this website! thanks
that being said i uninstalled the audio drivers and reinstalled them still got a BSOD while playing Heroes of newerth
that being said i uninstalled the audio drivers and reinstalled them still got a BSOD while playing Heroes of newerth
anyone?? i got a new dump file =)
�� Quote: Originally Posted by CyberArena 
anyone?? i got a new dump file =)
You want Option 2- display driver only.
Be sure to remove all Catalyst software first, and then uninstall your display drivers.
...Summary of the Dumps:
Code:
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Tue Aug 31 17:40:16.917 2010 (UTC - 4:00) System Uptime: 0 days 0:13:39.979 BugCheck C5, {fffffa80053b5838, 2, 1, fffff80002def90d} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::OpenOneAllocation+1c8 ) BUGCHECK_STR: 0xC5_2 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: hon.exe �������������������������������������������������������������������������������������� allrighty thanks bro! i did what u said uninstalled restarted and installed just the driver will see what happens now!
Very good. Keep us updated.
Good morning all so i got a couple more BSOD here from the same computer ugh this thing is killing me lol
thank you!!
thank you!!
Both of your most resent dumps are Driver Verifier enabled dumps and both blame wow.exe, World of Warcraft - WoW.exe Windows process - What is it?.
Please turn Driver Verifier off and lets see how your system does: Driver Verifier - Enable and Disable
Please turn Driver Verifier off and lets see how your system does: Driver Verifier - Enable and Disable
Thank you ugh that game is redic i swear it has so many problems with windows vista and windows 7 like the damn wow 134 error that wow says is not there problem and nvidia and ati are blaming blizzard like wtf never ending circle... lol i disabled verifier so will see what happens thanks!
You are welcome. Please keep us posted.
ok got another couple of dumps for you guys sigh this isn't fun anymore lol 
No it isn't fun. Let's see what we can do to end it.
One of the two dumps is error code 19, BAD_POOL_HEADER - usually caused by a device driver. The dump file blames Heroes of Newerth.
The second dump is error code 24, NTFS_FILE_SYSTEM - usual causes are Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure. This dump blames a Windows system file which is most likely not the cause. The dump also points to memory corruption.
It is time to test hardware. Since one of the dumps is error code 24, start by running Check Disk.
Next run Memtest to test your RAM. Follow the instructions in this tutorial by Jonathan King: RAM - Test with Memtest86+
Errors will show up in red. Post your results.
I still see two outdated drivers on your system:
I should have asked this earlier; are you overclocking? If so, stop and return everything overclocked to default values.
Keep us updated.
One of the two dumps is error code 19, BAD_POOL_HEADER - usually caused by a device driver. The dump file blames Heroes of Newerth.
The second dump is error code 24, NTFS_FILE_SYSTEM - usual causes are Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure. This dump blames a Windows system file which is most likely not the cause. The dump also points to memory corruption.
Code:
Kernel base = 0xfffff800`02c52000 PsLoadedModuleList = 0xfffff800`02e8fe50 Debug session time: Fri Oct 1 17:45:02.741 2010 (GMT-4) System Uptime: 0 days 0:31:51.787 Loading Kernel Symbols ............................................................... ................................................................ ................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 19, {20, fffff900c1f00280, fffff900c1f00830, 255b0004} Probably caused by : win32k.sys ( win32k!vProcessCursorShape+390 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_HEADER (19) The pool is already corrupt at the time of the current request. This may or may not be due to the caller. The internal pool links must be walked to figure out a possible cause of the problem, and then special pool applied to the suspect tags or the driver verifier to a suspect driver. Arguments: Arg1: 0000000000000020, a pool block header size is corrupt. Arg2: fffff900c1f00280, The pool entry we were looking for within the page. Arg3: fffff900c1f00830, The next pool entry. Arg4: 00000000255b0004, (reserved) Debugging Details: ------------------ BUGCHECK_STR: 0x19_20 POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efa0e0 fffff900c1f00280 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: hon.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002df56d3 to fffff80002cc2740 STACK_TEXT: fffff880`08a3a7b8 fffff800`02df56d3 : 00000000`00000019 00000000`00000020 fffff900`c1f00280 fffff900`c1f00830 : nt!KeBugCheckEx fffff880`08a3a7c0 fffff960`002d2f98 : fffff900`c0170018 fffff960`003c30d0 fffff900`746c7847 fffff900`c1f002b0 : nt!ExDeferredFreePool+0x12c4 fffff880`08a3a870 fffff960`001350de : fffff900`c1e9acd0 00000000`00000000 fffff900`00000001 fffff900`00000020 : win32k!vProcessCursorShape+0x390 fffff880`08a3a980 fffff960`00134c83 : 00000000`00000000 fffffa80`0559fe50 00000000`00000000 fffff900`00000000 : win32k!vSetPointer+0x2d2 fffff880`08a3aab0 fffff960`001a39b6 : fffff900`c00bf010 fffff900`c1eae290 00000000`00000000 00000000`00000000 : win32k!GreSetPointer+0x177 fffff880`08a3ab60 fffff960`00184cc3 : fffff900`c1fd3c30 fffff880`08a3aca0 00000000`0e554ec0 fffff900`c1f3a770 : win32k!zzzUpdateCursorImage+0x28e fffff880`08a3aba0 fffff960`001cbdeb : 00000000`00000000 fffff880`08a3aca0 00000000`0e554ec0 00000000`fffdb000 : win32k!zzzSetCursor+0x77 fffff880`08a3abf0 fffff800`02cc1993 : fffffa80`0626c930 00000000`0008e270 00000000`00000020 00000000`0008e260 : win32k!NtUserSetCursor+0x4b fffff880`08a3ac20 00000000`750e2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0008ebf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x750e2dd9 STACK_COMMAND: kb FOLLOWUP_IP: win32k!vProcessCursorShape+390 fffff960`002d2f98 488d0d41130f00 lea rcx,[win32k!xlateTable (fffff960`003c42e0)] SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: win32k!vProcessCursorShape+390 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c483f FAILURE_BUCKET_ID: X64_0x19_20_win32k!vProcessCursorShape+390 BUCKET_ID: X64_0x19_20_win32k!vProcessCursorShape+390 Followup: MachineOwner --------- Kernel base = 0xfffff800`02c64000 PsLoadedModuleList = 0xfffff800`02ea1e50 Debug session time: Fri Oct 1 18:21:38.002 2010 (GMT-4) System Uptime: 0 days 0:17:39.937 Loading Kernel Symbols ............................................................... ................................................................ ................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 24, {1904fb, fffff8800861b798, fffff8800861b000, fffff880012bfa91} Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefix+121 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* NTFS_FILE_SYSTEM (24) If you see NtfsExceptionFilter on the stack then the 2nd and 3rd parameters are the exception record and context record. Do a .cxr on the 3rd parameter and then kb to obtain a more informative stack trace. Arguments: Arg1: 00000000001904fb Arg2: fffff8800861b798 Arg3: fffff8800861b000 Arg4: fffff880012bfa91 Debugging Details: ------------------ EXCEPTION_RECORD: fffff8800861b798 -- (.exr 0xfffff8800861b798) ExceptionAddress: fffff880012bfa91 (Ntfs!NtfsFindPrefix+0x0000000000000121) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 00000000bde088c0 Attempt to read from address 00000000bde088c0 CONTEXT: fffff8800861b000 -- (.cxr 0xfffff8800861b000) rax=fffff8a00c622782 rbx=fffff8a0003814a0 rcx=000000000000b2ae rdx=0000000000000050 rsi=fffff8a0001f5bc0 rdi=fffff8a000381490 rip=fffff880012bfa91 rsp=fffff8800861b9d0 rbp=fffff8800861bc60 r8=0000000000000007 r9=00000000bde088c0 r10=fffff8800861ba30 r11=fffff8800861ba10 r12=0000000000000016 r13=0000000000000000 r14=0000000000000000 r15=fffff88007def438 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 Ntfs!NtfsFindPrefix+0x121: fffff880`012bfa91 410fb709 movzx ecx,word ptr [r9] ds:002b:00000000`bde088c0=???? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: spoolsv.exe CURRENT_IRQL: 1 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 00000000bde088c0 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0c0e0 00000000bde088c0 FOLLOWUP_IP: Ntfs!NtfsFindPrefix+121 fffff880`012bfa91 410fb709 movzx ecx,word ptr [r9] FAULTING_IP: Ntfs!NtfsFindPrefix+121 fffff880`012bfa91 410fb709 movzx ecx,word ptr [r9] BUGCHECK_STR: 0x24 LAST_CONTROL_TRANSFER: from fffff880012b0f74 to fffff880012bfa91 STACK_TEXT: fffff880`0861b9d0 fffff880`012b0f74 : fffffa80`04555360 fffff8a0`001f5bc0 fffff880`07def418 fffff880`0861bc10 : Ntfs!NtfsFindPrefix+0x121 fffff880`0861ba80 fffff880`012ab28d : fffffa80`04555360 fffffa80`04e308f0 fffff880`0861bc60 fffff880`0861bca8 : Ntfs!NtfsFindStartingNode+0x6e4 fffff880`0861bb50 fffff880`01214c0d : fffffa80`04555360 fffffa80`04e308f0 fffff880`07def3b0 00000000`00000000 : Ntfs!NtfsCommonCreate+0x3dd fffff880`0861bd30 fffff800`02ccc5c7 : fffff880`07def320 00000000`02317250 00000000`77bc4270 00000000`00000000 : Ntfs!NtfsCommonCreateCallout+0x1d fffff880`0861bd60 fffff800`02ccc581 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27 fffff880`07def1f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: Ntfs!NtfsFindPrefix+121 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Ntfs IMAGE_NAME: Ntfs.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc14f STACK_COMMAND: .cxr 0xfffff8800861b000 ; kb FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsFindPrefix+121 BUCKET_ID: X64_0x24_Ntfs!NtfsFindPrefix+121 Followup: MachineOwner --------- Quote:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.
Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"
CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP).
Copy/paste the results into your next post.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.
Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"
CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP).
Copy/paste the results into your next post.
Next run Memtest to test your RAM. Follow the instructions in this tutorial by Jonathan King: RAM - Test with Memtest86+
Errors will show up in red. Post your results.
I still see two outdated drivers on your system:
Quote:
intelsmb.sys Wed May 13 03:31:00 2009 -
Quote:
System Management Bus 2.0 (SMBus) Driver is a driver file from Intel Corporation belonging to Intel(R) SMBus Controller. http://downloadcenter.intel.com/Default.aspx. Update this driver
IOCBIOS.SYS Thu Jul 09 13:47:22 2009 - I think this is a thermal monitoring driver. Intel(R) Overclocking Device Driver is a driver file from Intel Corporation belonging to Intel(R) Extreme Tuning Utility Performance Tuning Driver. http://downloadcenter.intel.com/Default.aspx. update this driver.
IOCBIOS.SYS Thu Jul 09 13:47:22 2009 - I think this is a thermal monitoring driver. Intel(R) Overclocking Device Driver is a driver file from Intel Corporation belonging to Intel(R) Extreme Tuning Utility Performance Tuning Driver. http://downloadcenter.intel.com/Default.aspx. update this driver.
Keep us updated.
ok well it has blamed wow 2 times now and heroes of newerth im starting to think that this is a ram issues i have ran the standard memory test threw windows 7 but we all know how well Microsoft tools are lol i will run the ram test right now! and will see what happens thanks!!
Waiting to see your results. The Windows memory test is OK. In my opinion, it does not stress the RAM enough and is not thorough enough.
well ya that's what i was getting at it does the job but only skims the surface! ok so i started off with 1 2gb stick on the board i ran it for a total of 21 hours with 52 pass's no errors so i am now trying both sticks right now so i will let you know what happens then. but here is the thing i did not pick the parts out for this pc i just built it i don't see the ram anywhere in this mother board booklet for being correct for this board.
motherboard: asus P7P55D
Ram: ocz30b1600lv4gk
i know the motherboard booklet says do not put any ram over 1.65v on the board and this ram is 1.65v.
if this test comes back with no errors i will be lost... sigh
thanks for all the help guys hopefully i can learn something new from this lol
motherboard: asus P7P55D
Ram: ocz30b1600lv4gk
i know the motherboard booklet says do not put any ram over 1.65v on the board and this ram is 1.65v.
if this test comes back with no errors i will be lost... sigh
thanks for all the help guys hopefully i can learn something new from this lol
ok after putting the second stick of ram in i did not even get 1 pass done and there were already over 1020 errors
test: 4
Failing add:0040200080-1026.0mb
Good:db99eb9d
Bad:db59eb9b
Err:00c0000
test: 4
Failing add:0004020038-1026.0mb
Good:db99eb9d
Bad:db58eb9b
Err:00c1000
test: 4
Failing add:0004020030-1026.0mb
Good:db99eb9d
Bad:dbcceb9b
Err:00550000
to sum it up the
First test: i did i had 1 stick in Dim-A1 (no errors 52 pass)
Second test: i had both sticks in Dim-A1, Dim-A2 (1020 errors 1 pass)
Third test: i am ruining now but i took out the stick from Dim-A1 (it has made it threw its first pass with out any errors)
i think the problem comes from having both sticks installed on the board at a time can that be timing issues?
test: 4
Failing add:0040200080-1026.0mb
Good:db99eb9d
Bad:db59eb9b
Err:00c0000
test: 4
Failing add:0004020038-1026.0mb
Good:db99eb9d
Bad:db58eb9b
Err:00c1000
test: 4
Failing add:0004020030-1026.0mb
Good:db99eb9d
Bad:dbcceb9b
Err:00550000
to sum it up the
First test: i did i had 1 stick in Dim-A1 (no errors 52 pass)
Second test: i had both sticks in Dim-A1, Dim-A2 (1020 errors 1 pass)
Third test: i am ruining now but i took out the stick from Dim-A1 (it has made it threw its first pass with out any errors)
i think the problem comes from having both sticks installed on the board at a time can that be timing issues?
We have limited it down to 3 possible causes: a bad motherboard, a bad stick of RAM, or incompatibility between the sticks and board.
Make sure it isn't the 2nd stick of RAM. Run Memtest on that stick only, in Slot 1.
I suspect it will pass, however. Most likely the sticks are mismatched.
Try setting the RAM timings to 9-9-9-24, and then test both sticks at the same time.
Make sure it isn't the 2nd stick of RAM. Run Memtest on that stick only, in Slot 1.
I suspect it will pass, however. Most likely the sticks are mismatched.
Try setting the RAM timings to 9-9-9-24, and then test both sticks at the same time.
Lancaster is spot on; follow his advice and report back.
ok well i have had the second stick in slot A2 and have had the test runing for bout 4 hours now no errors so the sticks are not bad i know that for sure so ill have to take a look at the timeing in bios but im pretty sure its going to be incompatibility because the sticks of ram are not mentioned in the motherboard booklet what ram would u suggest for me i need 4 gigs at least
the bios had the ram set to 7-7-7-20 so i changed it to 9-9-9-24 with both ram on the board im running the test now
ok well with both sticks on the board and 18 hours and 24 pass later no errors so im gonna stop the testing on the ram and run the system i will post up results hopefully no more BSOD!!!!
thanks guy s
thanks guy s
Good work. I hope you get no more BSOD's. Thanks for the update.
alright so it has been bout half a day with no BSOD ill keep ya updated also do you guys have any go articles i can read about Ram timing i would like to know a little more about it thanks!!
That is good news and thanks for the update. Post your question about RAM timings in the hardware section. There are some real experts there who can steer you to the right reading materials.
sigh ok so i was playing FF14 and it crashed blue screen ugh
I am sorry to hear that. i recommend that you invest in RAM that is compatible with your motherboard.
so you really think its the ram then?? any suggestions on what ram i should buy?
Newegg.com - G.SKILL Ripjaws Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-12800CL9D-4GBRL
think i could get away with running this set on my board? it says its for my chipset and i7
o this set of ram because it was listing in the motherboard booklet
http://www.newegg.com/Product/Produc...82E16820231223
think i could get away with running this set on my board? it says its for my chipset and i7
o this set of ram because it was listing in the motherboard booklet
http://www.newegg.com/Product/Produc...82E16820231223
I think it is RAM because of the results from Memtest. Whether it is a compatibility problem or bad RAM. I don't know. I will ask the hardware guys to take a look at this thread. I am not an expert with RAM.
Your latest dump shows error code 19, BAD_POOL_HEADER, which is usually caused by a device driver. I see one outdated driver on your system:
Your latest dump shows error code 19, BAD_POOL_HEADER, which is usually caused by a device driver. I see one outdated driver on your system:
Quote:
intelsmb.sys Wed May 13 03:31:00 2009 - System Management Bus 2.0 (SMBus) Driver is a driver file from Intel Corporation belonging to Intel(R) SMBus Controller. http://downloadcenter.intel.com/Default.aspx
It's been a couple of days, hope you got the problem figured out.
If not, download CPUZ and post the CPU, Mainboard, Memory and SPD tabs.
Once we can see your exact RAM settings and recommended settings (SPD), a couple adjustments may be able to get this running better.
Looks like you saw some improvement when you changed the timings, did you also change the frequency?
Also, go into your BIOS and tell us what the DRAM and IMC voltages are.
Your motherboard recommended RAM list is found at Memory/Device Support: http://www.asus.com/product.aspx?P_ID=RBA8CzWoopUlYRFZ#
It looks like you have 2X2GB RAM, two cards, if this is correct they should in DIMM (blue) slots A1 and B1, as per page 2-18 of your Asus motherboard manual.
If you have been running the RAM in slots A1 and A2, this shouldn't cause crashes but will be in single channel mode, putting them in slots A1 and B1 will be Dual channel mode.
Let us know your progress or if you have found a solution.
If not, download CPUZ and post the CPU, Mainboard, Memory and SPD tabs.
Once we can see your exact RAM settings and recommended settings (SPD), a couple adjustments may be able to get this running better.
Looks like you saw some improvement when you changed the timings, did you also change the frequency?
Also, go into your BIOS and tell us what the DRAM and IMC voltages are.
Your motherboard recommended RAM list is found at Memory/Device Support: http://www.asus.com/product.aspx?P_ID=RBA8CzWoopUlYRFZ#
It looks like you have 2X2GB RAM, two cards, if this is correct they should in DIMM (blue) slots A1 and B1, as per page 2-18 of your Asus motherboard manual.
If you have been running the RAM in slots A1 and A2, this shouldn't cause crashes but will be in single channel mode, putting them in slots A1 and B1 will be Dual channel mode.
Let us know your progress or if you have found a solution.
alright good stuff guys i have been busy but ill will get to this some time this week ill let you know all the stuff u guys asked me thanks!!!
You are welcome. We will be here waiting.
Let us know when you have the time, no hurry.
ok got around to running cpu-z here is the result's
and i also looked for the driver intelsmb.sys on there website i only find a 2008 version
and i also looked for the driver intelsmb.sys on there website i only find a 2008 version
Your RAM settings are a little strange, is this RAM on your motherboard compatibility list?
It's 1600MHz RAM but doesn't say that on the SPD tabs.
Usually the SPD tab info is closer to standard settings, these are between standard settings, 609 ie 1218MHz.
Try setting the first four RAM timings manually at the JEDEC #3 settings of 7-7-7-16, and the command rate at 2. Leave the rest on auto.
Make sure the RAM cards are in slots A1 and B1.
Run memtest86+ as in this tutorial:
It's 1600MHz RAM but doesn't say that on the SPD tabs.
Usually the SPD tab info is closer to standard settings, these are between standard settings, 609 ie 1218MHz.
Try setting the first four RAM timings manually at the JEDEC #3 settings of 7-7-7-16, and the command rate at 2. Leave the rest on auto.
Make sure the RAM cards are in slots A1 and B1.
Run memtest86+ as in this tutorial:
If you get errors you can stop the test and let us know what errors you have.
thank you! i know they did look off to me the ram is not in the list. i have another set of ram on order right now will see how this one goes its on there list!
Let us know when you get your new RAM and how your system does with it.
will do!!
but i will try the settings you told me to as well just for giggles lol but its been a busy week!!
but i will try the settings you told me to as well just for giggles lol but its been a busy week!!
Good luck!!
Good decision on getting compatible RAM, it will be much better in the long run.
Sometimes you can get non-compatible RAM to run, but will have isssues popping up all the time.
What is the brand and part number of the RAM you ordered?
Let us know how it's running when you get it.
Sometimes you can get non-compatible RAM to run, but will have isssues popping up all the time.
What is the brand and part number of the RAM you ordered?
Let us know how it's running when you get it.
Không có nhận xét nào:
Đăng nhận xét