Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: Typical BSOD situation, minidump check?

14 Feb 2010   #1

Windows 7 64-bit
Typical BSOD situation, minidump check?

I got bluescreen when put the PC on and It said "Windows starting..." I am quite sure that my memory is causing this so please If someone could help me with this minidump to get this thing fixed. Here is the dump file zipped. Help will be appreciated! :)

Attached Files
File Type: zip (24.8 KB, 10 views)
My System SpecsSystem Spec
14 Feb 2010   #2

Win7 Ultimate X64

Dump file reports error 0x7e details here, BSOD Index this may well be memory but could also be a driver problem among others

Start with hardware tests
RAM check Memtest86+ - Advanced Memory Diagnostic Tool
HDD check HD Diagnostic
and also a system file scan
Start>cmd.exe>right click run as admin>type sfc /scannow

Try these and post back your results

Hope this helps
My System SpecsSystem Spec
14 Feb 2010   #3

Windows 7 64-bit

Yeah I have done those about week ago and here is the results:

Seatools hdd check ( took 4 hours ) All okay
Memtest86+ 10 passes no errors
sfc /scannow all okay
CHKDSK /R /F all okay

I have also got 0x25 and 0x50 errors from BSOD's. I updated my video drivers when the first BSOD came who blaim them. Thanks for helping dude, here's rep for ya!

What should I do now? :O
My System SpecsSystem Spec

14 Feb 2010   #4

Win7 Ultimate X64

Please post all dumps you got and we can have a look through them see if we can find any other clues
My System SpecsSystem Spec
14 Feb 2010   #5

Windows 7 64-bit

There are all minidumps (8 files) I had in my Windows/Minidump -folder. Hope that helps! =)
My System SpecsSystem Spec
14 Feb 2010   #6
Microsoft MVP


Running the dump files.....
My System SpecsSystem Spec
14 Feb 2010   #7
Microsoft MVP


8 memory dumps. 5 different STOP errors: STOP 0x19; 3 STOP 0x24; STOP 0x3B; 2 STOP 0x50; STOP 0xF4
Blame placed on 6 different causes: ntkrnlmp.exe; fltmgr.sys; 3 NTFS.SYS; csrss.exe; Pool_Corruption; memory_corruption

This is, IMO, leaning towards a hardware problem. With the fltmgr.sys and NTFS.SYS errors it causes me to suspect the storage sub-system of your computer. This includes the hard drive, cabling, and the motherboard.

So, let's start with that. Please perform these free hardware diagnostics:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.
H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
HD Diagnostic (read the details at the link)
Memory Diagnostics (read the details at the link) - this is for a different reason that I mention below...

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
Then, because of the memory and pool corruption, please run Driver Verifier according to these directions:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff 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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
Summary of the BSOD's:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan 31 09:53:31.745 2010 (GMT-5)
System Uptime: 0 days 0:01:14.431
BugCheck 50, {fffff8a00714c000, 0, fffff80002d6c09f, 0}
Probably caused by : ntkrnlmp.exe ( nt!HvMarkDirty+c0 )
PROCESS_NAME:  services.exe
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb  2 13:03:35.363 2010 (GMT-5)
System Uptime: 0 days 0:00:46.659
BugCheck 3B, {c0000005, fffff8800109711e, fffff88006647ca0, 0}
Probably caused by : fltmgr.sys ( fltmgr! ?? ::NNGAKEGL::`string'+1087 )
PROCESS_NAME:  csc.exe
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb  4 12:57:06.545 2010 (GMT-5)
System Uptime: 0 days 0:00:52.231
BugCheck F4, {3, fffffa80059ecb30, fffffa80059ece10, fffff80002dcb240}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb  4 12:54:43.051 2010 (GMT-5)
System Uptime: 0 days 0:00:55.736
BugCheck 19, {3, fffffa80039612c0, bffffa80039612c0, fffffa80039612c0}
Probably caused by : Pool_Corruption ( nt!ExFreePool+536 )
PROCESS_NAME:  WerFault.exe
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb  4 12:58:41.157 2010 (GMT-5)
System Uptime: 0 days 0:00:24.452
BugCheck 24, {1904fb, fffff88002f93728, fffff88002f92f80, fffff880010b4023}
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteFcb+233 )
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Feb  7 08:57:57.872 2010 (GMT-5)
System Uptime: 0 days 0:00:20.168
BugCheck 24, {1904fb, fffff880046a1798, fffff880046a0ff0, fffff880012e1a84}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefix+114 )
PROCESS_NAME:  ashServ.exe
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Feb 10 14:38:25.724 2010 (GMT-5)
System Uptime: 0 days 5:11:39.020
BugCheck 50, {fffff6dfffffff80, 0, fffff80002a5beed, 5}
Probably caused by : memory_corruption ( nt!MiMakeProtoAddressValid+4d )
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb 11 12:54:26.180 2010 (GMT-5)
System Uptime: 0 days 0:04:31.475
BugCheck 24, {1904fb, fffff880077f24b8, fffff880077f1d10, fffff80002a8d0c4}
Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquireExclusiveFcb+73 )
My System SpecsSystem Spec
15 Feb 2010   #8

Windows 7 64-bit

Okay thanks much for help! I will run CHKDSK /R /F and post the log here. I have done that multiple times without errors saying in the end of test. And ran a seatools software too with all okay. This happens ONLY AT COLD BOOT, and people are having this same issue with ASUS motherboard and G.Skill memory, As I. Memtest 86+ 10 passes without errors. But in cold boot can BIOS and memory like fail somehow?

I have one question:

Even if the BSOD shows that my HDD has something to do with this, could memory crash cause It?
My System SpecsSystem Spec
15 Feb 2010   #9

Windows 7 64-bit

Checked drive C: File System
Filesystem type is NTFS.

Disk check has been scheduled.
Windows checks the disk now.

CHKDSK scan files (stage 1 / 5) ...
102,144 file record processed. File Amendment carried out.
75 large file record processed. 0 defective file record processed. 0 EA records processed. 65 uudelleenjäsennystietuetta processed. CHKDSK check the indexes (stage 2 / 5) ...
137,972 index entry processed. Index Amendment carried out.
0 indeksoimatonta files reviewed. 0 indeksoimatonta files restored. CHKDSK check suojauskuvaimia (step 3 / 5) ...
102,144 file-SD / security symbol processed. Deleted 126 unused index 0x9 configuration file to the index $ SII.
Deleted 126 unused index 0x9 configuration file to the index $ SDH.
126 is deleted unused suojauskuvainta.
Suojauskuvainten review has been completed.
17,915 data files processed. CHKDSK check USN Journal-file ...
35914984 USN bytes-processed. USN Journal-file review is completed.
CHKDSK will check the file data (stage 4 / 5) ...
102,128 files processed. File data review conducted.
CHKDSK to check the free space (stage 5 / 5) ...
34371864 free clusters processed. Of free disk space check performed.
Windows has checked the file system. Errors were detected.

209612799 kilobytes total disk space.
71863464 KB in 78,388 files.
51,604 KB Index 17,916.
0 KB in a damaged sector.
210,275 KB in the system in use.
65,536 KB in the log file to use.
137487456 KB available disk.

4096 bytes / cluster.
52403199 reserve unit disc.
34371864 units available for booking at the album.

Internal data:
00 8f 01 00 3c 78 01 00 f1 d3 02 00 00 00 00 00 ......... x. ....<
89 0e 00 00 41 00 00 00 00 00 00 00 00 00 00 00 .... A. ..........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has checked the disc.
Wait. The computer is restarted.


*Suojauskuvain means security-something..

Let me know If you don't understand some word :)
My System SpecsSystem Spec
15 Feb 2010   #10

Windows 7 64-bit

I checked the eventlog thing and there was this type of event ( I didn't had BSOD on that time, not even today.. ?? )
My System SpecsSystem Spec

 Typical BSOD situation, minidump check?

Thread Tools

Similar help and support threads
Thread Forum
BSOD please check my minidump file and help me
I had the BSOD problem for some time and then the problem simply stopped. I was calm for few months until today... Here's the minidump file, I hope you can help me guys. Microsoft services
BSOD Help and Support
BSOD, Check out my minidump
Hi, my computer crashed a while ago (twice actually, but only 1 dump) and I've seen nothing majorly bad so far, but I want the forums to check out the dump for me to make sure it's nothing I have to worry about.
BSOD Help and Support
Minidump folder empty after BSOD,what's to check?
Sorry if it's a dumb question,but I've already enabled small memory dump in the Startup and Recovery settings. The directory is also the default one "%SystemRoot%\Minidump. But after I crash my system with installing SPTD 1.69,the folder is always empty. I wanted to ask for help since I couldn't...
BSOD Help and Support
BSOD again.. Minidump file check?
Hello! Once again I got BSOD during boot on desktop. Now when I'm putting minidump to a .zip it says that I can't do that :D What??? It says "Access denied" whatever I do with that file. I really want to archive it and send here for professionals analyze:confused:
BSOD Help and Support
Hello again! I started once again my pc just ten minutes ago and bsod came on desktop.. Then computer started automatically and bsod came while loading windows. Then I shut down computer and started again and the post message said lot of things and " overclock failed ". I have never overclocked...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 07:42.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App