Constant BSOD on clean install of windows 7

Toggle sidebar Toggle sidebar
C

Corn_Dog

Reputable
Aug 30, 2014
16
0
4,510
So I recently did a clean install of windows 7 on the machine I built about 2 years ago and now I am getting constant BSODs for anything I do. I've tried to update all the out of date drivers but I don't know which or what is causing these crashes.
Here is a dump file: http://www.filedropper.com/090815-21231-01

If anyone could figure out the issue it would be greatly appreciated.
 
Sort by date Sort by votes
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
bugcheck was caused by an illegal instruction being called, looks like your machine was running for 6 minutes. Look for heating problems like a CPU fan that is not spinning.

I would also reset your BIOS back to defaults (I just don't like the speed listed in BIOS current CPU speed=3485MHz) I don't like the external clock being at 102MHZ (this can mean your BIOS is overclocking the system BUS from 100MHZ)

You do have the current BIOS update but the also update the SATA driver for your board at the same time so Pick it up.


go here:
https://www.asus.com/us/Motherboards/P8Z77V/HelpDesk_Download/
pick up the update SATA driver dated 2015/09/01
machine info:

Manufacturer ASUSTeK COMPUTER INC.
Product P8Z77-V
Processor Version Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
Processor Voltage 8ah - 1.0V
External Clock 102MHz
Max Speed 3800MHz
Current Speed 3485MHz

 
Upvote 0 Downvote
C

Corn_Dog

Reputable
Aug 30, 2014
16
0
4,510


I set the BIOS to default and updated the SATA drivers and the problem still persists. Could it be something else?
Here's another dump file: http://www.filedropper.com/090815-27736-01
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
- system was up for 5 mins. Can you boot into BIOS and leave your system running for 10 minutes without problems? Check temperatures while in BIOS if you system has that ability. Confirm the CPU fan is working. Low voltage from the power supply could also cause this problem but more likely to just reboot on you.

- Can you boot memtest86 on its own image and run the tests?
----------------
You might also want to change your memory dump type to kernel memory dump to have more debug info saved to the memory dump file.
how to change memory dump type: https://www.sophos.com/en-us/support/knowledgebase/111474.aspx

if these tests pass, then boot windows and run cmd.exe as an admin, then run
sfc.exe /scannow
to check your core windows files for corruption.


then run
verifier.exe /standard /all
reboot and wait for the next bugcheck.

Note: use verifier.exe /reset to turn off verifier functions.
after you finish testing.

Verifier will check drivers for common errors and bugcheck the system if it finds a problem.


When I look at the date of the sata driver I still see a 2012 file date, also, I still see strange clock frequencies.
when you reset the BIOS to defaults, you saved the settings?
try to find a setting for the speed of the PCI bus in the BIOS, it should be set to 100 MHz not 102MHz

The time stamp of the memory dump looks like it was a new memory dump.




 
Upvote 0 Downvote
C

Corn_Dog

Reputable
Aug 30, 2014
16
0
4,510

I ran Memtest86 over night and it came back with no errors.

My dump file was set to Kernel before but with this my minidump folder was empty after crashes.

I tried running sfc.exe /scannow but the command prompt returns with "Windows Resource Protection could not perform the requested operation." after attempting to verification.

I'm pretty sure I updated SATA and set BIOS to default before, but I did both again just to be sure, and I did save those defaults in BIOS. However the crashes still occur though. I don't think it's overheating though because the system won't crash while in safe mode.

Here are the 2 most recent dump files: http://www.filedropper.com/090915-40731-01
http://www.filedropper.com/090915-28766-01

 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
try and get the kernel memory dump with verifier turned on. It will make a much bigger memory dump that will have the internal error logs and copies of all stacks and loaded device drivers. If verifier is turned on, it will also have debug tracing.


---------------

the first bugcheck was in a driver filter, the stack was messed up again.
-------
kernel memory dumps are stored in a different location and file name
c:\windows\memory.dmp



 
Upvote 0 Downvote
C

Corn_Dog

Reputable
Aug 30, 2014
16
0
4,510


Sorry about that. I assume the verifier was still on for this because I did not turn it off.
Here's the kernel dump file: http://www.filedropper.com/memory_3

 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
is this a 32 bit version of windows 7 ? looks like a 64 bit but the memory dump is in x86 code.



 
Upvote 0 Downvote
C

Corn_Dog

Reputable
Aug 30, 2014
16
0
4,510


This is a 64 bit version.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
here: https://support.microsoft.com/en-us/kb/2528507
there was a hot fix that needed to be applied to get the correct memory dump to be produced.
if you apply the hotfix or the windows update you should get a good memory dump or maybe your problem might just go away.

---------

maybe you need to install all of the windows 7 sp1 hotfixes? looking now to see why the debugger does not work.
this debug memory dump was from your machine not a virtual machine ?

I would do the reinstall. I am not sure what is going on, just the my debugger really does not like your memory dump.



[/quotemsg]

This is a 64 bit version.
[/quotemsg]

 
Upvote 0 Downvote
C

Corn_Dog

Reputable
Aug 30, 2014
16
0
4,510


So I just did another clean install and sadly the problem still persists :/
Also, windows update still is not working (It wasn't working before I just forgot to mention that)

Here's another dump file: http://www.filedropper.com/memory_5
I really don't know what to do at this point.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
still showing a invalid kernel context, the memory dump looks like a x86 memory dump
did you install all of the windows updates, including the one that covers this particular bug?
(see hotfix listed)


 
Upvote 0 Downvote
C

Corn_Dog

Reputable
Aug 30, 2014
16
0
4,510


I tried the hotfix but it said it's not applicable to my system when I tried to install. I did, however, install these: https://support.microsoft.com/en-us/kb/2775511

Could the problem with the dump files be that I was uploading from safe mode?
I have two more here that I uploaded out of safe mode
http://www.filedropper.com/091015-12074-01 - minidump
http://www.filedropper.com/memory_1 - memory.dmp
 
Upvote 0 Downvote
B

bytemewnc

Reputable
Jul 4, 2015
19
0
4,520


Have you tried removing ram and installing with only one stick? Also try installing from another medium, flash drive or a different installation disk or disk drive even.
 
Upvote 0 Downvote
C

Corn_Dog

Reputable
Aug 30, 2014
16
0
4,510


Installing Windows with one stick in? And I only have the one copy of Windows 7 on the disk it came on. It's an oem copy.

 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom