Strange Event logs

Discussion in 'Microsoft Surface Pro 2' started by G-man, Dec 10, 2013.

  1. G-man

    G-man Member

    Joined:
    Dec 3, 2013
    Messages:
    64
    Likes Received:
    6
    Trophy Points:
    8
    I have some entries in the event log from 11/21/2013 (I just got the system on 12/6, and fired it up on 12/9)

    • The device, \Device\Harddisk1\DR1, has a bad block.
    • The default transaction resource manager on volume D: encountered a non-retryable error and could not start. The data contains the error code.
    • Volume D: (\Device\HarddiskVolume6) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.


    I have no drive D:, and I am thinking this is from when the system was prepped at the factory?

    What is the \Device\Harddisk1\DR1 ? Is that the local hard drive? Is there a way to check my hard drive?

    Thanks,
     
  2. jollywombat

    jollywombat Member

    Joined:
    Nov 25, 2013
    Messages:
    171
    Likes Received:
    22
    Trophy Points:
    18
    Location:
    NY, USA
    My Device:
    SPro2
    D would be either a USB flash drive or SDHC/XC card that was plugged into the system at that time. The recovery partitions are on the disk, but are not mounted for regular access. I would not worry about it either way, its not your onboard SSD. Unsure if you have a refurbished unit or if it was simply updated to the latest image/firmware by the factory and their device had a bad block.
     
  3. javispedro

    javispedro Member

    Joined:
    Mar 16, 2014
    Messages:
    133
    Likes Received:
    4
    Trophy Points:
    18
    Location:
    Barcelona
    Just a curiosity I suspect.

    I was perusing the Windows event log on my new SFPro2 when I realized that there were some events dated on the same week as this device was manufactured (according to the lot no. 1403) . I suppose every SFPro must either have those or similar events (I mean, they are imaged, not individually tested).

    In my case I noticed that the following hardware was used:
    - No-name USB hubs (more than one)
    - A USB Ethernet adapter (not the MS one!)
    - A WD My Book USB disk
    - A WD My Passport USB disk (seemingly containing a partition called "IMAGING").
    - The v1 type cover
    - A D-Link Wireless adapter (funny)

    I can also see those in the device manager when using the devmgr_show_nonpresent_devices env var.
     
    Last edited: Mar 22, 2014

Share This Page

Search tags for this page
default transaction resource manager
,

event 41 surface pro

,
event id 41 on microsoft surface
,

event id error 14 on surface pro 4

,
retrieving event logs from surface pro3
,
surface pro 2 event 41 event logs
,
surface pro 2 event id 41
,
surface pro bt fail event log
,
surface pro event log
,
surface pro event log id 41