BSOD

[nabz87]

Hey guys i'm trying to help a friend of mine who is having bsod recently. I downloaded the Bluescreenviewer and found that problem is related to ntoskrnl.exe but what to do now ?!

My friend is using Win 7 64bit

I attached the dmp file. Thanks for the help

 

[mgorman87]

Please upload a full report
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

There was only one dump and it was from 2 months ago. I would only be guessing at what is the problem using only the one dump. After you upload the report, I will review it and post my thoughts

 

[MarkJ]

Same again, this dump file is two months old. When was the last BSOD? Has your friend changed any of the settings, follow this guide to check it is still set to save dump files.

Click on Start > Control Panel > System > Advanced System Settings (left pane) > Advanced tab > Settings button for Startup and Recovery. In the System Failure box make these settings.

Check > Write an event to the system log.
Check > Automatically restart.
Select > 'Small Memory Dump' in the Write debugging information box.
Small Dump Directory should read %SystemRoot%\Minidump.

Check at the bottom of the box that "Overwrite any existing file" is not checked. If it is you will have to go back to the "Write debugging information" box, change "Small memory dump" to "Complete memory dump" then you can uncheck the "Overwrite any existing file" box. Then go back and reset "complete memory dump" back to "Small memory dump". Heaven knows why microsoft designed it that way.

Hit OK, OK again and close the System box.

Let it crash a few more times and then you should find the dump files on the drive the OS is installed on (normally C) From windows explorer expand the C: drive and then expand Windows, you should see a file called minidump. In there will be the dump files with the extension .dmp, zip them up and attach to your next post.

The only dump sent in suggests a fault with the RAM (amongst other things) so try running the PC on one stick of memory at a time. The full list of possible causes are:

Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

The report indicates that no anti virus is installed, please confirm.

 

[nabz87]

Why are you saying the minidump file is empty? I opened it myslef with Bluescreenview and it showed a corrupted driver.

 

[MarkJ]

Why are you saying the minidump file is empty?

I didn't. I said this "Same again, this dump file is two months old" meaning that it is the same as the first dump file you sent in. How could that possibly translate to me saying the minidump file is empty

I'll explain again, there is only one dump file dated 19th March 2011. It points to a windows driver which is quite common and extremely unlikely to be the cause of the BSOD. I have suggested a start to the diagnosis based on what I saw in that file and given a guide on obtaining more dump files for analysis in order to help you solve the problem.

You have overlooked a question I asked at the end of my post.

 

[nabz87]

Oh well I missread your post, my bad. My friends is using avast.

 

[MarkJ]

OK, follow what I have suggested and then we may make some progress

Concentrate on what I suggested to get more minidumps.

 

[mgorman87]

Following up on MarkJ's post, your one BSOD is inconclusive as to what is causing the problem. It could be either a faulty driver or faulty hardware.

Looking through the event log it appears that your having 0x9f bugchecks which is a driver power state failure. This is most likely a device hooked up to the computer either through PCI slot or USB. Without the minidump we can't tell what it is.

Please run these tests and report back the results
1. Memtest86 - Run for 7-8 passes - http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
2. Prime95 - Run all three tests for 3-4 hours each or until fail - http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html
3. Hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests

You may also enable driver verifier and if it causes any crashes upload a new jcgriff2 report - http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Event[22413]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2011-05-03T23:39:30.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: TAYAOUT
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009f (0x0000000000000003, 0xfffffa8008c24050, 0xfffff80000ba2748, 0xfffffa800a6e98f0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .

Event[22414]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2011-05-03T23:39:30.000
  Event ID: 1005
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: TAYAOUT
  Description: 
Unable to produce a minidump file from the full dump file.

Event log is showing more BSOD but you're not creating minidumps.
Check out this post to try and fix this issue
http://www.techsupportforum.com/for...s-windows-7-and-vista-452654.html#post2687596


BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Mar 19 18:47:40.352 2011 (UTC - 4:00)
System Uptime: 0 days 1:01:29.258
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+388 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_nt!PoIdle+388
BiosReleaseDate = 02/11/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]