Multiple, assorted BSODs in 2 days...

[Roundhouse]

Another BSOD!

Hey guys,

I got my RMA'd RAM last Tuesday. My system has been stable for quite a while. But just now as I was playing StarCraft 2 (yup, the app that started it all =P), I got another BSOD. A MEMORY_MANAGEMENT BSOD.

Attached is the dump. Please let me know what you find.

 

[CarlTR6]

That is not the news we wanted to hear! I will take a look.

Error code 1A, MEMORY_MANAGEMENT. Usual causes are device driver, memory, kernel.

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_083010-31184-01.zip\083010-31184-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0344f000 PsLoadedModuleList = 0xfffff800`0368ce50
Debug session time: Sun Aug 29 19:13:12.551 2010 (GMT-4)
System Uptime: 0 days 9:02:03.283
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41289, ff162001, 2361, ff160c05}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a49 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041289, The subtype of the bugcheck.
Arg2: 00000000ff162001
Arg3: 0000000000002361
Arg4: 00000000ff160c05

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


BUGCHECK_STR:  0x1a_41289

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80003514379 to fffff800034bf740

STACK_TEXT:  
fffff880`07317988 fffff800`03514379 : 00000000`0000001a 00000000`00041289 00000000`ff162001 00000000`00002361 : nt!KeBugCheckEx
fffff880`07317990 fffff800`03547cc5 : 00000000`07008001 fffffa80`063e3560 fffff880`07317ca0 fffffa80`063e3560 : nt! ?? ::FNODOBFM::`string'+0x4a49
fffff880`073179d0 fffff800`037a6f31 : fffff880`00000010 fffffa80`065ddb01 fffffa80`065ddb30 fffffa80`00000000 : nt! ?? ::FNODOBFM::`string'+0x52eb0
fffff880`07317ac0 fffff800`034be993 : 00000000`00000898 fffffa80`0651c060 00000000`00001f80 00000000`02d2ebe8 : nt!NtQueryVirtualMemory+0x67f
fffff880`07317bb0 00000000`76f3ff8a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02d2ebc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f3ff8a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4a49
fffff800`03514379 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4a49

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1a_41289_nt!_??_::FNODOBFM::_string_+4a49

BUCKET_ID:  X64_0x1a_41289_nt!_??_::FNODOBFM::_string_+4a49

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

The dump does not point to anything specific. Make sure your new RAM is seated securely. I know you got new RAM, did you RMA the motherboard also?

I find a very old driver and another old driver that may be the sources of your problem. They certainly are not doing any good toward system stability.

lirsgt.sys Sat Mar 06 14:53:01 2004 - belongs to the software lirsgt by Tages SA. TAGES, the AAA Copy Protection System This software is way obsolete. Uninstall it.

wdcsam64.sys Wed Apr 16 04:39:08 2008 - Western Digital External Drive RAID ManagerWD Support > Downloads > Select Product. Update this driver. Go to the Western Digital site and search for the driver.

Post back when you ave uninstalled that copy protection program and updated the Western Digital RAID driver.

 

[Roundhouse]

That is not the news we wanted to hear!

Yup! I could not have said it better!

The Tages app was from The Chronicles of Riddick game that I just installed. As for the WD driver, i'll try to update it. It's just weird that the only updates that I could find in the WD site are firmware ones. Probably the drivers are in the included virtual cd within the firmware.

As for the Tages DRM, I don't think the game will run without it. I'll try to see if there are updates for it.

BTW, I didn't RMA the mobo. It was stable as I was waiting for the RMA'd RAM and was using a back up set of sticks.


EDIT: I just updated the Tages DRM and the WD drivers and also refitted the RAM. I'll observe how things play out and post.

 

[CarlTR6]

Very good - and we hope for GOOD news this time!!

 

[Roundhouse]

After almost a week of stable use, I got another BSOD.... but this time it is different.

After I re-fit the mem modules last weekend, my mem BSODs were gone. This new BSOD has the code for NTFS_FILE_SYSTEM. I left my computer open for about 2 hours so I didn't really see it bomb out. When I came back, I just saw a notification that it restarted unexpectedly. I used BlueScreenView to inspect the new dump file to be able to see the error message.

Attached is the dump.

Is my harddisk failing already?? It's not exactly old. It's just over a year old.

 

[Jonathan_King]

I would suggest a disk check/hard drive diagnostic.

Open an elevated command prompt and enter chkdsk /r.

HD Diagnostic

Install these network drivers: Realtek

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep  4 16:25:50.358 2010 (UTC - 4:00)
System Uptime: 0 days 11:23:39.090
BugCheck 24, {1904fb, fffff88007c192f8, fffff88007c18b60, fffff880010cd884}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFlushVolume+164 )
PROCESS_NAME:  MsMpEng.exe
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[Roundhouse]

Alright, I'll check with those tools. Thanks!

 

[Roundhouse]

Hi guys,

I got a couple of BSODs again. This time a couple of PFN_LIST_CORRUPT errors and 1 MEMORY_MANAGEMENT error.

Can you guys please look into these?

For good measure, I'll be doing a reformat and a clean install on my C: drive. A clean install might solve a couple of these instability issues...

Thanks in advance guys!

 

[CarlTR6]

All of three of the dumps indicate memory management or memory corruption issues.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, 4ade001, 0, fffff70001080000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 0000000004ade001
Arg3: 0000000000000000
Arg4: fffff70001080000
---------------

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 3dacd, 2, 3da45}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

0: 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: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000003dacd, page frame number
Arg3: 0000000000000002, current page state
Arg4: 000000000003da45, 0
-------------

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, b824b, 2, b8248}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

1: 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: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000000b824b, page frame number
Arg3: 0000000000000002, current page state
Arg4: 00000000000b8248, 0

Did you run Check Disk? If so, what were the results?

I see that you updated your Realtek drivers. Good job. I still find out of date drivers including two really obsolete ones. Before you do a reinstall, update these drivers. Out of date drivers can and do cause memory corruption.

atksgt.sys Sun May 17 09:36:34 2009 - belongs to the software atksgt by Tages SA. Update the driver or uninstall the software.

lirsgt.sys Sat Mar 06 14:53:01 2004 - belongs to the software lirsgt by Tages SA. This software is obsolete; uninstall it.

Tpkd.sys Thu May 21 17:36:18 2009 - InterLok system file belongs to the software InterLok(R) or InterLok Driver Kit or TPkd or Sonic RecordNow! or Adobe eBook Migration Utility or Interlok driver setup x or nGenius InfiniStream by PACE Anti-Piracy, Inc (www.paceap.com). Update the driver or uninstall the software.

wdcsam64.sys Wed Apr 16 04:39:08 2008 - Western Digital External Drive RAID Manager WD Support > Downloads > Select Product. Update this driver.

 

[Roundhouse]

atksgt.sys Sun May 17 09:36:34 2009 - belongs to the software atksgt by Tages SA. Update the driver or uninstall the software.

lirsgt.sys Sat Mar 06 14:53:01 2004 - belongs to the software lirsgt by Tages SA. This software is obsolete; uninstall it.

Tpkd.sys Thu May 21 17:36:18 2009 - InterLok system file belongs to the software InterLok(R) or InterLok Driver Kit or TPkd or Sonic RecordNow! or Adobe eBook Migration Utility or Interlok driver setup x or nGenius InfiniStream by PACE Anti-Piracy, Inc (www.paceap.com). Update the driver or uninstall the software.

wdcsam64.sys Wed Apr 16 04:39:08 2008 - Western Digital External Drive RAID Manager WD Support > Downloads > Select Product. Update this driver.

Thanks for the reply Carl.

I have already updated that Tages driver around 2 weeks ago and also the WD drivers. I don't know why it keeps showing as unupdated....

 

[CarlTR6]

I suspect that it updated to the latest driver available. If there is not a driver dated July 13, 2009 or later, it is not updated for Win 7. You might get by with the May 17, 2009 driver, which is a Vista driver. The 2008 driver will cause problems. You need to uninstall the Tages software associated with the 2008 driver. It is obsolete software not designed to run on Win 7. It will cause conflicts and crashes. It is like trying run a 1960's VW Beetle suspension on a new Ferrari; it ain't gonna work.

 

[Roundhouse]

It is like trying run a 1960's VW Beetle suspension on a new Ferrari; it ain't gonna work.

LOL!

I'm trying to look into a pattern here... BSODs usually creep up after around 9-10 hrs of continued computer use. Could that be an issue? I also have an nVidia GTX460 gpu and have a 520w Corsair PSU. I have read in other forums that i should be ok, but could it be voltage drops that's been causing the BSODs after a number of hours use? Is that even possible?

 

[CarlTR6]

It is like trying run a 1960's VW Beetle suspension on a new Ferrari; it ain't gonna work.

LOL!

I'm trying to look into a pattern here... BSODs usually creep up after around 9-10 hrs of continued computer use. Could that be an issue? I also have an nVidia GTX460 gpu and have a 520w Corsair PSU. I have read in other forums that i should be ok, but could it be voltage drops that's been causing the BSODs after a number of hours use? Is that even possible?

I suppose that is possible - nearly anything is possible with computers; but I don't see that as a very probably cause unless your PSU is going bad. I run my computer 24/7 and I haven't had a BSOD since January. Those in January were graphics card related and I got that problem solved.

If your BSOD's are caused by conflicts, they can happen anytime when the right combination of memory requests occur that conflict. It is possible for the conflict to be occurring and finally reaching the crash point - like pot of water finally reaching the boiling point. Keep in mind that Win 7 does not like obsolete third party drivers. These drivers were not engineered for the Win 7 OS. Win 7 is not an evolution from XP; it is a totally new OS.

 

[Roundhouse]

Keep in mind that Win 7 does not like obsolete third party drivers. These drivers were not engineered for the Win 7 OS. Win 7 is not an evolution from XP; it is a totally new OS.

Yeah. You're right. Thanks for the input. I'll be reformatting and reinstalling win 7 x64. Just installing the necessities for now or at least those apps with win 7 supported drivers and then observe for stability. Will check back if any BSODs shows up.

 

[CarlTR6]

OK, but if you don't want to go through the hassle of reinstalling all of your apps, just uninstall the obsolete ones. Either way, let us know. We want to see you running smoothly.

 

[Roundhouse]

As I was doing a clean install, I got a BSOD just as it came back from it's first restart and was just finishing up the install...

Does that mean that my BSODs are hardware related?

EDIT: Ouch! I tried to install again, I still got a BSOD right smack as it was completing the install.... hmmm... is it too consistent to be a hardware error? Could it be an installation disc error?

EDIT: I tried for a 3rd time, but I still got a BSOD! oh man... I can't even install Windows now? *sigh*

 

[CarlTR6]

Yes, it can be hardware or a corrupt installation media. I will see if I can get one of the installation guys involved. In the meantime, you can try removing all but one RAM stick and see if you can complete the installation.

 

[Roundhouse]

In the meantime, you can try removing all but one RAM stick and see if you can complete the installation.

Whoa! That worked! So you mean Win 7 x64 & Vista x64 have the same problems during installation? I heard Vista x64 has problems installing if you have more than 2GB of RAM installed during installation.

 

[karlsnooks]

Roundhouse,

To put your system on the level:

1. Go to the manufacturer's website. If you do not have the latest bios installed, then--download and install same.

2. Perform Step 1.

3. Perform a 100% clean install as explained in following link. Be sure to use the DiskPart CLEAN ALL command (and not simply CLEAN).
http://www.sevenforums.com/tutorials/91339-ssd-hdd-optimize-windows-reinstallation.html

4. do NOT install any additional drivers,

5. do go to the MS update site and update your system.

6. Make a complete System Image backup of your system using the procedure given in following link:
http://www.sevenforums.com/tutorials/663-backup-complete-computer-create-image-backup.html

7. Make a System Repair Disc. Using a computer without having a System Repair Disc is like driving a car without a spare tire.
________________________________________
DISC - CREATE A SYSTEM REPAIR DISC
START | type System Repair | Enter key | Create Disc button
________________________________________
________________________________________

 

[Jonathan_King]

Follow these directions for testing RAM. Particularly note Part 3: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Either that one stick you took out is bad, the motherboard slot is faulty, or you are using incompatible RAM.