Brand new computer, occasional BSOD, can't find any pattern

Arc · 19 Dec 2012

Dumps are vaguely saying about memory corruption, but not precisely.

First, scan the system for possible virus infection.

Then, if nothing found in those, test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

If it also comes clear, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

zap514 · 21 Dec 2012

Hmm, this is interesting, I just formated the harddrive and did a fresh windows install again, I only installed all the latest drivers from a USB device, then I used an ethernet cable to my router as usual. Tried to download firefox through internet explorer but every time the file got corrupt, then i used the same cable to my other two computers, running windows 7 and snow leopard, tried downloading the same file, multiple times and it never got corrupted. So i put firefox on a Usb and installed it on my new computer, then it worked fine but whenever i downloaded files they would still get corrupt almost every time.

I decided to let computer stay on overnight without an ethernet cable plugged in and in the morning it showed a BSOD.

It was not saved at the regular location but in C:\WIndows\memory.dmp
Also it's a lot larger than normal, 478Mb(!?)
The program "Whocrashed" gave me the following information:

crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x77 (0x0, 0xFFFFFA800D067B60, 0x0, 0xFFFFF880085D9680)
Error: KERNEL_STACK_INPAGE_ERROR
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
A third party driver was identified as the probable root cause of this system error.
Google query: KERNEL_STACK_INPAGE_ERROR

I have scanned with Tdsskiller and the computer appears to be clean.
Any ideas?

I could upload the file for you but then I would have to use another uploadingsite and it will probably take a while because my internet uploadconnection is very slow..

Arc · 21 Dec 2012

Upload the file when you can ... I cannot say anything about the crash not seeing the dump.

zap514 · 21 Dec 2012

It went faster than expected when zipped. here is the link to the file:
Skicka filer | Dela filer | Dela fil | ladda upp

Arc · 21 Dec 2012

You have memory dump configured. Set it to minidump.
Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

zap514 · 22 Dec 2012

Okay, I changed the settings and ran Verifier overnight and it crashed again.
Here is the new Minidump, hope that works better.