Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Random BSOD


  • Please log in to reply
10 replies to this topic

#1 Qazwsx1

Qazwsx1

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:09 PM

Posted 05 January 2011 - 10:18 PM

Hello everyone I am new to this forum but hope fully you guys can help me out I just built a new pc and I am randomly getting bsod's and sometimes my video just goes black and comp stalls during gaming. I have done a memory dmp analysis and here is what it gave me:

My Specs:
Asus p6x58d-e motherboard
core i7 920
ocz DDR3 1600 ocz3f1600lv2g
xfx 7800gt video card (have a hd 5870 on the way heh)
antec ea750 psu

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Downloads\010511-9157-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c54000 PsLoadedModuleList = 0xfffff800`02e91e50
Debug session time: Wed Jan  5 21:25:32.554 2011 (UTC - 5:00)
System Uptime: 0 days 4:47:22.600
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff680000b5988, 0, 0, fffff80002d0c4e4}

Probably caused by : memory_corruption ( nt!MiPageMightBeZero+8 )

Followup: MachineOwner
---------

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff680000b5988, memory referenced
Arg2: 0000000000000000, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002d0c4e4, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efc0e0
 fffff680000b5988 

CURRENT_IRQL:  0

FAULTING_IP: 
nt!MiPageMightBeZero+8
fffff800`02d0c4e4 f60220          test    byte ptr [rdx],20h

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff880035e75a0 -- (.trap 0xfffff880035e75a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80043fa370
rdx=fffff680000b5988 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d0c4e4 rsp=fffff880035e7738 rbp=fffffa80043fa370
 r8=0000000000000007  r9=ae0000016a8bdc46 r10=0000000000000000
r11=0000000000000007 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiPageMightBeZero+0x8:
fffff800`02d0c4e4 f60220          test    byte ptr [rdx],20h ds:20f0:fffff680`000b5988=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cc3ca9 to fffff80002cc4740

STACK_TEXT:  
fffff880`035e7458 fffff800`02cc3ca9 : 00000000`0000000a fffff680`000b5988 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`035e7460 fffff800`02cc2920 : 00000000`00000000 ae000001`6a8bd847 00000000`00000000 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`035e75a0 fffff800`02d0c4e4 : fffff800`02d0c3ba ffffffff`ffffffff 00000000`00000001 ffffffff`ffffffff : nt!KiPageFault+0x260
fffff880`035e7738 fffff800`02d0c3ba : ffffffff`ffffffff 00000000`00000001 ffffffff`ffffffff 00000000`00004767 : nt!MiPageMightBeZero+0x8
fffff880`035e7740 fffff800`02cd859e : fffffa80`072816d8 fffff880`035e7990 00000000`00000000 00000000`00000007 : nt!MiFreeWsleList+0x43e
fffff880`035e7930 fffff800`02cd899d : fffffa80`072816d8 fffff880`00000001 00000000`00000001 fffff880`035e7bb0 : nt!MiAgeWorkingSet+0x47e
fffff880`035e7ae0 fffff800`02cd8ee2 : 00000000`00004359 00000000`00000000 fffffa80`00000000 00000000`00000008 : nt!MiProcessWorkingSets+0x1e5
fffff880`035e7b80 fffff800`02cd9173 : 00000000`00000008 fffff880`035e7c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`035e7bd0 fffff800`02f68c06 : fffffa80`0551c8e0 00000000`00000080 fffffa80`054f3890 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`035e7d40 fffff800`02ca2c26 : fffff880`009b2180 fffffa80`0551c8e0 fffff880`009bd0c0 3f593f59`a67fa67f : nt!PspSystemThreadStartup+0x5a
fffff880`035e7d80 00000000`00000000 : fffff880`035e8000 fffff880`035e2000 fffff880`035e7710 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiPageMightBeZero+8
fffff800`02d0c4e4 f60220          test    byte ptr [rdx],20h

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiPageMightBeZero+8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiPageMightBeZero+8

BUCKET_ID:  X64_0xA_nt!MiPageMightBeZero+8

Followup: MachineOwner
---------


BC AdBot (Login to Remove)

 


#2 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,483 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:04:09 PM

Posted 05 January 2011 - 11:34 PM

Hi Qazwsx1, and welcome to BleepingComputer.

Please download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#3 Qazwsx1

Qazwsx1
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:09 PM

Posted 06 January 2011 - 12:43 AM

Wow that way was a lot easier then the writeup I used from this forum lol here it is:

==================================================
Dump File         : 010511-9157-01.dmp
Crash Time        : 1/5/2011 9:32:19 PM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x0000000a
Parameter 1       : fffff680`000b5988
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`00000000
Parameter 4       : fffff800`02d0c4e4
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\Minidump\010511-9157-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 292,816
==================================================


#4 Qazwsx1

Qazwsx1
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:09 PM

Posted 07 January 2011 - 01:48 AM

Anyone have an idea whats going on?

#5 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,483 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:04:09 PM

Posted 07 January 2011 - 10:02 AM

There are a couple of things that could be causing this. One of these could be the drivers for the graphics card, the other could be a problem with your RAM.

See if there is an update for the graphics.

You can test the RAM by downloading and running Memtest86.

***** A. If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-....iso.zip file.
3. Inside, you'll find memtest86+-....iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

Posted Image

8. Locate memtest86+-....iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

Posted Image

10. Once the CD is created, boot from it, and memtest will automatically start to run.

The running program will look something like this depending on the size and number of ram modules installed:


Posted Image

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

Posted Image

The following image is the test results area:

Posted Image

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#6 fueL

fueL

  • Members
  • 67 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Philadelphia, PA
  • Local time:07:09 PM

Posted 07 January 2011 - 11:00 AM

"IMAGE_NAME: memory_corruption"

I would recommend going through with dc3's steps and check your memory. 5-6 passes will tell you if the memory has errors, but if you run it overnight you're pretty much guaranteed to know if there are faults or not (the longer the run the program, the better) I've had memory modules not show errors until the 10th or 11th pass before

#7 Qazwsx1

Qazwsx1
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:09 PM

Posted 07 January 2011 - 11:46 PM

oh yeah I ran memtest86 the other day it passed but I only did one pass so sometime I'll have to run it for a couple of hours to get more then one pass to really test it. I just took out my 7800gt and replaced it with an HD5870 so that should take care of it being a video driver problem hopefully.

#8 Qazwsx1

Qazwsx1
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:09 PM

Posted 01 June 2011 - 01:28 AM

I'm still getting random BSOD's not a lot but every once and a while i'll get one here is a dump from today. Also I got rid of the nvidia card and I now have an ati radeon HD5870.

==================================================
Dump File         : 053111-8502-01.dmp
Crash Time        : 5/31/2011 3:52:02 PM
Bug Check String  : MEMORY_MANAGEMENT
Bug Check Code    : 0x0000001a
Parameter 1       : 00000000`00041284
Parameter 2       : 00000000`281f3001
Parameter 3       : 00000000`00018974
Parameter 4       : fffff700`01080000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7fd00
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17592 (win7sp1_gdr.110408-1631)
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\Minidump\053111-8502-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 287,884
==================================================

Edited by Qazwsx1, 01 June 2011 - 01:29 AM.


#9 hamluis

hamluis

    Moderator


  • Moderator
  • 55,748 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:06:09 PM

Posted 01 June 2011 - 02:14 PM

One BSOD message...seldom is useful in resolving/determining system problems.

Let's try this.

Download/install BlueScreenView, http://www.nirsoft.net/utils/blue_screen_view.html.

Double-click BlueScreenView.exe file.

When scanning is done, go Edit/Select All...then File/Save Selected Items.

Save the report as BSOD.txt.

Open BSOD.txt in Notepad, copy all content and paste it into your next reply.

Louis

#10 Qazwsx1

Qazwsx1
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:09 PM

Posted 01 June 2011 - 05:02 PM

==================================================

Dump File         : 053111-8502-01.dmp

Crash Time        : 5/31/2011 3:52:02 PM

Bug Check String  : MEMORY_MANAGEMENT

Bug Check Code    : 0x0000001a

Parameter 1       : 00000000`00041284

Parameter 2       : 00000000`281f3001

Parameter 3       : 00000000`00018974

Parameter 4       : fffff700`01080000

Caused By Driver  : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+7fd00

File Description  : NT Kernel & System

Product Name      : Microsoft® Windows® Operating System

Company           : Microsoft Corporation

File Version      : 6.1.7601.17592 (win7sp1_gdr.110408-1631)

Processor         : x64

Computer Name     : 

Full Path         : C:\Windows\Minidump\053111-8502-01.dmp

Processors Count  : 8

Major Version     : 15

Minor Version     : 7601

Dump File Size    : 287,884

==================================================



==================================================

Dump File         : 050211-8673-01.dmp

Crash Time        : 5/2/2011 8:52:57 PM

Bug Check String  : PFN_LIST_CORRUPT

Bug Check Code    : 0x0000004e

Parameter 1       : 00000000`00000099

Parameter 2       : 00000000`000398f4

Parameter 3       : 00000000`00000002

Parameter 4       : 00000000`00188df3

Caused By Driver  : secdrv.SYS

Caused By Address : secdrv.SYS+24162c8

File Description  : 

Product Name      : 

Company           : 

File Version      : 

Processor         : x64

Computer Name     : 

Full Path         : C:\Windows\Minidump\050211-8673-01.dmp

Processors Count  : 8

Major Version     : 15

Minor Version     : 7601

Dump File Size    : 288,780

==================================================



==================================================

Dump File         : 041711-8517-01.dmp

Crash Time        : 4/17/2011 5:40:13 PM

Bug Check String  : MEMORY_MANAGEMENT

Bug Check Code    : 0x0000001a

Parameter 1       : 00000000`00041284

Parameter 2       : 00000000`1b26b001

Parameter 3       : 00000000`0001658c

Parameter 4       : fffff700`01080000

Caused By Driver  : discache.sys

Caused By Address : discache.sys+53312c8

File Description  : 

Product Name      : 

Company           : 

File Version      : 

Processor         : x64

Computer Name     : 

Full Path         : C:\Windows\Minidump\041711-8517-01.dmp

Processors Count  : 8

Major Version     : 15

Minor Version     : 7601

Dump File Size    : 287,756

==================================================



==================================================

Dump File         : 040811-8611-01.dmp

Crash Time        : 4/8/2011 10:20:05 PM

Bug Check String  : MEMORY_MANAGEMENT

Bug Check Code    : 0x0000001a

Parameter 1       : 00000000`00041284

Parameter 2       : 00000000`2ac85001

Parameter 3       : 00000000`0001cf74

Parameter 4       : fffff700`01080000

Caused By Driver  : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+80640

File Description  : NT Kernel & System

Product Name      : Microsoft® Windows® Operating System

Company           : Microsoft Corporation

File Version      : 6.1.7601.17592 (win7sp1_gdr.110408-1631)

Processor         : x64

Computer Name     : 

Full Path         : C:\Windows\Minidump\040811-8611-01.dmp

Processors Count  : 8

Major Version     : 15

Minor Version     : 7601

Dump File Size    : 276,368

==================================================




Edited by Qazwsx1, 01 June 2011 - 05:04 PM.


#11 hamluis

hamluis

    Moderator


  • Moderator
  • 55,748 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:06:09 PM

Posted 01 June 2011 - 05:47 PM

http://www.neuber.com/taskmanager/process/secdrv.sys.html

https://www.faultwire.com/file_report/discache.sys.html

0x0000001A: MEMORY_MANAGEMENT
This memory management error is usually hardware related. If this occurs while installing Windows, also check the Windows system requirements including the amount of RAM and disk space required to load the operating system.

0x0000004E: PFN_LIST_CORRUPT
This indicates that the memory management Page File Number list is corrupted. Can be caused by corrupt physical RAM, or by drivers passing bad memory descriptor lists.

Memtest86+ Guide-How To's - Overclockers Forums - http://www.overclockers.com/forums/showthread.php?t=409152

I suggest doing extensive testing of the RAM modules, using the guide posted above.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users