|19 Apr 2012||#1|
BSOD Multiple Reasons
I built a new computer about a month ago and about a week or two after it was built, I started getting BSODs. All checks on boot are passing and all my fans have been running. I have tried re-installing Windows twice already. Here's a list of the incidents since system reset.
041612-9640-01.dmp 4/16/2012 11:14:27 AM BAD_POOL_CALLER 0x000000c2 00000000`00000099 fffff8a0`0832d900 00000000`00000000 00000000`00000000 dxgmms1.sys dxgmms1.sys+1b5fd x64 ntoskrnl.exe+7cc80 C:\Windows\Minidump\041612-9640-01.dmp 8 15 7601 293,128
041912-9781-01.dmp 4/19/2012 8:46:06 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00041790 fffffa80`0a8372c0 00000000`0000ffff 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+7cc80 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17790 (win7sp1_gdr.120305-1505) x64 ntoskrnl.exe+7cc80 C:\Windows\Minidump\041912-9781-01.dmp 8 15 7601 288,176
041912-9531-01.dmp 4/19/2012 12:49:23 AM MEMORY_MANAGEMENT 0x0000001a 00000000`00041201 fffff680`00758bc0 ed200003`1f19b867 fffffa80`0ec430b0 ntoskrnl.exe ntoskrnl.exe+7cc80 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17790 (win7sp1_gdr.120305-1505) x64 ntoskrnl.exe+7cc80 C:\Windows\Minidump\041912-9531-01.dmp 8 15 7601 293,072
041412-9594-01.dmp 4/14/2012 11:20:50 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff900`80734f50 00000000`00000001 fffff960`00284e5a 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+7cc80 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17790 (win7sp1_gdr.120305-1505) x64 ntoskrnl.exe+7cc80 C:\Windows\Minidump\041412-9594-01.dmp 8 15 7601 292,696
041212-9734-01.dmp 4/12/2012 9:35:39 PM PFN_LIST_CORRUPT 0x0000004e 00000000`00000099 00000000`003271c2 00000000`00000000 00000000`00328a42 ntoskrnl.exe ntoskrnl.exe+7cd40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17790 (win7sp1_gdr.120305-1505) x64 ntoskrnl.exe+7cd40 C:\Windows\Minidump\041212-9734-01.dmp 8 15 7601 292,624
It is my first built computer and I am getting fed up with trying to figure out what's wrong. Any help would be appreciated. Thanks ^_^.
|My System Specs|
|19 Apr 2012||#2|
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.
* 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.
|My System Specs|
|19 Apr 2012||#5|
These crashes were caused by memory corruption probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.
* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!
* If you have a Raid update its Driver.
*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-7 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.
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.
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).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .
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 "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.
If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking
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.
Thanks to JGriff2 & Usasma.
Using Driver Verifier (Windows Drivers)
|My System Specs|
|03 May 2012||#6|
So, I've been running the driver verifier since mid-day yesterday and no crashes. I ran the memtest about a week ago and when I went to check on it, the screen was mostly distorted. There was just a bunch of nonsense where the information should be. Certain things still showed, like the duration of the process. I'll be running it again tonight.
|My System Specs|
|10 May 2012||#9|
The latest crashes were related to your Marvell controllers and their drivers. Uninstall them through Device Manager. You will find them under IDE ATA/ATAPI controllers.
Let Windows install the appropriate drivers when it restarts.
|My System Specs|
|Similar help and support threads for2: BSOD Multiple Reasons|
|BSODs with multiple reasons.||BSOD Help and Support|
|Multiple BSOD's with multiple reasons||BSOD Help and Support|
|BSOD in vanilla computer with multiple reasons||BSOD Help and Support|
|BSOD MULTIPLE DIFFERENT REASONS(bad pool header etc etc)||BSOD Help and Support|
|BSOD for what seems several reasons||BSOD Help and Support|
|Windows 7: Four reasons to upgrade, four reasons to st||News|
|Google Voice: 5 Reasons to Use It, 5 Reasons to Think T||News|
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
All times are GMT -5. The time now is 05:52 PM.