Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Win XP 64bit BSOD mini dump


  • Please log in to reply

#1
chrisn770

chrisn770

    New Member

  • Member
  • Pip
  • 3 posts
Hi,

I am hoping someone will beable to shed some light on the cause of my new machine giving me BSOD about twice a day.
I have rebuilt the machine twice and it seems to start after installing SP2.

The BSOD reports a disk.sys problem and I have opened the mini dump files but don't have the experience to pinpoint where the problem lies. I can see references to driver faults and wrong sysmbols.

Justy hoping someone could provide some knowledeg to speed things up.

Here are the contents of a mini dump file.

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini031610-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsof...ownload/symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140
Debug session time: Tue Mar 16 17:15:39.562 2010 (UTC + 0:00)
System Uptime: 0 days 0:37:15.663
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffae03757806f, 0, fffffadf28c2c290, 5}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*** WARNING: Unable to verify checksum for disk.sys
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : disk.sys ( disk!memmove+60 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffae03757806f, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffffadf28c2c290, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: disk

FAULTING_MODULE: fffff80001000000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 45d69708

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
fffffae03757806f

FAULTING_IP:
disk!memmove+60
fffffadf`28c2c290 488b040a mov rax,qword ptr [rdx+rcx]

MM_INTERNAL_CODE: 5

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800010a5b15 to fffff8000102e890

STACK_TEXT:
fffffadf`21789448 fffff800`010a5b15 : 00000000`00000050 fffffae0`3757806f 00000000`00000000 fffffadf`21789520 : nt+0x2e890
fffffadf`21789450 00000000`00000050 : fffffae0`3757806f 00000000`00000000 fffffadf`21789520 00000000`00000005 : nt+0xa5b15
fffffadf`21789458 fffffae0`3757806f : 00000000`00000000 fffffadf`21789520 00000000`00000005 fffffadf`37c15c10 : 0x50
fffffadf`21789460 00000000`00000000 : fffffadf`21789520 00000000`00000005 fffffadf`37c15c10 00000000`00000000 : 0xfffffae0`3757806f


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
disk!memmove+60
fffffadf`28c2c290 488b040a mov rax,qword ptr [rdx+rcx]

SYMBOL_NAME: disk!memmove+60

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: disk.sys

BUCKET_ID: WRONG_SYMBOLS

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

0: kd> lmvm disk
start end module name
fffffadf`28c28000 fffffadf`28c3d000 disk C (pdb symbols) C:\Program Files\Debugging Tools for Windows (x64)\sym\disk.pdb\AC7BF32786D34E74BC5D7DCDE9B7E2451\disk.pdb
Loaded symbol image file: disk.sys
Mapped memory image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\disk.sys\45D6970815000\disk.sys
Image path: disk.sys
Image name: disk.sys
Timestamp: Sat Feb 17 05:47:52 2007 (45D69708)
CheckSum: 00000000
ImageSize: 00015000
File version: 5.2.3790.3959
Product version: 5.2.3790.3959
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0000.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: disk
OriginalFilename: disk.sys
ProductVersion: 5.2.3790.3959
FileVersion: 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
FileDescription: PnP Disk Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
0: kd> lmvm nt
start end module name
fffff800`01000000 fffff800`01497000 nt T (no symbols)
Loaded symbol image file: ntoskrnl.exe
Image path: ntoskrnl.exe
Image name: ntoskrnl.exe
Timestamp: Tue Dec 15 16:11:25 2009 (4B27B52D)
CheckSum: 00000000
ImageSize: 00497000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Thanks in advance
Chris
  • 0

Advertisements


#2
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
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.
  • 0

#3
chrisn770

chrisn770

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts
Hi Broni,

Thanks for your reply and advice. As requested I have included the output from the "bluescreen view" below.

==================================================
Dump File : Mini031610-02.dmp
Crash Time : 16/03/2010 19:48:21
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffae0`3757806f
Parameter 2 : 00000000`00000000
Parameter 3 : fffffadf`28c2c290
Parameter 4 : 00000000`00000005
Caused By Driver : mrxsmb.sys
Caused By Address : mrxsmb.sys+1216f06f
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini031610-02.dmp
Processors Count : 4
Major Version : 15
Minor Version : 3790
==================================================

==================================================
Dump File : Mini031610-01.dmp
Crash Time : 16/03/2010 16:38:37
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffadf`7f6aa7f1
Parameter 2 : 00000000`00000000
Parameter 3 : fffffadf`28c2c290
Parameter 4 : 00000000`00000000
Caused By Driver : eamon.sys
Caused By Address : eamon.sys+5a9357f1
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini031610-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 3790
==================================================

==================================================
Dump File : Mini031510-01.dmp
Crash Time : 15/03/2010 15:16:40
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffadf`42212732
Parameter 2 : 00000000`00000000
Parameter 3 : fffffadf`28c2c290
Parameter 4 : 00000000`00000000
Caused By Driver : vmnetbridge.sys
Caused By Address : vmnetbridge.sys+1c9ce732
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini031510-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 3790
==================================================

==================================================
Dump File : Mini031210-04.dmp
Crash Time : 12/03/2010 20:59:21
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffffadf`22dbfc78
Parameter 3 : fffffadf`29671480
Parameter 4 : fffffadf`29670e90
Caused By Driver : Npfs.SYS
Caused By Address : Npfs.SYS+3b8f6a0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini031210-04.dmp
Processors Count : 4
Major Version : 15
Minor Version : 3790
==================================================

==================================================
Dump File : Mini031210-03.dmp
Crash Time : 12/03/2010 16:26:35
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffadf`7f7824f7
Parameter 2 : 00000000`00000000
Parameter 3 : fffffadf`28c2c290
Parameter 4 : 00000000`00000000
Caused By Driver : hcmon.sys
Caused By Address : hcmon.sys+59be74f7
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini031210-03.dmp
Processors Count : 4
Major Version : 15
Minor Version : 3790
==================================================

==================================================
Dump File : Mini031210-02.dmp
Crash Time : 12/03/2010 14:51:10
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffadf`7fd77fa9
Parameter 2 : 00000000`00000000
Parameter 3 : fffffadf`28c2c290
Parameter 4 : 00000000`00000000
Caused By Driver : wdmaud.sys
Caused By Address : wdmaud.sys+5b184fa9
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini031210-02.dmp
Processors Count : 4
Major Version : 15
Minor Version : 3790
==================================================

==================================================
Dump File : Mini031210-01.dmp
Crash Time : 12/03/2010 14:11:58
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffadf`7edd02d7
Parameter 2 : 00000000`00000000
Parameter 3 : fffffadf`28c2c290
Parameter 4 : 00000000`00000000
Caused By Driver : hcmon.sys
Caused By Address : hcmon.sys+59b6a2d7
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini031210-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 3790
==================================================

==================================================
Dump File : Mini031010-01.dmp
Crash Time : 10/03/2010 15:51:11
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffadf`42dbbb92
Parameter 2 : 00000000`00000000
Parameter 3 : fffffadf`28c2c290
Parameter 4 : 00000000`00000000
Caused By Driver : mrxdav.sys
Caused By Address : mrxdav.sys+1dff6b92
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini031010-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 3790
==================================================

==================================================
Dump File : Mini030910-02.dmp
Crash Time : 09/03/2010 09:47:32
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`012876a5
Parameter 3 : fffffadf`242b9f40
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+2e890
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini030910-02.dmp
Processors Count : 4
Major Version : 15
Minor Version : 3790
==================================================

==================================================
Dump File : Mini030910-01.dmp
Crash Time : 09/03/2010 09:46:25
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`012876a5
Parameter 3 : fffffadf`242d4f40
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+2e890
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini030910-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 3790
==================================================

==================================================
Dump File : Mini030810-06.dmp
Crash Time : 08/03/2010 14:19:01
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffadf`bb162d1b
Parameter 2 : 00000000`00000000
Parameter 3 : fffffadf`28c2c2e0
Parameter 4 : 00000000`00000000
Caused By Driver : wdmaud.sys
Caused By Address : wdmaud.sys+963e3d1b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini030810-06.dmp
Processors Count : 4
Major Version : 15
Minor Version : 3790
==================================================

==================================================
Dump File : Mini030810-05.dmp
Crash Time : 08/03/2010 14:17:38
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffadf`903a63d6
Parameter 2 : 00000000`00000000
Parameter 3 : fffffadf`28c2c2e0
Parameter 4 : 00000000`00000000
Caused By Driver : splitter.sys
Caused By Address : splitter.sys+66a8f3d6
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini030810-05.dmp
Processors Count : 4
Major Version : 15
Minor Version : 3790
==================================================

==================================================
Dump File : Mini030810-04.dmp
Crash Time : 08/03/2010 14:15:49
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffadf`3ccfb262
Parameter 2 : 00000000`00000000
Parameter 3 : fffffadf`28c2c290
Parameter 4 : 00000000`00000000
Caused By Driver : mrxdav.sys
Caused By Address : mrxdav.sys+185ad262
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini030810-04.dmp
Processors Count : 4
Major Version : 15
Minor Version : 3790
==================================================

==================================================
Dump File : Mini030810-03.dmp
Crash Time : 08/03/2010 13:06:18
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffadf`550a9136
Parameter 2 : 00000000`00000000
Parameter 3 : fffffadf`28c2c290
Parameter 4 : 00000000`00000000
Caused By Driver : ndisuio.sys
Caused By Address : ndisuio.sys+2bc9e136
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini030810-03.dmp
Processors Count : 4
Major Version : 15
Minor Version : 3790
==================================================

==================================================
Dump File : Mini030810-02.dmp
Crash Time : 08/03/2010 13:01:19
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffadf`47457554
Parameter 2 : 00000000`00000000
Parameter 3 : fffffadf`28c2c290
Parameter 4 : 00000000`00000000
Caused By Driver : rasacd.sys
Caused By Address : rasacd.sys+1e16c554
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini030810-02.dmp
Processors Count : 4
Major Version : 15
Minor Version : 3790
==================================================

==================================================
Dump File : Mini030810-01.dmp
Crash Time : 08/03/2010 12:53:04
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffadf`8e912e56
Parameter 2 : 00000000`00000000
Parameter 3 : fffffadf`28c2c290
Parameter 4 : 00000000`00000000
Caused By Driver : secdrv.sys
Caused By Address : secdrv.sys+65397e56
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini030810-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 3790
==================================================
Regards
Chris
  • 0

#4
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Two most likely causes of your errors: bad RAM, or some infection.

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.
  • 0

#5
chrisn770

chrisn770

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts
Thanks for reply,

I have 4 x 2G mem sticks DDR2.

I will try a mem test because the issue is intermittent so may take some time running the PC adding a mem stick at a time.

Yesterday I went all day with no issues so not sure what a valid time line is for testing each mem stick.

One thing I did do yesterday is windows updates for nvidia driver, also unplugged an old IDE Hard Drive that I had connected to see if this was causing issues.

I will wait to see if it happens again before doing anymore troubleshooting as dont want to change too many things at the same time because I won't know what resolves the issue.

When I was looking through the mini dump output I pasted in a previous reply I noticed how many different "caused by driver" entries there were, i think 6 or 7 differnet referneces surely there is an underlying common issue. Interested how you came to the conclusion of bad mem or infection, just want to learn something from this so I can diagnose better in future.

Many thanks for your support

Chris
  • 0

#6
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts

I noticed how many different "caused by driver" entries there were, i think 6 or 7 differnet referneces

That's the info, which makes me think RAM, or some infection.

At the same time, you can always...

...start a new topic in the Malware Removal and Spyware Removal area.

Before you start a new topic click on this link --> Malware and Spyware Cleaning Guide, Please read before starting a new topic. This will give you a few preparations to make, as well as instruction for posting your OTListIt2 log.

If you are still having problems after being given a clean bill of health from the malware expert, then please return to THIS thread and we will pursue other options to help you solve your current problem(s).
  • 0

#7
Arbion

Arbion

    New Member

  • Member
  • Pip
  • 1 posts
Please Please help me. Today is the 4th day that my computer is restarting itself. I bought new RAM and replace it because I thought that the problem is there, but nothing happened, the same thing. I reformatted my PC, still the same problem. Please help me what to do to fix this problem. I searched on the internet to find the solution, with no success. Only here in this website is my hope to fix it.

Here is the copy of the BSOD.txt file created from BlueScreenView.

==================================================
Dump File : Mini101510-03.dmp
Crash Time : 10/15/2010 10:13:44 PM
Bug Check String : MACHINE_CHECK_EXCEPTION
Bug Check Code : 0x0000009c
Parameter 1 : 00000000`00000000
Parameter 2 : fffffadf`9f071240
Parameter 3 : 00000000`b2000000
Parameter 4 : 00000000`1040080f
Caused By Driver : hal.dll
Caused By Address : hal.dll+ef4c
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini101510-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 3790
==================================================

==================================================
Dump File : Mini101510-02.dmp
Crash Time : 10/15/2010 7:09:03 PM
Bug Check String : MACHINE_CHECK_EXCEPTION
Bug Check Code : 0x0000009c
Parameter 1 : 00000000`00000000
Parameter 2 : fffff800`00113bc0
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+ef4c
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini101510-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 3790
==================================================

==================================================
Dump File : Mini101510-01.dmp
Crash Time : 10/15/2010 4:45:09 PM
Bug Check String : MACHINE_CHECK_EXCEPTION
Bug Check Code : 0x0000009c
Parameter 1 : 00000000`00000000
Parameter 2 : fffffadf`9f071240
Parameter 3 : 00000000`b2000008
Parameter 4 : 00000000`1040080f
Caused By Driver : hal.dll
Caused By Address : hal.dll+ef4c
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini101510-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 3790
==================================================

==================================================
Dump File : Mini101410-04.dmp
Crash Time : 10/14/2010 11:37:20 PM
Bug Check String : MACHINE_CHECK_EXCEPTION
Bug Check Code : 0x0000009c
Parameter 1 : 00000000`00000000
Parameter 2 : fffff800`00113bc0
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+ef4c
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini101410-04.dmp
Processors Count : 2
Major Version : 15
Minor Version : 3790
==================================================

==================================================
Dump File : Mini101410-03.dmp
Crash Time : 10/14/2010 11:32:25 PM
Bug Check String : MACHINE_CHECK_EXCEPTION
Bug Check Code : 0x0000009c
Parameter 1 : 00000000`00000000
Parameter 2 : fffff800`00113bc0
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+ef4c
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini101410-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 3790
==================================================

==================================================
Dump File : Mini101410-02.dmp
Crash Time : 10/14/2010 10:57:29 PM
Bug Check String : MACHINE_CHECK_EXCEPTION
Bug Check Code : 0x0000009c
Parameter 1 : 00000000`00000000
Parameter 2 : fffffadf`9f071240
Parameter 3 : 00000000`b2000000
Parameter 4 : 00000000`1040080f
Caused By Driver : hal.dll
Caused By Address : hal.dll+ef4c
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini101410-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 3790
==================================================

==================================================
Dump File : Mini101410-01.dmp
Crash Time : 10/14/2010 5:40:58 PM
Bug Check String : MACHINE_CHECK_EXCEPTION
Bug Check Code : 0x0000009c
Parameter 1 : 00000000`00000000
Parameter 2 : fffffadf`9f071240
Parameter 3 : 00000000`b2000000
Parameter 4 : 00000000`1040080f
Caused By Driver : hal.dll
Caused By Address : hal.dll+ef4c
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini101410-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 3790
==================================================
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP