Random BSOD's - Mem Management, ntfs.sys, etc

fadlifari said:

hey zigzag the bsod still occurs even if i delete idm and NTIdrvr.sys, here is the dump files about the bsod recently.

NTIDriver is still there and the same date. IDM is updated but still could be causing it.


Again this DMP was not driver verified.

It is still a memory exception. It still need to have both Memtest and verifier run. If you have run memtest for 7-8 passes ou can pass on i t but verifier needs to be done in order to find which driver is giving you trouble.

Cant give you more help until you do.


These crashes were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

RAM - Test with Memtest86+



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Driver Verifier - Enable and Disable

last night i have ran the driver verifier, but when it crash the system wont save the minidump, it stucks on initializing driver..... that what's happen, and about memtest86 i cant get it run, because when it boots, suddenly my system reboots, and keep rebooting when i tried to run memtest i'm sorry that i have made you so much trouble, truth is i really need your help

about the nti driver, i have uninstalled the nti media manager, where else could the driver be? how could i find this file on my laptop?

i'll try to run the verifier again then i report back to you thanks

fadlifari said:

last night i have ran the driver verifier, but when it crash the system wont save the minidump, it stucks on initializing driver..... that what's happen, and about memtest86 i cant get it run, because when it boots, suddenly my system reboots, and keep rebooting when i tried to run memtest i'm sorry that i have made you so much trouble, truth is i really need your help

about the nti driver, i have uninstalled the nti media manager, where else could the driver be? how could i find this file on my laptop?

i'll try to run the verifier again then i report back to you thanks

NTI isnt that important. Verifier and memtest are. without them we dont know whats wrong

i am very sorry zigzag but i cannot run memtest i dont know why but when my system tries to run memtest it keeps rebooting.

by the way here is the latest bsod this morning.

i am so desperate i'm so sorry to disappoint you.

You arent disappointing me. It is just a little frustrating that I cant put my finger on the problem.

Latest DMP still says memory management.


If you are Booting from USB, did you format the USB and make it bootable?

i am very sorry to hear that, please dont be frustrated, because i am also desperate, you were very helpful to my problems, its just we dont know the core of the problem yet. okay to help you, i will explain the details :

1. about the memtest86+, i made a bootable usb from the file, then i boot from usb, for 5 seconds it seems the test was running but then the system reboots, it keeps rebooting and wont stop. i've read from the other forum that memtest86+ isnt compatible with 4gb of ram, so instead i made a bootable cd from memtest86, i'm so sure you know the difference about those two.

2. i've managed to run the driver verifier by looking at your post earlier about how to enable driver verifier, and i did. the system started to crash and i uploaded to you about the dumps. but you said that no drivers were verified in that dump. i ran the driver verifier again, but when it starts to bsod, the system couldn't save the minidump file despite that i have enable the saving small memory dump on the system configuration.

what should i do next?
i want to help you too, i know you can help me :)

fadlifari said:

i am very sorry to hear that, please dont be frustrated, because i am also desperate, you were very helpful to my problems, its just we dont know the core of the problem yet. okay to help you, i will explain the details :

1. about the memtest86+, i made a bootable usb from the file, then i boot from usb, for 5 seconds it seems the test was running but then the system reboots, it keeps rebooting and wont stop. i've read from the other forum that memtest86+ isnt compatible with 4gb of ram, so instead i made a bootable cd from memtest86, i'm so sure you know the difference about those two.

2. i've managed to run the driver verifier by looking at your post earlier about how to enable driver verifier, and i did. the system started to crash and i uploaded to you about the dumps. but you said that no drivers were verified in that dump. i ran the driver verifier again, but when it starts to bsod, the system couldn't save the minidump file despite that i have enable the saving small memory dump on the system configuration.

what should i do next?
i want to help you too, i know you can help me :)

Lets try the built in windows memory diagnostic. Go to start>search> type memory and click on the memory diagnostics and follow its directions.

okay so now i have had ran the windows memory diagnostic tools and where is the result? what should i do next ?
:)

fadlifari said:

okay so now i have had ran the windows memory diagnostic tools and where is the result? what should i do next ?

:)

There should have been a report at the end but if there wasnt you can look in event viewer

Go into event viewer (type eventvwr in search). Event viewer (local) and look for errors listed in the last day, week, etc. Then go to the windows log>application tab. Finally the windows Logs>system tabs.

You want to look for anything relating to memory diagnostics

BTW We will stick with you as long as you need help.

hello zigzag, i have ran the windows memory diagnostic tools and looking into event viewer, but there is no signs of memory diagnostic tools, i only found "windows memory diagnostics-schedule" but there is no info about my memory there. did you know where else could it be?

and i try to run WhoCrashed, and this is my result :


Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 11/8/2011 3:55:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110811-25552-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x4FA9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001519FA9, 0xFFFFF880096C09B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Tue 11/8/2011 2:43:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110811-24289-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000427C905, 0xFFFFF880099D9720, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 11/8/2011 2:32:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110811-27534-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80004597D99, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 11/8/2011 2:22:31 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110811-29858-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC63D4)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000F63D4, 0xFFFFF88008D50040, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Tue 11/8/2011 2:18:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110811-31231-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41284, 0xFFFFF683FF79C001, 0x645, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 11/7/2011 2:33:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110711-34819-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x1986)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004001986, 0xFFFFF88006A1FD60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

and i also uploaded my CBS.log

i hope these will help you figure out what my problem is :)

best of luck,
fadli