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

HP 1361 SB BSOD


  • Please log in to reply
6 replies to this topic

#1 tjbwin7

tjbwin7

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:12:49 AM

Posted 24 December 2012 - 09:00 AM

System is HP 1361 SB
Win 7/4gb RAM/Reinstalled twice and using all HP drivers
Updated Win 7 via Win Update but purposely did not choose any driver updates from MS thinking there was some conflicts

Following is debugging info:


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


Loading Dump File [C:\Users\103\Desktop\122412-23805-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 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02c5f000 PsLoadedModuleList = 0xfffff800`02ea3670
Debug session time: Mon Dec 24 01:00:22.905 2012 (UTC - 5:00)
System Uptime: 0 days 0:56:22.528
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc000001d, fffff80002cfb273, fffff88002ff38a8, fffff88002ff3100}

Probably caused by : hardware ( luafv!SynchronousFsControl+287 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80002cfb273, The address that the exception occurred at
Arg3: fffff88002ff38a8, Exception Record Address
Arg4: fffff88002ff3100, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

FAULTING_IP:
nt!MmUnlockPages+63
fffff800`02cfb273 c7 ???

EXCEPTION_RECORD: fffff88002ff38a8 -- (.exr 0xfffff88002ff38a8)
ExceptionAddress: fffff80002cfb273 (nt!MmUnlockPages+0x0000000000000063)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT: fffff88002ff3100 -- (.cxr 0xfffff88002ff3100)
rax=0000000000000000 rbx=fffff880051a4008 rcx=0000000001b03008
rdx=fffff88002ff3bc0 rsi=fffffa8007eda460 rdi=0000000000001008
rip=fffff80002cfb273 rsp=fffff88002ff3ae0 rbp=fffff880051a4008
r8=fffffa800bd5f470 r9=0000000000000000 r10=0000000000000000
r11=000000000000008b r12=0000000000000000 r13=fffffa800730bd70
r14=fffffa8007eda460 r15=0000000000000001
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nt!MmUnlockPages+0x63:
fffff800`02cfb273 c7 ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x7E

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

MISALIGNED_IP:
nt!MmUnlockPages+63
fffff800`02cfb273 c7 ???

LAST_CONTROL_TRANSFER: from fffff8800182f5e9 to fffff80002cfb273

FAILED_INSTRUCTION_ADDRESS:
nt!MmUnlockPages+63
fffff800`02cfb273 c7 ???

STACK_TEXT:
fffff880`02ff3ae0 fffff880`0182f5e9 : 00000000`0000008b fffffa80`0730bca0 fffffa80`0730bcd8 00000000`00000000 : nt!MmUnlockPages+0x63
fffff880`02ff3b70 fffff880`030be567 : fffffa80`0bd5f478 00000000`00000000 fffffa80`0730bca0 fffff880`00000000 : fltmgr!FltFreeCallbackData+0x79
fffff880`02ff3bc0 fffff880`030be666 : 00000000`00000000 fffff8a0`01b03008 fffffa80`0730bca0 fffffa80`0730bcd8 : luafv!SynchronousFsControl+0x287
fffff880`02ff3c40 fffff800`02f74e5a : 00000000`02c3d101 fffffa80`07024b50 00000000`00000080 fffffa80`07024b50 : luafv!UsnThread+0xd6
fffff880`02ff3d00 fffff800`02cced26 : fffff880`009ea180 fffffa80`07024b50 fffffa80`073c3b50 fffffa80`073d3810 : nt!PspSystemThreadStartup+0x5a
fffff880`02ff3d40 00000000`00000000 : fffff880`02ff4000 fffff880`02fee000 fffff880`02ff36f0 00000000`00000000 : nt!KxStartSystemThread+0x16


FOLLOWUP_IP:
luafv!SynchronousFsControl+287
fffff880`030be567 8bc3 mov eax,ebx

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: luafv!SynchronousFsControl+287

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .cxr 0xfffff88002ff3100 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID: X64_IP_MISALIGNED

BUCKET_ID: X64_IP_MISALIGNED

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

BC AdBot (Login to Remove)

 


#2 tjbwin7

tjbwin7
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:12:49 AM

Posted 24 December 2012 - 09:28 AM

Ran Blue Screen View Software:

Happens at random, no particular instigating event. System just stops. Only way I got to see Blue Screen was by changing parameter at startup to stop automatic restart.

I have not run in safe mode

Thanks Tim
==================================================
Dump File : 122412-23805-01.dmp
Crash Time : 12/24/2012 8:08:10 AM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c000001d
Parameter 2 : fffff800`02cfb273
Parameter 3 : fffff880`02ff38a8
Parameter 4 : fffff880`02ff3100
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+4a12
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+9c273
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122412-23805-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 274,960
==================================================

#3 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:01:49 AM

Posted 24 December 2012 - 07:48 PM

Hello

We will try to help you with your computer BSOD problem. These problems are often not simple, so gathering as much information about your computer will be important.

1. ) Please follow this link: BSOD Posting Instructions Windows 8 - Windows 7 - Vista.
  • Follow all instructions with the exception of:
    • Creating a new thread HERE and attach the file(s) after step 4
  • Note: Both files of Step 1 need to be in the Documents folder.
2. ) Upload the zipped folder to a File Sharing website of your choosing because Bleeping Computer has a 512 K only upload limit and this file will be much larger.
In addition:

3. ) To help us get a better look at your computer's hardware, please download and install Speccy by Piriform. (mirror site)
  • Run Speccy and from the top menu, select File --> Publish Snapshot. Click "Yes" to proceed.
  • Click, Copy to Clipboard and paste this address into your next post.

Regards,
Brooks



 


#4 tjbwin7

tjbwin7
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:12:49 AM

Posted 24 December 2012 - 09:33 PM

File links as follows
Thanks Tim
https://www.box.com/shared/o0mhozigskpb856z30qd

https://www.box.com/shared/pfor1c1j0aue3guewnlw

#5 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:01:49 AM

Posted 25 December 2012 - 01:26 PM

tjbwin7,

There was only one minidump file in the collection and as you had previously posted, the error is a Bugcheck code 1000007E.

Since this is a new Windows installation, make sure that you have all Windows Updates installed, then go to the HP website, enter your notebook model number (sticker on bottom) and install any updated drivers, especially chipset driver. It's good, as you have pointed out, to stay away from Windows Updates and third party driver download utilities when updating drivers. I see that there is a newer BIOS for your system.

Since a bad memory module can cause varied BSODs or computer freezing, it would be worth while testing memory. It is best to test memory outside the Windows operating system, so please follow this post: Windows 7 - RAM - Test with Memtest86+ to either create a bootable CD (Method 2) or bootable USB flash drive (Method 1) to run the test.
  • Once the computer is booted from the CD or USB flash drive, MemTest86+ with start automatically and continue until you stop it by pressing the ESC key.
  • My recommendation would be to run MemTest86+ overnight; 12 hours rather than just 7 passes.
    • There should be NO errors reported.
    • The test can be stopped by pressing the ESC key as soon as an error is reported or to stop the test after 12 hours.
  • See Part 3: If you have errors.
    • Caution: If your computer is still under warranty, opening the case to remove memory for testing purposes, may VOID that warranty.


BSOD Bug Check Code: For informational purposes only
Spoiler

Regards,
Brooks



 


#6 tjbwin7

tjbwin7
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:12:49 AM

Posted 27 December 2012 - 06:39 PM

I have replaced memory (christmas present) and so far no problems. Will keep you posted. Thx

#7 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:01:49 AM

Posted 27 December 2012 - 09:19 PM

Thanks for the update.

Regards,
Brooks



 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users