Typical BSOD situation, minidump check?

[WIGILOCO]

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!

 

[Pauly]

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

 

[WIGILOCO]

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

 

[Pauly]

Please post all dumps you got and we can have a look through them see if we can find any other clues

 

[WIGILOCO]

There are all minidumps (8 files) I had in my Windows/Minidump -folder. Hope that helps! =)

 

[usasma]

Running the dump files.....

 

[usasma]

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:

CHKDSK /R /F:
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"

CHKDSK LogFile:
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 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
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 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
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
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
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 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
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 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
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 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
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 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  KHALMNPR.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
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 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  VSSVC.exe

 

[WIGILOCO]

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?

 

[WIGILOCO]

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.


I TRANSLATED IT TO ENGLISH FROM FINNISH WITH GOOGLE TRANSLATING HOPE THIS LOG HELPS!

*Suojauskuvain means security-something..

Let me know If you don't understand some word

 

[WIGILOCO]

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

 

[usasma]

Thanks for the translation (I have no language skills - neither spoken nor programming)

The BSOD only offers clues as to what's happening. So, if it points to your hard drive, that's the most likely explanation. My troubleshooting revolves around this - so the first thing that I ask is that you perform hard drive tests (to support/refute the supposition that it's a hard drive issue). Once that's done, we can then move on to other tests if necessary.

Also, I suggest the memory test in my "canned" H/W Diagnostics speech because it's easier to run these tests up front. At work we run a hard drive diagnostic, a memory diagnostic, a motherboard diagnostic (about $400 US), and a virusscan before we start working on a system. It saves us many hours of troubleshooting if we run these tests first.


In your case, chkdsk shows errors in your file system (but not that they were corrected). Are you sure that this is the result from running CHKDSK /F /R - or maybe it's from another test where you just ran CHKDSK?

But, regardless of what it is, the presence of errors in CHKDSK means that there are issues with the file system on your hard drive. BUT, we don't know what caused the errors - so running the hard drive diagnostic is definitely needed at this point.

Unfortunately the event log error doesn't have any significant information in it. Have you checked in C:\Windows\Minidump to see if there was a memory dump created at that time?

 

[WIGILOCO]

Thanks for the translation (I have no language skills - neither spoken nor programming)

The BSOD only offers clues as to what's happening. So, if it points to your hard drive, that's the most likely explanation. My troubleshooting revolves around this - so the first thing that I ask is that you perform hard drive tests (to support/refute the supposition that it's a hard drive issue). Once that's done, we can then move on to other tests if necessary.

Also, I suggest the memory test in my "canned" H/W Diagnostics speech because it's easier to run these tests up front. At work we run a hard drive diagnostic, a memory diagnostic, a motherboard diagnostic (about $400 US), and a virusscan before we start working on a system. It saves us many hours of troubleshooting if we run these tests first.


In your case, chkdsk shows errors in your file system (but not that they were corrected). Are you sure that this is the result from running CHKDSK /F /R - or maybe it's from another test where you just ran CHKDSK?

But, regardless of what it is, the presence of errors in CHKDSK means that there are issues with the file system on your hard drive. BUT, we don't know what caused the errors - so running the hard drive diagnostic is definitely needed at this point.

Unfortunately the event log error doesn't have any significant information in it. Have you checked in C:\Windows\Minidump to see if there was a memory dump created at that time?

Okay thank you man! I ran the /f /r but I can run It now too again, It takes like 20-30 min to complete so not a big problem.

I checked the minidump and there was no dump file named that. But those messages are gone (bluescreen gone for 2 cold boots and 6 reboots, when I raised up lil bit HT and NB voltage )

But I will run the chkdsk now for to be sure, and post the result here translated. This doesn't take so long, maybe up to 30minutes. And I will run overnight the seatools again. Seatools results I will post tomorrow morning.

Very much thanks for the help, really appreciate your work!

 

[WIGILOCO]

Log Name: Application
Source: Microsoft-Windows-wininit
Date: 16.2.2010 23:42:30
Event ID: 1001
Task Category: None
Level: About
Keywords: Traditional
User: --
Computer: Wili
Description:


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,976 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.

47 is deleted unused index configuration file 0x9 index $ SII.
47 is deleted unused index configuration file 0x9 index $ SDH.
47 is deleted unused suojauskuvainta.
Suojauskuvainten review has been completed.
17,917 data files processed.

CHKDSK check USN Journal-file ...
35944456 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) ...
34455985 free clusters processed.

Of free disk space check performed.
Windows has checked the file system. No errors were detected.

209612799 kilobytes total disk space.
71525468 KB in 80,284 files.
53,044 KB Index 17,918.
0 KB in a damaged sector.
210,347 KB in the system in use.
65,536 KB in the log file to use.
137823940 KB available disk.

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

Internal data:
00 8f 01 00 a6 7f 01 00 17 e3 02 00 00 00 00 00 ................
94 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.

That is the just runned CHKDSK /F /R (took 42minutes)

The translator failed on that " Errors were detected " -thing. In my language there reads " No errors were detected ", so the NO word was missing somehow I fixed It on my own. Weird that the google translator failed like that.. But all good?

Maybe you did see some errors on my first check because I didn't notice that translating failure My bad!

 

[WIGILOCO]

Today I went to home and cold booted my pc and bsod came.. Now restarted and avast! doesn't work anymore.. I can't get It on. Here is the dump file:

 

[usasma]

This is where I got the "errors" from:

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.

If that was a translation glitch, then everything's OK.

This BSOD blames the kernel of the OS (we don't believe that - so we have to look elsewhere).
First, I'd uninstall Avast and reinstall it (or another antivirus).
Then, since this is a pool error - it's a good place to 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

​

 

[WIGILOCO]

everytime I boot those things give me errors ?!?