Hi Guys im having Problem with my ENDLESS BSOD im running Win7 64Bit 4GB with no Issue i Think? but. when im trying to Boot all of my Ram its goin Crazy and it Shows up 0x000000d1 DRIVER_IRQL_NOT_LESS_OR_EQUAL Caused by Driver tcpip.sys Caused by Address tcpip.sys+8d546 i dont know what this numbers are....if you want to know more Info im willing to give it.... Please help me to fix this i want use my pc more and more with no BSOD Here are some list of my Driver Nvidia GeForce GTS 250 Driver Version 8.17.12.7061 Realtek PCIe GBE Family Controller Driver Version 7.43.321.2011 Realtek High Definition Audio Driver Version 6.0.1.5859 Core i7 920 Corsair 6GB 3Pcs i forgot what kind of mem im running mem test for straight 3days almost with no errors

Bug Check Code 0xD1: http://msdn.microsoft.com/en-us/library/ff560244(VS.85).aspx Please use Microsoft Skydrive to upload dump files (c:\windows\minidumps). Once done, post a link here. You can also contact Microsoft CSS. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified IT Professional: Enterprise Administrator

Reads a lot like a rootkit/bootkit infection, can you boot to Safe Mode with networking?

i can boot windows when im using 4gb ram without any problems. but when im using 6gm ram BSOD show up with some numbers here Dump Files http://cid-9f06c78267e2ef35.office.live.com/downloadfolder.aspx/DUMP%20FILES?canary=HffmC8d0ad3pZmeICKFKPumyx8f63n537mr2uR%2fKjSM%3d3 Meggie21

Hello, why the link is not set for public access? If the output is what satrow posted then I suggest using memtest86+ to check that all is okay with your RAM and to update all possible drivers. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified IT Professional: Enterprise Administrator

What happens if you boot with the 2x1 GB RAM only? Uninstall Daemon Tools. Then uninstall it fully using the tool here. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {0, 2, 0, fffff880018e3546} *** 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 --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 0000000000000000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff880018e3546, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003902100 0000000000000000 CURRENT_IRQL: 2 FAULTING_IP: tcpip!TcpMppEventHandler+46 fffff880`018e3546 3b240f cmp esp,dword ptr [rdi+rcx] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff8800318c200 -- (.trap 0xfffff8800318c200) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880018e3546 rsp=fffff8800318c390 rbp=0000000000000000 r8=0000000000000008 r9=0000000000008a49 r10=0000000000008c81 r11=0000000000000004 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc tcpip!TcpMppEventHandler+0x46: fffff880`018e3546 3b240f cmp esp,dword ptr [rdi+rcx] ds:8080:00000000`00000000=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800036d22a9 to fffff800036d2d00 STACK_TEXT: fffff880`0318c0b8 fffff800`036d22a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`0318c0c0 fffff800`036d0f20 : fffffa80`0849ecb0 fffffa80`08da0590 fffffa80`08d62d5c fffff880`0318c418 : nt!KiBugCheckDispatch+0x69 fffff880`0318c200 fffff880`018e3546 : fffffa80`063bcc40 fffff880`018e3a88 fffffa80`063bdd40 00000000`00000000 : nt!KiPageFault+0x260 fffff880`0318c390 fffff880`018e3402 : fffffa80`065292e0 fffffa80`065292e0 00000000`00000002 00000000`00008a49 : tcpip!TcpMppEventHandler+0x46 fffff880`0318c3c0 fffff880`018e2790 : 00000000`00000022 00000000`00000162 fffffa80`063dbd40 fffffa80`00008a49 : tcpip!TcpTimerMppTimeoutHandler+0x72 fffff880`0318c470 fffff800`036de652 : fffff880`03164180 00000000`00000002 fffff880`0318c600 00000000`00000001 : tcpip!TcpPeriodicTimeoutHandler+0x70f fffff880`0318c570 fffff800`036de4f6 : fffffa80`065293b0 00000000`0000586b 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66 fffff880`0318c5e0 fffff800`036de3de : 00000000`d278b594 fffff880`0318cc58 00000000`0000586b fffff880`031672e8 : nt!KiProcessExpiredTimerList+0xc6 fffff880`0318cc30 fffff800`036de1c7 : 00000000`3712aac1 00000000`0000586b 00000000`3712aaa1 00000000`0000006b : nt!KiTimerExpiration+0x1be fffff880`0318ccd0 fffff800`036caa2a : fffff880`03164180 fffff880`0316f0c0 00000000`00000000 fffff800`037eab90 : nt!KiRetireDpcList+0x277 fffff880`0318cd80 00000000`00000000 : fffff880`0318d000 fffff880`03187000 fffff880`0318cd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -db !tcpip 8 errors : !tcpip (fffff880018e3547-fffff880018e357f) fffff880018e3540 b1 0d aa 31 10 00 3b *24 0f 85 82 37 01 00 8b *41 ...1..;$...7...A fffff880018e3550 f0 0f c1 05 28 32 10 *34 8b cf f0 0f c1 0d 22 *42 ....(2.4......"B fffff880018e3560 10 00 39 7b 10 0f 84 *ff 37 01 00 8b 43 10 3b *db ..9{....7...C.;. fffff880018e3570 48 8b 74 24 30 0f 85 *5f 37 01 00 48 8b 7c 24 *9a H.t$0.._7..H.|$. 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 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {0, 2, 0, fffff880018e3546} *** 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 --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 0000000000000000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff880018e3546, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003902100 0000000000000000 CURRENT_IRQL: 2 FAULTING_IP: tcpip!TcpMppEventHandler+46 fffff880`018e3546 3b240f cmp esp,dword ptr [rdi+rcx] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff8800318c200 -- (.trap 0xfffff8800318c200) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880018e3546 rsp=fffff8800318c390 rbp=0000000000000000 r8=0000000000000008 r9=0000000000008a49 r10=0000000000008c81 r11=0000000000000004 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc tcpip!TcpMppEventHandler+0x46: fffff880`018e3546 3b240f cmp esp,dword ptr [rdi+rcx] ds:8080:00000000`00000000=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800036d22a9 to fffff800036d2d00 STACK_TEXT: fffff880`0318c0b8 fffff800`036d22a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`0318c0c0 fffff800`036d0f20 : fffffa80`0849ecb0 fffffa80`08da0590 fffffa80`08d62d5c fffff880`0318c418 : nt!KiBugCheckDispatch+0x69 fffff880`0318c200 fffff880`018e3546 : fffffa80`063bcc40 fffff880`018e3a88 fffffa80`063bdd40 00000000`00000000 : nt!KiPageFault+0x260 fffff880`0318c390 fffff880`018e3402 : fffffa80`065292e0 fffffa80`065292e0 00000000`00000002 00000000`00008a49 : tcpip!TcpMppEventHandler+0x46 fffff880`0318c3c0 fffff880`018e2790 : 00000000`00000022 00000000`00000162 fffffa80`063dbd40 fffffa80`00008a49 : tcpip!TcpTimerMppTimeoutHandler+0x72 fffff880`0318c470 fffff800`036de652 : fffff880`03164180 00000000`00000002 fffff880`0318c600 00000000`00000001 : tcpip!TcpPeriodicTimeoutHandler+0x70f fffff880`0318c570 fffff800`036de4f6 : fffffa80`065293b0 00000000`0000586b 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66 fffff880`0318c5e0 fffff800`036de3de : 00000000`d278b594 fffff880`0318cc58 00000000`0000586b fffff880`031672e8 : nt!KiProcessExpiredTimerList+0xc6 fffff880`0318cc30 fffff800`036de1c7 : 00000000`3712aac1 00000000`0000586b 00000000`3712aaa1 00000000`0000006b : nt!KiTimerExpiration+0x1be fffff880`0318ccd0 fffff800`036caa2a : fffff880`03164180 fffff880`0316f0c0 00000000`00000000 fffff800`037eab90 : nt!KiRetireDpcList+0x277 fffff880`0318cd80 00000000`00000000 : fffff880`0318d000 fffff880`03187000 fffff880`0318cd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -db !tcpip 8 errors : !tcpip (fffff880018e3547-fffff880018e357f) fffff880018e3540 b1 0d aa 31 10 00 3b *24 0f 85 82 37 01 00 8b *41 ...1..;$...7...A fffff880018e3550 f0 0f c1 05 28 32 10 *34 8b cf f0 0f c1 0d 22 *42 ....(2.4......"B fffff880018e3560 10 00 39 7b 10 0f 84 *ff 37 01 00 8b 43 10 3b *db ..9{....7...C.;. fffff880018e3570 48 8b 74 24 30 0f 85 *5f 37 01 00 48 8b 7c 24 *9a H.t$0.._7..H.|$. 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

Its on Public Access and everyone can download it... i can boot in safe mode without having BSOD my problem here is.... why i cant boot my pc either on safemode when im using 6GB ram and i already run MEMTEST for almost 3days straight without any errors Meggie21

What happens if you boot with the 2x1 GB RAM only? Uninstall Daemon Tools. Then uninstall it fully using the tool here. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {0, 2, 0, fffff880018e3546} *** 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 --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 0000000000000000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff880018e3546, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003902100 0000000000000000 CURRENT_IRQL: 2 FAULTING_IP: tcpip!TcpMppEventHandler+46 fffff880`018e3546 3b240f cmp esp,dword ptr [rdi+rcx] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff8800318c200 -- (.trap 0xfffff8800318c200) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880018e3546 rsp=fffff8800318c390 rbp=0000000000000000 r8=0000000000000008 r9=0000000000008a49 r10=0000000000008c81 r11=0000000000000004 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc tcpip!TcpMppEventHandler+0x46: fffff880`018e3546 3b240f cmp esp,dword ptr [rdi+rcx] ds:8080:00000000`00000000=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800036d22a9 to fffff800036d2d00 STACK_TEXT: fffff880`0318c0b8 fffff800`036d22a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`0318c0c0 fffff800`036d0f20 : fffffa80`0849ecb0 fffffa80`08da0590 fffffa80`08d62d5c fffff880`0318c418 : nt!KiBugCheckDispatch+0x69 fffff880`0318c200 fffff880`018e3546 : fffffa80`063bcc40 fffff880`018e3a88 fffffa80`063bdd40 00000000`00000000 : nt!KiPageFault+0x260 fffff880`0318c390 fffff880`018e3402 : fffffa80`065292e0 fffffa80`065292e0 00000000`00000002 00000000`00008a49 : tcpip!TcpMppEventHandler+0x46 fffff880`0318c3c0 fffff880`018e2790 : 00000000`00000022 00000000`00000162 fffffa80`063dbd40 fffffa80`00008a49 : tcpip!TcpTimerMppTimeoutHandler+0x72 fffff880`0318c470 fffff800`036de652 : fffff880`03164180 00000000`00000002 fffff880`0318c600 00000000`00000001 : tcpip!TcpPeriodicTimeoutHandler+0x70f fffff880`0318c570 fffff800`036de4f6 : fffffa80`065293b0 00000000`0000586b 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66 fffff880`0318c5e0 fffff800`036de3de : 00000000`d278b594 fffff880`0318cc58 00000000`0000586b fffff880`031672e8 : nt!KiProcessExpiredTimerList+0xc6 fffff880`0318cc30 fffff800`036de1c7 : 00000000`3712aac1 00000000`0000586b 00000000`3712aaa1 00000000`0000006b : nt!KiTimerExpiration+0x1be fffff880`0318ccd0 fffff800`036caa2a : fffff880`03164180 fffff880`0316f0c0 00000000`00000000 fffff800`037eab90 : nt!KiRetireDpcList+0x277 fffff880`0318cd80 00000000`00000000 : fffff880`0318d000 fffff880`03187000 fffff880`0318cd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -db !tcpip 8 errors : !tcpip (fffff880018e3547-fffff880018e357f) fffff880018e3540 b1 0d aa 31 10 00 3b *24 0f 85 82 37 01 00 8b *41 ...1..;$...7...A fffff880018e3550 f0 0f c1 05 28 32 10 *34 8b cf f0 0f c1 0d 22 *42 ....(2.4......"B fffff880018e3560 10 00 39 7b 10 0f 84 *ff 37 01 00 8b 43 10 3b *db ..9{....7...C.;. fffff880018e3570 48 8b 74 24 30 0f 85 *5f 37 01 00 48 8b 7c 24 *9a H.t$0.._7..H.|$. 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 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {0, 2, 0, fffff880018e3546} *** 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 --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 0000000000000000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff880018e3546, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003902100 0000000000000000 CURRENT_IRQL: 2 FAULTING_IP: tcpip!TcpMppEventHandler+46 fffff880`018e3546 3b240f cmp esp,dword ptr [rdi+rcx] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff8800318c200 -- (.trap 0xfffff8800318c200) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880018e3546 rsp=fffff8800318c390 rbp=0000000000000000 r8=0000000000000008 r9=0000000000008a49 r10=0000000000008c81 r11=0000000000000004 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc tcpip!TcpMppEventHandler+0x46: fffff880`018e3546 3b240f cmp esp,dword ptr [rdi+rcx] ds:8080:00000000`00000000=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800036d22a9 to fffff800036d2d00 STACK_TEXT: fffff880`0318c0b8 fffff800`036d22a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`0318c0c0 fffff800`036d0f20 : fffffa80`0849ecb0 fffffa80`08da0590 fffffa80`08d62d5c fffff880`0318c418 : nt!KiBugCheckDispatch+0x69 fffff880`0318c200 fffff880`018e3546 : fffffa80`063bcc40 fffff880`018e3a88 fffffa80`063bdd40 00000000`00000000 : nt!KiPageFault+0x260 fffff880`0318c390 fffff880`018e3402 : fffffa80`065292e0 fffffa80`065292e0 00000000`00000002 00000000`00008a49 : tcpip!TcpMppEventHandler+0x46 fffff880`0318c3c0 fffff880`018e2790 : 00000000`00000022 00000000`00000162 fffffa80`063dbd40 fffffa80`00008a49 : tcpip!TcpTimerMppTimeoutHandler+0x72 fffff880`0318c470 fffff800`036de652 : fffff880`03164180 00000000`00000002 fffff880`0318c600 00000000`00000001 : tcpip!TcpPeriodicTimeoutHandler+0x70f fffff880`0318c570 fffff800`036de4f6 : fffffa80`065293b0 00000000`0000586b 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66 fffff880`0318c5e0 fffff800`036de3de : 00000000`d278b594 fffff880`0318cc58 00000000`0000586b fffff880`031672e8 : nt!KiProcessExpiredTimerList+0xc6 fffff880`0318cc30 fffff800`036de1c7 : 00000000`3712aac1 00000000`0000586b 00000000`3712aaa1 00000000`0000006b : nt!KiTimerExpiration+0x1be fffff880`0318ccd0 fffff800`036caa2a : fffff880`03164180 fffff880`0316f0c0 00000000`00000000 fffff800`037eab90 : nt!KiRetireDpcList+0x277 fffff880`0318cd80 00000000`00000000 : fffff880`0318d000 fffff880`03187000 fffff880`0318cd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -db !tcpip 8 errors : !tcpip (fffff880018e3547-fffff880018e357f) fffff880018e3540 b1 0d aa 31 10 00 3b *24 0f 85 82 37 01 00 8b *41 ...1..;$...7...A fffff880018e3550 f0 0f c1 05 28 32 10 *34 8b cf f0 0f c1 0d 22 *42 ....(2.4......"B fffff880018e3560 10 00 39 7b 10 0f 84 *ff 37 01 00 8b 43 10 3b *db ..9{....7...C.;. fffff880018e3570 48 8b 74 24 30 0f 85 *5f 37 01 00 48 8b 7c 24 *9a H.t$0.._7..H.|$. 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 i can boot safely with 4gb x2 ram without having BSOD also on Safe mode with networking Meggie21

Memtest + 'almost' no errors = not good enough. Check each stick for 7 passes of memtest - ANY errors need further investigation. Ok, uninstall Daemon Tools. Next, uninstall sptd.sys. Now test 'pairs' of RAM sticks:- #1+#2 RAM sticks work ok? #1+3 RAM sticks work ok? #2+#3 RAM sticks work ok? Then check and set the BIOS RAM settings to the settings listed by Corsair for your exact RAM sticks. Test with 3x2GB. Try setting the RAM settings in the BIOS to 1066Mhz. Test with 3x2GB. Still no good? Is the exact RAM type listed in the QVL for your motherboard - are you really sure = 3x2 is listed, same # as yours? BugCheck D1, {0, 2, 0, fffff880018e3546}*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : memory_corruption Corrupt Windows file (win32k.sys) = could be caused by malware.

Hello, please run a full scan on your disks to detect malware programs and then uninstall them. If this does not help, I think it will be better to contact your manufacturer Technical Support. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified IT Professional: Enterprise Administrator