0

Can anyone help with this frequent warning I get in the event viewer after 'windows has recovered fron an unexpected shutdown , running windows 7 ultimate .
Event viewer reports this .
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-05-27T18:18:43.000000000Z" />
<EventRecordID>9693</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>flinn-PC</Computer>
<Security />
</System>
- <EventData>
<Data Name="param1">0x0000004e (0x00000099, 0x00009810, 0x00000000, 0x0002ee10)</Data>
<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
<Data Name="param3">052712-51656-01</Data>
</EventData>
</Event>

3
Contributors
6
Replies
7
Views
5 Years
Discussion Span
Last Post by JorgeM
0

Hi
Can you please give us a little more information
If you follow these directions you should end up with a few BSOD events recorded and a place for us to start looking -

Please download BlueScreenView http://www.nirsoft.net/utils/blue_screen_view.html (in zip file)•Extract (right-click > Extract all) the contents of bluescreenview.zip.

•Double-click on the BlueScreenView.exe file, to run the program. (No installation is required.)

•When scanning is done (usually complete by the time the interface appears), go ...

•Edit > Select All

•File > Save Selected Items, and save the report to your Desktop as BSOD.txt.

•Close the BlueScreenView window... ... ...

•Open BSOD.txt using Notepad and go ... .... ..

•Edit > Select All

•Edit > Copy, and then paste the entire contents of the text file into your next reply.

0

Many thanks for the help , after a good deal of googling I ran the windows memory test and then memtest which revealed a fault with memory , so a simple test with the ram cards out one at a time revealed the one which was faulting .

0

Have since found out that it was not anything to do with bad memory but a failed hard disk , have bought a replacent hd and now everything is back to best . interesting that windows and Memtest both reported that memory was at fault when in fact it was not

0

Keep an eye on the RAM though. It is still possible that you may have intermittent issues with one or more of the RAM modules. Depending where the fault is within the RAM module it may or may not produce a BSOD.

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.