BSoD & Crashing with new PC

aav · 10 Dec 2010

I'm getting random but infrequent BSoDs with my dad's new PC. I'm going to tell you everything i did so this may be long

*note* I have reinstalled windows 7x64 twice.

Specs:

Core i3 540
Intel DH55pj Motherboard
Corsair 2GB DDR3 1333mhz (VS2GB1333D3)
Seagate 250GB HDD
Coolermaster elite 334 with thermal master 420W PSU

*First win 7 install*
The system has Windows 7 x64 installed and was bought 1 week back.

Initially ran memtest86+ for over 3 passes which did not show an error after the first BSoD. The PC worked fine for a day or two so i thought that it was just a fluke. Then while using the PC, some programs (like firefox and the search indexer) crashed. I opened CPU-Z which caused the system to freeze for a bit and then i got another BSoD. Ran the Windows 7 memory test and it said there is a hardware problem with the memory. I went on to corsair forums and they said to change the memory timings to manually configured (seems to solve the problem for some) so i did and also put the ram into another mem slot.
Ran prime95 and CPU z for an hour or so and there was no prob with the system. I also ran memtest for over 14 passes and...once again no error.

I have updated the BIOS (did that right after the first BSoD). I've checked the timings and voltage of the RAM from Corsair's website (9-9-9-24 1.5v) and that's what i set.

Had ESET installed but removed it and installed MSE.
Checked the c drive using checkdisk /f /r and checked for bad sectors...none.
Did the SFC /scannow and got no error.

I saved the minidumps and uploaded them as 1st install.zip

*second windows install*
The first install went BSoD crazy so i reformatted the c partition on my HDD and installed win 7 x64 off a USB drive.
Reinstalling Windows 7 with drivers and some other essential programs (Office 2010, messenger, firefox) still caused the system to crash. At first it was firefox crashing, now different parts of the system crash (see below) and i got new BSoD's (page fault in non-paged area with win32.sys). Some minidumps i couldn't upload because event viewer says creating it failed

. The system is really unstable at times and starting up in safe mode still causes firefox to crash. Could it be a hardware problem or a failed windows update of .net v4 causing this? or a corrupted install of win7 (though i checked the iso with win 7 iso checker)?

this repeatedly comes up at startup in the event viewer:

Session "Microsoft Security Essentials OOBE" stopped due to the following error: 0xC000000D

and these are the app crashes (most have multiple instances occuring like 4-5 times each):

Faulting application name: wmiprvse.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc794
Faulting module name: ole32.dll, version: 6.1.7600.16624, time stamp: 0x4c2984e3
Exception code: 0xc0000005
Fault offset: 0x000000000016f347
Faulting process id: 0x3b8
Faulting application start time: 0x01cb967301355e9f
Faulting application path: C:\Windows\system32\wbem\wmiprvse.exe
Faulting module path: C:\Windows\system32\ole32.dll
Report Id: 163905ed-0267-11e0-aa33-7071bca847ba

Faulting application name: WINWORD.EXE, version: 14.0.4734.1000, time stamp: 0x4b58fafb
Faulting module name: mso.dll, version: 14.0.4734.1000, time stamp: 0x4b59081c
Exception code: 0xc000041d
Fault offset: 0x0000000000022c81
Faulting process id: 0xf2c
Faulting application start time: 0x01cb9672c4a64a5e
Faulting application path: C:\Program Files\Microsoft Office\Office14\WINWORD.EXE
Faulting module path: C:\Program Files\Common Files\Microsoft Shared\office14\mso.dll
Report Id: 58af7417-0266-11e0-aa33-7071bca847ba

Faulting application name: svchost.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: RPCRT4.dll, version: 6.1.7600.16385, time stamp: 0x4a5be035
Exception code: 0xc0000005
Fault offset: 0x000000000004a154
Faulting process id: 0x48c
Faulting application start time: 0x01cb967078d7059c
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Windows\system32\RPCRT4.dll
Report Id: 9827f3b5-0265-11e0-aa33-7071bca847ba

Faulting application name: svchost.exe_SysMain, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: sysmain.dll, version: 6.1.7600.16385, time stamp: 0x4a5be07e
Exception code: 0xc0000005
Fault offset: 0x0000000000016d11
Faulting process id: 0x7c
Faulting application start time: 0x01cb9670780cb0a4
Faulting application path: C:\Windows\System32\svchost.exe
Faulting module path: c:\windows\system32\sysmain.dll
Report Id: 3853cded-0265-11e0-aa33-7071bca847ba

Faulting application name: msseces.exe, version: 1.0.2498.0, time stamp: 0x4c90a404
Faulting module name: gdiplus.dll, version: 6.1.7600.16385, time stamp: 0x4a5bde67
Exception code: 0xc000041d
Fault offset: 0x000000000009386b
Faulting process id: 0x9b8
Faulting application start time: 0x01cb967087964c0e
Faulting application path: C:\Program Files\Microsoft Security Essentials\msseces.exe
Faulting module path: C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7600.16385_none_2b4f45e87195f cc4\ gdiplus.dll
Report Id: ca03361a-0263-11e0-aa33-7071bca847ba

Faulting application name: lsass.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc155
Faulting module name: lsasrv.dll, version: 6.1.7600.16484, time stamp: 0x4b220e26
Exception code: 0xc000001d
Fault offset: 0x00000000000235ad
Faulting process id: 0x260
Faulting application start time: 0x01cb967027eb729b
Faulting application path: C:\Windows\system32\lsass.exe
Faulting module path: C:\Windows\system32\lsasrv.dll
Report Id: 7b0d3987-0263-11e0-aa52-7071bca847ba

Faulting application name: firefox.exe, version: 1.9.2.3951, time stamp: 0x4cc7ae16
Faulting module name: xul.dll, version: 1.9.2.3951, time stamp: 0x4cc7ad7f
Exception code: 0xc0000409
Fault offset: 0x000b99da
Faulting process id: 0x4d8
Faulting application start time: 0x01cb966bc73d2c90
Faulting application path: C:\Program Files (x86)\Mozilla Firefox\firefox.exe
Faulting module path: C:\Program Files (x86)\Mozilla Firefox\xul.dll
Report Id: 15edf4b6-025f-11e0-bd58-7071bca847ba

Faulting application name: svchost.exe_Winmgmt, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: wbemcore.dll, version: 6.1.7600.16385, time stamp: 0x4a5be088
Exception code: 0xc000001d
Fault offset: 0x00000000000108ed
Faulting process id: 0x7b8
Faulting application start time: 0x01cb96686d902d39
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Windows\system32\wbem\wbemcore.dll
Report Id: b42ea3e1-025b-11e0-bd58-7071bca847ba

Faulting application name: svchost.exe_ProfSvc, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: wbemcore.dll, version: 6.1.7600.16385, time stamp: 0x4a5be088
Exception code: 0xc000001d
Fault offset: 0x00000000000108ed
Faulting process id: 0x3ac
Faulting application start time: 0x01cb9667bfa0e074
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Windows\system32\wbem\wbemcore.dll
Report Id: 0f3f8b25-025b-11e0-bd58-7071bca847ba

Faulting application name: Explorer.EXE, version: 6.1.7600.16450, time stamp: 0x4aebab8d
Faulting module name: dwmapi.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdf27
Exception code: 0xc000041d
Fault offset: 0x000000000000282b
Faulting process id: 0x978
Faulting application start time: 0x01cb9622a4e99ba6
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: C:\Windows\system32\dwmapi.dll
Report Id: 57568c62-0216-11e0-a760-7071bca847ba

Faulting application name: TrustedInstaller.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc4b0
Faulting module name: wcp.dll, version: 6.1.7600.16385, time stamp: 0x4a5be07d
Exception code: 0x80000003
Fault offset: 0x0000000000235d17
Faulting process id: 0xb5c
Faulting application start time: 0x01cb962321adeee1
Faulting application path: C:\Windows\servicing\TrustedInstaller.exe
Faulting module path: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810b\ wcp.dll
Report Id: 603c9c7b-0216-11e0-a760-7071bca847ba

Faulting application name: mmc.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc808
Faulting module name: mscorwks.dll, version: 2.0.50727.4952, time stamp: 0x4bebe78c
Exception code: 0xc0000005
Fault offset: 0x00000000002000e9
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13

Faulting application name: wmpnetwk.exe, version: 12.0.7600.16385, time stamp: 0x4a5bd03d
Faulting module name: SHELL32.dll, version: 6.1.7600.16644, time stamp: 0x4c4ef25d
Exception code: 0xc0000409
Fault offset: 0x000000000009d8e1
Faulting process id: 0x6fc
Faulting application start time: 0x01cb95c5442420d5
Faulting application path: C:\Program Files\Windows Media Player\wmpnetwk.exe
Faulting module path: C:\Windows\system32\SHELL32.dll
Report Id: ee40e951-01b9-11e0-a21b-7071bca847ba

Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: WindowsCodecs.dll, version: 6.1.7600.16385, time stamp: 0x4a5be0a5
Exception code: 0xc0000005
Fault offset: 0x000000000003256f
Faulting process id: 0x950
Faulting application start time: 0x01cb95c11aac1a61
Faulting application path: C:\Windows\system32\Dwm.exe
Faulting module path: C:\Windows\system32\WindowsCodecs.dll
Report Id: c1ea9a9e-01b4-11e0-a21b-7071bca847ba

A critical system process, C:\Windows\system32\lsass.exe, failed with status code 255. The machine must now be restarted.

Bug Check:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffff800c00b1030, 0x0000000000000000, 0xfffff9600031ad93, 0x0000000000000005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffff800c2b180e0, 0x0000000000000000, 0xfffff96000113cd2, 0x0000000000000005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffff6837f797cf0, 0x0000000000000000, 0xfffff80002b9ea56, 0x0000000000000005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 121010-75816-01.

Multiple instances of this:

Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Host Process for Windows Services because of this error.

Program: Host Process for Windows Services
File:

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: 00000000
Disk type: 0

Oh and the USB drive i installed win 7 from always shows this whenever it was inserted (but i've formatted and run checkdisk on it which doesn't cause this prob anymore):

The driver detected a controller error on \Device\Harddisk1\DR5.

Ran sfc /scannow and got errors this time. System restore didn't fix it so i'm going to reinstall win 7 again before taking the pc back to the shop. Could anyone tell me what's going on?

1Bowtie · 10 Dec 2010

I would start with a clean install using the Windows 7 dvd and not the flash drive because there are way to many conflicts

CarlTR6 · 10 Dec 2010

Run SFC at least three times. If that does not work, follow 1Bowtie's suggestion.

I also see a driver, e1k62x64.sys, Intel-based Gigabit and Fast Ethernet adapter driver, that seems to have a bad repution for causing conflicts and problems. You can read more about it here: ASUSTeK Computer Inc.-Forum- Bluescreening Like Crazy.

Your dump blames memory corruption and does not point to a specific cause. I recommend that you test your RAM using Memtest86. Follow the instructions in this tutorial: RAM - Test with Memtest86+. Let Memtest run for at least 7 passes. This will take 6-8 hours. Post back with your result.

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a06000 PsLoadedModuleList = 0xfffff800`02c43e50
Debug session time: Thu Dec  9 19:56:35.048 2010 (GMT-5)
System Uptime: 0 days 0:03:14.562
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff6837f797cf0, 0, fffff80002b9ea56, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiGetWorkingSetInfo+286 )

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: fffff6837f797cf0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002b9ea56, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cae0e0
 fffff6837f797cf0 

FAULTING_IP: 
nt!MiGetWorkingSetInfo+286
fffff800`02b9ea56 488b0408        mov     rax,qword ptr [rax+rcx]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880044cd8a0 -- (.trap 0xfffff880044cd8a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000037f797cf0 rbx=0000000000000000 rcx=fffff68000000000
rdx=0000000006125000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002b9ea56 rsp=fffff880044cda30 rbp=fffff880044cdca0
 r8=fffff88007e796d0  r9=fffff7000108a568 r10=fffffa80009edf60
r11=fffff700010a9dd0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiGetWorkingSetInfo+0x286:
fffff800`02b9ea56 488b0408        mov     rax,qword ptr [rax+rcx] ds:002e:fffff683`7f797cf0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002af5b91 to fffff80002a77f00

STACK_TEXT:  
fffff880`044cd738 fffff800`02af5b91 : 00000000`00000050 fffff683`7f797cf0 00000000`00000000 fffff880`044cd8a0 : nt!KeBugCheckEx
fffff880`044cd740 fffff800`02a75fee : 00000000`00000000 fffffa80`03eb6b60 00000000`00003700 00000041`00000000 : nt! ?? ::FNODOBFM::`string'+0x40f5b
fffff880`044cd8a0 fffff800`02b9ea56 : fffffa80`019eb010 00000000`00000000 00000000`00000001 fffff880`044cdca0 : nt!KiPageFault+0x16e
fffff880`044cda30 fffff800`02dd66d1 : fffffa80`03036060 fffffa80`02f30301 fffffa80`03eb6b60 fffffa80`00000000 : nt!MiGetWorkingSetInfo+0x286
fffff880`044cdac0 fffff800`02a77153 : ffffffff`ffffffff fffffa80`03eb6b60 00000000`00000000 00000000`03c7f248 : nt! ?? ::NNGAKEGL::`string'+0x52977
fffff880`044cdbb0 00000000`76d700ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03c7f228 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d700ea


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiGetWorkingSetInfo+286
fffff800`02b9ea56 488b0408        mov     rax,qword ptr [rax+rcx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiGetWorkingSetInfo+286

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiGetWorkingSetInfo+286

BUCKET_ID:  X64_0x50_nt!MiGetWorkingSetInfo+286

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

0: kd> lmtsmn
start             end                 module name
fffff880`00ef8000 fffff880`00f4f000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`03ec4000 fffff880`03f4e000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`02c10000 fffff880`02c26000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`00e33000 fffff880`00e3e000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`00e00000 fffff880`00e09000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e09000 fffff880`00e33000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`0191a000 fffff880`01921000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`02d0b000 fffff880`02d1c000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`023b7000 fffff880`023d5000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`006a0000 fffff960`006c7000   cdd      cdd.dll      unavailable (00000000)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`0187e000 fffff880`018ae000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00d1a000 fffff880`00d78000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0110d000 fffff880`01180000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`02c00000 fffff880`02c10000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`0404b000 fffff880`04059000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`02c6a000 fffff880`02ced000   csc      csc.sys      Mon Jul 13 19:24:26 2009 (4A5BC22A)
fffff880`02ced000 fffff880`02d0b000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`03e97000 fffff880`03ea6000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`01868000 fffff880`0187e000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`041c0000 fffff880`041e2000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`041f4000 fffff880`041fd000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`041e8000 fffff880`041f4000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`018ae000 fffff880`018c1000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`018c1000 fffff880`018cd000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`052a4000 fffff880`05398000   dxgkrnl  dxgkrnl.sys  Mon Jul 13 19:38:56 2009 (4A5BC590)
fffff880`05398000 fffff880`053de000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`04800000 fffff880`0484c000   e1k62x64 e1k62x64.sys Tue Apr 06 03:37:39 2010 (4BBAE4C3)
fffff880`0109b000 fffff880`010af000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`0104f000 fffff880`0109b000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`013dc000 fffff880`013e6000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`0182e000 fffff880`01868000   fvevol   fvevol.sys   Mon Jul 13 19:22:15 2009 (4A5BC1A7)
fffff880`01400000 fffff880`0144a000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`02fe3000 fffff800`0302c000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`0485d000 fffff880`04881000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`04127000 fffff880`04183000   HdAudio  HdAudio.sys  Mon Jul 13 20:06:59 2009 (4A5BCC23)
fffff880`053de000 fffff880`053ef000   HECIx64  HECIx64.sys  Thu Sep 17 15:54:16 2009 (4AB293E8)
fffff880`011cc000 fffff880`011e5000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`04059000 fffff880`04061080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`01200000 fffff880`0120e000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`022ef000 fffff880`023b7000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`0144a000 fffff880`01453000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`02db5000 fffff880`02dd3000   i8042prt i8042prt.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`04885000 fffff880`052a36e0   igdkmd64 igdkmd64.sys Wed Jul 28 17:10:36 2010 (4C509CCC)
fffff880`04000000 fffff880`0404b000   IntcDAud IntcDAud.sys Mon Jun 21 05:45:55 2010 (4C1F34D3)
fffff880`02de2000 fffff880`02df8000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`02dd3000 fffff880`02de2000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff800`00bbb000 fffff800`00bc5000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`04063000 fffff880`040a6000   ks       ks.sys       Mon Jul 13 20:00:31 2009 (4A5BCA9F)
fffff880`013b1000 fffff880`013cb000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`015aa000 fffff880`015d5000   ksecpkg  ksecpkg.sys  Mon Jul 13 19:50:34 2009 (4A5BC84A)
fffff880`041e2000 fffff880`041e7200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`022c2000 fffff880`022d7000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`00dd4000 fffff880`00df7000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00cc2000 fffff880`00d06000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`018cd000 fffff880`018db000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`03fee000 fffff880`03ffd000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`01821000 fffff880`0182e000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00fe3000 fffff880`00ffd000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`018e4000 fffff880`01911000   MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0)
fffff880`023d5000 fffff880`023ed000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`02200000 fffff880`0222c000   mrxsmb   mrxsmb.sys   Mon Jul 13 19:23:59 2009 (4A5BC20F)
fffff880`0222c000 fffff880`02279000   mrxsmb10 mrxsmb10.sys Mon Jul 13 19:24:08 2009 (4A5BC218)
fffff880`02279000 fffff880`0229c000   mrxsmb20 mrxsmb20.sys Mon Jul 13 19:24:05 2009 (4A5BC215)
fffff880`0197f000 fffff880`0198a000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00f58000 fffff880`00f62000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`010af000 fffff880`0110d000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`03e8c000 fffff880`03e97000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`015ed000 fffff880`015ff000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01458000 fffff880`0154a000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`02c4a000 fffff880`02c56000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`019c6000 fffff880`019f5000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`04112000 fffff880`04127000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`03fc2000 fffff880`03fd1000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`03f4e000 fffff880`03f93000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`0154a000 fffff880`015aa000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`0198a000 fffff880`0199b000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`03e80000 fffff880`03e8c000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02a06000 fffff800`02fe3000   nt       ntkrnlmp.exe Mon Jul 13 19:40:48 2009 (4A5BC600)
fffff880`0120e000 fffff880`013b1000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`01911000 fffff880`0191a000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`03f9c000 fffff880`03fc2000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`02d98000 fffff880`02db5000   parport  parport.sys  Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`00fa2000 fffff880`00fb7000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00f62000 fffff880`00f95000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00fcc000 fffff880`00fd3000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00fd3000 fffff880`00fe3000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`013cb000 fffff880`013dc000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`02ae7000 fffff880`02b8d000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`04183000 fffff880`041c0000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00d06000 fffff880`00d1a000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`02c26000 fffff880`02c4a000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`03ea6000 fffff880`03ec1000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`01800000 fffff880`01821000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`013e6000 fffff880`01400000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`03e2f000 fffff880`03e80000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`02c56000 fffff880`02c61000   rdpbus   rdpbus.sys   Mon Jul 13 20:17:46 2009 (4A5BCEAA)
fffff880`01964000 fffff880`0196d000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`0196d000 fffff880`01976000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`01976000 fffff880`0197f000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`01000000 fffff880`0103a000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`022d7000 fffff880`022ef000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`02b8d000 fffff880`02b98000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`053ef000 fffff880`053fb000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`03fd1000 fffff880`03fee000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`015e5000 fffff880`015ed000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`03ac8000 fffff880`03b39000   spsys    spsys.sys    Mon May 11 13:20:58 2009 (4A085E7A)
fffff880`03a30000 fffff880`03ac8000   srv      srv.sys      Mon Jul 13 19:25:11 2009 (4A5BC257)
fffff880`02a00000 fffff880`02a69000   srv2     srv2.sys     Mon Jul 13 19:25:02 2009 (4A5BC24E)
fffff880`02b98000 fffff880`02bc5000   srvnet   srvnet.sys   Mon Jul 13 19:24:58 2009 (4A5BC24A)
fffff880`04881000 fffff880`04882480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01603000 fffff880`01800000   tcpip    tcpip.sys    Mon Jul 13 19:25:34 2009 (4A5BC26E)
fffff880`02bc5000 fffff880`02bd7000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`019b9000 fffff880`019c6000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`0199b000 fffff880`019b9000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`03e1b000 fffff880`03e2f000   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`02d1c000 fffff880`02d42000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`040a6000 fffff880`040b8000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`041fd000 fffff880`041fef00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`0484c000 fffff880`0485d000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`040b8000 fffff880`04112000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`02d42000 fffff880`02d98000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`00f95000 fffff880`00fa2000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`01921000 fffff880`0192f000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`0192f000 fffff880`01954000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`015d5000 fffff880`015e5000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00fb7000 fffff880`00fcc000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00d78000 fffff880`00dd4000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01180000 fffff880`011cc000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`03e00000 fffff880`03e1b000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`01954000 fffff880`01964000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00e45000 fffff880`00ee9000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00ee9000 fffff880`00ef8000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`03f93000 fffff880`03f9c000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`00040000 fffff960`0034f000   win32k   win32k.sys   Mon Jul 13 19:40:16 2009 (4A5BC5E0)
fffff880`00f4f000 fffff880`00f58000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`022a1000 fffff880`022c2000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)

Unloaded modules:
fffff880`018ae000 fffff880`018bc000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`018bc000 fffff880`018c8000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`018c8000 fffff880`018d1000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`018d1000 fffff880`018e4000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

aav · 10 Dec 2010

[QUOTE=CarlTR6;1122129]Run SFC at least three times. If that does not work, follow 1Bowtie's suggestion.

I also see a driver, e1k62x64.sys, Intel-based Gigabit and Fast Ethernet adapter driver, that seems to have a bad repution for causing conflicts and problems. You can read more about it here: ASUSTeK Computer Inc.-Forum- Bluescreening Like Crazy.

Your dump blames memory corruption and does not point to a specific cause. I recommend that you test your RAM using Memtest86. Follow the instructions in this tutorial: RAM - Test with Memtest86+. Let Memtest run for at least 7 passes. This will take 6-8 hours. Post back with your result.

[QUOTE]

Ran SCF 3 times- shows errors that can't be repaired.

I already ran memtest 3-4 times, each with 7 or more passes. Do you want me to run it again?

I'll check up on the intel driver...dunno why it's going crazy.

Oh and i can't install using DVD. i don't have a dvd drive

CarlTR6 · 10 Dec 2010

If you have already run Memtest, I suggest that you run it again from a cold boot after your computer has been off for a while. If no errors show up, your RAM is probably OK. Let us know.

You will see that Asus thread, that one solution was a new adapter.

aav · 10 Dec 2010

CarlTR6 said:

If you have already run Memtest, I suggest that you run it again from a cold boot after your computer has been off for a while. If no errors show up, your RAM is probably OK. Let us know.

You will see that Asus thread, that one solution was a new adapter.

K thanks a lot. I will let you know soon.

aav · 11 Dec 2010

ok. i ran a memtest on cold boot...got 1930+ errors. It seems it WAS the RAM after all!

Hmm...i guess i should rum memtest on a coldboot from now on.

Thanks CarlTR6!

CarlTR6 · 11 Dec 2010

You are welcome. There is more stress on RAM and other components during a cold boot as opposed to a warm boot. Good to know that you have found the source of your problems.