Windows 7: new problem

ttran · 08 Jul 2010

Based on what you said, I guess it is compatibility issue between the Ram number 2 and the mobo...does your computer run fine without ram 2? Have you tried that?

stellarknight · 08 Jul 2010

before i put on ram 2 and test only on ram 1 its fine
after i put on ram 2 with ram 1...... it will begin bsod

stellarknight · 08 Jul 2010

ok heres the list of my driver

ttran · 08 Jul 2010

Quote:

before i put on ram 2 and test only on ram 1 its fine
after i put on ram 2 with ram 1...... it will begin bsod

As I mentioned my friend, this is compatibility issue because both sticks of ram when tested individually give no error, but together give error

stellarknight · 08 Jul 2010

so what should i do? any advice?

richc46 · 09 Jul 2010

Ram that is not compatible has to be replaced.

stellarknight · 09 Jul 2010

what do you mean by replaced? by new one? or...... any other solutions?

richc46 · 09 Jul 2010

Take one stick of ram, that you know is good. Test it in all the slots. If one slot is bad, that has to be corrected. If all the slots are good, then you have to go out and buy more ram. The best practice is just to buy all that you want at one time. If you mix and match, you may wind up with the same problem that you have now. If two sticks are not identical, you will get the performance of the worst of the two or other problems like you have now.

stellarknight · 10 Jul 2010

hmm idk if this good or not but it might work try to get help from you guys

ttran · 10 Jul 2010

Quote:

STOP 0x0000001A: MEMORY_MANAGEMENT

Usual causes: Device driver, memory, kernel
STOP 0x0000004E: PFN_LIST_CORRUPT

Usual causes: Device driver, ?memory
STOP 0x00000024: NTFS_FILE_SYSTEM

Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
STOP 0x000000F5: FLTMGR_FILE_SYSTEM

Usual causes:

MSDN Listing (WDK): http://msdn.microsoft.com/en-us/library/ff560383(v=VS.85).aspx

STOP 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory

Code:

BugCheck 1A, {41289, 10db001, 1456, 10dfc45}

Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+273 )

Followup: MachineOwner
---------
BugCheck 24, {1904fb, 8d507a08, 8d5075e0, 82d2a81a}

Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteReservedBitmap+a3 )

Followup: MachineOwner
---------
BugCheck 4E, {99, ae994, 0, 33794}

Probably caused by : memory_corruption ( nt!MiBadShareCount+24 )

Followup: MachineOwner
---------
BugCheck 1A, {41284, 27d2b001, 1e056, c0802000}

Probably caused by : memory_corruption ( nt!MiLocateWsle+c1 )

Followup: MachineOwner
---------
BugCheck F5, {68, b070be38, b070be64, 0}

Probably caused by : fileinfo.sys ( fileinfo!FIStreamCleanup+94 )

Followup: MachineOwner
---------
BugCheck 4E, {99, a3c34, 2, a0233}

Probably caused by : memory_corruption ( nt!MiBadShareCount+24 )

Followup: MachineOwner
---------
BugCheck 4E, {99, a035c, 1, a025c}

Probably caused by : memory_corruption ( nt!MiBadShareCount+24 )

Followup: MachineOwner
---------
BugCheck 1A, {31, 879e0a10, b3c5d000, a0df4e85}

Probably caused by : memory_corruption ( nt!MiApplyCompressedFixups+70 )

Followup: MachineOwner
---------
BugCheck 4E, {99, 22f67, 0, 33c67}

Probably caused by : memory_corruption ( nt!MiBadShareCount+24 )

Followup: MachineOwner
---------
BugCheck 1A, {41790, c0802062, ffff, 0}

Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+41a )

Followup: MachineOwner
---------
BugCheck 1A, {5003, 8be00000, 6056, 96029009}

Probably caused by : memory_corruption ( nt!MiAllocateWsle+6f )

Followup: MachineOwner
---------
BugCheck 1A, {41201, c001b248, 1a045847, 87e4a960}

Probably caused by : memory_corruption ( nt!MiGetPageProtection+1a6 )

Followup: MachineOwner
---------
BugCheck 24, {1904fb, 807fea78, 807fe650, 8b44f9e7}

Probably caused by : Ntfs.sys ( Ntfs!NtfsUninitializeNtfsMcb+42 )

Followup: MachineOwner
---------
BugCheck 1000008E, {c0000005, 82c41033, ac1f49c4, 0}

Probably caused by : win32k.sys ( win32k!ClassAlloc+1b )

Followup: MachineOwner
---------
BugCheck 4E, {99, 92906, 0, 37e06}

Probably caused by : memory_corruption ( nt!MiBadShareCount+24 )

Followup: MachineOwner
---------
BugCheck 1A, {41284, 13dab001, 1d846, c0802000}

Probably caused by : memory_corruption ( nt!MiLocateWsle+c1 )

Followup: MachineOwner
---------
BugCheck 4E, {99, 118d7, 2, 1de7d}

Probably caused by : memory_corruption ( nt!MiBadShareCount+24 )

Followup: MachineOwner
---------
BugCheck 4E, {99, 9dfec, 0, 72dec}

Probably caused by : memory_corruption ( nt!MiBadShareCount+24 )

Followup: MachineOwner
---------
BugCheck 4E, {99, 5abd, 0, a33bd}

Probably caused by : memory_corruption ( nt!MiBadShareCount+24 )

Followup: MachineOwner
---------
BugCheck F5, {68, 88d13df8, 88d13e24, 0}

Probably caused by : fltmgr.sys ( fltmgr!FltReleaseFileNameInformation+43 )

Followup: MachineOwner
---------
BugCheck 1A, {3452, 2b09f000, c0892e30, 1a7dcc46}

Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+389 )

Followup: MachineOwner
---------
BugCheck 4E, {99, 2aaff, 2, 5a6fe}

Probably caused by : memory_corruption ( nt!MiBadShareCount+24 )

Followup: MachineOwner
---------
BugCheck 4E, {99, 9f8bf, 0, 9f9bf}

Probably caused by : memory_corruption ( nt!MiBadShareCount+24 )

Followup: MachineOwner
---------
BugCheck 1A, {3452, f74e000, c0836e30, 9814bc66}

Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+389 )

Followup: MachineOwner
---------
BugCheck 4E, {99, ae6ce, 0, 862ce}

Probably caused by : memory_corruption ( nt!MiBadShareCount+24 )

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

A lot of repetitive stop code with the same thing being blamed such as 1A and Memorry corruption, or 24 and ntfs.sys (hard drive controller driver).

Again, as richard mentioned earlier, ram that is not compatible need to be replaced. I'm not a hardware guy, however, I would replace my Ram if it is not compatible with my mobo.

As I mentioned, hard drive is mentioned in some of the dmp file, please run disk check and hd diagnostic (download from hd manufacture site)
Disk Check
HD Diagnostic

In looking through your drivers, I can see that you have this out of date drivers, please update it:

Code:

WPRO_40_1340 WPRO_40_1340.sys Wed Sep 03 06:26:41 2008 (48BDCBB1) 
CACE  Technologies, Inc.

Virtual CD program such as Deamon tool or Alcohol 120% are known for causing BSODs. Please remove them completely from your system, then use this tool to remove sptd.sys, component of those virtual Cd program
DuplexSecure - Downloads <----THIS IS VERY IMPORTANT THING U HAVE TO DO

Regard,

Tuan

Windows 7: new problem

new problem problems?