Hello
Seroxis and welcome to the Forums,
Please don't bump your thread; it's against the forum rules and disadvantageous for you as it makes the thread seem more busy as if you were receiving assistance.
2) No useless posts, e.g., thread bumping, useless one liners, junk posting to increase post count, and identical multi-postings in different forums.
Read here:
Forum Rules
----------
Please reupload your
MSINFO32 as it is corrupted;
- Open an Evevated Command Prompt.
- Copy the following;
msinfo32 /nfo %USERPROFILE%\Desktop\MSINFO32.NFO
- In Command Prompt; Click on the CMD icon in the upper left corner.
- Click on Edit, then click on Paste. Hit ENTER.
A file called MSINFO32.nfo will be created on your desktop, this may take a while, please be patient.
- Right click the file, and select Send to, click on Compressed (zipped) folder.
A .zip called MSINFO32.zip will be created on your desktop.
- Upload the .zip by following this tutorial.
----------
After running
Driver Verifier, please attach another run of the SF Diagnostic Tool, so that we have the most recent dump files.
Code:
DEFAULT_BUCKET_ID: [COLOR=Red][B]VERIFIER_ENABLED[/B][/COLOR]_VISTA_MINIDUMP
Have you disabled
Driver Verifier after running it?
To disable it, please follow option two of
this tutorial.
----------
Code:
<Value><![CDATA[Microsoft Windows 7 Ultimate]]></Value>
<Value><![CDATA[[COLOR=Red][B]6.1.7600 Build 7600[/B][/COLOR]]]></Value>
Please install Service Pack 1 and all available updates.
:info: Please read this before installing;
How to install Service Pack 1
:ar:
Service Pack Center
----------
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
[COLOR=Red][B]BugCheck C1[/B][/COLOR], {fffff980134bcc10, fffff980134bc02f, 8303e8, 23}
[COLOR=Red][B]Probably caused by : memory_corruption[/B][/COLOR] ( nt!MiCheckSpecialPoolSlop+9a )
Followup: MachineOwner
---------
Usual cause: Faulty driver, faulty RAM.
More info :ar:
Bug check 0xC1_23.
----------
Please use the SFC /SCANNOW command as displayed in option two of
this tutorial.
- Click on the
rb:.
- Open an elevated command prompt.
- Type "SFC /SCANNOW" without the quotations.
- Let SFC do it's thing, and then prompted to, restart.
If SFC found and repaired anything, please do the following:
- When restarted, open an elevated command prompt.
- Type (or copy) the following, this will create a .txt file on your desktop;
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
- In your next reply, please attach this file using the method displayed in this tutorial.
----------
Please run
Memtest86+ to test your RAM for issues.
Tip
Let
Memtest run for
at least 10 passes and preferably overnight as it may take very long to complete.
:ar: Especially read part three of the
tutorial, which explains you to test each RAM stick in all DIMM slots to filter out failing slots.
Suppose you have got the result like that:
test|Slot1|Slot2
RAM1|
Error
|
Error
RAM2|Good|Good
It is a RAM, a bad RAM.
But if you have got a result like that:
test|Slot1|Slot2
RAM1|
Error
|Good
RAM2|
Error
|Good
It is a motherboard issue. The particular slot is bad.
----------
In your next post, please attach the dump file created by running Driver Verifier, as it should have pinpointed the cause of your BSoD's.
Good luck and keep us posted,
Nommy
