Random BSOD when powering up comp

Fresh install of Ultimate x64. I'm not sure what it does because I usually press the button and go do some other stuff for a couple of minutes so I wasn't around to see what actually happened. I'll keep a closer eye on it now.

you have the dumpfiles attached. Thank you.

goguvarra said:

Fresh install of Ultimate x64. I'm not sure what it does because I usually press the button and go do some other stuff for a couple of minutes so I wasn't around to see what actually happened. I'll keep a closer eye on it now.

you have the dumpfiles attached. Thank you.

First time I have seen this one.

This bug check results from a serious error in a driver or other system file. The file header checksum does not match the expected checksum.
This can also be caused by faulty hardware in the I/O path to the file (a disk error, faulty RAM, or a corrupted page file).


I would run a system file check and if it passes then run memtest and verifier below.



I would also run a system file check to verify and repair the OS files


To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

It may need to be run up to three times before successful
Let us know the results from the report at the end

Read here for more information [URL]https://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html




If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



2-Driver verifier

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).

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 "Special Pool", "Force Pending I/O Requests" and "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:

Code:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Using Driver Verifier to identify issues with Windows drivers for advanced users

wow...something new even for you guys

thanks for the detailed answer. I'll test everything. Thing is system is running super smooth now after windows install. Previous install kept bugging me with a nvkldm.sys error which now is gone I hope after a graphics card change.

I also ran prime95 for a couple of hours and it reported no error with overcloked settings.

I'll run the memtest with default settings and see what happens.

thanks again.

goguvarra said:

wow...something new even for you guys

thanks for the detailed answer. I'll test everything. Thing is system is running super smooth now after windows install. Previous install kept bugging me with a nvkldm.sys error which now is gone I hope after a graphics card change.

I also ran prime95 for a couple of hours and it reported no error with overcloked settings.

I'll run the memtest with default settings and see what happens.

thanks again.

My pleasure and good luck

Ken

This is the loc from the system file check.

I saw what the error is now. The computer boots up normally until the windows 7 logo would appear but sometimes instead of that I get what white progress bar with "Windows is loading files" on top, which I think appears when you want to start it in safe mode.
After that the screen goes blank and the computer restarts or sometimes the startup check or whatever its called starts.

I'll run memtest to see what is happening

Memtest was ok for 1 pass. I think this is starting to show it is because of the overcloked memories. set them back at 800 mhz to see if it will crash again.