Solved BSOD seemingly randomly. No new apps or hardware installed

[Supermonkey47]

System info:
- Windows 7 Ultimate x64
- It is the original installed OS on the system
- It is full retail version
- Age of system (hardware) is approximately 6 months
- What is the age of OS installation is approximately 6 months
- I have not re-installed the OS since the initial build.

Suddenly, over the last week, my system has been suffering from BSOD randomly. The system seems to lock up just prior to the BSOD.

I have trying putting it into Safe Mode but the same occurs.

I have run a Memtest and no errors are reported.
I have run an SFC scan and no errors were reported.

My dump file and Perfmon are attached. Any light you can shed on this would be much appreciated.

Thanks

 

[zigzag3143]

No DMPS included in upload try this method.

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP


We could also use some system information, which you can get easily by running msinfo32.
To do that go to start>run>type msinfo32>enter

When it is finished running go to file>save>name it and upload to us here.


You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[Supermonkey47]

Im having trouble retrieving the DMP's. I have followed the instructions above, but I cant find the Minidumps folder in \Windows.

The system has BSOD since I enabled minidumps, but when it BSOD's, it says it is "collating dump data" then "initialising the disk" to save it, but it just hangs there forever. Is that why I cant find the minidumps?

In the meantime I have uploaded the System info from msinfo32 you requested.

Thanks

 

[zigzag3143]

Im having trouble retrieving the DMP's. I have followed the instructions above, but I cant find the Minidumps folder in \Windows.

The system has BSOD since I enabled minidumps, but when it BSOD's, it says it is "collating dump data" then "initialising the disk" to save it, but it just hangs there forever. Is that why I cant find the minidumps?

In the meantime I have uploaded the System info from msinfo32 you requested.

Thanks

For dumps to be produced. . .
▪ Page file must be on OS drive
▪ Page file base allocation size must be > than installed physical RAM
▪ Windows Error Reporting (WER) system service should be set to MANUAL
▪ Set page file to system managed, OS drive

Set System Crash/ Recovery Settings to "Kernel Memory Dump" - this will produce. . .
--> a Full Kernel Memory Dump - c:\windows\memory.dmp
--> a Mini Kernel dump c:\windows\minidump

The Full Kernel is overwritten each BSOD; a new mini kernel dump is created w/ different name for each BSOD

 

[Supermonkey47]

For dumps to be produced. . .
▪ Page file must be on OS drive
▪ Page file base allocation size must be > than installed physical RAM
▪ Windows Error Reporting (WER) system service should be set to MANUAL
▪ Set page file to system managed, OS drive

I can confirm that all of the above has been configured correctly. But when the BSOD occurs it still just stops at "initialising disk for crash dump" and goes no further. There are no files or folders in c:\windows\minidump or c:\windows\ or anywhere else on the system labelled memory.dmp. In fact there isnt a folder labelled c:\windows\minidump.

Set System Crash/ Recovery Settings to "Kernel Memory Dump" - this will produce. . .
--> a Full Kernel Memory Dump - c:\windows\memory.dmp
--> a Mini Kernel dump c:\windows\minidump

The Full Kernel is overwritten each BSOD; a new mini kernel dump is created w/ different name for each BSOD

I had previously set it to minidump as directed in the first reply, but have subsequently tried it with the full kernel dump, but neither produce results.

To check your system's "Recoveros" (Recovery) and Page File settings via Windows Management Instrumentation (WMI), run the following -

HTML output - WMI - "Recoveros" and Page File Settings (HTML)
Text file output - WMI - "Recoveros" and Page File Settings (TEXT)

I am afraid I dont quite understand what you asking me to run here. I can find a text file called $_WMIC_recoveros.txt would that be useful to help with any diagnosis?

Thanks for the ongoing help, apologies in advance if I am just being a bit dim!

 

[zigzag3143]

For dumps to be produced. . .
▪ Page file must be on OS drive
▪ Page file base allocation size must be > than installed physical RAM
▪ Windows Error Reporting (WER) system service should be set to MANUAL
▪ Set page file to system managed, OS drive

I can confirm that all of the above has been configured correctly. But when the BSOD occurs it still just stops at "initialising disk for crash dump" and goes no further. There are no files or folders in c:\windows\minidump or c:\windows\ or anywhere else on the system labelled memory.dmp. In fact there isnt a folder labelled c:\windows\minidump.

Set System Crash/ Recovery Settings to "Kernel Memory Dump" - this will produce. . .
--> a Full Kernel Memory Dump - c:\windows\memory.dmp
--> a Mini Kernel dump c:\windows\minidump

The Full Kernel is overwritten each BSOD; a new mini kernel dump is created w/ different name for each BSOD

I had previously set it to minidump as directed in the first reply, but have subsequently tried it with the full kernel dump, but neither produce results.

To check your system's "Recoveros" (Recovery) and Page File settings via Windows Management Instrumentation (WMI), run the following -

HTML output - WMI - "Recoveros" and Page File Settings (HTML)
Text file output - WMI - "Recoveros" and Page File Settings (TEXT)

I am afraid I dont quite understand what you asking me to run here. I can find a text file called $_WMIC_recoveros.txt would that be useful to help with any diagnosis?

Thanks for the ongoing help, apologies in advance if I am just being a bit dim!

You arent dim, in fact I am. I was supposed to clip that piece off, please ignore it.

 

[Supermonkey47]

thanks Zigzag, do you have any ideas on why the dumps arnt being created? Is there anything else I need to configure or try?

 

[zigzag3143]

thanks Zigzag, do you have any ideas on why the dumps arnt being created? Is there anything else I need to configure or try?

As indicated there are a lot of reasons why a DMP may not be created. It may just happen so early in the boot that the service required to report the crash hasnt even started yet

If you still cant get them please upload your event viewer logs there may be something in there to help

Please provide us with your Event Viewer administrative logs by following these steps:


Click Start Menu
Type eventvwr into Search programs and files (do not hit enter)
Right click eventvwr.exe and click Run as administrator
Expand Custom Views
Click Administrative Events
Right click Administrative Events
Save all Events in Custom View As...
Save them in a folder where you will remember which folder and save as Errors.evtx
Go to where you saved Errors.evtx
Right click Errors.evtx -> send to -> compressed (zipped) folder
Upload the .zip file here.

 

[Supermonkey47]

The BSOD doesn't seem to happen during boot. Instead it is any time between 10 and 20 mins after boot.

I have attached the event errors as requested.

Thanks.

 

[zigzag3143]

The BSOD doesn't seem to happen during boot. Instead it is any time between 10 and 20 mins after boot.

I have attached the event errors as requested.

Thanks.

The only errors in eventvwr that could explain no DMP files are HD controller errors. That and network setup is hugely delaying shutdown

I would run chkdsk


http://www.sevenforums.com/tutorials/433-disk-check.html

 

[Supermonkey47]

I have run chkdsk now and it has returned no errors or bad sectors. I have re-run Memtest86 for 3 passes and again there were no errors. But the system still BSODs after about 15-20 mins.

Is the only option left to re-install windows?

 

[James7679]

Not to replace the help of zigzag, but there are a few things to consider.
1. Your up-times do vary greatly, anywhere from 20 minutes to an hour and a half.
2. There are a lot of errors in event viewer, but it appears as most of them are repeated over and over.
3. You have a repeated error of MSE not loading properly.
4. There is no visible DIRECT correlation to your crashes.
5. You aren't getting minidumps(Possibly due to hard shut downs and the system not having the time to generate them)

It may be likely that you need to re-install, but it is possible that a repair install could fix your issues.

Also, heat could be causing these crashes. Open up your case and see if there is a large amount of dust inside. Try cleaning all components with a few cans of compressed air.

My final thought is that your power supply could be going bad, this could explain, also, the lack of mini-dumps. If the PSU, drops, the sudden loss of power would result in there not being a mini-dump.

Please fill out your system specs thoroughly and give the age of each component respectively.

 

[Supermonkey47]

Hi and thanks for your input.

I have now filled out my full specs and I can confirm that every component was purchased and fitted in mid September 2011. They are almost exactly 6 months old.

I have opened up the case and there is little to no dust, but I have given all the components a thorough blast with an air can just to be certain.

Unfortunately the problem still occurs.

Is MSE Microsoft Security Essentials? Shall I try and un-install that and see?

 

[Supermonkey47]

update:

I have un-installed MS Security Essentials just in case, but the system BSOD again anyway.

I dont think it is the power supply, when it hangs everything appears to be powered on still, then it BSOD's and still there is no power problem. The BSOD screen can remain like that for hours, but as always is hanging on "initialising disk for crash dump".

Even though the memtest showed no errors, I have now tried it with alternative memory installed, but still no improvement. Its looking like my only option is to try and do a repair install of Windows. Though Im not sure that it will help.

 

[James7679]

You can try doing a repair install. It wont hurt.

Let us know how it goes.

 

[Supermonkey47]

Ok, I was just about to do a repair install of Windows and it BSOD again. But this time the dump files were created. I ahve attached them for you to have a look at and see if they help in any way.

Thanks

 

[zigzag3143]

Ok, I was just about to do a repair install of Windows and it BSOD again. But this time the dump files were created. I ahve attached them for you to have a look at and see if they help in any way.

Thanks

This one was related to an OS file and your HDAudio.sys. I would update the Audio and run a system file heck to verify the OS file.


http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

 

[Supermonkey47]

Whilst I was trying to update the audio, another BSOD. File attached.

 

[zigzag3143]

Whilst I was trying to update the audio, another BSOD. File attached.

Critical object termination probably Related to nusb3xhc.sys USB 3.0 Host Controller Driver from NEC Electronics Corporation. I would re-install newest driver available and run a system file check.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

 

[Supermonkey47]

Thanks, I have just updated my audio drivers and USB host controller drivers. SFC scan reported no integrity problems.

Fingers crossed no more BSODs.

I will let you know!