BSOD problems

MonKENy

Platinum Member
Nov 1, 2007
2,026
3
81
Since ive built my PC awhile back i have intermittently had BSOD. I ran a who crashed it report and this is what its said of the last 3

System Information (local)
--------------------------------------------------------------------------------

computer name: MONKENY-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X4 965 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 8589205504 total
VM: 2147352576, free: 1916207104



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 7/31/2011 1:08:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073011-17093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FB4617, 0xFFFFF88005AC47A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 7/30/2011 2:22:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072911-15796-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88007024AB8, 0xFFFFF88007024310, 0xFFFFF80002FC2617)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

Any Ideas what it could be? Or where to start looking? I assume video Drivers but not sure.
 

Ultralight

Senior member
Jul 11, 2004
990
1
76
Do this: Start > Run > Event Viewer > Okay.

Note any Yellow Triangles or Red X's and what they flag.
 

MonKENy

Platinum Member
Nov 1, 2007
2,026
3
81
I have alot. is there a way to export the info?


hmmm seems like the warnings are all DBS errors and the Criticals are kernal power. that I assume is from rebooting on a BSOD
 
Last edited:

MonKENy

Platinum Member
Nov 1, 2007
2,026
3
81
Log Name: Application
Source: Microsoft-Windows-RPC-Events
Date: 4/20/2011 11:44:43 PM
Event ID: 11
Task Category: None
Level: Warning
Keywords:
User: LOCAL SERVICE
Computer: MonKENy-PC
Description:
Possible Memory Leak. Application (C:\Windows\System32\svchost.exe -k LocalServiceNetworkRestricted) (PID: 1004) has passed a non-NULL pointer to RPC for an [out] parameter marked [allocate(all_nodes)]. [allocate(all_nodes)] parameters are always reallocated; if the original pointer contained the address of valid memory, that memory will be leaked. The call originated on the interface with UUID ({3f31c91e-2545-4b7b-9311-9529e8bffef6}), Method number (20). User Action: Contact your application vendor for an updated version of the application.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-RPC-Events" Guid="{F4AED7C7-A898-4627-B053-44A7CAA12FCD}" />
<EventID>11</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2011-04-21T06:44:43.530750000Z" />
<EventRecordID>128</EventRecordID>
<Correlation />
<Execution ProcessID="1004" ThreadID="1896" />
<Channel>Application</Channel>
<Computer>MonKENy-PC</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="ApplicationName">C:\Windows\System32\svchost.exe -k LocalServiceNetworkRestricted</Data>
<Data Name="ProcessId">1004</Data>
<Data Name="InterfaceId">{3F31C91E-2545-4B7B-9311-9529E8BFFEF6}</Data>
<Data Name="Method">20</Data>
</EventData>
</Event>
 

MonKENy

Platinum Member
Nov 1, 2007
2,026
3
81
There are 5 of these, 3 for dr4 2 for dr1 and 1 for dr2

Log Name: System
Source: Disk
Date: 6/29/2011 3:22:09 PM
Event ID: 51
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: MonKENy-PC
Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Disk" />
<EventID Qualifiers="32772">51</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-06-29T22:22:09.339843700Z" />
<EventRecordID>23329</EventRecordID>
<Channel>System</Channel>
<Computer>MonKENy-PC</Computer>
<Security />
</System>
<EventData>
<Data>\Device\Harddisk1\DR1</Data>
<Binary>030080000100000000000000330004802D010000130000C0000000000000000000105400000000008799060000000000FFFFFFFF01000000580000C40200000000200A1240022040000000003C00000000000000000000004846560880FAFFFF0000000000000000B025750A80FAFFFF1050320B80FAFFFF082A000000000000280000002A0800000800000000000000700002000000000A000000003A0000000000000000000000</Binary>
</EventData>
</Event>
 

Ultralight

Senior member
Jul 11, 2004
990
1
76
Go to Seagate's website and search for their free harddrive utility called SeaTools for Windows.

Download the ISO file to your desktop, double click the file and whatever burning program you have available will burn it to a CD.

Reboot your system with CD in the drive (you may have to go into the BIOS to have your DVD drive placed as First Bootable). The utility will almost immediately engage after boot-up.

Run the following tests in this order: S.M.A.R.T., Short, DST, and especially the Long DST.
 

MonKENy

Platinum Member
Nov 1, 2007
2,026
3
81
I Ran the seatools everything passed. Ill run memtest tonight and report back any issues.