Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Brand New PC, keep getting BSOD :(


28 Nov 2010   #1

Windows 7 Home Premium 64bit
 
 
Brand New PC, keep getting BSOD :(

I'll try and make this quick.

Bought a new Dell Inspiron not long ago.

In the span of a week or two i literally got over 10 BSODs, it's usually when I'm moving chunks of music of movies from one hardrive to another.

So Dell told me there must be a hardware failure, they came round and changed my motherboard for free.

And then yesterday was my first day trying it out again and it happened again. This was when I was only uploading pictures onto Facebook! All i noticed was that is had the long 000000 number and then 1A at the end.

This is what I constantly have connected to my PC via USB: Mouse / Keyboard / Printer / External hardrive / Belkin Wireless Adapter.

Do you think it's possibly the External Hardrive or Belkin Adapter?

I've attached my mini dump, but I'm not a computer whizz so I don't even know what I'm looking for.

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


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

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03005000 PsLoadedModuleList = 0xfffff800`03242e50
Debug session time: Sat Nov 27 16:40:19.377 2010 (UTC + 0:00)
System Uptime: 0 days 6:21:46.000
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 18b3a90f0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 000000018b3a90f0
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: fffff8800317e520 -- (.trap 0xfffff8800317e520)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000000f rbx=0000000000000000 rcx=fffff8a001c63360
rdx=000000018b3a9120 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030809b3 rsp=fffff8800317e6b0 rbp=0000000000000000
r8=0000000000000001 r9=0000000000024fce r10=fffff780c0000488
r11=fffff780c0000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!ObFastReferenceObject+0x73:
fffff800`030809b3 f0480fc143d0 lock xadd qword ptr [rbx-30h],rax ds:e880:ffffffff`ffffffd0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80003021b7a to fffff80003075740

STACK_TEXT:
fffff880`0317e3b8 fffff800`03021b7a : 00000000`0000001a 00000000`00041287 00000001`8b3a90f0 00000000`00000000 : nt!KeBugCheckEx
fffff880`0317e3c0 fffff800`0307382e : 00000000`00000001 00000001`8b3a9120 00000000`00000200 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x42ba5
fffff880`0317e520 fffff800`030809b3 : fffff880`0317e7c8 00000000`00000000 fffff8a0`04d5ec70 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0317e6b0 fffff800`0317bd2c : fffffa80`048b9cb0 fffffa80`05db3000 00000000`00000000 fffff880`0317e701 : nt!ObFastReferenceObject+0x73
fffff880`0317e6e0 fffff800`030191ab : 00000003`00000000 00000000`00024fce fffffa80`03d45410 fffff880`0317e8a0 : nt!MiLogPageAccess+0xfc
fffff880`0317e730 fffff800`0338c1b5 : fffff980`0589c000 fffff8a0`030bfe80 00000000`00000000 fffff800`00000000 : nt! ?? ::FNODOBFM::`string'+0x2bee8
fffff880`0317ea10 fffff800`0308e567 : 00000000`00200000 fffffa80`05460440 00000000`00000000 00000000`00240000 : nt!CcUnmapVacb+0x5d
fffff880`0317ea50 fffff800`03065274 : fffffa80`07d50301 fffffa80`094fa8e0 fffffa80`05c00301 00000000`00000000 : nt!CcUnmapVacbArray+0x1b7
fffff880`0317eae0 fffff800`03068d1c : fffffa80`05c00330 00000000`00000011 fffffa80`05c00330 fffff800`00000000 : nt!CcDeleteSharedCacheMap+0x140
fffff880`0317eb50 fffff800`03069520 : fffff800`0327c100 fffff880`0317ec58 00000000`00000000 fffff800`00000000 : nt!CcWriteBehind+0x5bc
fffff880`0317ec00 fffff800`03082961 : fffffa80`05490ab0 fffff800`03069358 fffff800`0327c140 00000000`00000003 : nt!CcWorkerThread+0x1c8
fffff880`0317ecb0 fffff800`03319c06 : 31005f00`73007900 fffffa80`0548bb60 00000000`00000080 fffffa80`05472040 : nt!ExpWorkerThread+0x111
fffff880`0317ed40 fffff800`03053c26 : fffff880`02fd5180 fffffa80`0548bb60 fffff880`02fdffc0 5f006300`6e007500 : nt!PspSystemThreadStartup+0x5a
fffff880`0317ed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+42ba5
fffff800`03021b7a cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+42ba5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

FAILURE_BUCKET_ID: X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5

BUCKET_ID: X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5

Followup: MachineOwner


My System SpecsSystem Spec
.

28 Nov 2010   #2

Windows 7 Home Premium 64bit
 
 

I'm guessing I need to get my RAM changed also. This is upsetting considering it's a brand new PC

Is there a chance that my wireless adapter or my external hardrive (whish is always plugged in, and is always on) is causing it? It's strange though, I NEVER had this problem on my Vista and I always had my hardrive plugged in that PC.
My System SpecsSystem Spec
28 Nov 2010   #3

Windows 7 Ultimate x86 SP1
 
 

It seems your Wireless network adapter driver is obsolete, you must update it or check whether the device is supported with Windows 7.
Code:
MRVW24C.sys  Sun Oct 28 19:22:31 2007 -> Linksys, NetGear, DLink or Marvell Wireless USB Network Adapter
Then for troubleshooting purpose, remove McAfee and replace it with MSE.
You may go back to McAfee few days after the BSOD have gone.
http://www.microsoft.com/security_essentials/
My System SpecsSystem Spec
.


28 Nov 2010   #4

Windows 7 Home Premium 64bit
 
 

It just happened again, can you help me on this also?

I've changed the settings to Kernal Memory Dump before my computer froze

Went back to it my minidump folder and the brand new dump is only 269kb, I thought it would be so huge that I'll have to upload it on rapidshare but it's still very small?

Either way, now I've added on a ethernet adapter so that gets rid of my wireless adapter problem. You think it's my memory?
My System SpecsSystem Spec
28 Nov 2010   #5

Windows 7 Ultimate x86 SP1
 
 

There is no way to predict the size of a Kernel Memory Dump because its size depends
on the amount of kernel-mode memory allocated by the operating system and drivers
present on the machine.

Your last dump: PAGE_FAULT_IN_NONPAGED_AREA (50) can be caused by 3rd driver or RAM.
Then I see your wireless adapter driver still load in memory so you must delete it manually or rename into MRVW24C.bak. So that driver won't load in next reboot.
C:\Windows\system32\DRIVERS\MRVW24C.sys
MRVW24C.sys Sun Oct 28 19:22:31 2007

Then test your RAM with mmtest86 for at least 7 passes (better overnight).
RAM - Test with Memtest86+
My System SpecsSystem Spec
01 Dec 2010   #6

Windows 7 Home Premium 64bit
 
 

Hello wish.

Thank you for having a look. I did a RAM test and youw ere correct, of the RAMs was faulty. It's going to be replaced tomorrow. Hopefully that would correct my PC and I wouldn't experience anymore BSODs

I went onto my Drivers folder and just manually renamed it to bac. Would that stop it running now?

Is that all I needed to do regarding that driver?
My System SpecsSystem Spec
Reply

 Brand New PC, keep getting BSOD :(




Thread Tools



Similar help and support threads for2: Brand New PC, keep getting BSOD :(
Thread Forum
BSOD on brand new pc!! BSOD Help and Support
BSOD on brand new HP w/ W7 64 bit BSOD Help and Support
Brand new pc _ bsod BSOD Help and Support
Brand new PC, BSOD on wake! BSOD Help and Support
BsoD BRAND NEW PC BSOD Help and Support
BSOD on brand new computer BSOD Help and Support
Brand new computer, Brand new windows 7.. no wireless? Network & Sharing

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 05:28 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33